Back-to-back random access channel procedure

Abstract

Methods, systems, and devices are described for wireless communication. The techniques described herein provide back-to-back random access channel (RACH) procedures. In some examples, a user equipment (UE) can initiate a first RACH procedure associated with a first trigger. The first RACH procedure can be associated with a first number of RACH attempts and a first physical random access channel (PRACH) power control parameter value. The UE can initiate a second RACH procedure after initiation of the first RACH procedure. The second RACH procedure can be associated with a second trigger that is different from the first trigger. The UE can perform the second RACH procedure based on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

Description

Technical Field

[0001] The following discussion relates to wireless communication, including back-to-back random access channel procedures. Background Technology

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

[0003] The described technology relates to improved methods, systems, devices, and apparatuses for supporting back-to-back random access channel (RACH) procedures. For example, the described technology provides a new RACH procedure that inherits the number of RACH attempts from an ongoing RACH procedure when the new RACH procedure is initiated. In some examples, the new RACH procedure may inherit the Physical Random Access Channel (PRACH) power control result of the ongoing RACH procedure. In some examples, the UE may initiate a first RACH procedure associated with a first trigger. The first RACH procedure may be associated with a first number of RACH attempts and a first PRACH power control parameter value. The UE may initiate a second RACH procedure after the initiation of the first RACH procedure, and the second RACH procedure may be associated with a second trigger different from the first trigger. The UE may perform the second RACH procedure based on one or more of the first number of RACH attempts or the first PRACH power control parameter value. In some cases, the UE may stop the first RACH procedure based on the initiation of the second RACH procedure.

[0004] A method for wireless communication by a user equipment (UE) is described. The method may include: initiating a first random access channel (RACH) procedure associated with a first trigger, wherein the first RACH procedure is associated with a first number of RACH attempts and a first physical random access channel (PRACH) power control parameter value; initiating a second RACH procedure after the initiation of the first RACH procedure, wherein the second RACH procedure is associated with a second trigger different from the first trigger; and performing the second RACH procedure based on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

[0005] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the UE to: initiate a first RACH procedure associated with a first trigger, wherein the first RACH procedure is associated with a first number of RACH attempts and a first PRACH power control parameter value; initiate a second RACH procedure after the initiation of the first RACH procedure, wherein the second RACH procedure is associated with a second trigger different from the first trigger; and perform the second RACH procedure based on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

[0006] Another UE for wireless communication is described. The UE may include: components for initiating a first RACH procedure associated with a first trigger, wherein the first RACH procedure is associated with a first number of RACH attempts and a first PRACH power control parameter value; components for initiating a second RACH procedure after the initiation of the first RACH procedure, wherein the second RACH procedure is associated with a second trigger different from the first trigger; and components for performing the second RACH procedure based on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

[0007] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: initiate a first RACH process associated with a first trigger, wherein the first RACH process is associated with a first number of RACH attempts and a first PRACH power control parameter value; initiate a second RACH process after the initiation of the first RACH process, wherein the second RACH process is associated with a second trigger different from the first trigger; and perform the second RACH process based on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

[0008] Some examples of the methods, user equipment (devices), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for stopping the first RACH process based on initiating the second RACH process.

[0009] Some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: initializing one or more of a second number of RACH attempts associated with the second RACH procedure to the first number of RACH attempts; initializing a second PRACH power control parameter value associated with the second RACH procedure to the first PRACH power control parameter value, and wherein performing the second RACH procedure based on one or more of the first number of RACH attempts or the first PRACH power control parameter value includes performing the second RACH procedure based on one or more of the second number of RACH attempts and the second PRACH power control parameter value.

[0010] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, one or more of the first number of RACH attempts and the first PRACH power control parameter value are saved based on initiating the second RACH procedure.

[0011] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, the first number of RACH attempts corresponds to a first preamble transmission counter value, and the methods, apparatus, and nontransitory computer-readable media may also include operations, features, components, or instructions for setting the value of a variable associated with the number of RACH messages aborted to equal the first preamble transmission counter value based on initiating the second RACH procedure.

[0012] Some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: initializing a second preamble transmission counter associated with the second RACH procedure to the value of the variable associated with the number of aborted RACH messages, and wherein performing the second RACH procedure based on one or more of the first number of RACH attempts or the first PRACH power control parameter value includes performing the second RACH procedure based on the second preamble transmission counter value.

[0013] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, the first PRACH power control parameter value corresponds to a first preamble power ramp counter value, and the methods, apparatus, and nontransitory computer-readable media may also include operations, features, components, or instructions for setting the value of the power ramp variable to equal the first preamble power ramp counter value based on initiating the second RACH procedure.

[0014] Some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: initializing a second preamble power ramp counter associated with the second RACH procedure to the value of the power ramp variable, and wherein performing the second RACH procedure based on one or more of the first number of RACH attempts or the first PRACH power control parameter value includes performing the second RACH procedure based on the value of the second preamble power ramp counter. Attached Figure Description

[0015] Figure 1 An example of a wireless communication system supporting a back-to-back random access channel (RACH) procedure according to one or more aspects of this disclosure is shown.

[0016] Figure 2 An example of a wireless communication system supporting a back-to-back RACH process according to one or more aspects of this disclosure is shown.

[0017] Figure 3 An example of a process flow supporting a back-to-back RACH process is shown according to one or more aspects of this disclosure.

[0018] Figure 4 and Figure 5 A block diagram of an apparatus supporting a back-to-back RACH process according to one or more aspects of this disclosure is shown.

[0019] Figure 6 A block diagram of a communication manager supporting a back-to-back RACH process according to one or more aspects of this disclosure is shown.

[0020] Figure 7 A diagram of a system including an apparatus supporting a back-to-back RACH process is shown, according to one or more aspects of this disclosure.

[0021] Figure 8 and Figure 9 A flowchart illustrating a method for supporting a back-to-back RACH process according to one or more aspects of this disclosure is shown. Detailed Implementation

[0022] Some wireless communication systems can deploy network entities and user equipment (UEs). UEs can perform a Random Access Channel (RACH) procedure to synchronize with the network entity. A RACH procedure can be triggered for any of a variety of reasons, such as service requests, scheduling requests for a maximum number of attempts, and beam failure recovery. In some cases, a UE can operate in a cell of a network entity with adverse conditions, such as poor coverage and uplink interference. A UE can attempt multiple RACH attempts before the RACH procedure succeeds or before the maximum number of RACH attempts has been made. In some examples, a second RACH procedure can be triggered in the same cell for different reasons (by different types of triggers relative to the trigger used for the first RACH procedure) before the first RACH procedure is completed. If the RACH attempts for the first RACH procedure have failed several times, the probability of a successful RACH in that cell may be low. If another back-to-back RACH procedure (e.g., a second RACH procedure) is triggered and the UE performs another set of RACH attempts in the same cell, large outage delays may occur.

[0023] The techniques described herein for handling back-to-back RACH procedures can reduce interruption latency and have other potential benefits. For example, if a new RACH procedure is initiated during an ongoing RACH procedure, the new RACH procedure can inherit the number of RACH attempts from the ongoing RACH procedure when it is initiated. In some examples, the new RACH procedure can inherit the Physical Random Access Channel (PRACH) power control result of the ongoing RACH procedure. For example, a UE can initiate a first RACH procedure associated with a first trigger. This first RACH procedure can be associated with a first number of RACH attempts and a first PRACH power control parameter value. The UE can initiate a second RACH procedure after the initiation of the first RACH procedure, and the second RACH procedure can be associated with a second trigger different from the first trigger. The UE can perform the second RACH procedure based on one or more of the first number of RACH attempts or the first PRACH power control parameter value. In some cases, the UE can stop the first RACH procedure based on the initiation of the second RACH procedure.

[0024] The aspects of this disclosure are first described in the context of a wireless communication system. They are also described in the context of a process flow. The aspects of this disclosure are further illustrated and described by way of apparatus diagrams, system diagrams, and flowcharts relating to a back-to-back RACH process.

[0025] Figure 1 An example of a wireless communication system 100 supporting a back-to-back RACH process according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

[0029] In some examples, network entity 105 may communicate with core network 130, or with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

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

[0031] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access and Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) such as CU 160, a Distributed Unit (DU) such as DU 165, a Radio Unit (RU) such as RU 170, a RAN Intelligent Controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system such as SMO system 180, or any combination thereof. RU170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0032] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) may connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or a combination thereof, and DU 165, RU 170, or both may host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and may each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack, and RU 170 may support one or more different layers of the protocol stack. DU 165 may (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0033] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities of network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104, or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0034] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

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

[0036] The UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes operate as repeaters, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0037] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0038] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0039] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, and The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for 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).

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

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

[0042] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to transmit control information to UE 115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE 115 (e.g., a particular UE).

[0043] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas such as coverage area 110. In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) may overlap, but coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies may be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different RATs to support communication to coverage area 110 (e.g., different coverage areas).

[0044] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

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

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

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

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

[0049] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

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

[0051] Wireless communication system 100 may deploy network entity 105 and UE 115. UE 115 may perform a RACH procedure to synchronize with network entity 105. The RACH procedure may be triggered for various reasons, such as service requests, scheduling requests for the maximum number of attempts, and beam failure recovery. In some cases, UE 115 may operate in a cell of network entity 105 with adverse conditions, such as poor coverage and uplink interference. UE 115 may attempt multiple RACH attempts before the RACH procedure succeeds or before the maximum number of RACH attempts has been attempted. In some examples, a second RACH procedure may be triggered in the same cell for different reasons before the first RACH procedure is completed. If the RACH attempts of the first RACH procedure have failed several times, the probability of RACH success in that cell may be low. If another back-to-back RACH procedure (e.g., a second RACH procedure) is triggered and UE 115 performs another set of RACH attempts in the same cell, large outage delays may occur.

[0052] The techniques described herein for handling back-to-back RACH procedures can reduce interruption latency and have other potential benefits. If a new RACH procedure is initiated during an ongoing RACH procedure, the new RACH procedure can inherit the number of RACH attempts from the ongoing RACH procedure when it is initiated. In some examples, the new RACH procedure can inherit the PRACH power control result of the ongoing RACH procedure. For example, UE 115 can initiate a first RACH procedure associated with a first trigger. This first RACH procedure can be associated with a first number of RACH attempts and a first PRACH power control parameter value. UE 115 can initiate a second RACH procedure after the initiation of the first RACH procedure, and the second RACH procedure can be associated with a second trigger different from the first trigger. UE 115 can execute the second RACH procedure based on one or more of the first number of RACH attempts or the first PRACH power control parameter value. In some cases, UE 115 can stop the first RACH procedure based on the initiation of the second RACH procedure.

[0053] Figure 2 An example of a wireless communication system 200 supporting a back-to-back RACH process according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 includes a UE 115-a, which may be an example of UE 115 as described herein. The wireless communication system 200 may also include a network entity 105-a, which may be an example of network entity 105 as described herein.

[0054] UE 115-a can communicate with network entity 105-a using communication link 125-a. Communication link 125-a can be an example of an NR or LTE link between UE 115-a and network entity 105-a. Communication link 125-a can include a bidirectional link that enables both uplink and downlink communication. For example, network entity 105-a can use communication link 125-a to send downlink signals (e.g., downlink transmissions) to UE 115-a, such as downlink control signaling 205 and downlink data signaling 210, and UE 115-a can use communication link 125-a to send uplink signals (e.g., uplink transmissions) to network entity 105-a, such as uplink control signaling 215 and uplink data signaling 220.

[0055] UE 115-a can perform a RACH procedure to synchronize with network entity 105-a. For the random access procedure, UE 115-a can send a preamble message (Msg1) 225 to network entity 105-a, and network entity 105-a can send a random access response message (Msg2) 230 to UE 115-a. Upon receiving Msg2, UE 115-a can send message three (Msg3) 235 to network entity 105-a, and network entity 105-a can send a contention resolution message (Msg4) 240 to UE 115-a. The RACH procedure can be triggered for various reasons, such as service requests, scheduling requests for maximum retransmission, and beam failure recovery. In some cases, UE 115-a can operate in a cell of network entity 105-a with adverse conditions, such as poor coverage, large uplink interference, or network entity problems. UE115-a may attempt multiple RACH attempts before a RACH procedure succeeds or before the maximum number of RACH attempts have been made. In some examples, a second RACH procedure or a back-to-back RACH procedure may be triggered in the same cell for different reasons before the first RACH procedure is completed. If the RACH attempts of the first RACH procedure have failed several times in an unfavorable cell, the probability of RACH success in that cell may be low. If another back-to-back RACH procedure is triggered (e.g., the second RACH procedure) and UE115-a performs another set of RACH attempts in the same cell (e.g., another...), the probability of RACH success may be low. preambleTransMax Repeated RACH attempts can generate significant outage delays. In some cases, declaring a radio link failure and re-establishing a connection to a new cell may be a better option than remaining in the original cell to attempt more RACH attempts that would cause additional delays.

[0056] In some examples, a balance can be considered between RACH interruption delay and RACH success. RACH interruption delay can be approximated by [PRACH periodicity per synchronization signal block (SSB)]. [Number of RACH Attempts]. The number of RACH attempts can be a key factor affecting RACH latency, especially if the PRACH periodicity per SSB is configured to a large value. Under the current PRACH mechanism, regardless of the number of RACH attempts performed in the first RACH process, the RACH attempt counter can be restarted from 0 in the second back-to-back RACH process. Under the current PRACH power control mechanism, the initial PRACH power of the second back-to-back RACH process does not inherit the latest power ramp result from the first RACH process. Without inheriting previous power ramps, assuming the radio frequency (RF) conditions remain unchanged, more RACH attempts can be used for the second RACH process.

[0057] In high-speed train and highway scenarios, RF conditions may deteriorate drastically, and cell changes may occur frequently. RACH interruption delays are more likely to occur in these scenarios, and their impact on user experience is more severe. For example, UE 115-a may initiate the first RACH procedure after the maximum number of scheduling request (SR) attempts has been reached due to a lack of uplink permission. UE 115-a can perform five RACH attempts by sending a preamble message on PRACH, and these five RACH attempts may fail due to the lack of a random access response message (Msg2) or a contention resolution message (Msg4). Before the first RACH procedure reaches the maximum of ten RACH attempts, UE 115-a may be triggered for a second RACH procedure due to a beam failure. UE 115-a may abort the first RACH procedure and initiate the second RACH procedure. The second RACH procedure may reach the maximum of ten RACH attempts even if all attempts fail. UE 115-a can declare a radio link failure (RLF) and re-establish a connection to a new cell and restore the RRC connection. The RACH interruption delay for a back-to-back RACH process between the first and second RACH processes on the same cell can be greater than two seconds. For example, the periodicity in the SSB for transmitting the PRACH preamble of UE 115-a is 160ms. A first RACH process with five attempts can provide approximately 0.8 seconds (e.g., 160ms). 5) RACH interruption delay. A second RACH process with ten attempts can provide approximately 1.6 seconds (e.g., 160ms). 10) RACH outage delay. Several RACH attempts in an unfavorable cell can lead to large outage delays.

[0058] The techniques described herein for handling back-to-back RACH procedures reduce interruption latency and have other potential benefits. If a new RACH procedure is initiated during an ongoing RACH procedure, UE 115-a can abort the ongoing RACH procedure. UE 115-a can save variables from the just-aborted RACH procedure. For example, UE 115-a can save the variable PREAMBLE_TRANSMISSION_COUNTER from the aborted RACH procedure to a variable... Msg1_Num_RACHAborted UE 115-a can save the variable PREAMBLE_POWER_RAMPING_COUNTER of the aborted RACH procedure to a variable Msg1_ PwrRamping_Num_RACHAborted UE 115-a can be achieved by changing variables PREAMBLE_TRANSMISSION_COUNTER The value is set to the saved variable value. Msg1_Num_RACHAborted Instead of 1, and change the variable PREAMBLE_POWER_ RAMPING_COUNTER The value is set to Msg1_PwrRamping_Num_RACHAborted Instead of initializing the variables for a new RACH procedure with 1, UE 115-a can use the initialized variable values ​​to execute a new RACH procedure.

[0059] In some examples, techniques for handling back-to-back RACH processes offer two key advantages to avoid large outage latency. In some examples, when a newly triggered second RACH process is initiated, the second RACH process inherits the number of RACH attempts from the first RACH process. In some examples, when a newly triggered second RACH process is initiated, the second RACH process inherits the PRACH power control results from the first RACH process. Techniques for handling back-to-back RACH processes effectively avoid large outage latency and ensure RACH success rate in back-to-back RACH scenarios. Techniques for handling back-to-back RACH processes can provide a better user experience in scenarios with poor coverage and high uplink interference, such as high-speed train scenarios and highway scenarios.

[0060] refer to Figure 2UE 115-a may initiate a first RACH procedure associated with a first trigger. For the first RACH procedure, UE 115-a may perform a first RACH attempt 245 using PRACH power control parameter value 250. The first RACH attempt 245 may fail, and UE 115-a may perform a second RACH attempt 255 using PRACH power control parameter value 260. The second RACH attempt 255 may fail, and UE 115-a may perform a third RACH attempt 265 using PRACH power control parameter value 270. UE 115-a may initiate a second RACH procedure after the third RACH attempt 265 of the first RACH procedure. The second RACH procedure may be associated with a second trigger different from the first trigger. UE 115-a may perform the second RACH procedure based on one or more of a first number of RACH attempts (e.g., three RACH attempts) or a first PRACH power control parameter value (e.g., PRACH power control parameter value 270). In some cases, UE 115-a can stop (e.g., interrupt, terminate, or avoid continuing or completing) the first RACH procedure by initiating a second RACH procedure. UE 115-a can initialize a second number of RACH attempts associated with the second RACH procedure to a first number of RACH attempts (e.g., three RACH attempts). UE 115-a can initialize a second PRACH power control parameter value associated with the second RACH procedure to a first PRACH power control parameter value (e.g., PRACH power control parameter value 270). UE 115-a can use the initialized second number of RACH attempts and the initialized second PRACH power control parameter value to perform the second RACH procedure.

[0061] Figure 3 Examples of process flow 300 supporting a back-to-back RACH process according to one or more aspects of this disclosure are shown. In some examples, process flow 300 may be implemented as described in references respectively. Figure 1 and Figure 2 The described aspects of the wireless communication systems 100 and 200, or those implemented therein. For example, process flow 300 can be implemented by network entity 105-b, which can be as described in reference... Figure 1 and Figure 2 An example of network entity 105 is described. Process flow 300 can be implemented by UE 115-b, which can be as shown in the reference. Figure 1 and Figure 2 An example of a UE as described.

[0062] In some examples, the operations illustrated in process flow 300 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code (e.g., software executed by a processor), or any combination thereof. Alternative examples are possible, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added.

[0063] At 305, UE 115-b can initiate the first RACH procedure associated with the first trigger.

[0064] At 310, UE 115-b may send a preamble or Msg1 associated with the RACH attempt in the first RACH procedure. In some examples, the first RACH procedure may be associated with a first number of RACH attempts and a first PRACH power control parameter value.

[0065] At point 315, UE 115-b can initiate a second RACH procedure. The second RACH procedure can be associated with a second trigger that is different from the first trigger.

[0066] At 320, UE 115-b can stop the first RACH procedure by initiating a second RACH procedure.

[0067] At 325, UE 115-b may store one or more of a first number of RACH attempts and a first PRACH power control parameter value. In some examples, the first number of RACH attempts may correspond to a first preamble transmission counter value. In some examples, UE 115-b may set the value of a variable associated with the number of aborted RACH messages to equal the first preamble transmission counter value based on initiating a second RACH procedure. In some examples, UE 115-b may set the value of a power ramp variable to equal the first preamble power ramp counter value based on initiating a second RACH procedure.

[0068] At 330, UE 115-b may initialize a second number of RACH attempts associated with the second RACH procedure to a first number of RACH attempts. In some examples, UE 115-b may initialize a second preamble transmission counter associated with the second RACH procedure to the value of a variable associated with the number of RACH messages that were aborted.

[0069] At 335, UE 115-b can initialize the second PRACH power control parameter value associated with the second RACH procedure to the first PRACH power control parameter value. In some examples, UE 115-b can initialize the second preamble power ramp counter associated with the second RACH procedure to the value of the power ramp variable.

[0070] At 340, UE 115-b may perform a second RACH procedure based on one or more of the first number of RACH attempts or the first PRACH power control parameter value. In some examples, UE 115-b may perform a second RACH procedure based on one or more of the second number of RACH attempts and the second PRACH power control parameter value. In some examples, UE 115-b may perform a second RACH procedure based on a second preamble transmission counter value. In some examples, UE 115-b may perform a second RACH procedure based on a second preamble power ramp counter value.

[0071] Figure 4 A block diagram 400 is shown of an apparatus 405 supporting a back-to-back RACH process according to one or more aspects of this disclosure. Apparatus 405 may be an example of aspects of UE 115 as described herein. Apparatus 405 may include a receiver 410, a transmitter 415, and a communication manager 420. Apparatus 405 or one or more components of apparatus 405 (e.g., receiver 410, transmitter 415, communication manager 420) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0072] Receiver 410 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to back-to-back RACH processes). The information may be passed to other components of device 405. Receiver 410 may utilize a single antenna or a collection of antennas.

[0073] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with back-to-back RACH processes), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0074] The communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be examples of components used to perform various aspects of the back-to-back RACH process as described herein. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be able to perform one or more of the functions described herein.

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

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

[0077] In some examples, the communication manager 420 may be configured to use a receiver 410, a transmitter 415, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or integrate with the receiver 410, the transmitter 415, or both to acquire information, output information, or perform various other operations as described herein.

[0078] The communication manager 420 may support wireless communication according to examples disclosed herein. For example, the communication manager 420 may be capable of, configured to, or operable to support components for initiating a first RACH process associated with a first trigger, wherein the first RACH process is associated with a first number of RACH attempts and a first PRACH power control parameter value. The communication manager 420 may be capable of, configured to, or operable to support components for initiating a second RACH process after the initiation of the first RACH process, wherein the second RACH process is associated with a second trigger that is different from the first trigger (e.g., has a different trigger type from the first trigger). The communication manager 420 may be capable of, configured to, or operable to support components for performing a second RACH process based on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

[0079] By including or configuring a communication manager 420 according to an example as described herein, device 405 (e.g., controlling receiver 410, transmitter 415, communication manager 420 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for more efficient use of communication resources.

[0080] Figure 5 A block diagram 500 of an apparatus 505 supporting a back-to-back RACH process according to one or more aspects of this disclosure is shown. Apparatus 505 may be an example of aspects of apparatus 405 or UE 115 as described herein. Apparatus 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Apparatus 505 or one or more components of apparatus 505 (e.g., receiver 510, transmitter 515, communication manager 520) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0081] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to back-to-back RACH processes). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0082] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to back-to-back RACH processes), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0083] Device 505 or its various components may be examples of parts used to perform various aspects of a back-to-back RACH process as described herein. For example, communication manager 520 may include a first RACH process manager 525, a second RACH process manager 530, or any combination thereof. Communication manager 520 may be examples of aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use receiver 510, transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in combination with receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0084] Communication manager 520 may support wireless communication according to examples disclosed herein. First RACH process manager 525 is capable of, configured to, or operable to support components for initiating a first RACH process associated with a first trigger, wherein the first RACH process is associated with a first number of RACH attempts and a first PRACH power control parameter value. Second RACH process manager 530 is capable of, configured to, or operable to support components for initiating a second RACH process after the initiation of the first RACH process, wherein the second RACH process is associated with a second trigger different from the first trigger (e.g., having a different trigger type from the first trigger). Second RACH process manager 530 is capable of, configured to, or operable to support components for performing a second RACH process based on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

[0085] Figure 6A block diagram 600 is shown of a communication manager 620 supporting a back-to-back RACH process according to one or more aspects of this disclosure. The communication manager 620 may be an example of a communication manager 420, a communication manager 520, or aspects thereof as described herein. The communication manager 620 or its various components may be examples of parts for performing various aspects of the back-to-back RACH process as described herein. For example, the communication manager 620 may include a first RACH process manager 625, a second RACH process manager 630, a RACH attempt manager 635, a RACH power control manager 640, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0086] Communication manager 620 may support wireless communication according to examples disclosed herein. First RACH process manager 625 is capable of, configured to, or operable to support components for initiating a first RACH process associated with a first trigger, wherein the first RACH process is associated with a first number of RACH attempts and a first PRACH power control parameter value. Second RACH process manager 630 is capable of, configured to, or operable to support components for initiating a second RACH process after the initiation of the first RACH process, wherein the second RACH process is associated with a second trigger that is different from the first trigger (e.g., has a different trigger type than the first trigger). In some examples, second RACH process manager 630 is capable of, configured to, or operable to support components for performing a second RACH process based on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

[0087] In some examples, the first RACH process manager 625 is capable of, can be configured to, or is operable to support components for stopping the first RACH process based on initiating a second RACH process.

[0088] In some examples, the RACH attempt manager 635 is capable of, configured to, or operable to support components for initializing one or more of a second number of RACH attempts associated with a second RACH process to a first number of RACH attempts. In some examples, the RACH power control manager 640 is capable of, configured to, or operable to support components for initializing a second PRACH power control parameter value associated with a second RACH process to a first PRACH power control parameter value. In some examples, to support components for performing a second RACH process based on one or more of the first number of RACH attempts or the first PRACH power control parameter value, the second RACH process manager 630 is capable of, configured to, or operable to support components for performing a second RACH process based on one or more of the second number of RACH attempts and the second PRACH power control parameter value.

[0089] In some examples, the first RACH process manager 625 is capable of, configured to, or operable to support components for saving one or more of a first number of RACH attempts and a first PRACH power control parameter value based on initiating a second RACH process.

[0090] In some examples, the first number of RACH attempts corresponds to the first preamble transmission counter value, and the RACH attempt manager 635 is capable of, can be configured to, or is operable to support components for setting the value of a variable associated with the number of RACH messages aborted to equal the first preamble transmission counter value based on initiating a second RACH process.

[0091] In some examples, the RACH attempt manager 635 is capable of, configured to, or operable to support components for initializing a second preamble transmission counter associated with a second RACH procedure to a value associated with the number of RACH messages aborted. In some examples, to support components for executing a second RACH procedure based on one or more of a first number of RACH attempts or a first PRACH power control parameter value, the second RACH procedure manager 630 is capable of, configured to, or operable to support components for executing a second RACH procedure based on a second preamble transmission counter value.

[0092] In some examples, the first PRACH power control parameter value corresponds to the first preamble power ramp counter value, and the RACH power control manager 640 is capable of, configured to, or operable to support components for setting the value of the power ramp variable to equal the first preamble power ramp counter value based on initiating a second RACH procedure.

[0093] In some examples, the RACH power control manager 640 is capable of, configured to, or operable to support components for initializing a second preamble power ramp counter associated with a second RACH process to a value of a power ramp variable. In some examples, to support components for performing a second RACH process based on one or more of a first number of RACH attempts or a first RACH power control parameter value, the second RACH process manager 630 is capable of, configured to, or operable to support components for performing a second RACH process based on a second preamble power ramp counter value.

[0094] Figure 7 A diagram of a system 700 including device 705 supporting a back-to-back RACH process, according to one or more aspects of this disclosure, is shown. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or may include components thereof. Device 705 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller (e.g., I / O controller 710), a transceiver 715, one or more antennas 725, at least one memory 730, code 735, and at least one processor 740. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 745).

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

[0096] In some cases, device 705 may include a single antenna. However, in other cases, device 705 may have more than one antenna, which can concurrently transmit or receive multiple wireless transmissions. Transceiver 715 may communicate bidirectionally via one or more antennas 725 using a wired or wireless link as described herein. For example, transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. Transceiver 715, or transceiver 715 and one or more antennas 725, may be an example of transmitter 415, transmitter 515, receiver 410, receiver 510, or any combination thereof or components thereof as described herein.

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

[0098] At least one processor 740 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also known as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 740 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 740. At least one processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., functions or tasks supporting back-to-back RACH processes). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, the at least one processor 740 and the at least one memory 730 being configured to perform the various functions described herein. In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 740 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 740) and memory circuitry (which may include at least one memory 730)) or components that receive or obtain input and process the input to produce, generate, or obtain output. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 740 or a processing system including at least one processor 740 may be configured, capable of being configured, or operable to cause device 705 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code 735 (e.g., processor-executable code) stored in at least one memory 730 or otherwise executing the code.

[0099] The communication manager 720 may support wireless communication according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for initiating a first RACH process associated with a first trigger, wherein the first RACH process is associated with a first number of RACH attempts and a first PRACH power control parameter value. The communication manager 720 may be capable of, configured to, or operable to support components for initiating a second RACH process after the initiation of the first RACH process, wherein the second RACH process is associated with a second trigger that is different from the first trigger (e.g., has a different trigger type from the first trigger). The communication manager 720 may be capable of, configured to, or operable to support components for performing a second RACH process based on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

[0100] By including or configuring a communication manager 720 according to an example as described herein, device 705 can support techniques for improving communication reliability, reducing latency, utilizing communication resources more efficiently, and improving coordination between devices.

[0101] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 715, one or more antennas 725, or any combination thereof, or otherwise cooperating with them. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or executed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions that can be executed by at least one processor 740 to cause device 705 to perform various aspects of the back-to-back RACH process as described herein, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.

[0102] Figure 8 A flowchart illustrating a method 800 supporting a back-to-back RACH procedure according to one or more aspects of this disclosure is shown. Operation of method 800 may be implemented by a UE or its components as described herein. For example, operation of method 800 may be performed by, as referenced... Figures 1 to 7 The UE 115 described herein 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 described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0103] At 805, the method may include initiating a first RACH procedure associated with a first trigger, wherein the first RACH procedure is associated with a first number of RACH attempts and a first PRACH power control parameter value. The operation of 805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 805 may be provided by reference to [reference needed]. Figure 6 The first RACH process manager 625 described herein is used to perform the execution. Additionally or alternatively, the components used to perform 805 may (but are not required to) include, for example, an antenna 725, a transceiver 715, a communication manager 720, a memory 730 (including code 735), a processor 740, and / or a bus 745.

[0104] At 810, the method may include initiating a second RACH process after the initiation of the first RACH process, wherein the second RACH process is associated with a second trigger that is different from the first trigger (e.g., has a different trigger type than the first trigger). The operation of 810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 810 may be derived from references... Figure 6 The second RACH process manager 630 described herein is used to perform the execution. Additionally or alternatively, the components used to perform 810 may (but are not required to) include, for example, an antenna 725, a transceiver 715, a communication manager 720, a memory 730 (including code 735), a processor 740, and / or a bus 745.

[0105] At 815, the method may include performing a second RACH process based on one or more of a first number of RACH attempts or a first PRACH power control parameter value. The operation of 815 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 815 may be provided by reference to [reference needed]. Figure 6 The second RACH process manager 630 described herein is used to perform the execution. Additionally or alternatively, the components used to perform 815 may (but are not required to) include, for example, an antenna 725, a transceiver 715, a communication manager 720, a memory 730 (including code 735), a processor 740, and / or a bus 745.

[0106] Figure 9 A flowchart illustrating a method 900 supporting a back-to-back RACH procedure according to one or more aspects of this disclosure is shown. Operation of method 900 may be implemented by a UE or its components as described herein. For example, operation of method 900 may be performed by, as referenced... Figures 1 to 7 The UE 115 described herein 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 described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0107] At 905, the method may include initiating a first RACH procedure associated with a first trigger, wherein the first RACH procedure is associated with a first number of RACH attempts and a first PRACH power control parameter value. The operation of 905 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 905 may be provided by reference to [reference needed]. Figure 6 The first RACH process manager 625 described herein is used to perform the execution. Additionally or alternatively, the components used to perform 905 may (but are not required to) include, for example, an antenna 725, a transceiver 715, a communication manager 720, a memory 730 (including code 735), a processor 740, and / or a bus 745.

[0108] At 910, the method may include initiating a second RACH process after the initiation of the first RACH process, wherein the second RACH process is associated with a second trigger that is different from the first trigger (e.g., has a different trigger type than the first trigger). The operation of 910 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 910 may be derived from references... Figure 6 The second RACH process manager 630 described herein is used to perform the operation. Additionally or alternatively, the components used to perform the operation 910 may (but are not required to) include, for example, an antenna 725, a transceiver 715, a communication manager 720, a memory 730 (including code 735), a processor 740, and / or a bus 745.

[0109] At 915, the method may include stopping the first RACH process based on initiating a second RACH process. Although in Figure 9 The examples are illustrated as occurring after the second RACH procedure is initiated, but it should be understood that the first RACH procedure may alternatively be stopped (e.g., interrupted, terminated) before the second RACH procedure is initiated (e.g., based on the second trigger being received by UE 115, identified by UE 115, or occurring) or stopped concurrently with the initiation of the second RACH procedure (e.g., interrupted, terminated). The operation of 915 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 915 may be derived from references... Figure 6 The first RACH process manager 625 described herein is used to perform the execution. Additionally or alternatively, the components used to perform 915 may (but are not required to) include, for example, an antenna 725, a transceiver 715, a communication manager 720, a memory 730 (including code 735), a processor 740, and / or a bus 745.

[0110] At 920, the method may include performing a second RACH process based on one or more of a first number of RACH attempts or a first PRACH power control parameter value. The operation of 920 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 920 may be provided by reference to [reference needed]. Figure 6 The second RACH process manager 630 described herein is used to perform the operation. Additionally or alternatively, the components used to perform the operation 920 may (but are not required to) include, for example, an antenna 725, a transceiver 715, a communication manager 720, a memory 730 (including code 735), a processor 740, and / or a bus 745.

[0111] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication by a UE, the method comprising: initiating a first RACH procedure associated with a first trigger, wherein the first RACH procedure is associated with a first number of RACH attempts and a first physical random access channel (PRACH) power control parameter value; initiating a second RACH procedure after the initiation of the first RACH procedure, wherein the second RACH procedure is associated with a second trigger different from the first trigger; and performing the second RACH procedure based at least in part on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

[0112] Aspect 2: According to the method of aspect 1, the method further includes: stopping the first RACH process at least in part based on initiating the second RACH process.

[0113] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: initializing one or more of a second number of RACH attempts associated with the second RACH process to the first number of RACH attempts; and initializing a second PRACH power control parameter value associated with the second RACH process to the first PRACH power control parameter value, wherein performing the second RACH process based at least in part on one or more of the first number of RACH attempts or the first PRACH power control parameter value includes performing the second RACH process based at least in part on one or more of the second number of RACH attempts and the second PRACH power control parameter value.

[0114] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: saving one or more of the first number of RACH attempts and the first PRACH power control parameter value based at least in part on initiating the second RACH procedure.

[0115] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the first number of RACH attempts corresponds to a first preamble transmission counter value, the method further comprising: setting the value of a variable associated with the number of RACH messages aborted to equal the first preamble transmission counter value, at least in part based on initiating the second RACH procedure.

[0116] Aspect 6: The method according to aspect 5, the method further comprising: initializing a second preamble transmission counter associated with the second RACH procedure to the value of the variable associated with the number of aborted RACH messages, wherein performing the second RACH procedure based at least in part on one or more of the first number of RACH attempts or the first PRACH power control parameter value includes performing the second RACH procedure based at least in part on the second preamble transmission counter value.

[0117] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the first PRACH power control parameter value corresponds to the first preamble power ramp counter value, the method further comprising: setting the value of the power ramp variable to be equal to the first preamble power ramp counter value based at least in part on initiating the second RACH procedure.

[0118] Aspect 8: The method according to aspect 7, the method further comprising: initializing a second preamble power ramp counter associated with the second RACH process to the value of the power ramp variable, wherein performing the second RACH process based at least in part on one or more of the first number of RACH attempts or the first PRACH power control parameter value includes performing the second RACH process based at least in part on the value of the second preamble power ramp counter.

[0119] Aspect 9: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 8.

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

[0121] Aspect 11: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of Aspects 1 to 8.

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

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

[0124] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0125] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, graphics processing unit (GPU), neural processing unit (NPU), FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternatives, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

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

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

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

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

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

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

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

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

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Initiate a first random access channel (RACH) procedure associated with a first trigger, wherein the first RACH procedure is associated with a first number of RACH attempts and a first physical random access channel (PRACH) power control parameter value; A second RACH process is initiated after the first RACH process is initiated, wherein the second RACH process is associated with a second trigger that is different from the first trigger; as well as The second RACH process is performed at least in part based on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

2. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The first RACH process is stopped, at least in part, based on initiating the second RACH process.

3. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The second number of RACH attempts associated with the second RACH process is initialized to the first number of RACH attempts; and The second PRACH power control parameter value associated with the second RACH process is initialized to the first PRACH power control parameter value. in, In order to perform the second RACH procedure at least in part based on one or more of the first number of RACH attempts or the first PRACH power control parameter value, the one or more processors are also capable of operating individually or jointly to execute the code so that the UE performs the second RACH procedure at least in part based on one or more of the second number of RACH attempts and the second PRACH power control parameter value.

4. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The first number of RACH attempts and the first PRACH power control parameter value are saved at least in part based on initiating the second RACH procedure.

5. The UE of claim 1, wherein the first number of RACH attempts corresponds to a first preamble transmission counter value, and wherein the one or more processors are also capable of operating individually or jointly to execute the code to cause the UE to: At least in part, the value of a variable associated with the number of aborted RACH messages is set to equal the value of the first preamble transmission counter, based on initiating the second RACH procedure.

6. The UE of claim 5, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The second preamble transmission counter associated with the second RACH procedure is initialized to the value of the variable associated with the number of RACH messages that were aborted. in, In order to perform the second RACH procedure at least in part based on one or more of the first number of RACH attempts or the first PRACH power control parameter value, the one or more processors are also capable of operating individually or jointly to execute the code so that the UE performs the second RACH procedure at least in part based on the second preamble transmission counter value.

7. The UE of claim 1, wherein the first PRACH power control parameter value corresponds to the first preamble power ramp counter value, and wherein the one or more processors are also capable of operating individually or jointly to execute the code to cause the UE to: The value of the power ramp variable is set to be equal to the value of the first preamble power ramp counter, at least in part, based on initiating the second RACH procedure.

8. The UE of claim 7, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The second preamble power ramp counter associated with the second RACH process is initialized to the value of the power ramp variable. in, In order to perform the second RACH procedure at least in part based on one or more of the first number of RACH attempts or the first PRACH power control parameter value, the one or more processors are also capable of operating individually or jointly to execute the code so that the UE performs the second RACH procedure at least in part based on the second preamble power ramp counter value.

9. A method for wireless communication by a user equipment (UE), the method comprising: Initiate a first random access channel (RACH) procedure associated with a first trigger, wherein the first RACH procedure is associated with a first number of RACH attempts and a first physical random access channel (PRACH) power control parameter value; A second RACH process is initiated after the first RACH process is initiated, wherein the second RACH process is associated with a second trigger that is different from the first trigger; as well as The second RACH process is performed at least in part based on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

10. The method according to claim 9, further comprising: The first RACH process is stopped, at least in part, based on initiating the second RACH process.

11. The method according to claim 9, further comprising: The second number of RACH attempts associated with the second RACH process is initialized to the first number of RACH attempts; as well as The second PRACH power control parameter value associated with the second RACH process is initialized to the first PRACH power control parameter value. The second RACH process is performed based at least in part on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

12. The method according to claim 9, further comprising: The first number of RACH attempts and the first PRACH power control parameter value are saved at least in part based on initiating the second RACH procedure.

13. The method of claim 9, wherein the first number of RACH attempts corresponds to a first preamble transmission counter value, the method further comprising: At least in part, the value of a variable associated with the number of aborted RACH messages is set to equal the value of the first preamble transmission counter, based on initiating the second RACH procedure.

14. The method according to claim 13, further comprising: The second preamble transmission counter associated with the second RACH procedure is initialized to the value of the variable associated with the number of RACH messages that were aborted. The second RACH process is performed based at least in part on one or more of the first number of RACH attempts or the first PRACH power control parameter value, including performing the second RACH process based at least in part on the second preamble transmission counter value.

15. The method of claim 9, wherein the first PRACH power control parameter value corresponds to the first preamble power ramp counter value, the method further comprising: The value of the power ramp variable is set to be equal to the value of the first preamble power ramp counter, at least in part, based on initiating the second RACH procedure.

16. The method according to claim 15, further comprising: The second preamble power ramp counter associated with the second RACH process is initialized to the value of the power ramp variable. The second RACH process is performed based at least in part on one or more of the first number of RACH attempts or the first PRACH power control parameter value, including performing the second RACH process based at least in part on the second preamble power ramp counter value.

17. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to: Initiate a first random access channel (RACH) procedure associated with a first trigger, wherein the first RACH procedure is associated with a first number of RACH attempts and a first physical random access channel (PRACH) power control parameter value; A second RACH procedure is initiated after the first RACH procedure is initiated, wherein the second RACH procedure is associated with a second trigger different from the first trigger; and The second RACH process is performed at least in part based on one or more of the first number of RACH attempts or the first PRACH power control parameter value.

18. The non-transitory computer-readable medium of claim 17, wherein the instructions are further executable by the one or more processors to: The first RACH process is stopped, at least in part, based on initiating the second RACH process.

19. The non-transitory computer-readable medium of claim 17, wherein the instructions are further executable by the one or more processors to: Initialize one or more of the second number of RACH attempts associated with the second RACH process to the first number of RACH attempts; and The second PRACH power control parameter value associated with the second RACH process is initialized to the first PRACH power control parameter value. in, In order to perform the second RACH process based at least in part on one or more of the first number of RACH attempts or the first PRACH power control parameter value, the instructions are executable by the one or more processors to perform the second RACH process based at least in part on one or more of the second number of RACH attempts and the second PRACH power control parameter value.

20. The non-transitory computer-readable medium of claim 17, wherein the instructions are further executable by the one or more processors to: The first number of RACH attempts and the first PRACH power control parameter value are saved at least in part based on initiating the second RACH procedure.

Images