Systems, methods, and devices for RACH transmission with adaptation

Adaptive RACH transmission enables UEs to select the most suitable beam for synchronization, addressing inefficiencies in RACH processes by optimizing beam selection based on real-time measurements, thereby reducing latency and failure rates.

WO2026072389A1PCT designated stage Publication Date: 2026-04-02APPLE INC
View PDF 2 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-09-16
Publication Date
2026-04-02

AI Technical Summary

Technical Problem

Existing wireless communication systems face inefficiencies in random access channel (RACH) transmissions due to outdated beam indications during handover, leading to unnecessary RACH transmissions and potential failures when user equipment (UE) moves relative to the target base station, resulting in suboptimal synchronization.

Method used

Implementing RACH transmission with adaptation by allowing the UE to determine the most suitable beam based on real-time measurements, rather than relying solely on the serving base station's indication, through adaptive RACH information and configuration.

Benefits of technology

This approach reduces unnecessary RACH transmissions and improves synchronization efficiency by ensuring the UE performs RACH via the optimal beam, minimizing latency and failure rates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2025046625_02042026_PF_FP_ABST
    Figure US2025046625_02042026_PF_FP_ABST
Patent Text Reader

Abstract

The techniques described herein can include solutions for random access channel (RACH) transmission with adaptation. The UE can indicate measurements of synchronization signal blocks (SSBs) of beams of the target base station to a serving base station. The serving base station can select an optimal SSB and associated beam based on the measurements and trigger the UE to perform RACH transmission via the selected beam. The UE can determine whether to perform RACH transmission with adaptation by comparing current SSB measurements to the SSB indicated by the serving base station. If the optimal SSB is an SSB other than the SSB selected by the serving base station, the UE can perform RACH transmission with adaptation by transmitting the RACH transmission via a beam other than the beam associated with the SSB indicated by the serving base station.
Need to check novelty before this filing date? Find Prior Art

Description

Attorney Docket No.: 106842241640 (P68963WO1)SYSTEMS, METHODS, AND DEVICES FOR RACH TRANSMISSION WITH ADAPTATIONCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 700,547, filed September 27, 2024, the content of which is herein incorporated by reference in its entirety for all purposes.FIELD

[0002] This disclosure relates to wireless communication networks and mobile device capabilities.BACKGROUND

[0003] Wireless communication networks and wireless communication services are becoming increasingly dynamic, complex, and ubiquitous. For example, some wireless communication networks can be developed to implement fourth generation (4G), fifth generation (5G) or new radio (NR) technology. Such technology can include solutions for random access channel (RACH) transmissions between one or more entities, such as user equipments (UEs) and base stations.BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The present disclosure will be readily understood and enabled by the detailed description and accompanying figures of the drawings. Like reference numerals can designate like features and structural elements. Figures and corresponding descriptions are provided as non-limiting examples of aspects, implementations, etc., of the present disclosure, and references to "an" or “one” aspect, implementation, etc., may not necessarily refer to the same aspect, implementation, etc., and can mean at least one, one or more, etc.

[0005] Figure l is a diagram of an example of an overview according to one or more implementations described herein.

[0006] Figure 2 is a diagram of an example network according to one or more implementations described herein.

[0007] Figure 3 is a diagram of an example of RACH transmission with adaptation according to one or more implementations described herein.

[0008] Figure 4 is a diagram of an example process of RACH transmission with adaptation according to one or more implementations described herein.14932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)

[0009] Figure 5 is a diagram of an example of components of a device according to one or more implementations described herein.

[0010] Figure 6 is a diagram of example interfaces of baseband circuitry according to one or more implementations described herein.

[0011] Figure 7 is a block diagram illustrating components, according to one or more implementations described herein, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

[0012] Figure 8 is a diagram of an example process for RACH transmission with adaptation according to one or more implementations described herein.

[0013] Figure 9 is a diagram of an example process for RACH transmission with adaptation according to one or more implementations described herein.

[0014] Figure 10 is a diagram of an example process for RACH transmission with adaptation according to one or more implementations described herein.DETAILED DESCRIPTION

[0015] The following detailed description refers to the accompanying drawings. Like reference numbers in different drawings can identify the same or similar features, elements, operations, etc. Additionally, the present disclosure is not limited to the following description as other implementations can be utilized, and structural or logical changes made, without departing from the scope of the present disclosure.

[0016] Telecommunication networks can include user equipment (UEs) capable of communicating with base stations and / or other network access nodes. UEs and base stations can implement various techniques and communications standards for enabling UEs and base stations to discover one another, establish and maintain connectivity, and exchange information in an ongoing manner. Objectives of such techniques can include improving efficiency of random access channel (RACH) transmissions initiated by a base station via RACH transmission with adaptation.

[0017] A UE can connect to a network device, such as a base station, via a RACH process, where the UE and base station exchange messages to confirm and establish a connection for future communications. In some examples, a portion of a RACH process can be implemented to synchronize communications between the UE and base station. For example, the UE can transmit a RACH message to a base station for measuring timing differences between transmission and reception of messages. The determined timing24932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) difference can be used to adjust future communications.

[0018] In some examples, the base station can use a PDCCH order message to synchronize communications prior to handover. During handover, the UE switches communications from the current base station (e.g., serving base station) to a different base station (e.g., target base station). Prior to handover, the serving base station can indicate a PDCCH order message to trigger the UE to perform a RACH transmission, which can be used to synchronize communications with the target base station. The PDCCH order can include an indication of which beam of the target base station to use for synchronization, and the UE can perform a RACH transmission via the indicated beam of the target base station.

[0019] However, in some examples, conditions can change, resulting in the PDCCH order message indicating an outdated beam. In such examples, the UE can perform a RACH transmission unnecessarily. For example, the UE can change positions relative to the target base station, such that the beam associated with the strongest signal is no longer the beam indicated by the serving base station.

[0020] One or more of the techniques described herein address the foregoing deficiencies by providing solutions for unnecessary RACH transmissions. For example, the UE can be configured with RACH transmission with adaptation. RACH transmission with adaptation can include the UE determining whether to perform RACH transmission via the beam indicated by the serving base station. For example, the UE can compare measurements of multiple beams and perform a RACH transmission to connect with the target base station via the most suitable beam (e.g., optimal), such as the beam associated with the greatest signal strength, which may or may not be the beam indicated by the serving base station.

[0021] Figure 1 is a diagram of an example of an overview 100 according to one or more implementations described herein. Serving base station 120-1 (e.g., network entity, source base station, base station), an example of a base station with an established connection with UE 110, can communicate with UE 110 via serving beam 130. For example, serving base station 120-1 can indicate adaptive RACH information 150 to UE 110 based on the UE 110 being capable of supporting RACH transmission with adaptation (e.g., RACH with adaptation, RACH procedure with adaptation, PRACH transmission with adaptation). Adaptive RACH information 150 can include an indication as to whether UE 110 can perform RACH with adaptation, indication of which RACH adaptations are enabled, and parameters for UE 110 to use to determine whether to perform RACH with adaption. In some examples, adaptive RACH information 150 can be a configuration transmitted from serving base station 120-1 to UE 110 prior to UE 110 performing measurements. In some examples,34932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) adaptive RACH information 150 can be included as part of RACH order signaling.

[0022] UE 110 can perform various measurements associated with one or more synchronization signal blocks (SSBs) of target base station 120-2 (e.g., neighboring base station, candidate base station, base station, network entity). Each SSB can be transmitted (e.g., indicated, communicated) to UE 110 via beam 140. For example, SSB1 can be transmitted (and received) via beam 140-1, SSB2 can be transmitted via beam 140-2, and SSB3 can be indicated via beam 140-3. SSB measurements can include signal strength, such as reference signal received power (RSRP), among other measurements. UE 110 can report the measurements of SSB 1, SSB2, and SSB3 to serving base station 120-1 via a report, such as a layer 1 (LI) measurement report.

[0023] Serving base station 120-1 can trigger synchronization (e.g., uplink synchronization) of UE 110 with another entity, such as target base station 120-2, based on the measurement report from UE 110. In some examples, serving base station 120-1 can trigger synchronization by transmitting a PDCCH order message to UE 110 via layer 1 / layer 2 (L1 / L2). The PDCCH order can trigger UE 210 to transmit a RACH transmission to target base station 120-2 via beam 140 selcted by serving base station 120-1. For example, serving base station 120-1 can determine which beam 140 is the most suitable based on the measurement report from UE 110, and indicate the selected beam 140 to UE 110 as part of the PDCCH order. For example, the measurements report can indicate that SSB2 has the strongest signal, and serving base station 120-1 can indicate to UE 110 to use beam 140-2 to perform the RACH transmission (e.g., RACH procedure).

[0024] UE 110 can determine whether or not to perform RACH with adaptation (e.g., adaptive RACH transmission, adaptative RACH procedure) according to adaptive RACH information 160. UE 210 can determine whether RACH with adaptation is enabled, as indicated by adaptive RACH information 160. If enabled, UE 210 can determine whether to perform RACH with adaptation based on parameters indicated as part of adaptive RACH information 160. For example, adaptive RACH information 160 can enable UE 110 to perform RACH via the most suitable beam 140 which may or may not be beam 140-2 indicated by serving base station 120-1.

[0025] UE 210 can compare current SSB measurements to determine which beam 140 is the most suitable. For example, UE 210 can determine that beam 140-2, as indicated by serving base station 120-1, is still the most suitable and has the strongest signal strength, and can perform RACH via beam 140-2. In some examples, UE 210 can determine that beam 140-2 no longer is the most suitable beam, and can perform RACH with adaptation by44932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) transmitting a RACH message via a beam 140 other than beam 140-2 indicated by serving base station 120-1. In some examples, the RACH transmission can be the first message (e.g., message 1) of a RACH procedure. In some examples, the RACH transmission can be a physical random access channel (PRACH) transmission.

[0026] Figure 2 is an example network 200 according to one or more implementations described herein. Example network 200 can include UEs 210, 210-2, etc. (referred to collectively as “UEs 210” and individually as “UE 210”), a radio access network (RAN) 220, a core network (CN) 230, application servers 240, and external networks 250.

[0027] The systems and devices of example network 200 can operate in accordance with one or more communication standards, such as 2nd generation (2G), 3rd generation (3G), 4th generation (4G) (e.g., long-term evolution (LEE)), and / or 5th generation (5G) (e.g., new radio (NR)) communication standards of the 3rd generation partnership project (3GPP). Additionally, or alternatively, one or more of the systems and devices of example network 200 can operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc.), institute of electrical and electronics engineers (IEEE) standards (e.g., wireless metropolitan area network (WMAN), worldwide interoperability for microwave access (WiMAX), etc.), and more.

[0028] As shown, UEs 210 can include smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more wireless communication networks).Additionally, or alternatively, UEs 210 can include other types of mobile or non-mobile computing devices capable of wireless communications, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, etc. In some implementations, UEs 210 can include internet of things (loT) devices (or loT UEs) that can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections. Additionally, or alternatively, an loT UE can utilize one or more types of technologies, such as machine-to-machine (M2M) communications or machine-type communications (MTC) (e.g., to exchanging data with an MTC server or other device via a public land mobile network (PLMN)), proximity-based service (ProSe) or device-to-device (D2D) communications, sensor networks, loT networks, and more. Depending on the scenario, an M2M or MTC exchange of data can be a machine-initiated exchange, and an loT network can include interconnecting loT UEs (which can include uniquely identifiable embedded computing devices within an Internet infrastructure) with short-lived connections.54932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)In some scenarios, loT UEs can execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.

[0029] UEs 210 can communicate and establish a connection with one or more other UEs 210 via one or more wireless channels 212, each of which can comprise a physical communications interface / layer. The connection can include an M2M connection, MTC connection, D2D connection, sidelink (SL) connection, etc. The connection can involve a PC5 interface. In some implementations, UEs 210 can be configured to discover one another, negotiate wireless resources between one another, and establish connections between one another, without intervention or communications involving RAN node 222 or another type of network node. In some implementations, discovery, authentication, resource negotiation, registration, etc., can involve communications with RAN node 222 or another type of network node.

[0030] As described herein, UE 210 can communicate with RAN node 222 to request SL resources. RAN node 222 can respond to the request by providing UE 210 with a dynamic grant (DG) or configured grant (CG) regarding SL resources. A DG can involve a grant based on a grant request from UE 210. A CG can involve a resource grant without a grant request and can be based on a type of service being provided (e.g., services that have strict timing or latency requirements). UE 210 can perform a clear channel assessment (CCA) procedure based on the DG or CG, select SL resources based on the CCA procedure and the DG or CG; and communicate with another UE 210 based on the SL resources. The UE 210 can communicate with RAN node 222 using a licensed frequency band and communicate with the other UE 210 using an unlicensed frequency band.

[0031] UEs 210 can communicate and establish a connection with (e.g., be communicatively coupled) with RAN 220, which can involve one or more wireless channels 214-1 and 214-2, each of which can comprise a physical communications interface / layer. In some implementations, a UE can be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC), where a multiple receive and transmit (Rx / Tx) capable UE can use resources provided by different RAN network nodes (e.g., RAN network nodes 222-1 and 222-2) that can be connected via nonideal backhaul (e.g., where one network node provides NR access and the other network node provides either E-UTRA for LTE or NR access for 5G). In such a scenario, one network node can operate as a master node (MN) and the other as the secondary node (SN). The MN and SN can be connected via a network interface, and at least the MN can be connected to the CN 230. Additionally, at least one of the MN or the SN can be operated with shared spectrum64932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) channel access, and functions specified for UE 210 can be used for an integrated access and backhaul mobile termination (IAB-MT). Similar for UE 210, the IAB-MT can access the network using either one network node or using two different nodes with enhanced dual connectivity (EN-DC) architectures, new radio dual connectivity (NR-DC) architectures, or the like. In some implementations, a base station (as described herein) can be an example of network RAN network nodes.

[0032] As shown, UE 210 can also, or alternatively, connect to access point (AP) 216 via connection interface 218, which can include an air interface enabling UE 210 to communicatively couple with AP 216. AP 216 can comprise a wireless local area network (WLAN), WLAN node, WLAN termination point, etc. The connection interface 218 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, and AP 216 can comprise a wireless fidelity (Wi-Fi®) router or other AP. While not explicitly depicted in Fig. 2, AP 216 can be connected to another network (e.g., the Internet) without connecting to RAN 220 or CN 230. In some scenarios, UE 210, RAN 220, and AP 216 can be configured to utilize LTE-WLAN aggregation (LWA) techniques or LTE WLAN radio level integration with IPsec tunnel (LWIP) techniques. LWA can involve UE 210 in RRC CONNECTED being configured by RAN 220 to utilize radio resources of LTE and WLAN. LWIP can involve UE 210 using WLAN radio resources (e.g., connection interface 218) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) communicated via connection interface 218. IPsec tunneling can include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

[0033] RAN 220 can include one or more RAN nodes 222-1 and 222-2 (referred to collectively as RAN nodes 222, and individually as RAN node 222) that enable channels 214-1 and 214-2 to be established between UEs 210 and RAN 220. A RAN node 222 can be a base station and may be referred to herein as base station 222. RAN nodes 222 can include network access points configured to provide radio baseband functions for data and / or voice connectivity between users and the network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi®, etc.). As examples therefore, a RAN node can be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc.), a next generation base station (e.g., a 5G base station, NR base station, next generation eNBs (gNB), etc.). RAN nodes 222 can include a roadside unit (RSU), a transmission reception point (TRxP or TRP), and one or more other types of ground stations (e.g., terrestrial access points). In some scenarios, RAN node 222 can be a dedicated physical74932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) device, such as a macrocell base station, and / or a low power (LP) base station for providing femtocells, picocells or the like having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0034] Some or all of RAN nodes 222, or portions thereof, can be implemented as one or more software entities running on server computers as part of a virtual network, which can be referred to as a centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In these implementations, the CRAN or vBBUP can implement a RAN function split, such as a packet data convergence protocol (PDCP) split wherein radio resource control (RRC) and PDCP layers can be operated by the CRAN / vBBUP and other Layer 2 (L2) protocol entities can be operated by individual RAN nodes 222; a media access control (MAC) / physical (PHY) layer split wherein RRC, PDCP, radio link control (RLC), and MAC layers can be operated by the CRAN / vBBUP and the PHY layer can be operated by individual RAN nodes 222; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer can be operated by the CRAN / vBBUP and lower portions of the PHY layer can be operated by individual RAN nodes 222. This virtualized framework can allow freed- up processor cores of RAN nodes 222 to perform or execute other virtualized applications.

[0035] In some implementations, an individual RAN node 222 can represent individual gNB-distributed units (DUs) connected to a gNB-control unit (CU) via individual Fl or other interfaces. In such implementations, the gNB-DUs can include one or more remote radio heads or radio frequency (RF) front end modules (RFEMs), and the gNB-CU can be operated by a server (not shown) located in RAN 220 or by a server pool (e.g., a group of servers configured to share resources) in a similar manner as the CRAN / vBBUP. Additionally, or alternatively, one or more of RAN nodes 222 can be next generation eNBs (i.e., gNBs) that can provide evolved universal terrestrial radio access (E-UTRA) user plane and control plane protocol terminations toward UEs 210, and that can be connected to a 5G core network (5GC) 230 via an NG interface.

[0036] Any of the RAN nodes 222 can terminate an air interface protocol and can be the first point of contact for UEs 210. In some implementations, any of the RAN nodes 222 can fulfill various logical functions for the RAN 220 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. UEs 210 can be configured to communicate using orthogonal frequency-division multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 222 over a multicarrier communication channel in accordance with various communication techniques,84932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a single carrier frequency-division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink (SL) communications), although the scope of such implementations may not be limited in this regard. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0037] In some implementations, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 222 to UEs 210, and uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid (e.g., a resource grid or time-frequency resource grid) that represents the physical resource for downlink in each slot. Such a time-frequency plane representation can be a common practice for OFDM systems, which can make it intuitive for radio resource allocation. Each column and each row of the resource grid can correspond to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block can comprise a collection of resource elements (REs); in the frequency domain, this can represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[0038] Further, RAN nodes 222 can be configured to wirelessly communicate with UEs 210, and / or one another, over a licensed medium (also referred to as the “licensed spectrum” and / or the “licensed band”), an unlicensed shared medium (also referred to as the “unlicensed spectrum” and / or the “unlicensed band”), or combination thereof. A licensed spectrum can correspond to channels or frequency bands selected, reserved, regulated, etc., for certain types of wireless activity (e.g., wireless telecommunication network activity), whereas an unlicensed spectrum can correspond to one or more frequency bands that are not restricted for certain types of wireless activity. Whether a particular frequency band corresponds to a licensed medium or an unlicensed medium can depend on one or more factors, such as frequency allocations determined by a public-sector organization (e.g., a government agency, regulatory body, etc.) or frequency allocations determined by a private-sector organization involved in developing wireless communication standards and protocols, etc.

[0039] The PDSCH can carry user data and higher layer signaling to UEs 210. The physical downlink control channel (PDCCH) can carry information about the transport format and resource allocations related to the PDSCH channel, among other things. The94932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)PDCCH can also inform UEs 210 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (e.g., assigning control and shared channel resource blocks to UE 210 within a cell) can be performed at any of the RAN nodes 222 based on channel quality information fed back from any of UEs 210. The downlink resource assignment information can be sent on the PDCCH used for (e.g., assigned to) each of UEs 210.

[0040] One or more of the techniques, described herein, can enable UE 210 to perform RACH transmission with adaptation (e.g., RACH with adaptation). A serving base station 222 can transmit a PDCCH order to UE 210 to trigger UE 210 to indicate a RACH transmission to a target base station 222 via a beam indicated in the PDCCH order. UE 210 can compare SSB measurements of SSBs of a target base station 222 to determine which is the most suitable for synchronization. UE 210 can perform a RACH transmission via the most suitable beam, which can be different than a beam indicated by serving base station 222. In this way, UE 210 can adapt to changing conditions and perform RACH transmissions using the most suitable beams. These and many other features and aspects of the techniques described herein are presented below with reference to remaining Figures.

[0041] The RAN nodes 222 can be configured to communicate with one another via interface 223. In implementations where the system is an LTE system, interface 223 can be an X2 interface. In NR systems, interface 223 can be an Xn interface. The X2 interface can be defined between two or more RAN nodes 222 (e.g., two or more eNBs / gNBs or a combination thereof) that connect to evolved packet core (EPC) or CN 230, or between two eNBs connecting to an EPC. The RAN nodes 222 can be configured to communicate with the CN 230 via various interfaces, such as physical interfaces, including interface 224, interface 226, and interface 228.

[0042] In some implementations, the X2 interface can include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U can provide flow control mechanisms for user data packets transferred over the X2 interface and can be used to communicate information about the delivery of user data between eNBs or gNBs. For example, the X2-U can provide specific sequence number information for user data transferred from a master eNB (MeNB) to a secondary eNB (SeNB); information about successful in sequence delivery of PDCP packet data units (PDUs) to a UE 210 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 210; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like. The X2-C can provide intra-LTE access mobility functionality104932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)(e.g., including context transfers from source to target eNBs, user plane transport control, etc.), load management functionality, and inter-cell interference coordination functionality.

[0043] As shown, RAN 220 can be connected (e.g., communicatively coupled) to CN 230. CN 230 can comprise a plurality of network elements 232, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UEs 210) who are connected to the CN 230 via the RAN 220. In some implementations, CN 230 can include an evolved packet core (EPC), a 5G CN, and / or one or more additional or alternative types of CNs. The components of the CN 230 can be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some implementations, network function virtualization (NFV) can be utilized to virtualize any or all the above-described network node roles or functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below). A logical instantiation of the CN 230 can be referred to as a network slice, and a logical instantiation of a portion of the CN 230 can be referred to as a network sub-slice. Network Function Virtualization (NFV) architectures and infrastructures can be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components / functions.

[0044] As shown, CN 230, application servers 240, and external networks 250 can be connected to one another via interfaces 234, 236, and 238, which can include IP network interfaces. Application servers 240 can include one or more server devices or network elements (e.g., virtual network functions (VNFs) offering applications that use IP bearer resources with CN 230 (e.g., universal mobile telecommunications system packet services (UMTS PS) domain, LTE PS data services, etc.). Application servers 240 can also, or alternatively, be configured to support one or more communication services (e.g., voice over IP (VoIP) sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc.) for UEs 210 via the CN 230. Similarly, external networks 250 can include one or more of a variety of networks, including the Internet, thereby providing the mobile communication network and UEs 210 of the network access to a variety of additional services, information, interconnectivity, and other network features.

[0045] Figure 3 is a diagram of an example of RACH transmission with adaptation according to one or more implementations described herein. Fig. 3 is an example of114932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) communications between UE 210 and target base station 222-2 at time 1 and at time 2. For example, UE 210 can receive a PDCCH order from serving base station 222-1 and implement RACH with adaptation (e.g., adaptive RACH, RACH message, RACH transmission) to synchronize communications with target base station 222-2.

[0046] In some examples, UE 210 can perform a handover procedure. For example, UE 210 can perform a layer l(Ll) / layer 2 (L2) triggered inter-cell mobility (LTM) procedure, where UE 210 transfers communications from serving base station 222-1 to target base station 222-2. LTM can include indicating one or more measurement reports to serving base station 222-1, performing uplink synchronization with target base station 222-2, receiving a cell switch command from serving base station 222-1, establishing a connection with target base station 222-2 based on the cell switch command, and detaching from serving base station 222-2. Prior to receiving the cell switch command and switching base stations 222, UE 210 can perform uplink synchronization with target base station 222-2 (e.g., LTM candidate cell).

[0047] Uplink synchronization can include performing one or more measurements of one or more SSBs, transmitting the measurements to serving base station 222-1 via a measurement report, and receiving a PDCCH order from serving base station 222-1. The PDCCH order can include an index of an SSB associated with a beam 140 for UE 110 to use to perform a RACH transmission to facilitate synchronization with target base station 222-2.

[0048] Part of uplink synchronization can include UE 210 performing one or more measurements associated with SSBs (e.g., candidate SSBs) transmitted by target base station 222-2 and indicating the measurements to serving base station 22-1 via a report (e.g., LI measurement report). Each SSB can be transmitted via the respective beam 140. Base station 222-2 can use the report to determine which SSB, and associated beam, to indicate to UE 210 via the PDCCH order. However, latency can occur between the time UE 210 sends the measurement report and the time UE 210 receives the PDDCCH order.

[0049] Latency can be due to the length of the measurement period of the target base station 222-2, as UE 210 can be configured to measure multiple SSBs, which may include SSBs of other base stations 222 in addition to target base station 222-2. UE 210 can measure one SSB at a time (such as when supporting a round trip delay that is greater than the cyclic prefix and gap-based LI measurements), and rotates between SSBs. Thus, UE 210 can measure SSB1, and when finished, measure SSB2, etc.

[0050] UE 210 can indicate all measurements of SSBs in a single report, such that the measurement of the first measured SSB1 are older than the SSBs measured closer to the time124932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) of transmitting the report. The latency between measurement and transmission of the report can create differences between current conditions and measurements received by serving base station 222-1. UE 210 continues to measure SSBs after transmitting the report, such that when UE 210 receives the PDCCH order, UE 210 can have updated measurements that have not yet been indicated to serving base station 222-1. In some examples, measurement reporting can be periodic / semi-periodic, resulting in the newest measurements not being reported to serving base station 222-1 prior to receiving the PDCCH order.

[0051] In some examples, latency can be due to delayed indication of the PDCCH order. For example, serving base station 222-1 can receive the report from UE 210, and perform other transmissions prior to indicating the PDCCH order, such as triggering transmission configuration index (TCI) activation. In some examples, serving base station 222-1 can trigger PDCCH for multiple UEs 210 and associated target base stations 222-2 at one time. In some examples, latency can be a result of an interrupted PDCCH order.

[0052] Latency can result in the most suitable beam 140 being a different beam 140 than that indicated by serving base station 222-1. For example, UE 210 can move between the time UE 210 sends the measurement report and the time UE 210 receives the PDDCCH order. For example, UE 210 can be at a first positions at time 1, and a second position at time 2. During time 1, beam 140-2 can be the most suitable beam (e.g., beam with the strongest signal strength). At time 2, beam 140-1 can be the most suitable beam. The delay between measurement reporting and PDCCH order can result in UE 210 receiving instruction to perform a RACH transmission via a beam 140 that is no longer the most suitable beam 140.

[0053] In some examples, performing a RACH transmission, or portion of a RACH transmission, via a beam 140 that is not the most suitable beam 140 (e.g., optimal) can result in a failed RACH transmission, additional latency, or both. For example, UE 210 can indicate the RACH transmission (e.g., message), and target base station 222-2 may not indicate whether or not the message was successfully received. Thus, UE 210 may not be aware of the success of the RACH transmission. Rather, target base station 222-2 can indicate a timing advance (TA) to serving base station 222-1 to synchronize communications. However, if target base station 222-2 does not receive the RACH message, such as because the beam 140 used by UE 210 is no longer suitable, target base station 222-2 may not be able to indicate the TA to serving base station 222-1. After a period of time, target base station 222-2 can send another PDCCH order to UE 210. Failed RACH messages can result in delayed RACH transmissions and LTM procedures.

[0054] In order to prevent latency, UE 210 can perform RACH with adaptation. At time134932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)1, Prior to performing measurements, UE 210 can indicate an adaptive RACH capability to serving base station 222-1 (at 310). The adaptive RACH capability can indicate whether UE 210 has the capability to perform RACH with adaptation.

[0055] In response to receiving the indication that UE 210 is capable of supporting RACH with adaptation, serving base station 222-1 can configure UE 210 with adaptive RACH configuration 222-1 (at 320). Adaptive RACH configuration can include multiple candidate RACH configurations for UE 210. The configurations can include performing RACH (e.g., contention-free RACH (CFRA)) via a beam 140 other than the beam 140 indicated via the PDCCH order and performing contention-based RACH (CBRA).

[0056] Adaptive RACH configuration can include conditions for performing RACH with adaptation. For example, UE 210 can perform RACH with adaptation when measurements exceed a threshold, or based on measurements of SSBs relative to other SSBs. For example, UE 210 can perform RACH transmissions via a different beam 140 if the measurements of the associated SSB exceed a threshold.

[0057] UE 210 can perform one or more measurements of one or more SSBs (at 330). Measurements can include reference signal received power (RSRP), as well as other measurements that indicate signal strength and beam suitability. UE 210 can indicate the measurements to serving base station 222-1 (at 340). After sending the report at time 1, UE 210 can change positions, or move.

[0058] At time 2, when UE 210 has changed position, serving base station 222-1 can select beam 140 based on the report from UE 210. For example, serving base station 222-1 can select beam 140-2 based on the measurements of the report of SSB2 indicating the highest signal strength. Serving base station 222-1 can indicate for UE 210 to perform RACH transmission via beam 140-2 (e.g., using an index of beam 140-2) by sending a PDCCH order (at 350).

[0059] UE 210, having been configured by the adaptive RACH configuration to be able to perform RACH transmission with adaptation, can perform RACH transmission with adaptation (at 360). UE 210 can determine that SSB1 has the highest signal strength, indication that beam 140-1 is the most suitable beam 140, and perform RACH transmission with adaptation (e.g., RACH with adaptation) via beam 140-1.

[0060] To determine that SSB1 has the highest signal strength, UE 210 can compare the most recent measurement values of SSB1, SSB2, and SSB3. In some examples, the measurements of SSB 1 can be higher than a threshold, such as the RSRP being higher than a threshold. In some examples, the measurements can indicate that SSB1 has a higher signal144932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) strength relative to SSB2 and SSB3.

[0061] Fig. 4 is a diagram of an example of process 400 for RACH transmission with adaptation according to one or more implementations described herein. Process 400 can be implemented by UE 210, serving base station 222-1, target base station 222-2, or a combination thereof. In some implementations, some or all of process 400 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 400 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 4. In some implementations, some or all of the operations of process 400 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 400. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 4.

[0062] Process 400 can include indicating adaptive RACH capability (at 405). For example, UE 210 can indicate adaptive RACH capability to serving base station 222-1, such as via a report. The adaptive RACH capability can indicate whether UE 210 has the capability to perform RACH with adaptation. In some examples, UE 210 can indicate the capability to perform RACH with adaption by using a single bit, such as value 0 indicating that UE 210 is not capable and value 1 indicating that UE is capable. In some examples, UE 210 indicate capability per frequency range. For example, UE 210 can indicate whether UE 210 has the capability to perform RACH with adaptation for each frequency range of multiple possible frequency ranges.

[0063] Process 400 can include indicating an adaptive RACH configuration (at 410). For example, base station 222-1 can transmit adaptive RACH configuration to UE 210. In some examples, adaptive RACH configuration can be included as part of a message or another configuration, such as a downlink control information (DCI) or RRC message. The adaptive RACH configuration can configure UE 210 to perform RACH with adaptation based on the adaptive RACH capability of UE 210. Adaptive RACH configuration can include parameters to enable / disable RACH with adaptation, parameters to indicate and enable different RACH configuration adaptations, and conditions for adaptation. Multiple candidate RACH configurations can be configured to provide flexibility to UE 210, as UE 210 can select which configuration to use.

[0064] Adaptive RACH configuration can enable or disable RACH with adaptation. For example, a bit can be included as part of the configuration. The bit can enable RACH with adaptation with a first value (e.g., 0) that indicates RACH with adaptation is allowed, and154932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) disable RACH with adaptation with a second value (e.g., 1) that indicates RACH with adaptation is not allowed. When RACH with adaptation is not enabled, UE 210 may not perform RACH with adaptation.

[0065] In some examples, adaptive RACH configuration can include a parameter to indicate which adaptations are allowed. For example, a first adaptation (e.g., configuration, RACH transmission adaptation), can include enabling UE 210 to perform a RACH transmission based on a different SSB than that indicated by serving base station 222-1. In some examples, the RACH transmission can be the first message of a CFRA procedure. A second adaptation can include enabling UE 210 to transmit the RACH transmission as the first message of a CBRA procedure, which can be performed based on the SSB indicated by serving base station 222-2.

[0066] Adaptive RACH configuration can include one or more conditions to enable RACH with adaptation. Conditions can be applied to different adaptions. In some examples, conditions can be included in an RRC command, such as by including one or more thresholds as part of an RRC message. When the conditions are met, UE 210 can perform RACH with adaption. When not met, UE 210 can perform RACH according to network configuration (e g., PRACH order).

[0067] Conditions can include one or more thresholds of absolute measurement results. For example, measurements (e.g., Ll / layer 3 (L3) measurements) of SSBs associated with target base station 222-2. For example, UE 210 can perform RACH with adaption if a value of a measurement, such as an RSRP, of an SSB is greater than a threshold (e.g., -90 dBm). For example, UE 210 can perform RACH with adaptation via the beam associated with the SSB that has an RSRP that is greater than the threshold.

[0068] In some examples, conditions can include a relative measurement (e.g., L1 / L2 measurements) threshold. For example, UE 210 can compare one or more measurements of one or more SSB. The condition can include allowing RACH with adaptation when the difference between the measurement of another SSB and the measurement of the SSB indicated by the PRACH order is greater than the relative threshold. For example, UE 210 can select an SSB with an RSRP measurement that is greater than the SSB indicated by the PRACH order by a threshold (e.g., greater by x dB).

[0069] Process 400 can include transmitting at least one SSB (at 415). For example, target base station 222-2 can transmit SSBs to UE 210, each SSB indicated via a beam. UE 210 can perform measurements associated with (e.g., on, of) each SSB of target base station 222-2(at 420). Measurements can be L1 / L2 measurements and can include measurements that164932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) indicate signal strength of the SSB and can be used to infer suitability of the associated beam. Measurements can include RSRP, propagation delay, radio frame boundary, subframe boundary, cell identifiers, reference signal received quality (RSRQ), or a combination thereof. UE 210 can transmit the measurements to serving base station 222-1 as part of a measurement report (at 425). In some examples, the measurement report can include measurements of multiple SSBs. In some examples, the SSBs can be from multiple base stations 222.

[0070] Process 400 can include selecting an SSB (at 430). For example, serving base station 222-1 can select the SSB with the highest signal strength, which can be associated with the most suitable beam for UE 210 to use to perform a RACH transmission (e.g., for synchronization). Serving base station 222-1 can select the SSB based on the measurements of the measurement report.

[0071] Process 400 can include a PDCCH order (at 435). For example serving base station 222-1 can indicate a PDCCH order to UE 210 to initiate, or trigger, a RACH transmission with target base station 222-2. The PDCCH order can include an indication of the selected SSB, such as by including the index of the SSB. The selected SSB can be associated with a beam, such that the PDCCH order indicates a beam for RACH transmission.

[0072] In some examples, the PDCCH order can include adaptive RACH configuration information, such as an indication of whether RACH with adaptation is enabled or disabled for UE 210 and parameters to indicate which RACH adaptations are enabled or disabled. In some examples, serving base station 222-1 can include adaptive RACH configuration information as part of the PDCCH order, and refrain from transmitting the RACH configuration information separately. In some examples, serving base station 222-1 can indicate the RACH configuration information as a separate message than the PDCCH order, and the PDCCH order may not include RACH configuration information.

[0073] In some examples, RACH configuration information of the PDCCH order can included a component (e.g., parameter) to indicate whether RACH with adaptation is enabled or disabled. For example, a bit value can indicate enabled (e.g.., 0) or disabled (e.g., 1). The PDCCH order can include a parameter to indicate which adaptations are enabled or disabled. For example, a first adaptation can be enabled or disabled. The first adaption can include UE 210 performing CFRA based on an SSB that is different than the SSB indicated in the PDCCH order. In some examples, a second adaptation can be enabled or disabled. For example, the second adaptation can include UE 210 performing CBRA.174932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)

[0074] Process 400 can include determining whether to perform RACH transmission with adaptation (e.g., RACH with adaptation) (at 440). For example, UE 210 can determine, based on adaptive RACH configuration information (whether included as part of an adaptive RACH configuration message or PDCCH order), whether to perform RACH with adaptation.

[0075] UE 210 can determine whether RACH with adaptation is enabled. If RACH with adaptation is enabled, UE 210 can determine which adaptations are enabled (if any), and which conditions are met (if any). If adaptations are enabled and one or more conditions are met, UE 210 can perform RACH transmission with adaptation (at 445).

[0076] To determine whether conditions are met, UE 210 can determine that a second SSB other than the first SSB indicated by the PDCCH order exceeds a threshold or exceeds a relative threshold. UE 210 can compare measurements, such as RSRP, of the SSBs of target base station 222-2. For example, If the RSRP of a different second SSB is greater than a threshold, or greater than the indicated first SSB by a threshold, UE 210 can perform a RACH transmission with adaptation using the beam associated with the second SSB. For example, UE 210 can perform a CFRA procedure. In some examples, RACH transmission is a PRACH message.

[0077] If RACH with adaptation is not enabled, one or more adaptations are not enabled, or conditions are not met, UE 210 may not perform RACH transmission with adaption, and can perform RACH without adaption (at 445). For example, UE 210 can perform CBRA using the beam associated with the first SSB indicated by the PDCCH order. Conditions may not be met if measurements of SSBs other than the first SSB indicated by the PDCCH order do not exceed a threshold, or do not exceed the measurements of the indicated first SSB by a threshold.

[0078] Figure 5 is a diagram of an example of components of a device according to one or more implementations described herein. In some implementations, the device 500 can include application circuitry 502, baseband circuitry 504, RF circuitry 506, front-end module (FEM) circuitry 508, one or more antennas 510, and power management circuitry (PMC) 512 coupled together at least as shown. In some implementations, device 500 can include fewer elements (e.g., a RAN node may not utilize application circuitry 502, and can instead include a processor / controller to process data received from a core network. In some implementations, device 500 can include additional elements such as, for example, memory / storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device 500, etc.), or input / output (I / O) interface. In other implementations, the components184932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for cloud-RAN (C-RAN) implementations).

[0079] The application circuitry 502 can include one or more application processors. For example, the application circuitry 502 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with or can include memory / storage and can be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 500. In some implementations, processors of application circuitry 502 can process data packets received from a core network.

[0080] The baseband circuitry 504 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 504 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of RF circuitry 506 and to generate baseband signals for a transmit signal path of RF circuitry 506. Baseband circuitry 54 can interface with application circuitry 502 for generation and processing of the baseband signals and for controlling operations of RF circuitry 506. For example, in some implementations, baseband circuitry 504 can include a 3G baseband processor 504A, a 4G baseband processor 504B, a 5G baseband processor 504C, or other baseband processor(s) 504D for other existing generations, generations in development or to be developed in the future (e.g., 5G, 6G, 7G, etc.). Baseband circuitry 54 (e.g., one or more of baseband processors 504A-D) can handle various radio control functions that enable communication with one or more radio networks via RF circuitry 506. In other implementations, some or all of the functionality of baseband processors 504A-D can be included in modules stored in memory 804G and executed via a central processing unit (CPU) 504E. The radio control functions can include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, modulation / demodulation circuitry of baseband circuitry 504 can include Fast-Fourier Transform (FFT), precoding, or constellation mapping / de-mapping functionality. In some implementations, encoding / decoding circuitry of baseband circuitry 504 can include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functionality. Implementations of modulation / demodulation and encoder / decoder functionality are not limited to these examples and can include other suitable functionality in other implementations.194932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)

[0081] In some implementations, memory 504G can receive and / or store information and instructions for enabling UE 210, and / or one or more components thereof, to perform RACH transmission with adaptation (e.g., RACH with adaptation). For example, the information and instructions can cause and / or enable UE 210 to determine whether there is a more suitable beam to use to perform RACH transmission than the beam indicated by the serving base station. UE can compare measurements of signal strength of SSBs associated with each beam, and perform RACH according to the SSB and beam with the strongest signal strength, which can be different than the beam indicated by the serving base station. These and many other features and examples are described herein.

[0082] In some implementations, the baseband circuitry 504 can include one or more audio digital signal processor(s) (DSP) 504F. The audio DSPs 504F can include elements for compression / decompression and echo cancellation and can include other suitable processing elements in other implementations. Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some implementations. In some implementations, some or all of the constituent components of the baseband circuitry 504 and the application circuitry 502 can be implemented together such as, for example, on a system on a chip (SOC).

[0083] In some implementations, the baseband circuitry 504 can provide for communication compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 504 can support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), etc. Implementations in which the baseband circuitry 504 is configured to support radio communications of more than one wireless protocol can be referred to as multimode baseband circuitry.

[0084] RF circuitry 506 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various implementations, RF circuitry 806 can include switches, filters, amplifiers, etc., to facilitate the communication with the wireless network. RF circuitry 506 can include a receive signal path which can include circuitry to down-convert RF signals received from FEM circuitry 508 and provide baseband signals to baseband circuitry 504. RF circuitry 506 can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by baseband circuitry 504 and provide RF output signals to FEM circuitry 508 for transmission.204932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)

[0085] In some implementations, the receive signal path of the RF circuitry 506 can include mixer circuitry 506A, amplifier circuitry 506B and filter circuitry 506C. In some implementations, the transmit signal path of RF circuitry 506 can include filter circuitry 506C and mixer circuitry 506 A. RF circuitry 56 can also include synthesizer circuitry 506D for synthesizing a frequency for use by mixer circuitry 506A of the receive signal path and the transmit signal path. In some implementations, mixer circuitry 506A of the receive signal path can be configured to down-convert RF signals received from FEM circuitry 508 based on the synthesized frequency provided by synthesizer circuitry 506D. Amplifier circuitry 506B can be configured to amplify the down-converted signals and filter circuitry 506C can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to baseband circuitry 504 for further processing. In some implementations, the output baseband signals can be zero-frequency baseband signals, although this may not be a requirement. In some implementations, mixer circuitry 506A of the receive signal path can comprise passive mixers, although the scope of the implementations is not limited in this respect.

[0086] In some implementations, the mixer circuitry 506A of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 506D to generate RF output signals for the FEM circuitry 508. The baseband signals can be provided by the baseband circuitry 504 and can be filtered by filter circuitry 506C.

[0087] In some implementations, mixer circuitry 506A of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by synthesizer circuitry 506D to generate RF output signals for FEM circuitry 508. The baseband signals can be provided by baseband circuitry 504 and can be filtered by filter circuitry 506C. In some implementations, mixer circuitry 506A of the receive signal path and mixer circuitry 506A of the transmit signal path can include two or more mixers and can be arranged for quadrature down conversion and up conversion, respectively. In some implementations, mixer circuitry 506A of the receive signal path and mixer circuitry 506A of the transmit signal path can include two or more mixers and can be arranged for image rejection. In some implementations, mixer circuitry 506A of the receive signal path and mixer circuitry 506A can be arranged for direct down conversion and direct up conversion, respectively. In some implementations, mixer circuitry 506A of the receive signal path and mixer circuitry 506A of the transmit signal path can be configured for super-heterodyne214932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) operation.

[0088] In some implementations, the output baseband signals, and the input baseband signals can be analog baseband signals, although the scope of the implementations is not limited in this respect. In some alternate implementations, the output baseband signals, and the input baseband signals can be digital baseband signals. In these alternate implementations, RF circuitry 506 can include analog-to-digital converter (ADC) and digital- to-analog converter (DAC) circuitry and baseband circuitry 504 can include a digital baseband interface to communicate with RF circuitry 506.

[0089] In some dual-mode implementations, a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the implementations is not limited in this respect. In some implementations, the synthesizer circuitry 506D can be a fractional -N synthesizer or a fractional N / N+l synthesizer, although the scope of the implementations is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 506D can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0090] Synthesizer circuitry 506D can be configured to synthesize an output frequency for use by mixer circuitry 506A of RF circuitry 506 based on a frequency input and a divider control input. In some implementations, synthesizer circuitry 506D can be a fractional N / N+l synthesizer. In some implementations, frequency input can be provided by a voltage- controlled oscillator (VCO). Divider control input can be provided by either baseband circuitry 54 or the applications circuitry 502 depending on the desired output frequency. In some implementations, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications circuitry 502.

[0091] Synthesizer circuitry 506D of RF circuitry 506 can include a divider, a delay- locked loop (DLL), a multiplexer, and a phase accumulator. In some implementations, the divider can be a dual modulus divider (DMD), and the phase accumulator can be a digital phase accumulator (DPA). In some implementations, the DMD can be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example implementations, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these implementations, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay224932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) line is one VCO cycle.

[0092] In some implementations, synthesizer circuitry 506D can be configured to generate a carrier frequency as the output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some implementations, the output frequency can be a LO frequency (fLO). In some implementations, RF circuitry 506 can include an in- phase / quadrature (I / Q) / polar converter.

[0093] FEM circuitry 508 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 510, amplify the received signals and provide the amplified versions of the received signals to RF circuitry 56 for further processing. FEM circuitry 508 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by RF circuitry 506 for transmission by one or more of the one or more antennas 510. In various implementations, the amplification through the transmit or receive signal paths can be done solely in RF circuitry 506, solely in FEM circuitry 508, or in both RF circuitry 506 and FEM circuitry 508.

[0094] In some implementations, the FEM circuitry 508 can include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 506). The transmit signal path of the FEM circuitry 508 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 506), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 510).

[0095] In some implementations, the PMC 512 can manage power provided to the baseband circuitry 504. In particular, PMC 512 can control power-source selection, voltage scaling, battery charging, or direct current (DC) to DC (DC-to-DC) conversion. PMC 512 can often be included when device 500 is capable of being powered by a battery, for example, when device 500 is included in a UE. PMC 512 can increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[0096] While Fig. 5 shows PMC 512 coupled only with the baseband circuitry 54, in other implementations, PMC 512 can be additionally or alternatively coupled with, and234932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) perform similar power management operations for, other components such as, but not limited to, application circuitry 502, RF circuitry 506, or FEM circuitry 508.

[0097] In some implementations, the PMC 512 can control, or otherwise be part of, various power saving mechanisms of device 500. For example, if device 500 is in an RRC Connected state, where device 500 is still connected to the RAN node as device 500 expects to receive traffic shortly, then device 500 can enter a state known as discontinuous reception mode (DRX) after a period of inactivity. During this state, device 500 can power down for brief intervals of time and thus save power.

[0098] If there is no data traffic activity for an extended period of time, then device 500 can transition off to an RRC Idle state, where device 500 disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. Device 500 can go into a very low power state and device 500 can perform paging where again device 500 periodically can wake up to listen to the network and then power down again. Device 500 may not receive data in this state; in order to receive data, device 500 can transition back to RRC Connected state.

[0099] An additional power saving mode can allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device 500 can be unreachable to the network and can power down completely. Any data sent during this time can incur a large delay and device 500 can assume the delay is acceptable.

[0100] Processors of application circuitry 502 and processors of baseband circuitry 54 can be used to execute elements of one or more instances of a protocol stack. For example, processors of baseband circuitry 504, alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of baseband circuitry 504 can utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 can comprise a radio resource control layer. As referred to herein, Layer 2 can comprise a medium access control layer, a radio link control layer, and a packet data convergence protocol layer, described in further detail below. As referred to herein, Layer 1 can comprise a physical layer of a UE / RAN node.

[0101] Figure 6 is a diagram of example interfaces 600 of baseband circuitry according to one or more implementations described herein. One or more components or features of example interfaces 600 can correspond to one or more components or features described above or elsewhere. Baseband circuitry 64 can comprise processors 604A, 604B, 604C,244932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)604D, and 604E and a memory 604G utilized by said processors. Each of the processors 604A, 604B, 604C, 604D, and 604E can include a memory interface, 606A, 606B, 606C, 606D, and 606E, respectively, to send / receive data to / from the memory 604G. Baseband circuitry can be a component of a UE and / or another type of device or system capable of transmitting and / or receiving wireless signals.

[0102] In some implementations, memory 604G can receive, store, and / or provide information and instructions for transmitting adaptive RACH capability information, receiving adaptive RACH configuration, and performing RACH transmission with adaptation (e.g., RACH with adaptation). Further information and instructing can include determining whether there is a more suitable beam to use to perform RACH transmission than the beam indicated by the serving base station. UE 210 can compare measurements of signal strength of SSBs associated with each beam, and perform RACH according to the SSB and beam with the strongest signal strength, which can be different than the beam indicated by the serving base station.

[0103] Baseband circuitry 64 can further include one or more interfaces to communicatively couple to other circuitries / devices, such as a memory interface 612 (e.g., an interface to send / receive data to / from memory external to baseband circuitry 64), an application circuitry interface614 (e.g., an interface to send / receive data to / from the application circuitry as described herein), an RF circuitry interface 616, a wireless hardware connectivity interface 618 (e.g., an interface to send / receive data to / from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 620 (e.g., an interface to send / receive power or control signals to / from a PMC)

[0104] Figure 7 is a block diagram illustrating components, according to some example implementations, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Fig. 7 shows a diagrammatic representation of hardware resources 700 including one or more processors 710 (or processor cores), one or more memory / storage devices 720, and one or more communication resources 730, each of which can be communicatively coupled via a bus 740. For implementations where node virtualization or network function virtualization is utilized, a hypervisor can be executed to provide an execution environment for one or more network slices / sub-slices to utilize hardware resources 700. Hardware resources 700 can interact with hypervisor 72. For254932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) example, hypervisor 72 can schedule or otherwise manage hardware resource 700.

[0105] The processors 710 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) can include, for example, a processor 712 and a processor 714.

[0106] The memory / storage devices 720 can include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 720 can include, but are not limited to any type of volatile or non-volatile memory such as dynamic random-access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

[0107] In some implementations, memory / storage devices 720 receive and / or store information and instructions 755 for performing RACH transmission with adaptation (e.g., RACH with adaptation). For example, memory / storage devices 720 can include information and instructions for communicating adaptive RACH capability information, adaptive RACH configuration, SSB measurements, SSB measurements reports, and PDCCH order. Information and instructions 755 can include determining whether there is a more suitable beam to use to perform RACH transmission than the beam indicated by the serving base station. Information and instructions 755 can include comparing measurements of signal strength of SSBs associated with each beam, and perform RACH according to the SSB and beam with the strongest signal strength, which can be different than the beam indicated by the serving base station. These and many other features and examples are discussed herein.

[0108] Communication resources 730 can include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 74 or one or more databases 76 via a network78. For example, communication resources 730 can include wired communication components (e.g., for coupling via a universal serial bus), cellular communication components, near field communication components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

[0109] Instructions 750A, 750B, 750C, 750D, and / or 750E can comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of processors 710 to perform any one or more of the methodologies discussed herein.264932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)Instructions 750 can reside, completely or partially, within at least one of processors 710 (e.g., within a cache memory), memory / storage devices 720, or any suitable combination thereof. Furthermore, any portion of instructions 750A-E can be transferred to hardware resources 700 from any combination of peripheral devices 74 or databases 76. Accordingly, memory of processors 710, memory / storage devices 720, peripheral devices 74, and databases 76 are examples of computer-readable and machine-readable media.

[0110] Figure 8 is a diagram of an example process for RACH transmission with adaptation according to one or more implementations described herein. Process 800 can be implemented by UE 210, baseband circuitry, or both. In some implementations, some or all of process 800 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 800 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 8. In some implementations, some or all of the operations of process 800 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 800. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 8.[OHl] Process 800 can include receiving, from a serving base station, RACH configuration information comprising at least one condition for performing a RACH transmission (block 810). Process 800 can include receiving, from the serving base station, an indication of a first SSB associated with a first beam for performing the RACH transmission toward a target base station (block 820). Process 800 can include determining whether the at least one condition is satisfied (block 830). Process 800 can include, when the at least one condition is not satisfied, performing the RACH transmission toward the target base station using the first beam (block 840). Process 800 can include, when the at least one condition is satisfied, determining a second SSB associated with a second beam for performing the RACH transmission (block 850). Process 800 can include performing the RACH transmission using the second beam (block 860).

[0112] Figure 9 is a diagram of an example process for RACH transmission with adaptation according to one or more implementations described herein. Process 900 can be implemented by UE 210, baseband circuitry, or both. In some implementations, some or all of process 900 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 900 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 9. In some implementations, some or all of the operations of process 900 can be performed274932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) independently, successively, simultaneously, etc., of one or more of the other operations of process 900. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 9.

[0113] Process 900 can include transmit, to a UE, RACH configuration information comprising at least one condition for performing a RACH transmission, wherein the at least one condition comprises an indication that an adaptive RACH procedure is enabled (block 910). Process 900 can include selecting a first SSB associated with a first beam for performing a RACH transmission toward a target base station (block 920). Process 900 can include transmit, to the UE, an indication of the first SSB associated with the first beam (block 930).

[0114] Figure 10 is a diagram of an example process for RACH transmission with adaptation according to one or more implementations described herein. Process 1000 can be implemented by UE 210, baseband circuitry, or both. In some implementations, some or all of process 1000 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 1000 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 10. In some implementations, some or all of the operations of process 1000 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 1000. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 10.

[0115] Process 1000 can include processing RACH configuration information comprising at least one condition for performing a RACH transmission (block 1010). Process 1000 can include processing an indication of a first SSB associated with a first beam for performing the RACH transmission toward a target base station (block 1020). Process 1000 can include determining whether the at least one condition is satisfied (block 1030). Process 1000 can include, when the at least one condition is not satisfied, generating the RACH transmission toward the target base station using the first beam (block 1040). Process 1000 can include, when the at least one condition is satisfied, determining a second SSB associated with a second beam for performing the RACH transmission (block 1050). Process 1000 can include generating the RACH transmission using the second beam (block 1060).

[0116] Examples and / or implementations herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor (e.g., processor , etc.) with memory, an application-specific integrated circuit284932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)(ASIC), a field programmable gate array (FPGA), or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to implementations and examples described.

[0117] In example 1, which can also include one or more of the examples described herein, a UE (e.g., UE 210) can comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause UE 210 to: receive, from a serving base station, random access channel (RACH) configuration information comprising at least one condition for performing a RACH transmission; receive, from the serving base station, an indication of a first SSB associated with a first beam for performing the RACH transmission toward a target base station; determine whether the at least one condition is satisfied; when the at least one condition is not satisfied, perform the RACH transmission toward the target base station using the first beam; when the at least one condition is satisfied, determine a second SSB associated with a second beam for performing the RACH transmission; and perform the RACH transmission using the second beam.

[0118] In example 2, which can also include one or more of the examples described herein, wherein the at least one condition comprises: receiving, from the serving base station, an indication that an adaptive RACH procedure is enabled, a measured signal satisfying a signal threshold, or a combination thereof.

[0119] In example 3, which can also include one or more of the examples described herein, wherein the signal threshold comprises at least one of: a measurement threshold of beam suitability, a relative measurement threshold of beam suitability, or a combination thereof.

[0120] In example 4, which can also include one or more of the examples described herein, when the at least one condition is not satisfied, the RACH transmission comprises a first message of a CBRA procedure.

[0121] In example 5, which can also include one or more of the examples described herein, wherein, when the at least one condition is satisfied, the RACH transmission comprises a first message of a CFRA procedure.

[0122] In example 6, which can also include one or more of the examples described herein, wherein the RACH configuration information comprises: a bit indicating whether adaptive RACH is enabled, a second bit indicating whether a CFRA procedure is enabled, a third bit indicating whether a CBRA procedure is enabled, or a combination thereof.

[0123] In example 7, which can also include one or more of the examples described herein, the one or more processors are further configured to cause UE 210 to: receive, from294932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) the target base station, at least one SSB via at least one beam, wherein the at least one SSB comprises the first SSB and the second SSB, and the at least one beam comprises the first beam and the second beam.

[0124] In example 8, which can also include one or more of the examples described herein, the one or more processors are further configured to cause UE 210 to: perform measurements associated with the at least one SSB; and transmit, to the serving base station, a measurement report comprising the measurements of the at least one SSB.

[0125] In example 9, which can also include one or more of the examples described herein, wherein the measurements of the at least one SSB comprise at least a RSRP.

[0126] In example 10, which can also include one or more of the examples described herein, wherein receiving the indication of the first SSB is based on the measurement report.

[0127] In example 11, which can also include one or more of the examples described herein, wherein the one or more processors are further configured to cause the UE to: receive, from the serving base station, a PDCCH order, wherein the PDCCH order comprises the indication of the first SSB.

[0128] In example 12, which can also include one or more of the examples described herein, wherein the PDCCH order comprises the RACH configuration information.

[0129] In example 13, which can also include one or more of the examples described herein, the one or more processors are further configured to cause UE 210 to: transmit a RACH capability indicating a capability of the UE to perform RACH transmission using a beam other than the first beam, and wherein receiving the RACH configuration information is based on the RACH capability indicating that the UE is capable of performing the RACH transmission using a beam other than the first beam.

[0130] In example 14, which can also include one or more of the examples described herein, a base station can comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the base station to: transmit, to a UE, RACH configuration information comprising at least one condition for performing a RACH transmission, wherein the at least one condition comprises an indication that an adaptive RACH procedure is enabled; selecting a first SSB associated with a first beam for performing a RACH transmission toward a target base station; and transmit, to the UE, an indication of the first SSB associated with the first beam.

[0131] In example 15, which can also include one or more of the examples described herein, wherein the at least one condition comprises: transmitting, to the UE, an indication that the adaptive RACH procedure is enabled, wherein the adaptive RACH procedure304932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) comprises performing the RACH transmission toward the target base station using a second beam associated with a second SSB, a measured signal satisfying a signal threshold, or a combination thereof.

[0132] In example 16, which can also include one or more of the examples described herein, wherein the signal threshold comprises at least one of: a measurement threshold of beam suitability, a relative measurement threshold of beam suitability, or a combination thereof.

[0133] In example 17, which can also include one or more of the examples described herein, wherein the one or more processors are further executable to cause the base station to: receive, from the UE, a measurement report comprising measurements associated with at least one SSB associated with at least one beam of the target base station, wherein the at least one SSB comprises the first SSB, and the at least one beam comprises the first beam.

[0134] In example 18, which can also include one or more of the examples described herein, wherein the one or more processors are further executable to cause the base station to: select the first SSB based on the measurement report, and transmit the indication of the first SSB based the selection.

[0135] In example 19, which can also include one or more of the examples described herein, wherein the one or more processors are further executable to cause the base station to: transmit, to the UE, a PDCCH order, wherein the PDCCH order comprises the indication of the first SSB.

[0136] In example 20, which can also include one or more of the examples described herein, wherein the PDCCH order comprises the RACH configuration information.

[0137] In example 21, which can also include one or more of the examples described herein, baseband circuitry can comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the baseband circuitry to: process RACH configuration information comprising at least one condition for performing a RACH transmission; process an indication of a first SSB associated with a first beam for performing the RACH transmission toward a target base station; determine whether the at least one condition is satisfied; when the at least one condition is not satisfied, generate the RACH transmission toward the target base station using the first beam; when the at least one condition is satisfied, determine a second SSB associated with a second beam for performing the RACH transmission; and generate the RACH transmission using the second beam.

[0138] In example 22, which can also include one or more of the examples described herein, the one or more processors are further configured to cause UE 210 to: wherein the at314932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) least one condition comprises: processing an indication that an adaptive RACH procedure is enabled, a measured signal satisfying a signal threshold, or a combination thereof.

[0139] In example 23, which can also include one or more of the examples described herein, wherein the signal threshold comprises at least one of: a measurement threshold of beam suitability, a relative measurement threshold of beam suitability, or a combination thereof.

[0140] The examples discussed above also extend to method, computer-readable medium, and means-plus-function claims and implementations, any of which can include one or more of the features or operations of any one or combination of the examples mentioned above.

[0141] The above description of illustrated examples, implementations, aspects, etc., of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. While specific examples, implementations, aspects, etc., are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such examples, implementations, aspects, etc., as those skilled in the relevant art can recognize.

[0142] In this regard, while the disclosed subject matter has been described in connection with various examples, implementations, aspects, etc., and corresponding Figures, where applicable, it is to be understood that other similar aspects can be used or modifications and additions can be made to the disclosed subject matter for performing the same, similar, alternative, or substitute function of the subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single example, implementation, or aspect described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

[0143] In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a “means”) used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations. In addition, while a particular feature can have been disclosed with respect to only one of several implementations, such feature can be combined with one or more other features of the other implementations as can be desired and advantageous for any given application.324932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)

[0144] As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms “including”, “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.” Additionally, in situations wherein one or more numbered items are discussed (e.g., a “first X”, a “second X”, etc.), in general the one or more numbered items can be distinct, or they can be the same, although in some situations the context can indicate that they are distinct or that they are the same.

[0145] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.4932-9964-1 167, v. 2

Claims

Attorney Docket No.: 106842241640 (P68963WO1)CLAIMSWhat is claimed is:

1. A user equipment (UE), comprising: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the UE to: receive, from a serving base station, random access channel (RACH) configuration information comprising at least one condition for performing a RACH transmission; receive, from the serving base station, an indication of a first synchronization signal block (SSB) associated with a first beam for performing the RACH transmission toward a target base station; determine whether the at least one condition is satisfied; when the at least one condition is not satisfied, perform the RACH transmission toward the target base station using the first beam; when the at least one condition is satisfied, determine a second SSB associated with a second beam for performing theRACH transmission; and perform the RACH transmission using the second beam.

2. The UE of claim 1, wherein the at least one condition comprises: receiving, from the serving base station, an indication that an adaptive RACH procedure is enabled, a measured signal satisfying a signal threshold, or a combination thereof.

3. The UE of claim 2, wherein the signal threshold comprises at least one of: a measurement threshold of beam suitability, a relative measurement threshold of beam suitability, or a combination thereof.344932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1)4. The UE of claim 1, wherein, when the at least one condition is not satisfied, the RACH transmission comprises a first message of a contention-based RACH (CBRA) procedure.

5. The UE of claim 1, wherein, when the at least one condition is satisfied, the RACH transmission comprises a first message of a contention-free RACH (CFRA) procedure.

6. The UE of claim 1, wherein the RACH configuration information comprises: a bit indicating whether adaptive RACH is enabled, a second bit indicating whether a contention-free RACH (CFRA) procedure is enabled, a third bit indicating whether a contention-based RACH (CBRA) procedure is enabled, or a combination thereof.

7. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: receive, from the target base station, at least one SSB via at least one beam, wherein the at least one SSB comprises the first SSB and the second SSB, and the at least one beam comprises the first beam and the second beam.

8. The UE of claim 7, wherein the one or more processors are further configured to cause the UE to: perform measurements associated with the at least one SSB; and transmit, to the serving base station, a measurement report comprising the measurements of the at least one SSB.

9. The UE of claim 8, wherein the measurements of the at least one SSB comprise at least a reference signal received power (RSRP).

10. The UE of claim 8, wherein receiving the indication of the first SSB is based on the measurement report.

11. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to:354932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) receive, from the serving base station, a physical downlink control channel (PDCCH) order, wherein the PDCCH order comprises the indication of the first SSB.

12. The UE of claim 11, wherein the PDCCH order comprises the RACH configuration information.

13. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: transmit a RACH capability indicating a capability of the UE to perform RACH transmission using a beam other than the first beam, and wherein receiving the RACH configuration information is based on the RACH capability indicating that the UE is capable of performing the RACH transmission using a beam other than the first beam.

14. An electronic device, comprising: one or more processors; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods of claims 1-13.

15. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device, cause the electronic device to perform any of the methods of claims 1-13.

16. A base station, comprising: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the base station to: transmit, to a user equipment (UE), random access channel (RACH) configuration information comprising at least one condition for performing a RACH transmission, wherein the at least one condition comprises an indication that an adaptive RACH procedure is enabled;364932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) selecting a first synchronization signal block (SSB) associated with a first beam for performing a RACH transmission toward a target base station; and transmit, to the UE, an indication of the first SSB associated with the first beam.

17. The base station of claim 16, wherein the at least one condition comprises: transmitting, to the UE, an indication that the adaptive RACH procedure is enabled, wherein the adaptive RACH procedure comprises performing the RACH transmission toward the target base station using a second beam associated with a second SSB, a measured signal satisfying a signal threshold, or a combination thereof.

18. The base station of claim 17, wherein the signal threshold comprises at least one of a measurement threshold of beam suitability, a relative measurement threshold of beam suitability, or a combination thereof.

19. The base station of claim 16, wherein the one or more processors are further executable to cause the base station to: receive, from the UE, a measurement report comprising measurements associated with at least one SSB associated with at least one beam of the target base station, wherein the at least one SSB comprises the first SSB, and the at least one beam comprises the first beam.

20. The base station of claim 19, wherein the one or more processors are further executable to cause the base station to: select the first SSB based on the measurement report, and transmit the indication of the first SSB based the selection.

21. The base station of claim 16, wherein the one or more processors are further executable to cause the base station to: transmit, to the UE, a physical downlink control channel (PDCCH) order, wherein the PDCCH order comprises the indication of the first SSB.

22. An electronic device, comprising: one or more processors;374932-9964-1 167, v. 2Attorney Docket No.: 106842241640 (P68963WO1) memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods of claims 16-21.

23. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device, cause the electronic device to perform any of the methods of claims 16-21.

24. Baseband circuitry, comprising: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the baseband circuitry to: process random access channel (RACH) configuration information comprising at least one condition for performing a RACH transmission; process an indication of a first synchronization signal block (SSB) associated with a first beam for performing the RACH transmission toward a target base station; determine whether the at least one condition is satisfied; when the at least one condition is not satisfied, generate the RACH transmission toward the target base station using the first beam; when the at least one condition is satisfied, determine a second SSB associated with a second beam for performing the RACH transmission; and generate the RACH transmission using the second beam.384932-9964-1 167, v. 2

Citation Information

Patent Citations

  • UE RACH resource configuration selection function and resource prioritization to support slicing

    US20230180301A1

  • System and method for random access resource selection

    US20230292357A1