Random access procedure selection by integrated access and backhaul nodes

Abstract

Methods, systems, and devices for wireless communication are described. A child node can communicate with a parent node in an integrated access and backhaul (IAB) communication system, and the parent node can transmit system information to the child node that can indicate one or more random access channel (RACH) procedure configurations, such as a user equipment (UE)-specific RACH procedure configuration and an IAB-specific (e.g., IAB-specific) RACH procedure configuration. The child node can be configured to utilize the UE-specific RACH procedure configuration or the IAB-specific RACH procedure configuration, such as if the child node satisfies one or more conditions or if an indication is received from the parent node. The child node can determine to utilize the UE-specific RACH procedure configuration for communications with the parent node, and can perform a RACH procedure with the parent node in accordance with the UE-specific RACH procedure configuration.

Description

[0001] Cross-referencing

[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 034,859, filed June 4, 2020, entitled “RANDOM ACCESS PROCEDURE SELECTION BY AN INTEGRATED ACCESS AND BACKHAUL NODE”, and U.S. Patent Application No. 17 / 320,665, filed May 14, 2021, entitled “RANDOM ACCESS PROCEDURE SELECTION BY AN INTEGRATED ACCESS AND BACKHAUL NODE”, each of which is assigned to the assignee of this application. Technical Field

[0003] The following text generally refers to wireless communication, and more specifically to the selection of the Random Access Channel (RACH) protocol by the Integrated Access and Backhaul (IAB) nodes.

[0004] background

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

[0006] In some wireless communication systems, a base station (such as a parent Integrated Access and Backhaul (IAB) node) can provide system information to at least its child IAB nodes to enable these child nodes to communicate with the base station. This system information may include an indication of the IAB-specific Random Access Channel (RACH) protocol configuration to be used by the child IAB nodes. In some cases, the IAB-specific RACH protocol is configured for static IAB nodes, but the IAB node may be a mobile IAB node (e.g., an IAB mobile terminal (MT)). Thus, the IAB-specific RACH protocol configuration may result in unsuccessful RACH transmissions and may introduce latency into the system when used by a mobile IAB node.

[0007] Overview

[0008] The described technology relates to improved methods, systems, apparatuses, and devices for supporting random access channel (RACH) protocol selection by integrated access and backhaul (IAB) nodes. Generally, the described technology provides improved RACH protocol performance and reduced latency in communication systems by enabling child nodes to determine which RACH protocol configuration (such as a UE-specific RACH protocol configuration or an IAB-specific RACH protocol configuration) to use. Child nodes (e.g., IAB nodes) can communicate with parent nodes (such as parent IAB nodes, base stations, etc.) in an IAB communication system, and the parent node can transmit system information to the child node that can indicate RACH protocol information. The child node can receive this system information from the parent node, which can indicate both UE-specific and IAB-specific RACH protocol configurations. The child node can be configured to utilize either the UE-specific or IAB-specific RACH protocol configuration. In some situations, a child node may use a UE-specific RACH procedure configuration when one or more conditions are met or when it receives an instruction from the parent node. The child node may determine whether to use the UE-specific RACH procedure configuration for connection with the parent node via RACH procedure, and may execute the RACH procedure with the parent node according to the UE-specific RACH procedure configuration.

[0009] A method for wireless communication at a first wireless node is described. The method may include: receiving system information from a parent base station indicating a UE-specific RACH protocol configuration and a UE-specific RACH protocol configuration, wherein the first wireless node is a wireless backhaul node to the parent base station; determining whether to use the UE-specific RACH protocol configuration to communicate with the parent base station; and performing a RACH protocol with the parent base station according to the UE-specific RACH protocol configuration.

[0010] An apparatus for wireless communication at a first wireless node is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. These instructions are executable by the processor to cause the apparatus to: receive system information from a parent base station indicating a UE-specific RACH protocol configuration and a UE-specific RACH protocol configuration, wherein the first wireless node is a RACH backhaul node to the parent base station; determine to use the UE-specific RACH protocol configuration to communicate with the parent base station; and execute a RACH protocol with the parent base station according to the UE-specific RACH protocol configuration.

[0011] Another apparatus for wireless communication at a first wireless node is described. The apparatus may include means for: receiving system information from a parent base station indicating a UE-specific RACH protocol configuration and a UE-specific RACH protocol configuration, wherein the first wireless node is a wireless backhaul node to the parent base station; determining to use the UE-specific RACH protocol configuration to communicate with the parent base station; and performing RACH protocol with the parent base station according to the UE-specific RACH protocol configuration.

[0012] A non-transient computer-readable medium is described, storing code for wireless communication at a first wireless node. The code may include instructions executable by a processor to: receive system information from a parent base station indicating a UE-specific RACH protocol configuration and a UE-specific RACH protocol configuration, wherein the first wireless node is a wireless backhaul node to the parent base station; determine to use the UE-specific RACH protocol configuration to communicate with the parent base station; and perform RACH protocol communication with the parent base station according to the UE-specific RACH protocol configuration.

[0013] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, determining to use a UE-specific RACH protocol configuration may include operations, features, means, or instructions for selecting a UE-specific RACH protocol configuration based on the fact that a first radio node is a mobile radio backhaul node.

[0014] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, selecting a UE-specific RACH procedure configuration may further include operations, features, means, or instructions for: determining that the next UE-specific RACH timing occurs before the next radio backhaul-specific RACH timing, and selecting a UE-specific RACH procedure configuration based on the fact that the next UE-specific RACH timing occurs before the next radio backhaul-specific RACH timing.

[0015] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, determining to use a UE-specific RACH procedure configuration may include operations, features, means, or instructions for selecting a UE-specific RACH procedure configuration based on satisfying one or more measurement thresholds.

[0016] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, selecting a UE-specific RACH protocol configuration may further include operations, features, means, or instructions for: determining a reference signal received power (RSRP) associated with communication with a parent base station, identifying that the determined RSRP exceeds a threshold RSRP from one or more measurement thresholds, and selecting a UE-specific RACH protocol configuration based on the identification.

[0017] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, selecting a UE-specific RACH procedure configuration may further include operations, features, means, or instructions for: determining the change over time of an RSRP or Channel Quality Indicator (CQI) associated with communication with a parent base station, identifying that the determined change exceeds a corresponding threshold RSRP change or threshold CQI change from one or more measurement thresholds, and selecting a UE-specific RACH procedure configuration based on that identification.

[0018] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, selecting a UE-specific RACH protocol configuration may further include operations, features, means, or instructions for: determining the round-trip time (RTT) associated with communication with a parent base station, identifying that the determined RTT may be less than a threshold RTT from one or more measurement thresholds, and selecting a UE-specific RACH protocol configuration based on the identifier.

[0019] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, selecting a UE-specific RACH protocol configuration may further include operations, features, means, or instructions for: determining a change in RTT associated with communication with a parent base station, identifying that the determined change in RTT exceeds a threshold change in RTT from one or more measurement thresholds, and selecting a UE-specific RACH protocol configuration based on the identification.

[0020] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, the one or more measurement thresholds may be different for different categories of wireless nodes, including mobile wireless backhaul nodes, static wireless backhaul nodes, wide-area wireless backhaul nodes, and local wireless backhaul nodes.

[0021] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means or instructions for receiving one or more measurement thresholds from a parent base station via a System Information Block (SIB) transmission.

[0022] Examples of methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means, or instructions for receiving one or more measurement thresholds from a parent base station via unicast transmission, including F1 application protocol transmission, radio resource control (RRC) transmission, media access control (MAC) control element (CE) transmission, downlink control information (DCI) transmission, or combinations thereof.

[0023] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, determining to use a UE-specific RACH protocol configuration may include operations, features, means, or instructions for: identifying that the number of RACH attempts using a UE-specific RACH protocol configuration exceeds a threshold number of attempts, and selecting a UE-specific RACH protocol configuration based on that identification.

[0024] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means, or instructions for: attempting to perform RACH procedures with a parent base station according to a UE-specific RACH procedure configuration, identifying that the number of RACH attempts using the UE-specific RACH procedure configuration exceeds a threshold number of attempts, and determining, based on the identification, to switch from using the UE-specific RACH procedure configuration to using the radio backhaul-specific RACH procedure configuration.

[0025] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, determining to use a UE-specific RACH protocol configuration may include operations, features, means, or instructions for receiving signaling from a parent base station that activates the UE-specific RACH protocol configuration for communication with the parent base station.

[0026] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, receiving signaling to activate RACH protocol configurations that vary from UE to UE may further include operations, features, means, or instructions for receiving DCI, MAC-CE, RRC signaling, or combinations thereof.

[0027] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means or instructions for transmitting to a parent base station a message requesting activation of a UE-specific RACH procedure configuration, wherein reception of signaling for activating the UE-specific RACH procedure configuration may be based on the request.

[0028] In some examples of the methods, apparatus (equipment) and non-transient computer-readable media described herein, the request may be transmitted in uplink control information (UCI) transmission, MAC-CE transmission, F1 application protocol transmission, or RRC transmission, or a combination thereof.

[0029] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means or instructions for determining to switch from using a UE-specific RACH protocol configuration to using a RACH protocol configuration that varies from radio backhaul, wherein the power ramp counter may not be reset during the handover.

[0030] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, determining to use a UE-specific RACH protocol configuration may include operations, features, means, or instructions for selecting a UE-specific RACH protocol configuration based on an information element that sorts RACH protocols in a DCI transmission, wherein the information element indicates that a first radio node should use a UE-specific RACH protocol configuration.

[0031] In some examples of the methods, apparatus (equipment) and non-transient computer-readable media described herein, the first wireless node may be an IAB node.

[0032] A method for wireless communication at a parent base station is described. The method may include: transmitting system information to a first wireless node indicating a UE-specific RACH protocol configuration and a UE-specific RACH protocol configuration, wherein the first wireless node is a wireless backhaul node to the parent base station; determining that the UE-specific RACH protocol configuration is being used by the first wireless node to communicate with the parent base station; and performing RACH procedures with the first wireless node according to the UE-specific RACH protocol configuration.

[0033] An apparatus for wireless communication at a parent base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. These instructions are executable by the processor to cause the apparatus to: transmit system information to a first wireless node indicating a UE-specific RACH protocol configuration and a UE-specific RACH protocol configuration, wherein the first wireless node is a wireless backhaul node to the parent base station; determine that the UE-specific RACH protocol configuration is being used by the first wireless node to communicate with the parent base station; and perform RACH protocol with the first wireless node according to the UE-specific RACH protocol configuration.

[0034] Another apparatus for wireless communication at a parent base station is described. The apparatus may include means for: transmitting system information to a first wireless node indicating a UE-specific RACH protocol configuration and a UE-specific RACH protocol configuration, wherein the first wireless node is a wireless backhaul node to the parent base station; determining that the UE-specific RACH protocol configuration is being used by the first wireless node to communicate with the parent base station; and performing RACH procedures with the first wireless node according to the UE-specific RACH protocol configuration.

[0035] A non-transient computer-readable medium is described, storing code for wireless communication at a parent base station. The code may include instructions that can be executed by a processor: transmitting system information to a first wireless node indicating a UE-specific RACH protocol configuration and a UE-specific RACH protocol configuration, wherein the first wireless node is a wireless backhaul node to the parent base station; determining that the UE-specific RACH protocol configuration is being used by the first wireless node to communicate with the parent base station; and executing a RACH protocol with the first wireless node according to the UE-specific RACH protocol configuration.

[0036] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, determining that a UE-specific RACH protocol configuration can be used may include operations, features, means, or instructions for determining that a first radio node may be a mobile radio backhaul node, wherein the UE-specific RACH protocol configuration can be used based on the first radio node being a mobile radio backhaul node.

[0037] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means, or instructions for: determining one or more measurement thresholds for a first radio node to determine whether to use a UE-specific RACH procedure configuration; and transmitting an instruction to the first radio node regarding the one or more measurement thresholds.

[0038] In some examples of the methods, apparatus (equipment) and non-transient computer-readable media described herein, one of the one or more measurement thresholds may be RSRP associated with communication with a first wireless node.

[0039] In some examples of the methods, apparatus (equipment) and non-transient computer-readable media described herein, one of the one or more measurement thresholds may be the change of RSRP or CQI over time associated with communication with the first wireless node.

[0040] In some examples of the methods, apparatus (equipment) and non-transient computer-readable media described herein, one of the one or more measurement thresholds may be the RTT associated with communication with the first wireless node.

[0041] In some examples of the methods, apparatus (equipment) and non-transient computer-readable media described herein, the one or more measurement thresholds may be different for different categories of wireless nodes, including mobile wireless backhaul nodes, static wireless backhaul nodes, wide-area wireless backhaul nodes, and local wireless backhaul nodes.

[0042] In some examples of the methods, apparatus (equipment) and non-transient computer-readable media described herein, the indication of the one or more measurement thresholds may be transmitted via SIB transmission.

[0043] In some examples of the methods, apparatus (equipment) and non-transient computer-readable media described herein, the indication of the one or more measurement thresholds may be transmitted via unicast transmission, including F1 application protocol transmission, RRC transmission, MAC-CE transmission, DCI transmission, or combinations thereof.

[0044] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, determining that a UE-specific RACH protocol configuration may be used may include operations, features, means, or instructions for transmitting signaling to a first radio node that activates a UE-specific random access protocol configuration for communication with the first radio node.

[0045] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, the transmission of signaling activating RACH protocol configurations that vary from UE to UE may further include operations, features, means or instructions for transmitting DCI, MAC-CE, RRC signaling or combinations thereof.

[0046] Some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein may further include operations, features, means or instructions for receiving from a first radio node a message requesting activation of a UE-specific RACH protocol configuration, wherein transmission of signaling for activating the UE-specific RACH protocol configuration may be based on the request.

[0047] In some examples of the methods, apparatus (equipment) and non-transient computer-readable media described herein, the request may be received in a UCI transmission, a MAC-CE transmission, an F1 application protocol transmission, or an RRC transmission, or a combination thereof.

[0048] In some examples of the methods, apparatus (devices) and non-transient computer-readable media described herein, determining that a UE-specific RACH procedure configuration may be used may include operations, features, means, or instructions for transmitting information elements that order the RACH procedure in a DCI transmission, wherein the information elements indicate that the first radio node should use a UE-specific random access procedure configuration.

[0049] In some examples of the methods, apparatus (equipment) and non-transient computer-readable media described herein, the first wireless node may be an IAB node. Brief description of the attached diagram

[0051] Figure 1 Examples of systems for supporting wireless communication using the Random Access Channel (RACH) protocol selection performed by Integrated Access and Backhaul (IAB) nodes, according to various aspects of this disclosure, are explained.

[0052] Figure 2 Examples of systems for supporting RACH protocol selection by IAB nodes are explained according to various aspects of this disclosure.

[0053] Figure 3 An example of the process flow supporting RACH procedure selection by an IAB node according to various aspects of this disclosure is explained.

[0054] Figure 4 and 5 A block diagram is shown that supports the selection of devices by IAB nodes according to various aspects of this disclosure.

[0055] Figure 6 A block diagram is shown illustrating the communication manager that supports RACH protocol selection by IAB nodes according to various aspects of this disclosure.

[0056] Figure 7A diagram of a system including devices supporting RACH protocol selection by an IAB node is shown, according to various aspects of this disclosure.

[0057] Figure 8 and 9 A block diagram is shown that supports the selection of devices by IAB nodes according to various aspects of this disclosure.

[0058] Figure 10 A block diagram is shown illustrating the communication manager that supports RACH protocol selection by IAB nodes according to various aspects of this disclosure.

[0059] Figure 11 A diagram of a system including devices supporting RACH protocol selection by an IAB node is shown, according to various aspects of this disclosure.

[0060] Figures 12 to 15 A flowchart illustrating the method for supporting RACH procedure selection by an IAB node according to various aspects of this disclosure is shown.

[0061] Detailed description

[0062] Some wireless communication systems can be configured to support Integrated Access and Backhaul (IAB) networks, where one or more access nodes have a wireless backhaul connection to the network. An IAB network architecture may include an IAB donor node (e.g., a parent IAB node) that controls the IAB network connected to the core network and terminating at a User Equipment (UE), and any number of IAB nodes (e.g., child IAB nodes) that can act as relays for communication between the UE and the core network. In some aspects, the IAB network shares resources between the access link and the backhaul link. Generally, an IAB donor node (also referred to as an anchor node) is an access node with a wired connection to the core network. A donor node may have a central unit (CU), which is a central entity that controls or otherwise configures resources within the IAB network. A donor node may also have one or more distributed units (DUs) that act as scheduling nodes to schedule the child nodes of the IAB donor node. Downstream from an IAB donor node may include one or more IAB nodes (also referred to as wireless nodes) within the IAB network, where each downstream IAB node constitutes a hop within the IAB network. Each IAB node can relay traffic from an IAB donor node via one or more hops. In one example, each IAB node may have a DU and a mobile terminal (MT). The DU of an IAB node can act as a scheduling node that schedules child nodes of that particular IAB node, which can be a UE or a child radio node (e.g., a UE or base station within the IAB network). The MT can act as a scheduled node similar to a UE scheduled by its parent IAB node. In this context, the parent IAB node can be an IAB donor node (e.g., an anchor node) or a parent IAB node (e.g., an upstream radio node) within the IAB network.

[0063] In some wireless communication systems, a parent IAB node (such as a base station) can provide system information to several connected devices (e.g., child IAB nodes, IAB-MT nodes, UEs) to enable these devices to communicate with the base station. In some cases, the system information may include indications of one or more Random Access Channel (RACH) protocol configurations. For example, the system information may include indications of UE-specific RACH protocol configurations, IAB-specific RACH protocol configurations, or combinations thereof. Devices (such as parent and child nodes) can establish communication using RACH protocols based on the selected RACH protocol configuration. For example, the RACH protocol may include a series of handshake messages communicated between the parent and child nodes. In some examples, the RACH protocol may be used when a child node has data to transmit but has not been assigned uplink resources. In other examples, the RACH protocol may be used when a child node is switched from a source parent node to a target parent node. In any case, the RACH protocol enables the child node to synchronize with the network and communicate with the parent node.

[0064] In conventional communication systems, if a device receives both UE-specific and IAB-specific RACH protocol configurations, the UE can use the UE-specific RACH protocol configuration, and the IAB node can use the IAB-specific RACH protocol configuration. The parameters of the IAB-specific RACH protocol configuration can be configured based on the IAB node being static. In some cases, the IAB node can be a mobile IAB node and can operate similarly to the UE. Due to the mobile nature of IAB nodes, mobile IAB nodes can use different RACH protocol configuration parameters to achieve higher performance compared to static IAB nodes. For example, if a mobile IAB node is configured to execute RACH protocols more frequently than a static IAB node, reduced latency can be achieved. Thus, in a conventional system where a mobile IAB node is configured to use a static IAB RACH protocol configuration, it may result in increased latency and reduced network performance.

[0065] To improve RACH procedures in an IAB network, if an IAB node receives both an IAB-specific RACH procedure configuration and a UE-specific RACH procedure configuration in system information from its parent node, the IAB node can be configured to use either the IAB-specific or UE-specific RACH procedure configuration. In some cases, the option to use the UE-specific RACH procedure configuration can be based on one or more conditions. For example, if an IAB node is mobile or becomes mobile, a child IAB node can be configured to select the UE-specific RACH procedure configuration. Additionally or alternatively, these one or more conditions can be one or more thresholds, such as a power or quality threshold for communication between the child and parent nodes (e.g., a Reference Signal Received Power (RSRP) threshold, a Channel Quality Indicator (CQI) threshold), a threshold for the power or quality of communication between the child and parent nodes as a function of time, a Round Trip Time (RTT) threshold, a threshold for RTT as a function of time, or a combination thereof. In some cases, this condition may be the maximum number of RACH retransmissions configured using a UE-specific RACH procedure, or the maximum number of RACH retransmissions configured using an IAB-specific RACH procedure. As an addition to or alternative to this condition, the option to use a UE-specific RACH procedure configuration may be based on dynamic or semi-persistent signaling received from the parent node indicating that the child IAB node can use a UE-specific RACH procedure configuration.

[0066] Specific aspects of the topics described herein can be implemented to achieve one or more advantages. The described techniques can support improvements to RACH procedures in IAB-supported networks by reducing latency, increasing reliability, and other advantages. Thus, the supported techniques can include improved network operation, and in some examples, enhanced network efficiency and other benefits.

[0067] The aspects of this disclosure are initially described in the context of a wireless communication system. Aspects concerning process flow are then described. The aspects of this disclosure are further explained and described by means of, and with reference to, apparatus diagrams, system diagrams, and flowcharts relating to RACH procedure selection performed by IAB nodes.

[0068] Figure 1 Examples of wireless communication systems 100 supporting RACH protocol selection by IAB nodes according to various aspects of this disclosure are described. Wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low latency communication, communication with low-cost and low-complexity devices, or any combination thereof.

[0069] Base station 105 can be distributed across a geographical area to form wireless communication system 100, and can be different types of devices or devices with different capabilities. Base station 105 and UE 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110, and UE 115 and base station 105 can establish one or more communication links 125 on the coverage area 110. Coverage area 110 can be an example of a geographical area over which base station 105 and UE 115 can support signal communication according to one or more radio access technologies.

[0070] Each UE 115 can be distributed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. Each UE 115 can be a different type of device or a device with different capabilities. Figure 1 The document describes some example UE 115s. The UE 115 described herein can communicate with various types of devices, such as other UE 115s, base station 105, or network equipment (e.g., core network nodes, relay equipment, IAB nodes, or other network equipment)... Figure 1 As shown in the image.

[0071] Each base station 105 may communicate with the core network 130, or with each other, or both. For example, base station 105 may interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base stations 105 may communicate with each other directly (e.g., directly between base stations 105), indirectly (e.g., via the core network 130), or directly and indirectly on backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some examples, backhaul link 120 may be or include one or more radio links.

[0072] One or more of the base stations 105 described herein may include, or may be referred to by those skilled in the art as, base transceiver station, radio base station, access point, radio transceiver, B node, evolved B node (eNB), next-generation B node or gigabit B node (any of which may be referred to as gNB), home B node, home evolved B node, or other suitable terms.

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

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

[0075] UE 115 and base station 105 can wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term "carrier" can refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the radio spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used in conjunction with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0076] The signal waveform transmitted on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are 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 code rate of the modulation scheme, or both). Thus, the more resource elements the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate the UE 115 can achieve. Wireless communication resources can refer to a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and using multiple spatial layers can further improve the data rate or data integrity of communication with the UE 115.

[0077] The time interval of base station 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period T. s =1 / (Δf) max ·N f ) seconds, where Δf max This can represent the maximum supported subcarrier spacing, while N f This can represent the maximum supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0078] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into several 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 several symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple mini-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N) symbols. f (Number) sampling periods. The duration of a symbol period can depend on the subcarrier interval or the operating frequency band.

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

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

[0081] In some examples, base station 105 may be mobile, and thus provide communication coverage to mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. Wireless communication system 100 may include, for example, a heterogeneous network, in which different types of base stations 105 use the same or different radio access technologies to provide coverage to various geographic coverage areas 110.

[0082] Wireless communication system 100 may be configured to support ultra-reliable communication or low latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low latency communication (URLLC) or mission-critical communication. UE 115 may be designed to support ultra-reliable, low latency, or mission-critical functions (e.g., mission-critical functions). Ultra-reliable communication may include private or group communication and may be supported by one or more mission-critical services, such as Mission-Critical Talk-to-Talk (MCPTT), Mission-Critical Video (MCVideo), or Mission-Critical Data (MCData)). Support for mission-critical functions may include prioritization of services, and mission-critical services may be used for public safety or general business applications. The terms ultra-reliable, low latency, mission-critical, and ultra-reliable low latency are used interchangeably herein.

[0083] In some examples, UE 115 may also be able to communicate directly with other UE 115 on a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UE 115s utilizing D2D communication may be within the geographic coverage area 110 of base station 105. Other UE 115s in such a group may be outside the geographic coverage area 110 of base station 105 or may be unable to receive transmissions from base station 105 for other reasons. In some examples, groups of UE 115s communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between the individual UE 115s without involving base station 105.

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

[0085] Some network devices (such as base station 105) may include sub-components, such as access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with each UE 115 through one or more other access network transport entities 145, which may be referred to as a radio headend, smart radio headend, or transmit / receive point (TRP). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio headends and ANCs) or combined into a single network device (e.g., base station 105).

[0086] Wireless communication system 100 can operate using one or more frequency bands, typically in the range of 300 MHz to 300 GHz. Generally, the 300 MHz to 3 GHz band is referred to as a UHF band or decimeter band because the wavelengths range from approximately 1 decimeter to 1 meter. UHF waves can be blocked or redirected by buildings and environmental features, but these waves can penetrate various structures sufficiently for macrocells to provide service to UE 115 located indoors. Compared to transmissions using smaller frequencies and longer waves in the lower HF or VHF portions of the spectrum below 300 MHz, UHF wave transmission can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

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

[0088] Base station 105 or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels that can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may coexist at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with base station 105 may be located in different geographical locations. Base station 105 may have an antenna array with several rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

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

[0090] Some wireless communication systems can be configured to support IAB networks, where one or more access nodes have a wireless backhaul connection to the network. In such communication systems, a parent IAB node (e.g., an IAB donor node, parent base station 105) can be connected to the core network and can communicate with one or more devices (such as child IAB nodes or UE 115, or combinations thereof). The parent node can transmit system information to the one or more devices, which can indicate RACH protocol information to the child nodes. The child nodes can receive the system information from the parent node, which can indicate a UE-specific RACH protocol configuration and a wireless backhaul-specific (e.g., IAB-specific) RACH protocol configuration. The child nodes can be configured to utilize either a UE-specific RACH protocol configuration or an IAB-specific RACH protocol configuration. In some cases, the child node can use a UE-specific RACH protocol configuration upon fulfillment of one or more conditions or upon receiving an indication from the parent node. The child node can determine whether to configure the RACH procedure, which varies depending on the UE, for the connection with the parent node via the RACH procedure, and can execute the RACH procedure with the parent node according to the RACH procedure configuration that varies depending on the UE.

[0091] Figure 2 An example of a wireless communication system 200 supporting RACH protocol selection by an IAB node according to various aspects of this disclosure is described. The wireless communication system 200 may include base station 105-a (e.g., a parent base station), and UEs 115a and 115-b, which may be as described in reference... Figure 1 Examples of base station 105 and UE 115 described herein. Wireless communication system 200 may also include sub-nodes 205-a and 205-b (e.g., sub-IAB nodes, IAB-MT). Base station 105a may serve a geographic coverage area 110-a. In some cases, sub-nodes 205-a or 205-b, or both, may be configured to perform RACH procedures with base station 105-a using a RACH procedure configuration that varies depending on the UE or the IAB, and may perform RACH configuration determination procedures. Additionally or alternatively, other wireless devices (such as base station 105-a or UEs 115-a and 115-b) or some combination of these devices may implement RACH configuration determination procedures.

[0092] Wireless communication system 200 can be configured to support an IAB network, wherein one or more access nodes have a wireless backhaul connection to the network. For example, base station 105-a (e.g., a parent node, IAB donor node, parent base station) can be connected to the network and communicate with one or more UEs 115, or one or more child nodes (e.g., child IAB nodes, IAB-MTs), or a combination thereof. For example, base station 105-a can communicate with child nodes 205-a and 205-b on communication links 210-a and 210-b, respectively, and base station 105-a can communicate with UE 115-a on communication link 210-d. In some cases, child node 205 can act as a relay node to one or more UEs 115, wherein the one or more UEs 115 can be referred to as children of child node 205. For example, child node 205-a can communicate with UE 115-b on communication link 210-b. Alternatively, UE 115-b can receive communications directly from base station 105-a.

[0093] In the wireless communication system 200, devices can establish communication with other devices via a RACH procedure. For example, a child node 205 can execute a RACH procedure with a base station 105 to establish communication, a UE 115 can execute a RACH procedure with a child node 205 to establish communication, and a UE 115 can execute a RACH procedure with a base station 105 to establish communication. In some examples, the RACH procedure can be used when a child node 205 has data to transmit but has not been assigned uplink resources for communication with its parent node. In other examples, the RACH procedure can be used when a child node 205 is switched from a source base station 105 to a target base station 105. In any case, the RACH procedure enables the child node 205 to synchronize with the network and communicate with the base station 105. The RACH procedure may include a series of handshake messages transmitted between the devices. For example, child node 205 may transmit RACH message 1 (msg1) to base station 105-a, which may include a RACH preamble, and base station 105-a may respond to child node 205 with RACH message 2 (msg2), which may include a RACH preamble response. The RACH preamble response may include information for child node 205 (e.g., uplink permission, modulation and coding scheme (MCS) configuration, resource block (RB) assignment, and other configuration information). Child node 205 may receive and decode RACH msg2 and configure RACH message 3 (msg3) and transmit it to base station 105-a. In some cases, RACH msg3 may include a Radio Resource Control (RRC) connection request. Base station 105-a may receive and decode RACH msg3 to generate RACH message 4 (msg4) using the received information (e.g., an RRC connection request). Base station 105-a may transmit RACH message 4, which may include an RRC connection establishment corresponding to child node 205.

[0094] Before executing the RACH procedure, the network may determine one or more RACH procedure configurations. In some cases, the RACH procedure configuration may vary from device to device. For example, base station 105-a may be configured with a UE-specific RACH procedure configuration and an IAB-specific RACH procedure configuration. Alternatively, base station 105-a may be configured with a common RACH procedure configuration for use by any device (such as UE 115 or sub-node 205). The RACH configuration may define RACH periodicity, etc. The network (such as base station 105-a) may transmit one or more RACH procedure configurations to UE 115 and sub-node 205 so that the two devices can identify the two RACH configurations. The one or more RACH procedure configurations may be included in system information so that base station 105-a can transmit system information to UE 115 and sub-node 205, which may indicate a UE-specific RACH procedure configuration, or an IAB-specific RACH procedure configuration, or a combination thereof, or indicate a common RACH procedure configuration.

[0095] In some implementations, the configuration of the IAB-specific RACH procedure and the UE-specific RACH procedure can differ. For example, the IAB-specific RACH procedure can be based on the IAB node (e.g., a child node) being static, which is the opposite of the UE-specific RACH procedure based on the UE 115 being mobile. Additionally or alternatively, the IAB node can be located further from base station 105-a than UE 115-a, resulting in a larger maximum RTT associated with the IAB node. For example, UE 115 within coverage area 110-a can communicate with base station 105-a. However, if UE 115 moves outside coverage area 110-a, UE 115 can perform a handover procedure and communicate with a different base station 105. However, if child node 205 is outside coverage area 110-a, child node 205 can communicate with base station 105-a. For example, child node 205-b may be outside coverage area 110-a but can communicate with base station 105-a. Thus, the maximum distance UE 115 can travel from its serving base station 105 may be less than the maximum distance child node 205 can travel from its serving base station 105, resulting in a larger maximum RTT for child node 205. Device-specific RACH configurations can account for this difference in maximum RTT and device mobility.

[0096] In a conventional system, if base station 105-a is configured with a device-specific RACH protocol configuration, each device may need to use its associated RACH protocol configuration. For example, if subnode 205 receives instructions for both a UE-specific RACH protocol configuration and an IAB-specific RACH protocol configuration, subnode 205 may need to use the IAB-specific RACH protocol configuration. In some wireless communication systems, IAB nodes (such as subnode 205) can be mobile or become mobile (e.g., IAB nodes may be placed on mobile vehicles (such as cars, trains, airplanes, etc.) or on some other mobile object). As described herein, a conventional IAB-specific RACH protocol configuration may be based on the IAB node being static. Thus, the parameters of the IAB-specific RACH protocol configuration may not efficiently serve mobile IAB nodes. For example, mobile IAB nodes may need to execute RACH protocols more frequently than the periodicity defined by the IAB-specific RACH protocol configuration. This can lead to latency and reduced reliability in the network.

[0097] To mitigate latency and improve network performance, if an IAB node receives both a UE-specific RACH procedure configuration and an IAB-specific RACH procedure configuration, the IAB node (such as child node 205) can be configured to select between the UE-specific and IAB-specific RACH procedure configurations to execute the RACH procedure. In some cases, a UE-specific RACH procedure can allow for a more efficient (e.g., faster) RACH procedure. For example, a UE-specific RACH procedure can be configured to have more RACH opportunities than an IAB-specific RACH procedure. Thus, if the IAB node can select between the UE-specific and IAB-specific RACH procedure configurations, the number of RACH opportunities available to the IAB node can be increased.

[0098] In some scenarios, the option to use a UE-specific RACH protocol configuration can be based on one or more conditions. Each IAB node in the network can be statically configured or receive dynamic, semi-persistent, or aperiodic indications for these one or more conditions. In some scenarios, these one or more conditions may include that the IAB node is mobile. For example, child node 205 can determine that it is mobile, and based on this, determine that it can choose between a UE-specific RACH protocol configuration and an IAB-specific RACH protocol configuration. Additionally or alternatively, any IAB node, regardless of mobility, can choose between various RACH protocol configurations. In some scenarios, child node 205 (which may or may not be mobile) can select a RACH protocol configuration based on the RACH timing of each RACH protocol configuration or based on some other RACH protocol configuration parameters. For example, subnode 205 can determine that it can select between RACH procedure configurations based on one or more conditions, and can determine that the UE-specific RACH procedure configuration is configured with a RACH timing earlier than the next IAB-specific RACH procedure configuration. Subnode 205 can determine which UE-specific RACH procedure configuration to use based on this RACH timing determination.

[0099] In some scenarios, the one or more conditions can be configured differently for each different category of IAB node (e.g., mobile IAB node, static IAB node, wide-area IAB node, local IAB node). For example, different sets of conditions can be configured for each different category of IAB node. In such scenarios, base station 105-a can transmit indications of the one or more category-specific conditions associated with a particular category to the IAB nodes in a unicast manner (e.g., FI application protocol between CU and DU, RRC, Media Access Control (MAC) control element (MAC-CE), downlink control information (DCI)). For example, base station 105a can transmit a separate unicast message to each IAB node of a different category, which may include one or more conditions associated with that category. Additionally or alternatively, the one or more conditions can be similarly configured across multiple different categories of IAB nodes. For example, a common set of conditions can be configured for use by multiple different types of IAB nodes. In such a scenario, base station 105a may broadcast an indication of the one or more shared conditions to each IAB node served by base station 105a (e.g., broadcast in SIB).

[0100] In some cases, the one or more conditions may include one or more signal power or signal quality thresholds for communication between subnode 205 and base station 105-a. For example, the one or more conditions may include an RSRP threshold, a CQI threshold, or both, or some other signal power or signal quality threshold. Subnode 205 may measure RSRP, CQI, or both associated with communication between subnode 205 and base station 105-a. If the measured RSRP or CQI is higher than the RSRP threshold or CQI threshold, subnode 205 may use a UE-specific RACH protocol configuration or an IAB-specific RACH protocol configuration. In some cases, the higher the RSRP or CQI measurement, the closer subnode 205 can be to base station 105-a, resulting in subnode 205 having the same or similar RTT as UE 115. Thus, a UE-specific RACH protocol configuration can serve subnode 205 more efficiently than an IAB-specific RACH protocol configuration.

[0101] In some implementations, one or more of the signal power or signal quality thresholds can be set to 0 (e.g., 0 dB). In such cases, the measured signal power or signal quality can always be greater than the threshold, so as long as the threshold is 0, the child node 205 can use the UE-specific RACH protocol configuration. In some cases, even if the threshold is set to 0, the child node 205 can be mobile to use the UE-specific RACH protocol configuration. In some implementations, one or more of the signal power or signal quality thresholds can be set to infinity or some other large number. In such cases, the measured signal power or signal quality can always be less than the threshold, so as long as the threshold is infinity, the child node 205 cannot use the UE-specific RACH protocol configuration.

[0102] In some cases, the one or more conditions may include one or more thresholds associated with changes in signal power or signal quality over time for communication between subnode 205 and base station 105-a. For example, subnode 205 may be configured with a threshold associated with changes in RSRP over time, or a threshold associated with changes in CQI over time, or both, or some other change matrix. The subnode may be configured with thresholds and the amount of time on which changes can be measured. Subnode 205 may use criteria based on the measured RSRP or CQI, which captures the amount of change, to determine whether subnode 205 can be configured using a UE-specific RACH procedure. In some cases, a large change in RSRP or CQI, or some other channel quality or power indicator, may be an indication that subnode 205 is mobile relative to its parent node (e.g., base station 105-a). Thus, when subnode 205 or base station 105 detects a large change in RSRP or CQI over time, subnode 205 can be configured to use a RACH procedure configuration that varies from UE to IAB.

[0103] In some scenarios, the one or more conditions may include one or more RTT thresholds associated with communication between child node 205 and base station 105a. In some implementations, child node 205 may already be connected to the network and child node 205 may reside on a cell where child node 205 previously performed an initial RACH procedure to connect to the network. In such scenarios, child node 205 may identify the RTT associated with communication between child node 205 and parent node (e.g., base station 105-b). In some scenarios, RTT may be estimated based on one or more timing indication messages received from parent node and / or another network node. Timing indication messages may be uplink timing advance commands (TACs) or timing difference indications (e.g., T_delta indications that can be used in an IAB network to estimate downlink transmission timing at the parent node). As an addition to or replacement for the RTT threshold, the threshold may be defined based on TACs, T_delta, or combinations thereof. Child node 205 may determine to perform a RACH procedure to obtain updated uplink resource information. This RACH procedure may be referred to as a non-initial RACH procedure. For non-initial RACH procedures when subnode 205 has identified the RTT associated with communication between subnode 205 and base station 105-a, the RTT can be a parameter that subnode 205 can use to determine the eligibility of subnode 205 to use UE-specific RACH procedure configuration. In some cases, subnode 205 can be configured with an RTT threshold. A measured RTT associated with subnode 205 below the threshold can indicate that subnode 205 is within the maximum RTT associated with UE 115. Thus, subnode 205 can use UE-specific RACH procedure configuration. Additionally or alternatively, subnode 205 can be configured with a threshold for RTT variation over time. The subnode can be configured with a threshold and an amount of time on which the change can be measured. A measured RTT change greater than the threshold can be an indication that subnode 205 is moving. Thus, subnode 205 can use UE-specific RACH procedure configuration.

[0104] In some implementations, child node 205 may be configured to begin a RACH procedure using an IAB-specific RACH procedure configuration (e.g., an IAB-specific RACH procedure configuration only). In some cases, the parent node (e.g., base station 105-a) or child node 205 may fail to receive and successfully decode one or more RACH messages. For example, base station 105a may fail to successfully decode RACH msg1 from the child node. In such cases, child node 205 may retransmit RACH msg1 until base station 105a successfully decodes RACH msg1 and responds with RACH msg2. Child node 205 may be configured to retransmit RACH msg1 or some other RACH message using an IAB-specific RACH procedure configuration up to a pre-configured number of retransmissions (e.g., maxNumOfReTx). If child node 205 has reached the pre-configured number of retransmissions using the RACH procedure configuration that varies from IAB to 205 and the result is unsuccessful, then child node 205 may be allowed to use the RACH procedure configuration that varies from UE to 205.

[0105] In some implementations, child node 205 may use a UE-specific RACH procedure configuration after one or more conditions described herein are met, or child node 205 may use a UE-specific RACH procedure configuration even if one or more conditions described herein are not met. Child node 205 may use the UE-specific RACH procedure configuration to execute RACH procedures. In some situations, the parent node (e.g., base station 105-a) or child node 205 may fail to receive and successfully decode one or more RACH messages. For example, base station 105a may fail to successfully decode RACH msg1 from the child node. In such cases, child node 205 may retransmit RACH msg1 until base station 105a successfully decodes RACH msg1 and responds with RACH msg2. Child node 205 may be configured to use a UE-specific RACH procedure configuration to retransmit RACH msg1 or some other RACH message up to a pre-configured number of retransmissions (e.g., maxNumOfReTx). If child node 205 has reached the pre-configured number of retransmissions using a UE-specific RACH procedure configuration and the result is unsuccessful, child node 205 may be configured (e.g., required) to switch to an IAB-specific RACH procedure configuration.

[0106] In some scenarios, the use of UE-specific RACH can be dynamically indicated to the sub-node 205 (e.g., IAB-MT) by the network (e.g., base station 105-a). For example, when base station 105-a indicates both UE-specific RACH protocol configuration and IAB-specific RACH protocol configuration, base station 105-a can dynamically transmit an activation or deactivation signal (e.g., in DCI or MAC-CE) to indicate whether the sub-node 205 is allowed to use the UE-specific RACH protocol configuration. Additionally or alternatively, base station 105-a can semi-statically transmit an activation or deactivation signal (e.g., in an RRC message) to indicate whether the sub-node 205 is allowed to use the UE-specific RACH protocol configuration. In some scenarios, the sub-node 205 can transmit a request to base station 105-a to use the UE-specific RACH protocol configuration. For example, child node 205 may transmit a request to base station 105-a in uplink transmissions such as Uplink Control Information (UCI), MAC-CE, etc. In another example, child node 205 may transmit a request to a CU entity in RRC, FI application protocol, etc. In some cases, child node 205 may receive an activation or deactivation signal from base station 105-a in response to the request. In some cases, for ordered RACH of the Physical Downlink Control Channel (PDCCH), base station 105-a may transmit a DCI to child node 205, which includes information elements (IEs) that can indicate whether child node 205 (e.g., IAB-MT) can use an IAB-specific RACH protocol configuration or a UE-specific RACH protocol configuration for ordered RACH transmission.

[0107] In some implementations, if child node 205 retransmits a RACH message, it can retransmit each retransmission at a higher transmission power based on a pre-configured power ramp. Child node 205 can be configured with a power ramp counter that increments at each retransmission. If child node 205 switches between different RACH protocol configurations due to unsuccessful retransmissions, the power ramp counter may not be reset. For example, child node 205 can transmit RACH messages based on a RACH protocol configuration that varies depending on the UE or the IAB. The RACH message may not be successfully decoded by base station 105-a, and child node 205 can retransmit the RACH message at a higher transmission power using the same RACH protocol configuration until a pre-configured parameter (e.g., until a specific amount of time or a specific number of retransmissions). When the pre-configured parameter is reached, child node 205 can switch RACH protocol configurations and continue retransmitting RACH messages using the new RACH protocol configuration, while continuing to execute a transmission power ramp with each retransmission.

[0108] One or more conditions, determinations, and procedures described herein can be used in any combination to determine whether child node 205 can be configured with RACH procedures that vary from UE to UE.

[0109] Figure 3 An example of process flow 300 supporting RACH protocol selection performed by an IAB node according to various aspects of this disclosure is explained. Process flow 300 can illustrate an example RACH configuration selection protocol performed by an IAB node. For example, a sub-node 305-a (e.g., a first radio node, IAB-MT) can execute a RACH configuration determination protocol to select a RACH protocol configuration for performing RACH protocols with base station 105-b. Base station 105-b and sub-node 305-a can be references Figure 1 and 2 Examples of corresponding wireless devices described. In some cases, instead of child node 305-a performing the RACH configuration determination procedure, different types of wireless devices (e.g., UE or base station 105-b) can perform the procedure. The following alternative examples can be implemented, some of which may be performed in a different order than described or not at all. In some cases, the steps may include additional features not mentioned below, or further steps may be added.

[0110] At 305, child node 305-a can receive system information from parent base station 105-b, which indicates RACH protocol configuration that varies from UE to RACH protocol configuration (e.g., from IAB to RACH protocol configuration), where child node 305-a is a radio backhaul node to parent base station 105-b.

[0111] At 310, child node 305-a can determine whether to use a UE-specific RACH protocol configuration to communicate with parent base station 105-b. In some cases, determining whether to use a UE-specific RACH protocol configuration includes selecting the UE-specific RACH protocol configuration based on the fact that child node 305-a is a mobile radio backhaul node. In some implementations, selecting the UE-specific RACH protocol configuration includes determining that the next UE-specific RACH timing occurs before the next radio backhaul-specific RACH timing, and selecting the UE-specific RACH protocol configuration based on the fact that the next UE-specific RACH timing occurs before the next radio backhaul-specific RACH timing.

[0112] In some cases, determining whether to use a UE-specific RACH protocol configuration includes selecting the UE-specific RACH protocol configuration based on meeting one or more measurement thresholds. Base station 105-b may determine the one or more measurement thresholds and transmit an indication of the one or more measurement thresholds to sub-node 305-a. In some cases, the indication of the one or more measurements may be included in system information. In one example, selecting a UE-specific RACH protocol configuration includes determining the RSRP associated with communication with parent base station 105-a, identifying that the determined RSRP exceeds a threshold RSRP from the one or more measurement thresholds, and selecting a UE-specific RACH protocol configuration based on this identification. In another example, selecting a UE-specific RACH protocol configuration includes determining the change in RSRP or CQI associated with communication with parent base station 105-a over time, identifying that the determined change exceeds a corresponding threshold RSRP change or threshold CQI change from the one or more measurement thresholds, and selecting a UE-specific RACH protocol configuration based on this identification.

[0113] In another example, selecting a UE-specific RACH protocol configuration includes determining the RTT associated with communication with parent base station 105-a, identifying that the determined RTT is less than a threshold RTT from one or more measurement thresholds, and selecting a UE-specific RACH protocol configuration based on the identifier. In yet another example, selecting a UE-specific RACH protocol configuration includes determining a change in RTT associated with communication with parent base station 105-a, identifying that the determined changed RTT exceeds a threshold changed RTT from one or more measurement thresholds, and selecting a UE-specific RACH protocol configuration based on the identifier.

[0114] In some cases, the one or more measurement thresholds may differ for different categories of wireless nodes, including mobile wireless backhaul nodes, static wireless backhaul nodes, wide-area wireless backhaul nodes, and local wireless backhaul nodes. In some cases, child node 305-a may receive the one or more measurement thresholds from parent base station 105-a via System Information Block (SIB) transmission. In some cases, child node 305-a may receive the one or more measurement thresholds from parent base station 105-a via unicast transmission, including F1 application protocol transmission, RRC transmission, MAC-CE transmission, DCI transmission, or combinations thereof.

[0115] In some implementations, determining which UE-specific RACH protocol configuration to use includes identifying that the number of RACH attempts using the RACH protocol configuration that varies with radio backhaul exceeds a threshold number of attempts, and selecting the UE-specific RACH protocol configuration based on that identifier.

[0116] In some cases, child node 305-a may attempt to execute RACH procedures with parent base station 105-a according to UE-specific RACH procedure configuration, identify that the number of RACH attempts using UE-specific RACH procedure configuration exceeds a threshold number of attempts, and determine, based on this identification, to switch from using UE-specific RACH procedure configuration to using radio backhaul-specific RACH procedure configuration.

[0117] In some scenarios, determining the need for a UE-specific RACH protocol configuration involves receiving signaling from parent base station 105-a that activates the UE-specific RACH protocol configuration for communication with parent base station 105-a. Sub-node 305-a may receive DCI, MAC-CE, RRC signaling, or combinations thereof that activate the UE-specific RACH protocol configuration. In some scenarios, sub-node 305-a may transmit a message to parent base station 105-b requesting activation of the UE-specific RACH protocol configuration, based on this request. This request may be transmitted via UCI transmission, MAC-CE transmission, F1 application protocol transmission, or RRC transmission, or combinations thereof.

[0118] Sub-node 305-a can determine whether to switch from using a UE-specific RACH protocol configuration to using a radio backhaul-specific RACH protocol configuration, wherein the power ramp counter is not reset during the switch. In some cases, determining the use of a UE-specific RACH protocol configuration includes selecting the UE-specific RACH protocol configuration based on the IE that sorts the RACH protocols in the DCI transmission, wherein the IE indicates that sub-node 305-a should use the UE-specific RACH protocol configuration.

[0119] In 315, the parent base station 105-b can determine that the RACH protocol configuration, which varies from UE to UE, is being used by the child node 305-a to communicate with the parent base station 105-b.

[0120] At 320, child node 305-a can execute the RACH procedure with parent base station 105-b according to the RACH procedure configuration that varies from UE to RACH. In some cases, child node 305-a can execute the RACH procedure with parent base station 105-b to establish a connection with parent base station 105-b, to transmit system information requests, for uplink synchronization, for beam fault recovery, etc.

[0121] Figure 4A block diagram 400 of a device 405 supporting RACH protocol selection by an IAB node according to various aspects of this disclosure is shown. Device 405 may be an example of various aspects of UE 115 as described herein. Device 405 may include a receiver 410, a communications manager 415, and a transmitter 420. Device 405 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0122] Receiver 410 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to RACH procedure selection by IAB nodes). This information can be transmitted to other components of device 405. Receiver 410 can be a reference... Figure 7 Examples of various aspects of the transceiver 720 described. The receiver 410 may utilize a single antenna or an array of antennas.

[0123] Communication manager 415 can receive system information from the parent base station indicating UE-specific RACH protocol configurations and UE-specific RACH protocol configurations, where the first radio node is a radio backhaul node to the parent base station; determine whether to use the UE-specific RACH protocol configuration to communicate with the parent base station; and perform RACH protocol with the parent base station according to the UE-specific RACH protocol configuration. Communication manager 415 may be an example of various aspects of communication manager 710 described herein.

[0124] The communication manager 415 or its sub-components may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functionality of the communication manager 415 or its sub-components may be performed by a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described in this disclosure.

[0125] The communication manager 415 or its subcomponents may be physically located at various locations, including being distributed such that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, the communication manager 415 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of this disclosure, the communication manager 415 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0126] Transmitter 420 can transmit signals generated by other components of device 405. In some examples, transmitter 420 may coexist with receiver 410 in a transceiver module. For example, transmitter 420 may be a reference... Figure 7 Examples of various aspects of the transceiver 720 described. The transmitter 420 may utilize a single antenna or an array of antennas.

[0127] The communication manager 415, as described herein, can be implemented to achieve one or more potential advantages. One implementation may allow device 405 to execute RACH procedures with the parent node more efficiently. For example, device 405 may be configured to determine whether it can use a UE-specific RACH procedure or an IAB-specific RACH procedure. If device 405 is able to use either RACH procedure, it can determine which RACH procedure to use to reduce the latency associated with executing that RACH procedure.

[0128] Based on the RACH procedure determination technique described herein (e.g., controlling receiver 410, transmitter 420, or as referred to...), Figure 7 The processor of the UE 115 described in the transceiver 720 can increase the reliability and efficiency of executing RACH procedures in IAB networks.

[0129] Figure 5 A block diagram 500 of device 505 supporting RACH procedure selection by an IAB node according to various aspects of this disclosure is shown. Device 505 may be an example of aspects of device 405 or UE 115 as described herein. Device 505 may include receiver 510, communication manager 515, and transmitter 535. Device 505 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0130] Receiver 510 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to RACH procedure selection by IAB nodes). This information can be transmitted to other components of device 505. Receiver 510 can be a reference... Figure 7 Examples of various aspects of the transceiver 720 described. The receiver 510 may utilize a single antenna or an array of antennas.

[0131] Communication manager 515 may be an example of aspects of communication manager 415 as described herein. Communication manager 515 may include system information manager 520, RACH configuration selector 525, and RACH performance manager 530. Communication manager 515 may be an example of aspects of communication manager 710 as described herein.

[0132] System Information Manager 520 can receive system information from the parent base station indicating RACH protocol configurations that vary depending on the UE and those that vary depending on the radio backhaul, where the first radio node is the radio backhaul node to the parent base station. RACH Configuration Selector 525 can determine which UE-specific RACH protocol configuration to use for communication with the parent base station. RACH Performance Manager 530 can execute the RACH protocol with the parent base station according to the UE-specific RACH protocol configuration.

[0133] Transmitter 535 can transmit signals generated by other components of device 505. In some examples, transmitter 535 may coexist with receiver 510 in a transceiver module. For example, transmitter 535 may be a reference... Figure 7 Examples of various aspects of the transceiver 720 described. The transmitter 535 may utilize a single antenna or an array of antennas.

[0134] Figure 6 A block diagram 600 of a communication manager 605 supporting RACH protocol selection by an IAB node according to various aspects of this disclosure is shown. Communication manager 605 may be an example of aspects of communication manager 415, communication manager 515, or communication manager 710 described herein. Communication manager 605 may include a system information manager 610, a RACH configuration selector 615, a RACH performance manager 620, an RSRP manager 625, a signal change manager 630, an RTT manager 635, a RACH attempt manager 640, a RACH activation receiver 645, and a RACH activation request transmitter 650. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0135] System Information Manager 610 can receive system information from the parent base station indicating UE-specific RACH protocol configurations and UE-specific RACH protocol configurations, where the first radio node is the radio backhaul node to the parent base station. RACH Configuration Selector 615 can determine which UE-specific RACH protocol configuration to use for communication with the parent base station. RACH Performance Manager 620 can execute RACH protocols with the parent base station based on the UE-specific RACH protocol configuration. In some cases, the first radio node is an IAB node.

[0136] In some examples, the RACH configuration selector 615 can select a RACH protocol configuration that varies from UE to UE based on the fact that the first radio node is a mobile radio backhaul node.

[0137] In some examples, the RACH configuration selector 615 can determine that the next UE-specific RACH timing occurs before the next RACH timing that ...

[0138] In some examples, the RACH configuration selector 615 can select a RACH procedure configuration that varies from UE to RACH based on the satisfaction of one or more measurement thresholds.

[0139] RSRP manager 625 can determine the RSRP associated with communication with the parent base station. In some examples, RSRP manager 625 can identify a determined RSRP that exceeds a threshold RSRP derived from one or more measurement thresholds. In some examples, RACH configuration selector 615 can select a UE-specific RACH protocol configuration based on this identifier.

[0140] Signal change manager 630 can determine changes in RSRP or CQI associated with communication with the parent base station over time. In some examples, signal change manager 630 can identify a determined change exceeding a corresponding threshold RSRP change or threshold CQI change from one or more measurement thresholds. In some examples, RACH configuration selector 615 can select a UE-specific RACH protocol configuration based on this identifier.

[0141] RTT manager 635 can determine the RTT associated with communication with the parent base station. In some examples, RTT manager 635 can identify that the determined RTT is less than a threshold RTT from one or more measurement thresholds. In some examples, RACH configuration selector 615 can select a UE-specific RACH procedure configuration based on this identifier.

[0142] In some examples, the RTT manager 635 can determine changes in the RTT associated with communication with the parent base station. In some examples, the RTT manager 635 can identify a determined change in RTT that is less than a threshold change in RTT from one or more measurement thresholds. In some examples, the RACH configuration selector 615 can select a UE-specific RACH protocol configuration based on this identifier.

[0143] In some cases, the one or more measurement thresholds may differ for different categories of wireless nodes, including mobile wireless backhaul nodes, static wireless backhaul nodes, wide-area wireless backhaul nodes, and local wireless backhaul nodes. In some examples, the RACH configuration selector 615 may receive the one or more measurement thresholds from the parent base station via SIB transmission. In some examples, the RACH configuration selector 615 may receive the one or more measurement thresholds from the parent base station via unicast transmission, including F1 application protocol transmission, RRC transmission, MAC-CE transmission, DCI transmission, or a combination thereof.

[0144] The RACH attempt manager 640 can identify that the number of RACH attempts using a RACH protocol configuration that varies depending on the radio backhaul exceeds a threshold number of attempts. In some examples, the RACH configuration selector 615 can select a UE-specific RACH protocol configuration based on this identifier.

[0145] In some examples, the RACH attempt manager 640 may attempt to execute a RACH procedure with the parent base station based on a UE-specific RACH procedure configuration. In some examples, the RACH attempt manager 640 may identify that the number of RACH attempts using the UE-specific RACH procedure configuration exceeds a threshold number of attempts. In some examples, the RACH configuration selector 615 may determine, based on this identifier, whether to switch from using the UE-specific RACH procedure configuration to using the radio backhaul-specific RACH procedure configuration.

[0146] RACH activation receiver 645 can receive signaling from the parent base station that activates a UE-specific RACH protocol configuration for communication with the parent base station. In some examples, RACH activation receiver 645 can receive DCI, MAC-CE, RRC signaling, or a combination thereof. RACH activation request transmitter 650 can transmit a message to the parent base station requesting activation of the UE-specific RACH protocol configuration, wherein reception of signaling for activating the UE-specific RACH protocol configuration is based on this request. In some cases, this request is transmitted in a UCI transmission, MAC-CE transmission, F1 application protocol transmission, or RRC transmission, or a combination thereof.

[0147] In some examples, the RACH configuration selector 615 can determine whether to switch from using a UE-specific RACH protocol configuration to using a radio backhaul-specific RACH protocol configuration, wherein the power ramp counter is not reset during the switch. In some examples, the RACH configuration selector 615 can select a UE-specific RACH protocol configuration based on an information element that sorts the RACH protocols in the DCI transmission, wherein the information element indicates that the first radio node should use the UE-specific RACH protocol configuration.

[0148] Figure 7 A diagram of a system 700 including device 700 supporting RACH protocol selection by an IAB node is shown according to various aspects of this disclosure. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or a component including such devices. Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communication manager 710, an I / O controller 715, a transceiver 720, an antenna 725, a memory 730, and a processor 740. These components may be in electronic communication via one or more buses (e.g., bus 745).

[0149] The communication manager 710 can receive system information from the parent base station indicating RACH procedure configurations that vary depending on the UE and RACH procedure configurations that vary depending on the radio backhaul, wherein the first radio node is a radio backhaul node to the parent base station; determine whether to use the RACH procedure configuration that varies depending on the UE to communicate with the parent base station; and perform RACH procedures with the parent base station according to the RACH procedure configuration that varies depending on the UE.

[0150] The I / O controller 715 manages the input and output signals of device 705. The I / O controller 715 can also manage peripheral devices not integrated into device 705. In some cases, the I / O controller 715 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 715 may utilize an operating system, such as... MS- MS- OS / Or another known operating system. In other cases, the I / O controller 715 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 715 may be implemented as part of a processor. In some cases, a user may interact with the device 705 via the I / O controller 715 or via hardware components controlled by the I / O controller 715.

[0151] Transceiver 720 can communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, transceiver 720 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 720 may also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and to demodulate packets received from the antenna.

[0152] In some cases, a wireless device may include a single antenna 725. However, in other cases, the device may have more than one antenna 725, which may be able to transmit or receive multiple wireless transmissions concurrently.

[0153] Memory 730 may include random access memory (RAM) and read-only memory (ROM). Memory 730 may store computer-readable, computer-executable code 735, including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 730 may particularly include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0154] Processor 740 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 740 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 740. Processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., memory 730) to cause device 705 to perform various functions (e.g., functions or tasks supporting RACH procedure selection by LAB nodes).

[0155] Code 735 may include instructions for implementing various aspects of this disclosure, including instructions for supporting wireless communication. Code 735 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 735 may not be directly executed by processor 740, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0156] The communication manager 710 described herein can be implemented to achieve one or more potential advantages. One implementation may allow device 705 to execute RACH procedures with the parent node more efficiently. For example, device 705 may be configured to determine whether it can use a UE-specific RACH procedure or an IAB-specific RACH procedure. If device 705 is able to use either RACH procedure, it can determine which RACH procedure to use to reduce the waiting time associated with executing that RACH procedure.

[0157] Figure 8A block diagram 800 of a device 805 supporting RACH protocol selection by an IAB node according to various aspects of this disclosure is shown. Device 805 may be an example of various aspects of base station 105 as described herein. Device 805 may include a receiver 810, a communications manager 815, and a transmitter 820. Device 805 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0158] Receiver 810 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to RACH procedure selection by IAB nodes). This information can be transmitted to other components of device 805. Receiver 810 can be a reference... Figure 11 Examples of various aspects of the transceiver 1120 described herein. The receiver 810 may utilize a single antenna or an array of antennas.

[0159] The communication manager 815 can transmit system information to a first radio node indicating a UE-specific RACH protocol configuration and a UE-specific RACH protocol configuration, where the first radio node is a radio backhaul node to a parent base station; determine that the UE-specific RACH protocol configuration is being used by the first radio node to communicate with the parent base station; and perform RACH protocol with the first radio node according to the UE-specific RACH protocol configuration. The communication manager 815 may be an example of various aspects of the communication manager 1110 described herein.

[0160] The communication manager 815 or its sub-components may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functionality of the communication manager 815 or its sub-components may be performed by a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0161] The communication manager 815 or its subcomponents may be physically located at various locations, including being distributed such that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, the communication manager 815 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of this disclosure, the communication manager 815 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0162] Transmitter 820 can transmit signals generated by other components of device 805. In some examples, transmitter 820 may coexist with receiver 810 in a transceiver module. For example, transmitter 820 may be a reference... Figure 11 Examples of various aspects of the transceiver 1120 described. The transmitter 820 may utilize a single antenna or an array of antennas.

[0163] By including or configuring a UE communication manager 820 according to an example as described herein, device 820 can support techniques for improved communication reliability, reduced latency, more efficient utilization of communication resources, and improved inter-device coordination. Figure 9 A block diagram 900 of a device 905 supporting RACH protocol selection by an IAB node according to various aspects of this disclosure is shown. Device 905 may be an example of aspects of device 805 or base station 105 as described herein. Device 905 may include a receiver 910, a communications manager 915, and a transmitter 935. 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).

[0164] Receiver 910 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to RACH procedure selection by IAB nodes). This information can be transmitted to other components of device 905. Receiver 910 can be a reference... Figure 11 Examples of various aspects of the transceiver 1120 described herein. The receiver 910 may utilize a single antenna or an array of antennas.

[0165] Communication manager 915 may be an example of aspects of communication manager 815 as described herein. Communication manager 915 may include system information module 920, RACH determination module 925, and RACH execution module 930. Communication manager 915 may be an example of aspects of communication manager 1110 as described herein.

[0166] System information module 920 can transmit system information to the first radio node indicating RACH protocol configurations that vary depending on the UE and those that vary depending on the radio backhaul, wherein the first radio node is a radio backhaul node to the parent base station. RACH determination module 925 can determine that the RACH protocol configuration that varies depending on the UE is being used by the first radio node to communicate with the parent base station. RACH execution module 930 can execute the RACH protocol with the first radio node according to the RACH protocol configuration that varies depending on the UE.

[0167] Transmitter 935 can transmit signals generated by other components of device 905. In some examples, transmitter 935 may coexist with receiver 910 in a transceiver module. For example, transmitter 935 may be a reference... Figure 11 Examples of various aspects of the transceiver 1120 are described. The transmitter 935 may utilize a single antenna or an array of antennas.

[0168] Figure 10 A block diagram 1000 of a communication manager 1005 supporting RACH protocol selection by an IAB node according to various aspects of this disclosure is shown. The communication manager 1005 may be an example of aspects of the communication manager 815, communication manager 915, or communication manager 1110 described herein. The communication manager 1005 may include a system information module 1010, a RACH determination module 1015, a RACH execution module 1020, a threshold module 1025, a RACH activation transmitter 1030, and a RACH activation request receiver 1035. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0169] System information module 1010 can transmit system information to a first radio node indicating RACH protocol configurations that vary depending on the UE and those that vary depending on the radio backhaul, wherein the first radio node is a radio backhaul node to the parent base station. RACH determination module 1015 can determine that the UE-specific RACH protocol configuration is being used by the first radio node to communicate with the parent base station. RACH execution module 1020 can execute the RACH protocol with the first radio node according to the UE-specific RACH protocol configuration. In some cases, the first radio node is an IAB node.

[0170] The threshold module 1025 can determine one or more measurement thresholds for the first radio node to use in determining whether to use a UE-specific RACH protocol configuration. In some examples, the threshold module 1025 can transmit an indication of the one or more measurement thresholds to the first radio node.

[0171] In some cases, one of the one or more measurement thresholds is the RSRP associated with communication with the first wireless node. In some cases, one of the one or more measurement thresholds is the change in RSRP or CQI associated with communication with the first wireless node over time. In some cases, one of the one or more measurement thresholds is the RTT associated with communication with the first wireless node.

[0172] In some cases, the one or more measurement thresholds are different for different categories of wireless nodes, including mobile wireless backhaul nodes, static wireless backhaul nodes, wide-area wireless backhaul nodes, and local wireless backhaul nodes. In some cases, the indication of the one or more measurement thresholds is transmitted via SIB transmission. In some cases, the indication of the one or more measurement thresholds is transmitted via unicast transmission, including F1 application protocol transmission, RRC transmission, MAC-CE transmission, DCI transmission, or a combination thereof.

[0173] RACH activation transmitter 1030 can transmit signaling to a first radio node that activates a UE-specific RACH protocol configuration for communication with the first radio node. In some examples, RACH activation transmitter 1030 can transmit DCI, MAC-CE, RRC signaling, or a combination thereof. RACH activation request receiver 1035 can receive from the first radio node a message requesting activation of a UE-specific RACH protocol configuration, wherein the transmission of signaling for activating the UE-specific RACH protocol configuration is based on this request. In some cases, this request is received in a UCI transmission, MAC-CE transmission, F1 application protocol transmission, or RRC transmission, or a combination thereof.

[0174] In some examples, the RACH determination module 1015 can determine that the first radio node is a mobile radio backhaul node, wherein a UE-specific RACH protocol configuration is used based on the fact that the first radio node is a mobile radio backhaul node. In some examples, the RACH determination module 1015 can transmit an information element in the DCI transmission that orders the RACH protocol, wherein the information element indicates that the first radio node should use a UE-specific RACH protocol configuration.

[0175] Figure 11 A diagram of a system 1100 including device 1105 supporting RACH protocol selection by an IAB node is shown according to various aspects of this disclosure. Device 1105 may be an example of or include components of device 805, device 905, or base station 105 as described herein. Device 1105 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communication manager 1110, a network communication manager 1115, a transceiver 1120, an antenna 1125, a memory 1130, a processor 1140, and an inter-station communication manager 1145. These components may be in electronic communication via one or more buses (e.g., bus 1150).

[0176] The communication manager 1110 can transmit system information to the first radio node indicating RACH procedure configurations that vary depending on the UE and those that vary depending on the radio backhaul, wherein the first radio node is a radio backhaul node to the parent base station; determine that the RACH procedure configurations that vary depending on the UE are being used by the first radio node to communicate with the parent base station; and perform RACH procedures with the first radio node according to the RACH procedure configurations that vary depending on the UE.

[0177] The network communication manager 1115 can manage communication with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1115 can manage the delivery of data communication by client devices (such as one or more UEs 115).

[0178] Transceiver 1120 can communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, transceiver 1120 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1120 may also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and to demodulate packets received from the antenna.

[0179] In some cases, the wireless device may include a single antenna 1125. However, in other cases, the device may have more than one antenna 1125, which may be able to transmit or receive multiple wireless transmissions concurrently.

[0180] Memory 1130 may include RAM, ROM, or a combination thereof. Memory 1130 may store computer-readable code 1135 including instructions that, when executed by a processor (e.g., processor 1140), cause the device to perform the various functions described herein. In some cases, memory 1130 may, in particular, include a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0181] Processor 1140 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1140 may be configured to use a memory controller to operate a memory array. In some cases, the memory controller may be integrated into processor 1140. Processor 1140 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks supporting RACH procedure selection by LAB nodes).

[0182] Inter-site communication manager 1145 manages communication with other base stations 105 and may include a controller or scheduler for cooperating with other base stations 105 to control communication with UE 115. For example, inter-site communication manager 1145 may coordinate the scheduling of transmissions to UE 115 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, inter-site communication manager 1145 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between base stations 105.

[0183] Code 1135 may include instructions for implementing various aspects of this disclosure, including instructions for supporting wireless communication. Code 1135 may be stored in a non-transient computer-readable medium, such as system memory or other types of memory. In some cases, code 1135 may not be directly executed by processor 1140, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0184] By including or configuring a UE communication manager 1135 according to an example as described herein, device 820 can support techniques for improved communication reliability, reduced latency, more efficient utilization of communication resources, and improved inter-device coordination.

[0185] Figure 12 A flowchart illustrating method 1200 for supporting RACH procedure selection by an IAB node according to various aspects of this disclosure is shown. Operation of method 1200 may be implemented by UE 115 or its components as described herein. For example, operation of method 1200 may be implemented by, as referred to... Figures 4 to 7 The described communication manager is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the following functions. Alternatively or alternatively, the UE can use dedicated hardware to perform aspects of the following functions.

[0186] At 1205, the UE can receive system information from the parent base station indicating RACH protocol configurations that vary depending on the UE and those that vary depending on the radio backhaul, where the first radio node is the radio backhaul node to the parent base station. Operation of 1205 can be performed according to the methods described herein. In some examples, aspects of the operation of 1205 can be determined by reference to [reference needed]. Figures 4 to 7 The system information manager described is used to execute this.

[0187] In step 1210, the UE can determine whether to use a UE-specific RACH protocol configuration to communicate with the parent base station. The operation of step 1210 can be performed according to the methods described herein. In some examples, aspects of the operation of step 1210 can be determined by reference to [reference needed]. Figures 4 to 7 The RACH configuration selector described is used for execution.

[0188] In section 1215, the UE can execute the RACH procedure with the parent base station according to a RACH procedure configuration that varies from UE to UE. The operation of section 1215 can be performed according to the methods described herein. In some examples, aspects of the operation of section 1215 can be derived from, as referenced... Figures 4 to 7 The RACH execution manager is described for execution.

[0189] Figure 13 A flowchart illustrating method 1300 for supporting RACH procedure selection by an IAB node according to various aspects of this disclosure is shown. Operation of method 1300 may be implemented by UE 115 or its components as described herein. For example, operation of method 1300 may be implemented by, as referred to... Figures 4 to 7 The described communication manager is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the following functions. Alternatively or alternatively, the UE can use dedicated hardware to perform aspects of the following functions.

[0190] At 1305, the UE can receive system information from the parent base station indicating RACH protocol configurations that vary depending on the UE and those that vary depending on the radio backhaul, where the first radio node is the radio backhaul node to the parent base station. Operation of 1305 can be performed according to the methods described herein. In some examples, aspects of the operation of 1305 can be determined by reference to [reference needed]. Figures 4 to 7 The system information manager described is used to execute this.

[0191] In step 1310, the UE can determine whether to use a UE-specific RACH protocol configuration to communicate with the parent base station. The operation of step 1310 can be performed according to the methods described herein. In some examples, aspects of the operation of step 1310 can be determined by reference to... Figures 4 to 7 The RACH configuration selector described is used for execution.

[0192] In section 1315, the UE can select a UE-specific RACH protocol configuration based on whether the first radio node is a mobile radio backhaul node. Operation of section 1315 can be performed according to the methods described herein. In some examples, aspects of operation of section 1315 can be derived from references... Figures 4 to 7 The RACH configuration selector described is used for execution.

[0193] In step 1320, the UE can execute the RACH procedure with the parent base station according to a UE-specific RACH procedure configuration. The operation of step 1320 can be performed according to the methods described herein. In some examples, aspects of the operation of step 1320 can be derived from, as referenced... Figures 4 to 7 The RACH execution manager is described for execution.

[0194] Figure 14 A flowchart illustrating method 1400 for supporting RACH protocol selection by an IAB node according to various aspects of this disclosure is shown. Operation of method 1400 may be implemented by base station 105 or its components as described herein. For example, operation of method 1400 may be implemented by, as referred to... Figures 8 to 11 The described communication manager is used to perform this. In some examples, the base station can execute a set of instructions to control the functional elements of the base station to perform the following functions. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the following functions.

[0195] At 1405, the base station can transmit system information to a first radio node indicating a RACH protocol configuration that varies depending on the UE and a RACH protocol configuration that varies depending on the radio backhaul, wherein the first radio node is a radio backhaul node to the parent base station. The operation of 1405 can be performed according to the methods described herein. In some examples, aspects of the operation of 1405 can be derived from references... Figures 8 to 11 The system information module described is used for execution.

[0196] At 1410, the base station can determine that a RACH protocol configuration, varying from UE to UE, is being used by the first radio node to communicate with the parent base station. The operation of 1410 can be performed according to the methods described herein. In some examples, aspects of the operation of 1410 can be determined by referring to... Figures 8 to 11 The RACH determination module is described and executed.

[0197] In step 1415, the base station can perform the RACH procedure with the first radio node according to a RACH procedure configuration that varies from UE to RACH. The operation of step 1415 can be performed according to the methods described herein. In some examples, aspects of the operation of step 1415 can be described as follows: Figures 8 to 11 The RACH execution module is described and used for execution.

[0198] Figure 15 A flowchart illustrating method 1500 for supporting RACH protocol selection by an IAB node according to various aspects of this disclosure is shown. Operation of method 1500 may be implemented by base station 105 or its components as described herein. For example, operation of method 1500 may be implemented by, as referred to... Figures 8 to 11 The described communication manager is used to perform this. In some examples, the base station can execute a set of instructions to control the functional elements of the base station to perform the following functions. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the following functions.

[0199] In step 1505, the base station can determine one or more measurement thresholds for the first radio node to use to determine whether to use a UE-specific RACH protocol configuration. Operation of step 1505 can be performed according to the methods described herein. In some examples, aspects of operation of step 1505 can be determined as described in reference... Figures 8 to 11 The threshold module described is used for execution.

[0200] In 1510, the base station can transmit an indication of the one or more measurement thresholds to the first wireless node. The operation of 1510 can be performed according to the method described herein. In some examples, aspects of the operation of 1510 can be derived from, as referenced... Figures 8 to 11 The threshold module described is used for execution.

[0201] In step 1515, the base station can transmit system information to a first radio node indicating RACH protocol configurations that vary depending on the UE and those that vary depending on the radio backhaul, where the first radio node is the radio backhaul node to the parent base station. The operation of step 1515 can be performed according to the methods described herein. In some examples, aspects of the operation of step 1515 can be derived from references... Figures 8 to 11 The system information module described is used for execution.

[0202] At 1520, the base station can determine that a RACH protocol configuration, varying from UE to UE, is being used by the first radio node to communicate with the parent base station. Operation of 1520 can be performed according to the methods described herein. In some examples, aspects of operation of 1520 can be determined by referring to... Figures 8 to 11 The RACH determination module is described and executed.

[0203] In step 1525, the base station can perform the RACH procedure with the first radio node according to a RACH procedure configuration that varies from UE to RACH. The operation of step 1525 can be performed according to the methods described herein. In some examples, aspects of the operation of step 1525 can be described as follows: Figures 8 to 11 The RACH execution module is described and used for execution.

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

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

[0206] Aspect 1: A method for wireless communication at a first wireless node, comprising: receiving from a parent base station system information indicating a random access procedure configuration varying from a UE and a random access procedure configuration varying from a wireless backhaul, wherein the first wireless node is a wireless backhaul node to the parent base station; determining to use the UE-varying random access procedure configuration to communicate with the parent base station; and executing a random access procedure with the parent base station according to the UE-varying random access procedure configuration.

[0207] Aspect 2: The method of aspect 1, wherein determining to use a UE-specific random access procedure configuration includes: selecting a UE-specific random access procedure configuration at least in part based on the fact that the first radio node is a mobile radio backhaul node.

[0208] Aspect 3: The method of aspect 2, wherein selecting the UE-specific random access procedure configuration further includes: determining that the next UE-specific random access opportunity occurs before the next UE-specific random access opportunity; and selecting the UE-specific random access procedure configuration at least in part based on the fact that the next UE-specific random access opportunity occurs before the next UE-specific random access opportunity.

[0209] Aspect 4: The method of any one of Aspects 1 to 3, wherein determining to use a UE-specific random access procedure configuration includes: selecting a UE-specific random access procedure configuration at least in part based on satisfying one or more measurement thresholds.

[0210] Aspect 5: The method of aspect 4, wherein selecting a UE-specific random access procedure configuration further includes: determining a reference signal received power associated with communication with a parent base station; identifying a threshold reference signal received power that exceeds one or more measurement thresholds; and selecting a UE-specific random access procedure configuration based at least in part on the identifier.

[0211] Aspect 6: The method of any one of Aspects 4 to 5, wherein selecting a UE-specific random access procedure configuration further comprises: determining a change over time in a reference signal received power or channel quality indicator associated with communication with a parent base station; identifying a corresponding threshold reference signal received power change or threshold channel quality indicator change from the one or more measurement thresholds; and selecting a UE-specific random access procedure configuration based at least in part on the identification.

[0212] Aspect 7: The method of any one of Aspects 4 to 6, wherein selecting a UE-specific random access procedure configuration further comprises: determining a round-trip time associated with communication with a parent base station; identifying that the determined round-trip time is less than a threshold round-trip time from the one or more measurement thresholds; and selecting a UE-specific random access procedure configuration based at least in part on the identifier.

[0213] Aspect 8: The method of any one of Aspects 4 to 7, wherein selecting a UE-specific random access procedure configuration further comprises: determining a change in round-trip time associated with communication with a parent base station; identifying that the determined change in round-trip time exceeds a threshold change in round-trip time from the one or more measurement thresholds; and selecting a UE-specific random access procedure configuration based at least in part on the identification.

[0214] Aspect 9: The method of any one of Aspects 4 to 8, wherein the one or more measurement thresholds are different for different categories of wireless nodes, including mobile wireless backhaul nodes, static wireless backhaul nodes, wide-area wireless backhaul nodes, and local wireless backhaul nodes.

[0215] Aspect 10: The method of any one of Aspects 4 to 9 further includes: receiving the one or more measurement thresholds from the parent base station via system information block transmission.

[0216] Aspect 11: The method of any one of Aspects 4 to 10 further includes: receiving the one or more measurement thresholds from a parent base station via unicast transmission, the unicast transmission including F1 application protocol transmission, radio resource control transmission, media access control (MAC) control element transmission, downlink control information transmission, or a combination thereof.

[0217] Aspect 12: The method of any one of Aspects 1 to 11, wherein determining to use a UE-specific random access procedure configuration includes: identifying that the number of random access attempts using a UE-specific random access procedure configuration exceeds a threshold number of attempts; and selecting a UE-specific random access procedure configuration based at least in part on the identifier.

[0218] Aspect 13: The method of any one of Aspects 1 to 12 further includes: attempting to execute a random access procedure with a parent base station based on a random access procedure configuration that varies from UE to UE; identifying that the number of random access attempts using the random access procedure configuration that varies from UE to UE exceeds a threshold number of attempts; and determining, at least in part based on the identifier, to switch from using the random access procedure configuration that varies from UE to UE to using the random access procedure configuration that varies from radio backhaul.

[0219] Aspect 14: The method of any one of Aspects 1 to 13, wherein determining to use a UE-specific random access procedure configuration includes: receiving signaling from a parent base station that activates a UE-specific RACH procedure configuration for communication with the parent base station.

[0220] Aspect 15: As in aspect 14, where

[0221] Receiving signaling to activate the random access procedure configuration, which varies from UE to UE, further includes:

[0222] Receive downlink control information, media access control (MAC) control elements, radio resource control signaling, or a combination thereof.

[0223] Aspect 16: The method of any one of Aspects 14 to 15, further comprising: transmitting to a parent base station a message requesting activation of a UE-specific random access procedure configuration, wherein reception of signaling for activating the UE-specific random access procedure configuration is at least partially based on the request. Aspect 17: The method of Aspect 16, wherein the request is transmitted in uplink control information transmission, media access control (MAC) control element transmission, F1 application protocol transmission, or radio resource control transmission, or a combination thereof.

[0224] Aspect 18: The method of any one of Aspects 1 to 17 further includes: determining to switch from using a random access procedure configuration that varies from UE to using a random access procedure configuration that varies from radio backhaul, wherein the power ramp counter is not reset during the switch.

[0225] Aspect 19: The method of any one of Aspects 1 to 18, wherein determining to use a UE-specific random access procedure configuration comprises: selecting a UE-specific random access procedure configuration based at least in part on an information element that sorts the random access procedures in the downlink control information transmission, wherein the information element indicates that the first radio node should use a UE-specific random access procedure configuration.

[0226] Aspect 20: The method of any one of Aspects 1 to 19, wherein the first wireless node is an integrated access backhaul node.

[0227] Aspect 21: A method for wireless communication at a parent base station, comprising: transmitting system information to a first wireless node indicating a random access procedure configuration varying from that of a UE and a random access procedure configuration varying from that of a wireless backhaul, wherein the first wireless node is a wireless backhaul node to the parent base station; determining that the random access procedure configuration varying from that of the UE is being used by the first wireless node to communicate with the parent base station; and performing a random access procedure with the first wireless node according to the random access procedure configuration varying from that of the UE.

[0228] Aspect 22: The method of aspect 21, wherein determining that a UE-specific random access procedure configuration is being used includes: determining that a first radio node is a mobile radio backhaul node, wherein the UE-specific random access procedure configuration is used at least in part based on the fact that the first radio node is a mobile radio backhaul node.

[0229] Aspect 23: The method of any one of Aspects 21 to 22 further includes: determining one or more measurement thresholds for a first radio node to determine whether to use a random access procedure configuration that varies from UE to UE; and transmitting an indication of the one or more measurement thresholds to the first radio node.

[0230] Aspect 24: The method of aspect 23, wherein one of the one or more measurement thresholds is a reference signal received power associated with communication with the first wireless node.

[0231] Aspect 25: The method of any one of Aspects 23 to 24, wherein one of the one or more measurement thresholds is a change over time in reference signal received power or channel quality indicator related to communication with the first wireless node.

[0232] Aspect 26: The method of any one of aspects 23 to 25, wherein one of the one or more measurement thresholds is related to the round-trip time of communication with the first wireless node.

[0233] Aspect 27: The method of any one of Aspects 23 to 26, wherein the one or more measurement thresholds are different for different categories of wireless nodes, including mobile wireless backhaul nodes, static wireless backhaul nodes, wide-area wireless backhaul nodes and local wireless backhaul nodes.

[0234] Aspect 28: The method of any of Aspects 23 to 27, wherein an indication of the one or more measurement thresholds is transmitted via a system information block transmission.

[0235] Aspect 29: The method of any one of Aspects 23 to 28, wherein the indication of the one or more measurement thresholds is transmitted via unicast transmission, the unicast transmission including F1 application protocol transmission, radio resource control transmission, media access control (MAC) control element transmission, downlink control information transmission, or a combination thereof.

[0236] Aspect 30: The method of any one of Aspects 21 to 29, wherein determining that a random access procedure configuration varying from the UE is being used includes: transmitting signaling to a first radio node that activates the random access procedure configuration varying from the UE for communication with the first radio node.

[0237] Aspect 31: The method of aspect 30, wherein transmitting signaling to activate random access procedure configurations that vary from UE to UE further includes transmitting downlink control information, media access control (MAC) control elements, radio resource control signaling, or a combination thereof.

[0238] Aspect 32: The method of any one of Aspects 30 to 31 further includes: receiving from a first radio node a message requesting activation of a random access procedure configuration that varies from UE to UE, wherein the transmission of signaling for activating the random access procedure configuration that varies from UE to UE is at least partially based on the request.

[0239] Aspect 33: The method of aspect 32, wherein the request is received in uplink control information transmission, media access control (MAC) control element transmission, F1 application protocol transmission, or radio resource control transmission, or a combination thereof.

[0240] Aspect 34: The method of any one of Aspects 21 to 33, wherein determining that a UE-specific random access procedure configuration is being used includes: transmitting an information element that orders the random access procedure in a downlink control information transmission, wherein the information element indicates that the first radio node should use a UE-specific random access procedure configuration.

[0241] Aspect 35: The method of any of Aspects 21 to 34, wherein the first wireless node is an integrated access backhaul node.

[0242] Aspect 36: An apparatus for wireless communication at a first wireless node, 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 as described in any of Aspects 1 to 20.

[0243] Aspect 37: An apparatus for wireless communication at a first wireless node, comprising: at least one means for performing a method as described in any of aspects 1 to 20.

[0244] Aspect 38: A non-transient computer-readable medium storing code for wireless communication at a first wireless node, the code including instructions executable by a processor to perform methods as described in any of Aspects 1 to 20.

[0245] Aspect 39: An apparatus for wireless communication at a parent base station, 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 as described in any of Aspects 21 to 35.

[0246] Aspect 40: An apparatus for wireless communication at a parent base station, comprising at least one means for performing the method of any one of aspects 21 to 35.

[0247] Aspect 41: A non-transient computer-readable medium storing code for wireless communication at a parent base station, the code including instructions executable by a processor to perform methods as described in any of Aspects 21 to 35.

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

[0249] The information and signals described herein can be represented using any of a wide variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout this description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

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

[0251] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored or transmitted as one or more instructions or code on a computer-readable medium. Other examples and implementations fall within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that different parts of the function are implemented at different physical locations.

[0252] Computer-readable media includes both non-transient computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transient storage media can be any available medium accessible to a general-purpose 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, magnetic disk storage or other magnetic storage devices, or any other non-transient medium that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Similarly, any connection is also legitimately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then that coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable media. As used in this article, disk and disc include CDs, laser discs, optical discs, DVDs, floppy disks, and Blu-ray discs, where disks often magnetically reproduce data while discs optically reproduce data using lasers. Combinations of these media are also included within the scope of computer-readable media.

[0253] As used herein (including in the claims), the word "or" in an enumeration of items (e.g., an enumeration of items accompanied by phrases such as "at least one of" or "one or more of") indicates an inclusive enumeration, such that an enumeration of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Similarly, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

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

[0255] This document, illustrated with reference to the accompanying drawings, describes exemplary configurations but does not represent all examples that can be implemented or fall within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and does not imply "superior" or "outperforming" other examples. This detailed description includes specific details to provide an understanding of the described techniques. However, these techniques 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 described examples.

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

Claims

1. A method for performing wireless communication at a first wireless node, comprising: Receive system information from the parent node indicating random access procedure configurations that vary depending on the user equipment (UE) and random access procedure configurations that vary depending on the radio backhaul, wherein the first radio node is a radio backhaul node to the parent node. Determining to use the UE-specific random access procedure configuration to communicate with the parent node, wherein determining to use the UE-specific random access procedure configuration includes selecting the UE-specific random access procedure configuration at least in part based on the fact that the first radio node is a mobile radio backhaul node; and The random access procedure with the parent node is executed according to the selected random access procedure configuration that varies from UE to UE.

2. The method of claim 1, wherein selecting the UE-specific random access procedure configuration further comprises: The next random access opportunity, which varies from UE to UE, is determined to occur before the next random access opportunity, which varies from radio backhaul. as well as The UE-specific random access procedure configuration is selected at least in part based on the fact that the next UE-specific random access opportunity occurs before the next UE-specific random access opportunity.

3. The method of claim 1, wherein determining to use the UE-specific random access procedure configuration includes: The UE-specific random access procedure configuration is selected at least in part based on meeting one or more measurement thresholds.

4. The method of claim 3, wherein selecting the UE-specific random access procedure configuration further comprises: Determine the reference signal received power associated with the communication with the parent node; The reference signal received power identified exceeds the threshold reference signal received power derived from one or more measurement thresholds; as well as The UE-specific random access procedure configuration is selected at least in part based on the identifier.

5. The method of claim 3, wherein selecting the UE-specific random access procedure configuration further comprises: Determine the change over time of the reference signal received power or channel quality indicator associated with the communication with the parent node; The identifier indicates that the change exceeds the corresponding threshold reference signal received power change or threshold channel quality indicator change from one or more of the measurement thresholds; and The UE-specific random access procedure configuration is selected at least in part based on the identifier.

6. The method of claim 3, wherein selecting the UE-specific random access procedure configuration further comprises: Determine the round-trip time associated with communication with the parent node; The round-trip time determined by the identifier is less than the threshold round-trip time from the one or more measurement thresholds; as well as The UE-specific random access procedure configuration is selected at least in part based on the identifier.

7. The method of claim 3, wherein selecting the UE-specific random access procedure configuration further comprises: Determine the changes in round-trip time associated with communication with the parent node; The change in the round-trip time identified by the identifier exceeds the threshold change round-trip time from one or more of the measurement thresholds; as well as The UE-specific random access procedure configuration is selected at least in part based on the identifier.

8. The method of claim 3, wherein the one or more measurement thresholds are different for different categories of wireless nodes, wherein the categories of wireless nodes include mobile wireless backhaul nodes, static wireless backhaul nodes, wide-area wireless backhaul nodes, and local wireless backhaul nodes.

9. The method of claim 3, further comprising: The one or more measurement thresholds are received from the parent node via system information block transmission.

10. The method of claim 3, further comprising: The one or more measurement thresholds are received from the parent node via unicast transmission, which includes F1 application protocol transmission, radio resource control transmission, media access control (MAC) control element transmission, downlink control information transmission, or a combination thereof.

11. The method of claim 1, wherein determining to use the UE-specific random access procedure configuration comprises: The number of random access attempts configured using the random access procedure, which varies depending on the wireless backhaul, exceeds the threshold number of attempts. as well as The UE-specific random access procedure configuration is selected at least in part based on the identifier.

12. The method of claim 1, further comprising: The random access procedure with the parent node is attempted to be executed according to the UE-specific random access procedure configuration. The number of random access attempts configured using the UE-specific random access procedure exceeds the threshold number of attempts; and The decision to switch from using the UE-specific random access protocol configuration to using the UE-specific random access protocol configuration is determined at least in part based on the identifier.

13. The method of claim 1, wherein determining to use the UE-specific random access procedure configuration comprises: Receive signaling from the parent node to activate the UE-specific random access procedure configuration for communication with the parent node.

14. The method of claim 13, wherein receiving the signaling activating the UE-specific random access procedure configuration further comprises: Receive downlink control information, media access control (MAC) control elements, radio resource control signaling, or a combination thereof.

15. The method of claim 13, further comprising: A message requesting activation of the UE-specific random access procedure configuration is transmitted to the parent node, wherein the reception of the signaling for activating the UE-specific random access procedure configuration is at least in part based on the request.

16. The method of claim 15, wherein the request is transmitted in uplink control information transmission, media access control (MAC) control element transmission, F1 application protocol transmission, or radio resource control transmission, or a combination thereof.

17. The method of claim 1, further comprising: It is determined whether to switch from using the UE-specific random access procedure configuration to using the radio backhaul-specific random access procedure configuration, wherein the power ramp counter is not reset during the switch.

18. The method of claim 1, wherein determining to use the UE-specific random access procedure configuration comprises: The UE-specific random access procedure configuration is selected at least in part based on information elements that sort the random access procedure in the downlink control information transmission, wherein the information elements indicate that the first radio node should use the UE-specific random access procedure configuration.

19. The method of claim 1, wherein the first wireless node is an integrated access backhaul node.

20. A method for wireless communication at a parent node, comprising: System information indicating random access procedure configurations that vary depending on the user equipment (UE) and the random access procedure configurations that vary depending on the wireless backhaul is transmitted to a first wireless node, wherein the first wireless node is a wireless backhaul node to the parent node. Determining that the UE-specific random access procedure configuration is being used by the first radio node to communicate with the parent node, wherein determining that the UE-specific random access procedure configuration is being used includes determining that the first radio node is a mobile radio backhaul node, wherein the UE-specific random access procedure configuration is used at least in part based on the fact that the first radio node is a mobile radio backhaul node; as well as The random access procedure with the first radio node is executed according to the UE-specific random access procedure configuration.

21. The method of claim 20, further comprising: One or more measurement thresholds are determined for the first wireless node to use to determine whether to use the UE-specific random access procedure configuration; as well as The first wireless node is informed of the one or more measurement thresholds.

22. The method of claim 21, wherein one of the one or more measurement thresholds is a reference signal received power, a reference signal received power or channel quality indicator change over time, round-trip time, or a combination thereof, relating to communication with the first wireless node.

23. The method of claim 20, wherein determining that the UE-specific random access procedure configuration is being used comprises: Signaling is transmitted to the first wireless node to activate the UE-specific random access procedure configuration for communication with the first wireless node.

24. The method of claim 23, wherein transmitting the signaling activating the UE-specific random access procedure configuration further comprises: Transmits downlink control information, media access control (MAC) control elements, radio resource control signaling, or a combination thereof.

25. The method of claim 23, further comprising: A request to activate the UE-specific random access procedure configuration is received from the first radio node, wherein the transmission of the signaling for activating the UE-specific random access procedure configuration is at least partially based on the request.

26. The method of claim 20, wherein determining that the UE-specific random access procedure configuration is being used comprises: In the downlink control information transmission, information elements are transmitted that order the random access procedure, wherein the information elements indicate that the first radio node should use the UE-specific random access procedure configuration.

27. An apparatus for performing wireless communication at a first wireless node, comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor, the instructions causing the device to: Receive system information from the parent node indicating random access procedure configurations that vary depending on the user equipment (UE) and random access procedure configurations that vary depending on the radio backhaul, wherein the first radio node is a radio backhaul node to the parent node. Determining to use the UE-specific random access procedure configuration to communicate with the parent node, wherein determining to use the UE-specific random access procedure configuration includes selecting the UE-specific random access procedure configuration at least in part based on the fact that the first radio node is a mobile radio backhaul node; and The random access procedure with the parent node is executed according to the UE-specific random access procedure configuration.

28. An apparatus for wireless communication at a parent node, comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor, the instructions causing the device to: System information indicating random access procedure configurations that vary depending on the user equipment (UE) and the random access procedure configurations that vary depending on the wireless backhaul is transmitted to a first wireless node, wherein the first wireless node is a wireless backhaul node to the parent node. Determining that the UE-specific random access procedure configuration is being used by the first radio node to communicate with the parent node, wherein determining that the UE-specific random access procedure configuration is being used includes determining that the first radio node is a mobile radio backhaul node, wherein the UE-specific random access procedure configuration is used at least in part based on the fact that the first radio node is a mobile radio backhaul node; as well as The random access procedure with the first radio node is executed according to the UE-specific random access procedure configuration.

29. An apparatus for performing wireless communication at a first wireless node, comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor, the instructions causing the device to perform the method as described in any one of claims 2-19.

30. An apparatus for wireless communication at a parent node, comprising: processor; Memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor, the instructions causing the device to perform the method as described in any one of claims 21-26.

Images