Techniques for performing a random access channel (RACH) procedure in a non-anchor cell

Abstract

Certain aspects of this disclosure provide techniques for improving the execution of a random access channel (RACH) procedure in a non-anchor cell. One method typically includes: transmitting a first random access signal on a first non-anchor carrier associated with a first non-anchor cell of the device to initiate a first RACH procedure in the first non-anchor cell; and, based on the first RACH procedure failing to complete successfully within a time duration following the transmission of the first random access signal, transmitting a second random access signal on an anchor carrier associated with an anchor cell of the device or a second non-anchor carrier associated with a second non-anchor cell of the device to initiate a second RACH procedure in the anchor cell or the second non-anchor cell.

Description

Background Technology Technical Field

[0002] Various aspects of this disclosure relate to wireless communications, and more specifically to techniques for performing random access channel (RACH) procedures in non-anchored cells.

[0003] Related technical descriptions

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems may employ multiple access technologies that enable communication with several users by sharing available wireless communication system resources.

[0005] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers. Therefore, there is a continuous expectation for improving the technical performance of wireless communication systems, including, for example: improving communication speed and data carrying capacity; improving the efficiency of shared communication media; reducing the power used by transmitters and receivers during communication; improving the reliability of wireless communication; avoiding redundant transmission and / or reception and related processing; improving the coverage area of ​​wireless communication; increasing the number and types of devices that can access the wireless communication system; increasing the ability of different types of devices to communicate with each other; and increasing the number and types of available wireless communication media. Therefore, there is a need for further improvements to wireless communication systems to overcome the aforementioned technical challenges and other obstacles. Summary of the Invention

[0006] One aspect provides a method for wireless communication by an apparatus. The method includes: transmitting a first random access signal on a first non-anchor carrier associated with a first non-anchor cell of a network entity to initiate a first random access channel (RACH) procedure in the first non-anchor cell; and, based on the first RACH procedure failing to complete successfully within a time duration following the transmission of the first random access signal, transmitting a second random access signal on an anchor carrier associated with an anchor cell of the network entity or a second non-anchor carrier associated with a second non-anchor cell of the network entity to initiate a second RACH procedure in the anchor cell or the second non-anchor cell.

[0007] On the other hand, a method for wireless communication by a device is provided. The method includes: receiving configuration of one or more RACH timings, wherein the one or more RACH timings are not configured for the active uplink bandwidth portion (BWP) of the device, wherein the active uplink BWP is a first uplink BWP of a non-anchor cell of a network entity; switching the active uplink BWP of the device from the first uplink BWP to a second uplink BWP based on the fact that the one or more RACH timings are not configured for the active uplink BWP, wherein the second uplink BWP includes: another uplink BWP of a non-anchor cell; or an initial uplink BWP of an anchor cell of a network entity; and performing a RACH procedure using the second uplink BWP as the active uplink BWP for the device.

[0008] On the other hand, a method for wireless communication by a device is provided. The method includes: performing a RACH procedure in an anchor cell of a network entity; and transmitting an indication of the device's ability to support non-anchor cell operation.

[0009] Other aspects provide: one or more means capable of operating to, configured to, or otherwise adapted to perform any portion of any method described herein (e.g., such that performance can be implemented by only one means or in a distributed manner across multiple means); one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of the one or more means, cause the one or more means to perform any portion of any method described herein (e.g., such that instructions can be included in only one computer-readable medium or in a distributed manner across multiple computer-readable media, such that instructions can be executed by only one processor or by multiple processors in a distributed manner, such that in the one or more means...). Each device may include one or more processors, and / or enable execution to be performed by only one device or in a distributed manner across multiple devices; one or more computer program products embodied on one or more computer-readable storage media including code for performing any part of any method described herein (e.g., enabling the code to be stored in only one computer-readable medium or in a distributed manner across computer-readable media); and / or one or more devices including one or more components for performing any part of any method described herein (e.g., enabling execution to be performed by only one device or by multiple devices in a distributed manner). By way of example, a device may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks. A device may include: one or more memories; and one or more processors configured to enable the device to perform any part of any method described herein. In some examples, one or more processors may be pre-configured to perform the various functions or operations described herein without being configured by software.

[0010] For illustrative purposes, the following description and figures illustrate certain features. Attached Figure Description

[0011] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of this disclosure.

[0012] Figure 1 An example wireless communication network is depicted.

[0013] Figure 2 An example decomposed base station architecture is described.

[0014] Figure 3 Various aspects of the example base station and example user equipment (UE) are described.

[0015] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures used in wireless communication networks are described.

[0016] Figure 5A An example wireless communication network supporting multi-carrier operation is depicted.

[0017] Figure 5B Example anchor cells and non-anchor cells in multi-carrier operation are depicted.

[0018] Figure 6 Example configurations that can be supported by anchor carriers and non-anchor carriers in a multi-carrier implementation are described.

[0019] Figure 7A This is an example process flowchart depicting an example four-step random access procedure performed between a UE and a network entity in an anchored cell or a non-anchored cell.

[0020] Figure 7B This is an example process flowchart depicting an example two-step random access procedure performed between a UE and a network entity in an anchored cell or a non-anchored cell.

[0021] Figure 8 The process flow for carrier switching communication between network entities and UEs in a network is described.

[0022] Figure 9A and Figure 9B The process flow for communication between a network entity and a UE in the network to indicate the UE's ability to support non-anchor cell operation is described.

[0023] Figure 10 A method for wireless communication is described.

[0024] Figure 11 Another method for wireless communication is described.

[0025] Figure 12 Another method for wireless communication is described.

[0026] Figure 13 Various aspects of the example communication device are described. Detailed Implementation

[0027] This disclosure provides apparatus, methods, processing systems, and computer-readable media for performing a random access channel (RACH) procedure in a non-anchored cell.

[0028] The RACH procedure is a process initiated between a user equipment (UE) in an idle state and a network entity. This procedure is used by the UE to obtain initial access to the Radio Access Network (RAN) and request the radio resources required for wireless communication. As used herein, the UE's idle state (also referred to as "idle mode," "Radio Resource Control (RRC) idle mode," and / or "RRC idle state") refers to the UE's RRC state, in which the UE is not connected, or in other words, does not have an RRC connection established with the network entity or other network nodes. When the RACH procedure is completed, the UE may transition to a connected state (also referred to as "connected mode," "RRC connected mode," and / or "RRC connected state") and continue communication with the network entity.

[0029] A UE can use a single carrier at a network entity to perform a RACH procedure with that network entity, which can be configured to utilize one or more carriers (e.g., corresponding to different frequencies). Specifically, in some cases, multi-carrier operation can be supported to improve system access and data transmission capacity beyond that provided by a single carrier at the network entity. For example, a network entity can provide communication coverage for a coverage area called a cell and use a carrier to communicate with a UE within that cell. Different carriers can have different propagation properties and therefore can cover different coverage areas, allowing the same network entity to provide different coverage areas or cells when communicating using different carriers.

[0030] Network entities can use anchor carriers in anchor cells to communicate with the UE. In addition, to increase capacity, network entities can support additional carriers in non-anchor cells (e.g., which may overlap with anchor cells) used for communication with the UE, referred to as "non-anchor carriers".

[0031] In some cases, such as to help increase the overall capacity for random access, the UE and network entity may use anchor carriers and one or more non-anchor carriers to perform RACH procedures. For example, the network entity and UE may utilize at least one non-anchor carrier in a non-anchor cell to transmit one or more RACH messages (also known as RACH transmission) as part of the RACH procedure for initial access. Providing support for RACH procedures in non-anchor cells, in addition to anchor cells, can help reduce the number of RACH procedures performed via anchor carriers, especially when a large number of devices are supported at the network entity, thereby creating more opportunities for efficient connection establishment between the UE and the RAN. Furthermore, since non-anchor cells may support on-demand RACH signaling, where the network entity uses non-anchor carriers to provide signaling only based on some instructions and / or requests, network energy saving (NES) can be achieved.

[0032] It should be noted that performing RACH in a specific cell refers to using a carrier associated with that cell to transmit RACH messages between the UE and a network entity. For example, performing RACH in an anchor cell refers to using an anchor carrier associated with the anchor cell to transmit RACH messages between the UE and a network entity. In another example, performing RACH in a non-anchor cell refers to using a non-anchor carrier associated with the non-anchor cell to transmit RACH messages between the UE and a network entity.

[0033] While the ability to perform RACH in non-anchor cells, in addition to the anchor cell, may be advantageous for the reasons stated above, supporting RACH procedures in non-anchor cells may lead to additional problems that may need to be addressed. For example, in some cases, RACH procedures performed in non-anchor cells may fail due to radio frequency (RF) interference, poor signal quality, and / or weak coverage in the non-anchor cell. Furthermore, in order to perform RACH in non-anchor cells, the UE may need to utilize one or more RACH opportunities configured, which correspond to one or more resources (e.g., time-frequency resources) available for transmitting RACH during the RACH procedure. However, in some cases, RACH opportunities may not be configured for the uplink bandwidth portion (BWP) activated for use by the UE in the non-anchor cell. Specifically, to conserve power at the UE, only one uplink BWP may be activated for the UE at a time in a non-anchor cell, and the activated uplink BWP may not include any RACH opportunities configured for performing the RACH procedure.

[0034] Therefore, the aspects described herein provide improvements to the RACH process in non-anchor cells, such as those for handling such scenarios. Specifically, the aspects described herein introduce techniques for carrier handover and / or BWP handover for the RACH process.

[0035] When a RACH procedure initiated between the UE and the network entity using a non-anchor carrier associated with a non-anchor cell of the network entity fails, the carrier handover technique described herein may be used. Carrier handover may include switching from performing a failed RACH procedure in a non-anchor cell of the network entity to performing another RACH procedure in (1) an anchor cell of the network entity or (2) another non-anchor cell of the network entity to establish an RRC connection.

[0036] When a RACH timing is not configured for the UE's active uplink BWP, the BWP handover technique described herein can be used. BWP handover may involve switching the active uplink BWP for the UE from a first uplink BWP to a second uplink BWP, based on the fact that the first uplink BWP does not include any RACH timing for performing the RACH procedure. In some cases, the active uplink BWP for the UE that does not include any RACH timing (e.g., the first uplink BWP) is the active uplink BWP of a non-anchor cell of a network entity. In this case, the UE may switch its active uplink BWP to another uplink BWP in the same non-anchor cell (e.g., a first option for the second uplink BWP) or to the initial uplink BWP of the anchor cell of the network entity (e.g., a second option for the second uplink BWP), and use the newly activated uplink BWP to perform the RACH procedure.

[0037] Carrier handover techniques can help reduce access latency associated with RACH procedures. For example, when the amount of time required to successfully complete a RACH procedure in a non-anchor cell is significant (e.g., exceeding the expected threshold time for performing the RACH procedure), carrier handover allows the UE to switch from performing the RACH procedure in a non-anchor cell to performing it in an anchor cell or another non-anchor cell. Furthermore, BWP handover techniques provide the UE with an alternative solution for performing the RACH procedure when the RACH timing is not configured for the UE's active uplink BWP. Therefore, the UE can continue to use such non-anchor cells to perform the RACH procedure (e.g., this can help increase the overall capacity for random access).

[0038] Furthermore, certain aspects described herein provide techniques for instructing network entities on the UE's ability to support non-anchor cell operation. Network entities can use this information to perform load balancing between anchor cells and one or more non-anchor cells. For example, a network entity can schedule some communications (e.g., uplink and / or downlink communications) to occur between the UE and the network entity using one or more non-anchor carriers from one or more non-anchor cells to alleviate traffic in anchor cells using anchor carriers.

[0039] An introduction to wireless communication networks

[0040] The techniques and methods described herein can be used in a variety of wireless communication networks. Although aspects herein may be described using terms commonly associated with 3G, 4G, 5G, 6G, and / or other generations of wireless technologies, aspects of this disclosure are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0041] Figure 1An example of a wireless communication network 100 in which the aspects described herein can be implemented is depicted.

[0042] Generally, wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of the BS, servers, etc.). Since such communication devices are part of wireless communication network 100 and facilitate wireless communication, they may be referred to as wireless communication devices. For example, various functions of the network and various devices associated with and interacting with the network may be considered network entities. Furthermore, wireless communication network 100 includes terrestrial and non-terrestrial aspects (also referred to herein as non-terrestrial network entities). Terrestrial aspects include terrestrial network entities such as terrestrial network entities (e.g., BS 102), and non-terrestrial aspects include satellite 140 and / or airborne or spaceborne platforms, which may include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and UEs.

[0043] In the depicted example, wireless communication network 100 includes BS 102, UE 104 and one or more core networks (such as Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0044] Figure 1 Various example UE 104s are described, which may more generally include: cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players, cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, data centers, or other similar devices. UE 104 may also be more generally referred to as mobile devices, wireless devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, and others.

[0045] BS 102 communicates wirelessly with UE 104 via communication link 120 (e.g., sending or receiving signals to or from UE 104). Communication link 120 between BS 102 and UE 104 may include uplink (UL) transmission (also referred to as reverse link) from UE 104 to BS 102 and / or downlink (DL) transmission (also referred to as forward link) transmission from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity.

[0046] BS 102 may typically include: NodeB, enhanced NodeB (eNB), next-generation enhanced NodeB (ng-eNB), next-generation NodeB (gNB or gNodeB), access point, transceiver base station, radio base station, radio transceiver, transceiver functionality, transmit / receive point, and / or others. Each of BS 102 provides communication coverage for a corresponding coverage area 110, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, BS may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femtocells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0047] Generally, a cell can refer to a portion, partition, or segment of wireless communication coverage served by network entities within a wireless communication network. A cell can have geographical characteristics (such as a geographical coverage area) and radio frequency characteristics (such as time and / or frequency resources dedicated to the cell). For example, multiple cells employing different frequency resources (e.g., bandwidth portions) and / or different time resources can cover a specific geographical coverage area. As another example, a single cell can cover a specific geographical coverage area. In some contexts (e.g., carrier aggregation scenarios and / or multi-connectivity scenarios), the terms "cell" or "serving cell" can refer to or correspond to a specific carrier frequency (e.g., component carrier) used for wireless communication, and "cell group" can refer to or correspond to multiple carriers used for wireless communication. As an example, in a carrier aggregation scenario, a UE can communicate on multiple component carriers corresponding to multiple (serving) cells in the same cell group, and in a multi-connectivity (e.g., dual-connectivity) scenario, a UE can communicate on multiple component carriers corresponding to multiple cell groups.

[0048] Although BS 102 is described as a single communication device in various aspects, it can be implemented in a variety of configurations. For example, to give a few examples, one or more components of the base station can be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS 102) can include components located at a single physical location or components located at various physical locations. In examples where the base station includes components located at various physical locations, the various components can each perform functions, such that the various components collectively achieve functionality similar to a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0049] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. BSs 102 can communicate directly or indirectly (e.g., via EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.

[0050] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410MHz to 7125MHz, which is often (interchangeably) referred to as “sub-6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250MHz to 71,000MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). In some cases, FR2 can be further defined according to subranges (such as a first subrange FR2-1 including 24,250MHz to 52,600MHz and a second subrange FR2-2 including 52,600MHz to 71,000MHz). Base stations configured to communicate using mmWave / near mmWave radio bands (e.g., mmWave base stations such as BS 180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0051] The communication link 120 between BS 102 and, for example, UE 104 can be via one or more carriers, which may have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other MHz) and may be aggregated in various ways. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0052] Compared to lower-frequency communication, communication using higher frequency bands may have higher path loss and shorter range. Therefore, some base stations (e.g., Figure 1The beamforming 182 of the BS 180 (180) with the UE 104 can be used to improve path loss and range. For example, the BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182''. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182''. The UE 104 may also transmit beamformed signals to the BS 180 in one or more transmit directions 182''. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182''. The BS 180 and UE 104 may then perform beamforming training to determine the optimal receive and transmit directions for each of the BS 180 and UE 104. It is worth noting that the transmit and receive directions of the BS 180 may be the same or different. Similarly, the sending and receiving directions of UE 104 can be the same or different.

[0053] The wireless communication network 100 further includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

[0054] Some UEs 104 may use device-to-device (D2D) communication link 158 to communicate with each other. The D2D communication link 158 may use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and / or physical sidelink feedback channel (PSFCH).

[0055] EPC 160 may include various functional components, including: Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and / or Packet Data Network (PDN) Gateway 172, as in the illustrated example. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connectivity management.

[0056] Generally, user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP services 176, which may include, for example, the Internet, intranets, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming services, and / or other IP services.

[0057] The BM-SC 170 provides functionality for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or schedule MBMS transmissions. The MBMS Gateway 168 can distribute MBMS services to BS 102 within a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and / or be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0058] 5GC 190 may include various functional components, including: Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196.

[0059] AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides services such as Quality of Service (QoS) flow and session management.

[0060] Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides UE IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0061] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated base stations, decomposed base stations, components of base stations, integrated access and backhaul (IAB) nodes, relay nodes, and sidelink nodes.

[0062] Figure 2An example decomposed base station 200 architecture is depicted. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some specific implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0063] Each unit in a cell (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the cells, or an associated processor or controller that provides instructions to the cell's communication interface, may be configured to communicate with one or more other cells via the transmission medium. For example, these cells may include a wired interface configured to receive signals or transmit signals to one or more other cells via a wired transmission medium. Additionally or alternatively, a cell may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive signals on a wireless transmission medium or transmit signals to one or more other cells, or both.

[0064] In some aspects, CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by CU 210. CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface such as an E1 interface. CU 210 can be implemented to communicate with DU 230 for network control and signaling, as needed.

[0065] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 may at least partially host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0066] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, the RU240 controlled by the DU 230 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration allows the DU 230 and CU 210 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0067] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 205 can be configured to interact with cloud computing platforms such as Open Cloud (O-Cloud) 290 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, SMO framework 205 may communicate with hardware aspects of the 4G RAN, such as Open eNB (O-eNB) 211, via the O1 interface. Additionally, in some implementations, the SMO framework 205 may communicate directly with one or more DU 230s and / or one or more RU 240s via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205.

[0068] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, through data collection and actions, connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

[0069] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 225 and may be received from non-network data sources or network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 205 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0070] Figure 3 Various aspects of examples BS 102 and UE 104 are described.

[0071] Generally, BS 102 includes various processors (e.g., 318, 320, 330, 338, and 340), antennas 334a to 334t (collectively referred to as 334), transceivers 332a to 332t (collectively referred to as 332) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 312) and the wireless reception of data (e.g., data sink 314). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement the various wireless communication-related functions described herein. Note that BS 102 may have the features described herein. Figure 2 The decomposed architecture described.

[0072] Generally, UE 104 includes various processors (e.g., 358, 364, 366, 370, and 380), antennas 352a to 352r (collectively referred to as 352), transceivers 354a to 354r (collectively referred to as 354) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieval from data source 362) and the wireless reception of data (e.g., provision to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement the various wireless communication-related functions described herein.

[0073] Regarding example downlink transmission, BS 102 includes a transmission processor 320 that can receive data from data source 312 and control information from controller / processor 340. This control information may be for a Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid Automatic Repeat Request (HARQ) Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), and / or others. In some examples, this data may be for a Physical Downlink Shared Channel (PDSCH).

[0074] The transmitter processor 320 can process data and control information (e.g., encoding and symbol mapping) to obtain data symbols and control symbols, respectively. The transmitter processor 320 can also generate reference symbols (such as those for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS)).

[0075] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 332a to 332t. Each modulator in transceivers 332a to 332t can process the corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 332a to 332t can be transmitted via antennas 334a to 334t, respectively.

[0076] To receive downlink transmissions, UE 104 includes antennas 352a to 352r that receive downlink signals from BS 102 and provide the received signals to demodulators (DEMODs) in transceivers 354a to 354r, respectively. Each demodulator in transceivers 354a to 354r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0077] The RX MIMO detector 356 acquires received symbols from all demodulators in transceivers 354a to 354r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. The receive processor 358 processes the detected symbols (e.g., demodulation, deinterleaving, and decoding), provides the decoded data of UE 104 to data sink 360, and provides the decoded control information to controller / processor 380.

[0078] Regarding the example uplink transmission, UE 104 further includes a transmission processor 364 that receives and processes data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for Physical Uplink Control Channel (PUCCH)). Transmission processor 364 can also generate reference symbols for reference signals (e.g., for Sounding Reference Signal (SRS)). Symbols from transmission processor 364 may be pre-decoded by TX MIMO processor 366, where applicable, further processed by modulators in transceivers 354a to 354r (e.g., for SC-FDM), and transmitted to BS 102.

[0079] At BS 102, uplink signals from UE 104 can be received by antennas 334a to 334t, processed by demodulators in transceivers 332a to 332t, detected where applicable by RX MIMO detector 336, and further processed by receiver processor 338 to obtain decoded data and control information transmitted by UE 104. Receiver processor 338 can provide the decoded data to data sink 314 and the decoded control information to controller / processor 340.

[0080] Memory 342 and memory 382 can store data and program code for BS 102 and UE 104, respectively.

[0081] Scheduler 344 can schedule UE to send data on the downlink and / or uplink.

[0082] In various respects, BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceivers 332a to 332t, antennas 334a to 334t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 334a to 334t, transceivers 332a to 332t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0083] In various respects, UE 104 can also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a to 354t, antennas 352a to 352t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 352a to 352t, transceivers 354a to 354t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0084] In some respects, the processor can be configured to perform various operations (such as those associated with the methods described herein) and to send (output) data to or receive data from another interface configured to send or receive data, respectively.

[0085] In various aspects, artificial intelligence (AI) processors 318 and 370 may perform AI processing for BS 102 and / or UE 104, respectively. AI processor 318 may include AI accelerator hardware or circuitry, such as one or more neural processing units (NPUs), one or more neural network processors, one or more tensor processors, one or more deep learning processors, etc. AI processor 370 may similarly include AI accelerator hardware or circuitry. As examples, AI processor 370 may perform AI-based beam management, AI-based channel state feedback (CSF), AI-based antenna tuning, and / or AI-based localization (e.g., non-line-of-sight localization prediction). In some cases, AI processor 318 may use hardware-accelerated AI inference and / or AI training to process feedback (e.g., CSF) from UE 104. AI processor 318 may, for example, use hardware-accelerated AI inference associated with CSF to decode compressed CSF from UE 104. In some cases, AI processor 318 may perform certain RAN-based functions, including, for example, network planning, network performance management, energy-efficient network operation, etc.

[0086] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes the use of wireless communication networks (such as Figure 1 All aspects of the data structure of the wireless communication network 100.

[0087] Specifically, Figure 4A Figure 400 is an example of the first subframe within a 5G (e.g., 5G NR) frame structure. Figure 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. Figure 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and Figure 4D Figure 480 illustrates an example of a UL channel within a 5G subframe.

[0088] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single-Carrier Frequency Division Multiplexing (SC-FDM) will (e.g., as...) Figure 4B and Figure 4D The system bandwidth (as depicted in the text) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0089] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0090] exist Figure 4A and Figure 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and X is flexibly used between DL and UL. The UE can be configured using a slot format via a received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may include one or more slots. In some examples, each slot may include 12 or 14 symbols, depending on the Cyclic Prefix (CP) type (e.g., 12 symbols per slot for extended CP, or 14 symbols per slot for regular CP). Subframes may also include micro-slots, which typically have fewer symbols than the entire slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0091] In some respects, the number of time slots within a subframe (e.g., the time slot duration within a subframe) is based on a parameter set that defines the frequency-domain subcarrier spacing and symbol duration, as further described herein. In some respects, given a parameter set μ, each subframe has 2 μ The number of time slots is 1. Therefore, parameter sets (µ) 0 through 6 allow for 1, 2, 4, 8, 16, 32, and 64 time slots per subframe, respectively. In some cases, extended CP (e.g., 12 symbols per time slot) can be used with specific parameter sets; for example, parameter set 2 allows for 4 time slots per subframe. Subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to... kHz, where μ is the parameter set from 0 to 6. As an example, the parameter set... Corresponding to a subcarrier spacing of 15 kHz, and the parameter set This corresponds to a subcarrier spacing of 960 kHz. Symbol length / duration is negatively correlated with subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D It provides a slot format with 14 symbols per slot (e.g., regular CP) and a parameter set with 4 slots per subframe. Example. In this case, the slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0092] like Figure 4A , Figure 4B , Figure 4C and Figure 4D As depicted, the resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme, including, for example, quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM).

[0093] like Figure 4A As illustrated in the example, some REs in the RE carry information for the UE (e.g., Figure 1 and Figure 3 The reference (pilot) signal (RS) for the UE (104) may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0094] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0095] The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identifier.

[0096] The secondary synchronization signal (SSS) can be located within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing.

[0097] Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH Block (SSB) (and in some cases, a Synchronization Signal Block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and / or paging messages.

[0098] like Figure 4C As illustrated, some REs in the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol before the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE104 can transmit a Sounding Reference Signal (SRS). SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0099] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0100] Example of multicarrier operation

[0101] Narrowband Internet of Things (NB-IoT) is a standards-based low-power wide-area (LPWA) technology developed to enable IoT architectures and connect numerous IoT devices via existing mobile networks. NB-IoT can be used to serve large-scale IoT applications and low-complexity IoT devices. NB-IoT can be optimized for services characterized by small, latency-tolerant, and infrequent data transmissions. Furthermore, NB-IoT can be designed to: (1) meet the performance requirements of large-scale IoT in terms of enhanced coverage to support devices deployed in deep indoor environments such as basements; (2) achieve power-efficient operation to facilitate device battery life exceeding ten years; and (3) support a large number of devices transmitting small and infrequent data.

[0102] To enable communication from a large number of devices, NB-IoT supports multi-carrier operation, and more specifically, two types of carriers: anchor carriers and non-anchor carriers. Anchor carriers support cell-defined broadcast transmissions, including RAN synchronization and system information signaling (e.g., SSB and SIB transmissions). Non-anchor carriers can be activated to improve system access and data transmission capacity beyond that provided by anchor carriers. While NB-IoT is introduced as an example use case for multi-carrier operation, it should be noted that multi-carrier operation can also be used in other types of use cases.

[0103] Figure 5A An example wireless communication network 500 supporting multi-carrier operation is depicted (e.g., such as an NB-IoT wireless communication system). As shown in the figure, the wireless communication network 500 (e.g., regarding...) Figure 1 Examples of the wireless communication network 100 depicted and described may include network entities 502 such as BS (e.g., regarding...). Figure 1 and Figure 3 The BS 102 depicted and described or related to Figure 2 Examples of decomposed base stations depicted and described) and UE 504 (e.g., regarding Figure 1 and Figure 3 (Example of UE 104 as depicted and described).

[0104] Network entity 502 can be configured to communicate using multiple different carriers (e.g., specific carrier frequencies, such as FR1, FR2, etc.). For example, network entity 502 is shown as being configured to communicate using anchor carrier 506 and non-anchor carriers 508(1) to 508(3). Thus, network entity 502 can provide coverage in a given cell using each of anchor carrier 506 and non-anchor carriers 508(1) to 508(3). Although network entity 502 is shown as being able to communicate using three non-anchor carriers, it should be noted that network entity 502 can be configured to communicate using any number of non-anchor carriers.

[0105] For example, such as Figure 5B As shown, network entity 502 can provide coverage in anchor cell 510 using anchor carrier 506. Furthermore, network entity 502 can provide coverage in non-anchor cells 516, 518, and 520 using non-anchor carriers 508(1), 508(2), and 508(3), respectively. As shown, non-anchor cells 516, 518, and 520 overlap with anchor cell 510, and anchor cell 510 covers all non-anchor cells 516, 518, and 520. Furthermore, as shown, cells 510 to 520 are not concentric. However, it should be noted that this is merely an example arrangement of anchor and non-anchor cells. In other cases, one or more of the anchor and / or non-anchor cells may be concentric, may have the same coverage area, may overlap in different ways, may not overlap, etc.

[0106] In some respects, anchor carrier 506 may carry all channels (e.g., including broadcast channels) as well as synchronization and system information signaling (e.g., SSB and SIB). For example, SSB / SIB / paging may be continuously supported in anchor cell 510 corresponding to anchor carrier 506. Therefore, the signaling carried in anchor carrier 506 may support cell selection / reselection and / or wake-up signal (WUS) configurations (e.g., C-WUS configuration) for dynamic (e.g., on-demand) SSB / SIB1 transmission in non-anchor cells 516, 518, and / or 520.

[0107] In some respects, unlike anchor carrier 506, non-anchor carriers 508(1) to 508(3) may not transmit common signaling, synchronization signaling, and / or system information signaling. The non-anchor cell associated with non-anchor carrier 508 may be a cell where UE 504 cannot receive such common signaling, synchronization signaling, and / or system information signaling. Therefore, the random access procedure used to establish an RRC connection may only be supported on anchor carrier 506. Thus, in this case, UE 504 may be configured to, for example, initiate a RACH procedure in anchor cell 510 using anchor carrier 506 to initially establish an RRC connection using anchor carrier 506 (instead of one of the non-anchor carriers 508(1) to 508(3)). After establishing an RRC connection using anchor carrier 506, UE 504 may utilize non-anchor carriers 508(1) to 508(3) for unicast services, which may help reduce the use of anchor carrier 506 to carry such services.

[0108] To increase the overall capacity of random access (and in some cases, paging), support for random access procedures can be extended in certain other respects to communication between network entity 502 and UE 504 using non-anchor carriers 508(1) to 508(3) (e.g., while also maintaining support for RACH procedures between UE 504 and network entity 502 using anchor carrier 506). For example, non-anchor carriers 508(1), 508(2), and / or 508(3) can support the transmission of SSBs and / or SIBs (such as SIB1 (e.g., carrying basic information that UE 504 can use to perform initial attachment)) that enable UE 504 to perform RACH procedures using non-anchor carriers 508(1), 508(2), and / or 508(3), respectively.

[0109] Therefore, for specific implementations of multi-carrier systems, different configurations for SSB and SIB1 transmission can be considered, such as... Figure 6 As described in [the text]. Figure 6 As shown, the anchor carrier can support the transmission of SSB 604 and SIB1 606, enabling the UE to receive SSB 604 and SIB1 606 in the anchor cell 602 associated with the anchor carrier. As detailed below, the RACH procedure used by the UE for initial access to the RAN can be initiated by the network entity broadcasting and the UE receiving random access configuration (e.g., in system information within the SSB (or SIB1)). Therefore, by supporting the transmission of SSB 604 and SIB1 606 in anchor cell 602, the UE can be configured to use the anchor carrier associated with anchor cell 602 to perform RACH procedure 608 with the network entity to establish a connection with the RAN.

[0110] In some respects, the UE may additionally or alternatively use a non-anchor carrier to perform the initial attachment to a network entity. Therefore, different configurations for transmitting SSB 614 and SIB 616 in non-anchor cell 612 using a non-anchor carrier can be considered. For example, as... Figure 6 As shown in Table 630, in the first option, the network entity can support "Always On SSB" in non-anchor cell 612, which indicates that the network entity can support transmitting SSB 614 in non-anchor cell 612 at any time using a non-anchor carrier. For example, the network entity can use a non-anchor carrier (such as on a periodic broadcast basis) to transmit SSB 614 in non-anchor cell 612 to allow the UE to perform RACH procedure 618 using the non-anchor carrier associated with non-anchor cell 612. In the second option, the network entity can support "On-Demand SSB" in non-anchor cell 612, which indicates that the network entity can provide SSB in non-anchor cell 612 on demand using a non-anchor carrier. For example, the network entity can use a non-anchor carrier to transmit SSB 614 in non-anchor cell 612 based on received instructions and / or requests, so that the UE can use the non-anchor carrier associated with non-anchor cell 612 to perform RACH procedure 618 with the network entity. In the second option, the anchor carrier associated with anchor cell 602 and the non-anchor carrier associated with non-anchor cell 612 can be in different bands. In the third option, the network entity can support "SSB-less" SSB transmission in non-anchor cell 612 using a non-anchor carrier, indicating that the network entity may not use a non-anchor carrier to provide SSB in non-anchor cell 612. Therefore, the UE may not be able to use a non-anchor carrier in non-anchor cell 612 that supports "SSB-less" SSB transmission to perform RACH procedure 618 with the network entity. In the third option, the anchor carrier associated with anchor cell 602 and the non-anchor carrier associated with non-anchor cell 612 can be in the same band.

[0111] Furthermore, different SIB configurations are provided in Table 632. In the first option, the network entity may support transmitting SIB1 using only the anchor carrier in anchor cell 602. Therefore, transmitting SIB1 in non-anchor cell 612 may not be supported. However, in the second option, the network entity may support "on-demand SIB1" using a non-anchor carrier in non-anchor cell 612, which indicates that the network entity can provide SIBs on demand in non-anchor cell 612. For example, the network entity may transmit SIBs in non-anchor cell 612 using a non-anchor carrier based on (e.g., instructions and / or requests received from the UE), such that the UE can use the non-anchor carrier associated with non-anchor cell 612 to perform RACH procedure 618 with the network entity.

[0112] In addition to anchor cells, providing RACH support in non-anchor cells allows UEs to connect to network entities faster, facilitates load balancing at the network entity, and / or can contribute to increased NES (Network Execution System). For example, offloading RACH procedures to non-anchor cells can help reduce the number of RACH procedures performed via anchor carriers, especially when a large number of devices are supported at the network entity (e.g., for NB-IoT). Therefore, the UE can use a non-anchor carrier to perform RACH procedures instead of waiting a long time to successfully complete the RACH procedure using an anchor carrier, which allows for faster establishment of the connection between the UE and the RAN. Furthermore, since non-anchor cells may support "on-demand SSB / SIB1" instead of "always-on SSB / SIB1," energy can be saved when the network entity is not performing such transmissions.

[0113] Example random access procedure

[0114] Some wireless communication systems (e.g., E-UTRA systems and / or 5G NR systems) provide designated channels (such as RACH) and corresponding random access procedures for random access. For example, a UE can use RACH for initial access to the RAN. The random access procedure can be performed for any of a variety of events, including, for example, initial access from an idle state (e.g., RRC idle), RRC connection re-establishment, handover, downlink and / or uplink data arrival (e.g., when the UE is idle), or device location. As described above, a UE can perform the RACH procedure for initial access to the RAN in either an anchor cell or a non-anchor cell.

[0115] Figure 7A A flowchart illustrating an example four-step RACH procedure 700a performed between UE 704 and network entity 702 is provided. In some respects, UE 704 is about... Figure 1 and Figure 3 The UE 104 described and depicted, and network entity 702 are about Figure 1 and Figure 3 The base station 102 depicted and described or about Figure 2 The decomposed base station depicted and described. In some aspects, the four-step RACH procedure 700a can be performed in the anchor cell associated with network entity 702. In some aspects, the four-step RACH procedure 700a can be performed in the non-anchor cell associated with network entity 702.

[0116] The RACH procedure 700a may optionally begin at 706, where network entity 702 broadcasts and UE 704 receives the random access configuration, for example, in system information within a synchronization signal block or within an RRC message. The random access configuration may indicate or include one or more parameters for random access communication, such as defining the RACH, the number of random access preambles (e.g., preamble sequences) available for random access, power ramp parameters, response window size, etc.

[0117] At 708, UE 704 transmits a first message (MSG1) to network entity 702 on the Physical Random Access Channel (PRACH). In some aspects, MSG1 may indicate or include a RACH preamble. The RACH preamble may indicate or include a preamble signature associated with the RACH preamble. The preamble signature may correspond to a specific preamble sequence (e.g., a Zadoff Chu sequence) generated across the time-frequency resources used for preamble transmission. For contention-based random access, a preamble sequence may be randomly selected from a set of preamble sequences (e.g., in some cases, up to 64 sequences). The preamble signature can be used to identify UE 704 for scheduling communications with network entities (e.g., MSG2 and MSG3). The term "RACH preamble" may refer to or correspond to "random access preamble," "preamble," "preamble sequence," and / or "preamble signature."

[0118] At 710, network entity 702 may respond with a Random Access Response (RAR) message (MSG2). For example, network entity 702 may transmit PDCCH communication including downlink control information (DCI) that schedules the RAR on the PDSCH. The RAR may include, for example, certain parameters for uplink transmission, such as a Random Access (RA) preamble identifier (RAPID), timing advance, uplink (UL) grant (e.g., indicating one or more time-frequency resources for uplink transmission), cell radio network temporary identifier (C-RNTI), and backoff parameter values. The RAPID may correspond to a preamble signature and indicate that the RAR is for UE 704 transmitting MSG1 at 706. As an example, the RAPID may identify a specific frequency resource used for preamble transmission. As further described herein, the backoff parameter value may be used to determine the RACH timing for transmitting subsequent RACH transmissions (e.g., preamble transmissions). The RACH timing may correspond to one or more time-frequency resources available for transmitting the preamble in the RACH.

[0119] At 712, in response to MSG2, UE 704 sends a third message (MSG3) on the PUSCH to network entity 702. In some aspects, MSG3 may include an RRC connection request, a tracking area update (e.g., for UE mobility), and / or a scheduling request (for UL transmission). As an example, MSG 3 uses the time-frequency resources indicated in the UL approval of the RAR.

[0120] At 714, network entity 702 may respond to MSG3 by transmitting a contention resolution message (MSG4). In some cases, if UE 704 is unable to receive or decode MSG3 and / or MSG4, UE 704 may repeat the RACH procedure, such as the four-step RACH procedure 700a.

[0121] In some cases, a two-step RACH procedure can be used to reduce latency associated with random access. As the name suggests, a two-step RACH procedure can effectively merge the four messages of a four-step RACH procedure into two messages.

[0122] Figure 7B A flowchart illustrating an example two-step RACH procedure 700b performed between UE 704 and network entity 702 is provided. Similar to the four-step RACH procedure 700a, in some respects, the two-step RACH procedure 700b can be performed in an anchor cell associated with network entity 702. Furthermore, in some respects, the two-step RACH procedure 700b can be performed in a non-anchor cell associated with network entity 702.

[0123] The two-step RACH procedure 700b may optionally begin at 750, where network entity 702 broadcasts and UE 704 receives the random access configuration, for example, in system information within a synchronization signal block or in an RRC message.

[0124] At 752, UE 704 transmits a first message (MSGA) to network entity 702, which effectively combines the above-mentioned... Figure 7A The MSG1 and MSG3 are described. In some aspects, the MSGA includes a RACH preamble and a payload for random access. For example, the payload may include the UE-ID and other signaling information, such as buffer status reports or scheduling requests. For example, the RACH preamble of the MSGA may be transmitted on the RACH, and the payload of the MSGA may be transmitted on the PUSCH.

[0125] At 754, network entity 702 may transmit a Random Access Response Message (MSGB), which can effectively combine MSG2 and MSG4 described above. For example, the MSGB may include RAPID, timing advance, backoff parameter values, contention resolution messages, uplink and / or downlink grant and transmit power control commands.

[0126] As described herein, in some respects, to gain initial access to the RAN, UE 704 may perform a four-step RACH procedure 700a or a two-step RACH procedure 700b in a non-anchor cell of network entity 702. In some cases, the four-step RACH procedure 700a or the two-step RACH procedure 700b may fail due to RF interference, poor signal quality, and / or weak coverage in the non-anchor cell. Therefore, techniques for handling RACH procedure failures in non-anchor cells may be desired.

[0127] Furthermore, in order to perform a four-step RACH procedure 700a or a two-step RACH procedure 700b in a non-anchor cell of network entity 702, UE 704 may need to utilize one or more RACH timings to be configured, which correspond to one or more resources available for transmitting RACH during the RACH procedure. In some respects, RACH timings may not be configured for UE 704's active uplink BWP.

[0128] Specifically, a BWP is a designated portion of the total bandwidth of a carrier (e.g., an anchor carrier and / or a non-anchor carrier). UE 704 can be configured to utilize one or more downlink BWPs and one or more uplink BWPs per cell. To conserve power at UE 704, one downlink BWP and one uplink BWP configured for a cell at UE 704 can be active at UE 704 at a given time (e.g., while other BWPs are deactivated). In some respects, the active uplink BWP of UE 704 is the uplink BWP of the non-anchor cell of network entity 702, and this active uplink BWP may not include any configured RACH timing to enable UE 704 to send a RACH preamble and thereby initiate a RACH procedure in the non-anchor cell to obtain initial access to the RAN. Therefore, techniques for handling cases where the RACH timing is not configured for the non-anchor cell and the uplink BWP active for UE 704 is available, enabling the UE to obtain initial access to the RAN.

[0129] Aspects related to RACH process improvement in non-anchor cells

[0130] The aspects described in this paper introduce techniques for carrier switching and / or BWP switching for the RACH process to handle the scenarios described above.

[0131] For example, when a RACH procedure initiated between the UE and the network entity using a non-anchor carrier associated with a non-anchor cell of the network entity fails, carrier handover techniques can be used. Carrier handover may include switching from performing a failed RACH procedure in a non-anchor cell of the network entity to performing another RACH procedure in (1) an anchor cell of the network entity or (2) another non-anchor cell of the network entity to establish an RRC connection.

[0132] In some cases, carrier handover can be used to reduce latency associated with initial access. For example, a UE initially performing RACH in a non-anchor cell can determine whether to handover to another cell to perform RACH after a threshold time period has elapsed since the start of the RACH procedure. Handover based on this threshold time period can help reduce latency associated with multiple devices (e.g., UEs) attempting to perform RACH in the same cell (e.g., the same non-anchor cell) of a network entity. Furthermore, this carrier handover approach provides flexibility for the UE to select the next cell to perform the RACH procedure after the first RACH procedure has failed by allowing the UE to choose between multiple anchor and / or non-anchor cells (where multiple non-anchor cells are configured to support the execution of the RACH procedure). This flexibility allows the UE to select the cell that provides the fastest connection to the RAN (compared to performing the RACH procedure in one of the other cells).

[0133] Furthermore, when a RACH timing is not configured for the UE's active uplink BWP, the BWP handover technique described herein can be used. BWP handover may involve switching the active uplink BWP for the UE from a first uplink BWP to a second uplink BWP based on the fact that the first uplink BWP does not include any RACH timing for performing the RACH procedure. In some cases, the active uplink BWP for the UE that does not include any RACH timing (e.g., the first uplink BWP) is the active uplink BWP of a non-anchor cell of a network entity. In this case, the UE may switch its active uplink BWP to another uplink BWP in the same non-anchor cell (e.g., the first option for the second uplink BWP) or to the initial uplink BWP of the anchor cell of the network entity (e.g., the second option for the second uplink BWP) and use the newly activated uplink BWP to perform the RACH procedure. This BWP handover method provides the UE with different options for performing RACH when the UE's current active uplink BWP does not support the UE performing RACH in a specific cell (e.g., without RACH timing).

[0134] In some respects, the techniques described herein also enable the UE to notify the network entity of its ability to support non-anchor cell operation. After the UE establishes an RRC connection with the network entity, the network entity can use this information to offload services between the network entity and the UE from the anchor cell to the network entity's non-anchor cell.

[0135] Example operations of entities used for carrier switching in a communication network

[0136] Figure 8 A process flow 800 for communication in a network between network entity 802 and UE 804 is described. In some aspects, network entity 802 may be related to... Figure 1 and Figure 3 The BS 102 depicted and described or related to Figure 2 Examples of decomposed base stations depicted and described. Similarly, UE 804 could be about... Figure 1 and Figure 3 Examples of UE104 depicted and described herein. However, in other respects, UE 804 may be another type of wireless communication device, and network entity 802 may be another type of network entity or network node, such as those described herein.

[0137] In some respects, network entity 802 supports communication using an anchor carrier associated with anchor cell 806 of network entity 802, a first non-anchor carrier associated with a first non-anchor cell 808(1) of network entity 802, and a second non-anchor carrier associated with a second non-anchor cell 808(2) of network entity 802. In some respects, anchor cell 806, the first non-anchor cell 808(1), and the second non-anchor cell 808(2) support RACH procedures (e.g., such as regarding...). Figure 7A and Figure 7B The four-step RACH process 700a and / or the two-step RACH process 700b are depicted and described. That is, UE 804 can perform the RACH process in anchor cell 806 using an anchor carrier, in first non-anchor cell 808(1) using a first non-anchor carrier, and / or in second non-anchor cell 808(2) using a second non-anchor carrier. Specifically, in process flow 800, UE 804 can switch from performing the first RACH process in first non-anchor cell 808(1) using the first non-anchor carrier to performing the second RACH process in anchor cell 806 using an anchor carrier or in second non-anchor cell 808(2) using the second non-anchor carrier.

[0138] like Figure 8As shown, process flow 800 begins at 820, where UE 804 sends a first random access signal to initiate a first RACH procedure in the first non-anchor cell 808(1) of network entity 802. UE 804 may use a first non-anchor carrier to send the first random access signal in the first non-anchor cell 808(1).

[0139] In some respects, before transmitting the first random access signal at 820, UE 804 may receive one or more reference signals (RS) (e.g., such as SSB, discovery reference signal, etc.) from network entity 802 in second non-anchor cell 808(2) on a second non-anchor carrier at 812. At 814, UE 804 may receive one or more RS from network entity 802 in first non-anchor cell 808(1) on a first non-anchor carrier. Furthermore, at 816, UE 804 may receive one or more RS from network entity 802 in anchor cell 806 on an anchor carrier. Although Figure 8 The transmission of RS is depicted in all cells of anchor cell 806, first non-anchor cell 808(1), and second non-anchor cell 808(2), but in some other examples, RS may be transmitted in less than all of these cells (e.g., only anchor cell 806 and first non-anchor cell 808(1)). Furthermore, although Figure 8 The text describes the transmission of RS in anchor cell 806, first non-anchor cell 808(1), and second non-anchor cell 808(2) at different times and in the order of second non-anchor cell 808(2), first non-anchor cell 808(1), and anchor cell 806(3). However, in some other examples, RS can be transmitted simultaneously and / or in conjunction with... Figure 8 The RS is sent in different orders as shown.

[0140] At 818, UE 804 can measure the received RS. UE 804 can determine the RACH procedure to be performed in the first non-anchor cell 808(1) based on one or more of these measurements.

[0141] For example, in some respects, when communicating with network entity 802 in a first non-anchored cell 808(1) using a first non-anchored carrier, UE 804 may measure one or more RSs received in the first non-anchored cell 808(1) to determine one or more channel conditions (e.g., reference signal received power (RSRP), signal-to-noise ratio (SNR), channel quality, etc.). Similarly, when communicating with network entity 802 in a second non-anchored cell 808(2) using a second non-anchored carrier, UE 804 may measure one or more RSs received in the second non-anchored cell 808(2) to determine one or more channel conditions. Furthermore, when communicating with network entity 802 in an anchored cell 806 using an anchored carrier, UE 804 may measure one or more RSs received in the anchored cell 806 to determine one or more channel conditions. UE 804 may determine the RACH procedure to be performed in the first non-anchored cell 808(1) based on one or more channel conditions (e.g., when the RSRP for communication using the first non-anchored carrier is greater than the RSRP for communication using the second non-anchored carrier and / or the RSRP for communication using the anchored carrier).

[0142] As another example, in some respects, when communicating with network entity 802 in a first non-anchored cell 808(1) using a first non-anchored carrier, UE 804 may measure one or more RSs received in the first non-anchored cell 808(1) to determine one or more channel conditions, such as signal quality. UE 804 may determine to perform a RACH procedure in the first non-anchored cell 808(1) based on the determined channel conditions satisfying one or more thresholds (e.g., the determined signal quality satisfying (e.g., greater than) a threshold signal quality).

[0143] In some respects, before transmitting the first random access signal at 820, UE 804 may receive at 810 an instruction to perform a first RACH procedure in the first non-anchored cell 808(1) using a first non-anchored carrier. Based on this instruction, UE 804 may determine to perform the first RACH procedure in the first non-anchored cell 808(1), and thus transmit the first random access signal at 820 on the first non-anchored carrier associated with the first non-anchored cell 808(1).

[0144] After the first random access signal is transmitted in the first non-anchor cell 808(1) at 820, the RACH procedure in the first non-anchor cell 808(1) can be started, and a timer can be started. The timer can indicate the maximum duration for which the RACH procedure is permitted to be performed in the first non-anchor cell 808(1). t Therefore, when the timer is started, it can count down from that maximum time amount. If the timer expires (for example, when set to...), tIf the RACH procedure in the first non-anchor cell 808(1) has not yet been completed, then UE 804 may perform a carrier handover to initiate another RACH procedure in the second non-anchor cell 808(2) using the anchor carrier or using the second non-anchor carrier. In some respects, the time duration ( t The reception time duration ( ) is fixed. In some respects, the UE804 reception time duration ( ) t Configuration of () Figure 8 (Not shown in the image).

[0145] for Figure 8 In the example, the RACH procedure initiated in the first non-anchor cell 808(1) may not be completed before the timer expires (e.g., it may take longer than the timer expires). t (Not completed within ) Therefore, at 822, UE 804's RACH-based procedure failed to complete within the time duration ( t The RACH process in the first non-anchor cell 808(1) was successfully completed but failed.

[0146] Based on the time duration after the first RACH procedure failed to complete following the transmission of the first random access signal ( t Successfully completed within ) , UE 804 can perform carrier handover. One or more options are available for performing carrier handover. For example, in Figure 8 In the first option shown, UE 804 can switch to performing the RACH procedure in another non-anchor cell of network entity 802 (such as a second non-anchor cell 808(2)). Alternatively, in Figure 8 In the second option shown, UE 804 can switch to performing the RACH procedure in anchor cell 806 of network entity 802.

[0147] In Option 1, switching from performing the first RACH procedure in the first non-anchor cell 808(1) to performing the second RACH procedure in the second non-anchor cell 808(2) may include UE 804 using a second non-anchor carrier at 824 to transmit a second random access signal to initiate the second RACH procedure in the second non-anchor cell 808(2). After the transmission of the second random access signal, the second RACH procedure in the second non-anchor cell 808(2) may begin establishing an RRC connection between UE 804 and network entity 802 (e.g., at 826).

[0148] In option 2, switching from performing the first RACH procedure in the first non-anchor cell 808(1) to performing the second RACH procedure in the anchor cell 806 may include UE 804 using an anchor carrier at 828 to transmit a second random access signal to initiate the second RACH procedure in the anchor cell 806. After the transmission of the second random access signal, the second RACH procedure in the anchor cell 806 may begin establishing an RRC connection between UE 804 and network entity 802 (e.g., at 830).

[0149] In some respects, after establishing an RRC connection between UE 804 and network entity 802 using option 2, UE 804 may report its ability to support non-anchor cell operation to network entity 802. For example, at 832, UE 804 sends an indication of its ability to support non-anchor cell operation. UE 804 may send this indication in anchor cell 806 using an anchor carrier. In some cases, UE 804 may send this indication via an RRC message after successfully completing the second RACH procedure in anchor cell 806.

[0150] In some respects, UE 804 may send an indication to network entity 802 of its ability to support non-anchor cell operation before successfully completing the second RACH procedure in anchor cell 806. For example, UE 804 may send this indication via a message about the second RACH procedure performed in anchor cell 806 in option 2. In some respects, the message about the second RACH procedure may be a second random access signal sent by UE 804 at 828. In some respects, the message about the second RACH procedure may be MSG1 and / or MSG3 (e.g., such as regarding...) sent by UE 804 during the second RACH procedure. Figure 7A The MSG1 and MSG3 described and illustrated.

[0151] In some other respects, the capability of UE 804 may be implied by UE 804 attempting to use a first non-anchor carrier to initially perform a first RACH procedure with a first non-anchor cell 808(1) (e.g., at 820). Therefore, UE 804 may not need to transmit an indication to network entity 802 of UE 804's ability to support non-anchor cell operation.

[0152] In some respects, UE 804 is based on one or more measurements determined at 818 and / or on the performance of one or more other measurements. Figure 8(Not shown in the image) to determine whether to perform option 1 or option 2 for carrier handover. For example, in some respects, after determining at 822 that the first RACH procedure has failed, UE 804 may again receive and measure RS in anchor cell 806 on the anchor carrier and / or second non-anchor cell 808 (2) on the second non-anchor carrier. UE 804 may base its measurement on the measurement determined at 818 and / or the new measurement obtained after determining that the first RACH procedure has failed ( Figure 8 (not shown) to determine whether to perform the second RACH procedure in the second non-anchor cell 808(2) (e.g., option 1) or to determine whether to perform the second RACH procedure in the anchor cell 806 (e.g., option 2).

[0153] For example, UE 804 may determine whether to perform a second RACH procedure in the second non-anchor cell 808(2) (e.g., option 1) rather than in the anchor cell 806 (e.g., option 2) based on one or more channel conditions (e.g., RSRP, SNR, channel quality, etc.) determined according to the measured RS being better (or vice versa) for the second non-anchor cell 808(2) than for the anchor cell 806. As another example, UE 804 may determine whether to perform a second RACH procedure in the second non-anchor cell 808(2) (e.g., option 1) based on one or more channel conditions (e.g., RSRP, SNR, channel quality, etc.) determined according to the measured RS in the second non-anchor cell 808(2) meeting a threshold (e.g., signal quality meets a threshold signal quality). Similarly, UE 804 may determine whether to perform a second RACH procedure in the anchor cell 806 (e.g., option 2) based on one or more channel conditions (e.g., signal quality meets a threshold signal quality) determined according to the measured RS in the anchor cell 806.

[0154] Example operations of entities used in communication networks to indicate the ability to support non-anchor cell operations.

[0155] although Figure 8 An example scenario is described where two RACH procedures are initiated because the first RACH procedure in the non-anchor cell fails to complete successfully within time duration (t). However, in some other example scenarios, the first RACH procedure may not fail, whether initiated in the anchor cell or the non-anchor cell. Therefore, the UE may execute only one RACH procedure to establish an RRC connection with the network entity. Executing a RACH procedure in a non-anchor cell implicitly indicates the UE's ability to support non-anchor cell operation. However, executing a RACH procedure in the anchor cell may not implicitly indicate the UE's ability to support non-anchor cell operation. Therefore, the UE may transmit an indication of its ability to support non-anchor cell operation on the anchor carrier in the anchor cell.

[0156] Figures 9A to 9BThe process flow 900a and 900b for communication between network entity 902 and UE 904 in the network are described. Figure 9A The process flow 900a describes the communication between network entity 902 and UE 904 to perform the RACH procedure in the non-anchor cell of network entity 902 (e.g., the first non-anchor cell 908(1)). Figure 9B The process flow 900b describes the communication between network entity 902 and UE 904 to perform the RACH procedure in anchor cell 906 of network entity 902.

[0157] In some respects, a network entity 902 can be about Figure 1 and Figure 3 The BS 102 depicted and described or related to Figure 2 Examples of decomposed base stations depicted and described. Similarly, UE 904 could be about... Figure 1 and Figure 3 Examples of UE 104 depicted and described herein. However, in other respects, UE 904 may be another type of wireless communication device, and network entity 902 may be another type of network entity or network node, such as those described herein.

[0158] In some respects, network entity 902 supports communication using an anchor carrier associated with anchor cell 906 of network entity 902, a first non-anchor carrier associated with a first non-anchor cell 908(1) of network entity 902, and a second non-anchor carrier associated with a second non-anchor cell 908(2) of network entity 902. In some respects, anchor cell 906, the first non-anchor cell 908(1), and the second non-anchor cell 908(2) support RACH procedures (e.g., such as regarding...). Figure 7A and Figure 7B The four-step RACH procedure 700a and / or the two-step RACH procedure 700b are depicted and described. That is, UE 904 may perform the RACH procedure in anchor cell 906 using an anchor carrier, in first non-anchor cell 908(1) using a first non-anchor carrier, and / or in second non-anchor cell 908(2) using a second non-anchor carrier.

[0159] exist Figure 9A In process flow 900a, UE 904 performs the RACH procedure in the first non-anchored cell 908(1) using the first non-anchored carrier. Figure 9AAs shown, process flow 900a begins at 920, where UE 904 sends a random access signal to initiate a RACH procedure in the first non-anchor cell 908(1) of network entity 902. UE 904 may send the random access signal on a first non-anchor carrier associated with the first non-anchor cell 908(1). After sending the random access signal on the first non-anchor carrier at 920, the RACH procedure in the first non-anchor cell 908(1) may begin to establish an RRC connection between UE 904 and network entity 902 (e.g., at 922). Figure 9A In the example, the RACH process initiated in the first non-anchor cell 908(1) may be successful.

[0160] Further for Figure 9A The example in the text suggests that UE 904 supports non-anchor cell operation based on UE 904 performing a RACH procedure in the first non-anchor cell 908(1) using the first non-anchor carrier. Therefore, UE 904 may not need to transmit an indication of this capability of UE 904 to network entity 902.

[0161] exist Figure 9B In process flow 900b, UE 904 uses the anchor carrier to perform the RACH procedure in anchor cell 906. For example... Figure 9B As shown, process flow 900b begins at 930, where UE 904 sends a random access signal to initiate a RACH procedure in anchor cell 906 of network entity 902. UE 904 may send the random access signal on the anchor carrier associated with anchor cell 906. After sending the random access signal on the anchor carrier at 930, the RACH procedure in anchor cell 906 may begin to establish an RRC connection between UE 904 and network entity 902 (e.g., at 932). Figure 9B In the example, the RACH procedure initiated in anchor cell 906 may be successful.

[0162] Further for Figure 9B The example in the text can indicate to network entity 902 the ability of UE 904 to support non-anchor cell operation. In some aspects, such as Figure 9B As shown, at 934, UE 904 can send an indication via RRC message after successfully completing the RACH procedure in anchor cell 906.

[0163] In some other aspects, UE 904 may send an indication to network entity 902 of its ability to support non-anchor cell operation before successfully completing the RACH procedure in anchor cell 906. For example, UE 904 may send this indication via a message from the RACH procedure performed in anchor cell 906. In some aspects, the RACH procedure message may include a random access preamble. In some aspects, the RACH procedure message may be MSG1 and / or MSG3 (e.g., such as information about...) sent by UE 904 during the RACH procedure. Figure 7A The MSG1 and MSG3 described and illustrated.

[0164] In some aspects, the indication of UE 904's ability to support non-anchor cell operation includes an indication of UE 904's ability to support non-anchor cell operation by frequency bands in one or more frequency bands. In other aspects, the indication of UE 904's ability to support non-anchor cell operation includes an indication of UE 904's ability to support non-anchor cell operation by frequency band groups in one or more frequency band groups. For example, UE 904 may support non-anchor cell operation only in certain frequency bands or frequency band groups, and thus indicates which frequency bands or frequency band groups UE 904 supports and does not support non-anchor cell operation for. A frequency band group may be a contiguous group or set of frequency bands that are frequency-contiguous, or it may include frequency bands that are frequency-discontinuous.

[0165] Example operation of entities used for BWP handover in a communication network

[0166] As mentioned above Figure 7A and Figure 7B As described, when the UE determines that it is performing RACH with a network entity in an anchor cell or a non-anchor cell, the UE may transmit one or more RACH transmissions (e.g., RACH preamble transmissions) to the network entity. The UE may transmit RACH transmissions at one or more RACH timings configured at the UE.

[0167] For example, the UE can receive configuration for one or more RACH timings for transmitting RACH. RACH timings can be configured for different UL BWPs configured at the UE. As an illustrative example, a UE attempting to establish a connection with a network entity can communicate with the network entity in an anchor cell associated with an anchor carrier and in one or more non-anchor cells associated with one or more non-anchor carriers of the network entity. While not intended to be restrictive, in this example, the UE can communicate with the network entity in one anchor cell and one non-anchor cell. The UE can be configured using one or more uplink BWPs for the anchor cell and one or more uplink BWPs for the non-anchor cells. RACH timings can be configured for the uplink BWPs configured for the anchor cell and / or for the uplink BWPs configured for the non-anchor cells.

[0168] In some respects, fewer than all uplink BWPs configured for non-anchor cells can be configured using RACH timings. Therefore, in some cases, an uplink BWP for a non-anchor cell that is activated for the UE when communicating in a non-anchor cell may not include any RACH timings. Without RACH timings, the UE may be unable to transmit RACH and therefore may be unable to perform the RACH procedure to gain initial access to the RAN. To address such scenarios, the aspects described herein allow the UE to perform BWP handover.

[0169] For example, a UE can switch its active uplink BWP from a first uplink BWP to a second uplink BWP to perform a RACH procedure. The first uplink BWP can be an uplink BWP of a non-anchor cell that does not include any configured RACH timings. The second uplink BWP that the UE switches to and activates from the first uplink BWP can be (1) another uplink BWP of the same non-anchor cell that includes the first uplink BWP, or (2) the initial uplink BWP of the anchor cell. The second uplink BWP can include one or more RACH timings for transmitting RACH. Therefore, the UE can use the second uplink BWP to perform a RACH procedure.

[0170] In some cases, the second uplink BWP belonging to the same non-anchor cell as the first uplink BWP is the uplink BWP that the UE is instructed to use for the RACH procedure. For example, the UE may receive an indication of a second uplink BWP designated for use in a non-anchor cell RACH procedure.

[0171] In some cases where the second uplink BWP is the initial uplink BWP (e.g., when the UE switches to the initial uplink BWP using the anchor cell), the UE may perform a cell handover to perform the RACH procedure in the anchor cell instead of the non-anchor cell.

[0172] Example Operation

[0173] Figure 10 It shows a device (such as) Figure 1 and Figure 3 Method 1000 for wireless communication of UE 104.

[0174] Method 1000 begins at block 1005, wherein a first random access signal is transmitted on a first non-anchor carrier associated with a first non-anchor cell of a network entity to initiate a first RACH procedure in the first non-anchor cell.

[0175] Then, method 1000 proceeds to block 1010, wherein, based on the failure of the first RACH procedure to be successfully completed within the time duration following the transmission of the first random access signal, a second random access signal is transmitted on an anchor carrier associated with the anchor cell of the network entity or a second non-anchor carrier associated with the second non-anchor cell of the network entity to initiate a second RACH procedure in the anchor cell or the second non-anchor cell.

[0176] In some respects, method 1000 also includes receiving one or more RSs associated with the second non-anchor carrier.

[0177] In some respects, method 1000 also includes measuring one or more RS to determine the signal quality of the second non-anchor carrier.

[0178] In some aspects, block 1010 includes transmitting a second random access signal on a second non-anchor carrier based on the signal quality of the second non-anchor cell satisfying a threshold signal quality, in order to initiate a second RACH procedure in the second non-anchor cell.

[0179] In some respects, block 1010 includes transmitting a second random access signal on the anchor carrier based on the signal quality of the second non-anchor cell not meeting a threshold signal quality, in order to initiate a second RACH procedure in the anchor cell.

[0180] In some respects, method 1000 also includes sending an indication of the device's ability to support non-anchor cell operation.

[0181] In some respects, sending an indication includes sending an indication via an RRC message after the second RACH procedure has been successfully completed in the anchor cell.

[0182] In some respects, sending instructions includes sending instructions via messages through a second RACH process.

[0183] In some respects, the messages of the second RACH procedure include a second random access signal.

[0184] In some respects, indications of the device’s ability to support non-anchor cell operation include corresponding indications of the device’s ability to support non-anchor cell operation by frequency bands in one or more frequency bands or by frequency band groups in one or more frequency band groups.

[0185] In some respects, the duration of time is fixed.

[0186] In some respects, method 1000 also includes configuration for receiving time duration.

[0187] In some aspects, method 1000 further includes receiving one or more RSs. In some aspects, method 1000 further includes measuring one or more RSs to determine the signal quality of the first non-anchor cell. In some aspects, block 1005 includes transmitting a first random access signal on a first non-anchor carrier based on the signal quality of the first non-anchor cell to initiate a first RACH procedure in the first non-anchor cell.

[0188] In some aspects, method 1000 further includes receiving an instruction for performing a first RACH procedure in a first non-anchored cell. In some aspects, block 1005 includes transmitting a first random access signal on a first non-anchored carrier based on the instruction to initiate a first RACH procedure in the first non-anchored cell.

[0189] In some respects, method 1000 or any aspect thereof may be made by means of a device (such as...) Figure 13 The communication device 1300 performs the operation, and the device includes various components capable of operating, configured, or adapted to perform the method 1000. The communication device 1300 is described in further detail below.

[0190] It should be noted that Figure 10 This is merely one example of a method, and other methods that include fewer, additional, or alternative operations may also be consistent with this disclosure.

[0191] Figure 11 It shows a device (such as) Figure 1 and Figure 3 Method 1100 for wireless communication of UE 104.

[0192] Method 1100 begins at block 1105, wherein configuration of one or more RACH timings is received, wherein one or more RACH timings are not configured for the active uplink BWP of the device, wherein the active uplink BWP is the first uplink BWP of the non-anchor cell of the network entity.

[0193] Then, method 1100 proceeds to block 1110, wherein based on one or more RACH timings not being configured for an active uplink BWP, the device's active uplink BWP is switched from a first uplink BWP to a second uplink BWP, wherein the second uplink BWP includes: another uplink BWP for a non-anchor cell; or the initial uplink BWP for an anchor cell of a network entity.

[0194] Then, method 1100 proceeds to block 1115, where the second uplink BWP is used as the active uplink BWP for the device to perform the RACH procedure.

[0195] In some respects, method 1100 also includes receiving an indication that another uplink BWP is designated for use in a non-anchor cell RACH procedure.

[0196] In some respects, the second uplink BWP includes the initial uplink BWP; and box 1115 includes performing the RACH procedure in the anchor cell.

[0197] In some respects, one or more RACH timings are configured for the second uplink BWP.

[0198] In some respects, the second uplink BWP includes the initial uplink BWP of the anchor cell; and method 1100 further includes sending an indication of the device's ability to support non-anchor cell operation.

[0199] In some respects, sending an indication includes sending an indication via an RRC message after the RACH procedure has been successfully completed.

[0200] In some respects, sending instructions includes sending instructions via messages through the RACH procedure.

[0201] In some respects, the messages in the RACH procedure include a random access preamble.

[0202] In some respects, indications of the device’s ability to support non-anchor cell operation include corresponding indications of the device’s ability to support non-anchor cell operation by frequency bands in one or more frequency bands or by frequency band groups in one or more frequency band groups.

[0203] In some respects, method 1100 or any aspect thereof may be made by means of a device (such as...) Figure 13 The communication device 1300 performs the operation, and the device includes various components capable of operating, configured, or adapted to perform the method 1100. The communication device 1300 is described in further detail below.

[0204] It should be noted that Figure 11 This is merely one example of a method, and other methods that include fewer, additional, or alternative operations may also be consistent with this disclosure.

[0205] Figure 12 It shows a device (such as) Figure 1 and Figure 3 Method 1200 for wireless communication of UE 104.

[0206] Method 1200 begins at box 1205, in which the RACH procedure is performed in the anchor cell of the network entity.

[0207] Then, method 1200 proceeds to block 1210, where an indication is sent regarding the device's ability to support non-anchor cell operation.

[0208] In some respects, frame 1210 includes sending an indication via an RRC message after the RACH procedure has been successfully completed in the anchor cell.

[0209] In some respects, box 1210 includes sending instructions via messages from the RACH process.

[0210] In some respects, the messages in the RACH procedure include a random access preamble.

[0211] In some respects, indications of the device’s ability to support non-anchor cell operation include corresponding indications of the device’s ability to support non-anchor cell operation by frequency bands in one or more frequency bands or by frequency band groups in one or more frequency band groups.

[0212] In some respects, method 1200 or any aspect thereof may be made possible by means of a device (such as...) Figure 13 The communication device 1300 performs the operation, and the device includes various components capable of operating, configured, or adapted to perform the method 1200. The communication device 1300 is described in further detail below.

[0213] It should be noted that Figure 12 This is merely one example of a method, and other methods that include fewer, additional, or alternative operations may also be consistent with this disclosure.

[0214] Example communication device

[0215] Figure 13 Various aspects of the example communication device 1300 are described. In some aspects, the communication device 1300 is user equipment, such as those described above. Figure 1 and Figure 3 The UE 104 described.

[0216] Communication device 1300 includes a processing system 1305 coupled to a transceiver 1375 (e.g., a transmitter and / or receiver). Transceiver 1375 is configured to transmit and receive signals for communication device 1300 via antenna 1380, such as various signals as described herein. Processing system 1305 may be configured to perform processing functions for communication device 1300, including processing signals received by and / or to be transmitted by communication device 1300.

[0217] Processing system 1305 includes one or more processors 1310. In various aspects, the one or more processors 1310 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as per [reference to...]. Figure 3As described. One or more processors 1310 are coupled to a computer-readable medium / memory 1340 via a bus 1370. In some aspects, the computer-readable medium / memory 1340 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1310, enable the one or more processors 1310 to execute and cause the one or more processors to perform: regarding Figure 10 The described method 1000 or any aspect thereof, including regarding Figure 10 Any operation described; regarding Figure 11 The described method 1100 or any aspect thereof, including regarding Figure 11 Any operation described; and regarding Figure 12 The described method 1200 or any aspect thereof, including regarding Figure 12 Any operation described. Note that references to processors performing the functions of communication device 1300 may include one or more processors, such as performing the functions of communication device 1300 in a distributed manner.

[0218] In the depicted example, computer-readable medium / memory 1340 stores code 1345 for transmitting, code 1350 for receiving, code 1355 for measuring, code 1360 for switching, and code 1365 for executing. Processing of codes 1345 to 1365 enables communication device 1300 to execute and allows the communication device to perform: regarding Figure 10 The described method 1000 or any aspect thereof; regarding Figure 11 The described method 1100 or any aspect thereof; and regarding Figure 12 The method 1200 described or any aspect thereof.

[0219] One or more processors 1310 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1340, including circuitry 1315 for transmitting, circuitry 1320 for receiving, circuitry 1325 for measuring, circuitry 1330 for switching, and circuitry 1335 for execution. Processing using circuitry 1315 to 1335 enables communication device 1300 to execute and allows the communication device to perform: regarding Figure 10 The described method 1000 or any aspect thereof; regarding Figure 11 The described method 1100 or any aspect thereof; and regarding Figure 12 The method 1200 described or any aspect thereof.

[0220] More generally, components used for communication, sending, transmitting, or outputting for transmission may include Figure 3 The UE104 illustrated includes a transceiver 354, an antenna 352, a transmit processor 364, a TX MIMO processor 366, an AI processor 370, and / or a controller / processor 380. Figure 13 The transceiver 1375 and / or antenna 1380 of the communication device 1300 in the middle Figure 13 One or more processors 1310 of the communication device 1300. Components for communicating, receiving, or acquiring may include... Figure 3 The UE 104 illustrated includes a transceiver 354, an antenna 352, a receiver processor 358, an AI processor 370, and / or a controller / processor 380. Figure 13 The transceiver 1375 and / or antenna 1380 of the communication device 1300 in the middle Figure 13 One or more processors 1310 of the communication device 1300 in the middle.

[0221] Example Terms

[0222] Specific implementation examples are described in the following numbered clauses: Clause 1: A method for wireless communication by an apparatus, the method comprising: transmitting a first random access signal on a first non-anchor carrier associated with a first non-anchor cell of a network entity to initiate a first RACH procedure in the first non-anchor cell; and, based on the first RACH procedure failing to complete successfully within a time duration following the transmission of the first random access signal, transmitting a second random access signal on an anchor carrier associated with an anchor cell of the network entity or a second non-anchor carrier associated with a second non-anchor cell of the network entity to initiate a second RACH procedure in the anchor cell or the second non-anchor cell.

[0223] Clause 2: The method according to Clause 1 further includes: receiving one or more RSs associated with the second non-anchor carrier; and measuring the one or more RSs to determine the signal quality of the second non-anchor carrier.

[0224] Clause 3: The method according to Clause 2, wherein transmitting the second random access signal comprises transmitting the second random access signal on the second non-anchor carrier based on the signal quality of the second non-anchor cell satisfying a threshold signal quality, to initiate the second RACH procedure in the second non-anchor cell.

[0225] Clause 4: The method according to Clause 2, wherein transmitting the second random access signal includes transmitting the second random access signal on the anchor carrier based on the signal quality of the second non-anchor cell not meeting a threshold signal quality, to initiate the second RACH procedure in the anchor cell.

[0226] Clause 5: The method described in Clause 4 further includes sending an indication of the device's ability to support non-anchor cell operation.

[0227] Clause 6: The method according to Clause 5, wherein sending the indication includes sending the indication via an RRC message after the second RACH procedure is successfully completed in the anchor cell.

[0228] Clause 7: The method according to Clause 5, wherein sending the instruction includes sending the instruction via a message from the second RACH procedure.

[0229] Clause 8: The method described in Clause 7, wherein the message of the second RACH procedure includes the second random access signal.

[0230] Clause 9: The method according to Clause 5, wherein the indication of the device’s ability to support the non-anchor cell operation includes a corresponding indication of the device’s ability to support the non-anchor cell operation by frequency bands in one or more frequency bands or by frequency band groups in one or more frequency band groups.

[0231] Clause 10: The method according to any one of Clauses 1 to 9, wherein the duration of the time is fixed.

[0232] Clause 11: The method according to any one of Clauses 1 to 10 further includes a configuration for receiving the time duration.

[0233] Clause 12: The method according to any one of Clauses 1 to 11, the method further comprising: receiving one or more RSs; and measuring the one or more RSs to determine the signal quality of the first non-anchor cell, wherein transmitting the first random access signal comprises transmitting the first random access signal on the first non-anchor carrier based on the signal quality of the first non-anchor cell to initiate the first RACH procedure in the first non-anchor cell.

[0234] Clause 13: The method according to any one of Clauses 1 to 12, the method further comprising receiving an instruction for performing the first RACH procedure in the first non-anchored cell, wherein transmitting the first random access signal comprises transmitting the first random access signal on the first non-anchored carrier based on the instruction to initiate the first RACH procedure in the first non-anchored cell.

[0235] Clause 14: A method for wireless communication by a device, the method comprising: receiving configuration of one or more RACH timings, wherein the one or more RACH timings are not configured for the active uplink BWP of the device, wherein the active uplink BWP is a first uplink BWP of a non-anchor cell of a network entity; switching the active uplink BWP of the device from the first uplink BWP to a second uplink BWP based on the fact that the one or more RACH timings are not configured for the active uplink BWP, wherein the second uplink BWP includes: another uplink BWP of the non-anchor cell; or an initial uplink BWP of an anchor cell of the network entity; and performing a RACH procedure using the second uplink BWP as the active uplink BWP for the device.

[0236] Clause 15: The method according to Clause 14 further includes receiving an indication that the other uplink BWP is designated for use in the RACH procedure of the non-anchor cell.

[0237] Clause 16: The method according to any one of Clauses 14 to 15, wherein: the second uplink BWP includes the initial uplink BWP; and performing the RACH procedure using the second uplink BWP as the active uplink BWP includes performing the RACH procedure in the anchor cell.

[0238] Clause 17: The method according to any one of Clauses 14 to 16, wherein one or more RACH timings are configured for the second uplink BWP.

[0239] Clause 18: The method according to any one of Clauses 14 to 17, wherein: the second uplink BWP includes the initial uplink BWP of the anchor cell; and the method further includes: sending an indication of the device's ability to support non-anchor cell operation.

[0240] Clause 19: The method according to Clause 18, wherein sending the indication includes sending the indication via an RRC message after the successful completion of the RACH procedure.

[0241] Clause 20: The method according to Clause 18, wherein sending the instruction includes sending the instruction via a message from the RACH procedure.

[0242] Clause 21: The method according to Clause 20, wherein the message of the RACH procedure includes a random access preamble.

[0243] Clause 22: The method according to Clause 18, wherein the indication of the device’s ability to support the non-anchor cell operation includes a corresponding indication of the device’s ability to support the non-anchor cell operation by frequency bands in one or more frequency bands or by frequency band groups in one or more frequency band groups.

[0244] Clause 23: A method for wireless communication by a device, the method comprising: performing a RACH procedure in an anchor cell of a network entity; and sending an indication of the device's ability to support non-anchor cell operation.

[0245] Clause 24: The method according to Clause 23, wherein sending the indication includes sending the indication via an RRC message after the RACH procedure is successfully completed in the anchor cell.

[0246] Clause 25: The method according to any one of Clauses 23 to 24, wherein sending the instruction includes sending the instruction via a message from the RACH procedure.

[0247] Clause 26: The method according to Clause 25, wherein the message of the RACH procedure includes a random access preamble.

[0248] Clause 27: The method according to any one of Clauses 23 to 26, wherein the indication of the device's ability to support the non-anchor cell operation includes a corresponding indication of the device's ability to support the non-anchor cell operation by frequency bands in one or more frequency bands or by frequency band groups in one or more frequency band groups.

[0249] Clause 28: One or more apparatuses comprising: one or more memories including executable instructions; and one or more processors configured to execute the executable instructions and cause the one or more apparatuses to perform the method according to any one of Clauses 1 to 27.

[0250] Clause 29: One or more means comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the one or more means to perform the method according to any one of Clauses 1 to 27.

[0251] Clause 30: One or more means comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to perform the method according to any one of Clauses 1 to 27.

[0252] Clause 31: One or more apparatuses, said apparatuses comprising components for performing the method according to any one of Clauses 1 to 27.

[0253] Clause 32: One or more non-transitory computer-readable media, the one or more non-transitory computer-readable media comprising executable instructions that, when executed by one or more processors of one or more devices, cause the one or more devices to perform the method according to any one of Clauses 1 to 27.

[0254] Clause 33: One or more computer program products embodied on one or more computer-readable storage media, the one or more computer-readable storage media including code for performing the method according to any one of Clauses 1 to 27.

[0255] Clause 34: A user equipment (UE) comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the UE to perform a method according to any one of Clauses 1 to 27.

[0256] Clause 35: A network entity comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the network entity to perform a method according to any one of Clauses 1 to 27.

[0257] Additional Notes

[0258] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in others. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Moreover, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of this disclosure disclosed herein may be embodied by one or more elements of these claims.

[0259] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, AI processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0260] As used in this article, the phrase “at least one of” in a list of items refers to any combination of those items, including a single member. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0261] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, etc. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Furthermore, "determine" can include parsing, selecting, picking, building, etc.

[0262] As used herein, unless otherwise stated, “coupled to” and “coupled with” generally encompass both direct and indirect coupling (e.g., including intermediate aspects of coupling). For example, stating that a processor is coupled to memory allows for direct coupling or coupling via an intermediate aspect such as a bus.

[0263] The methods disclosed herein include one or more actions for implementing the methods. These actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.

[0264] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. References to singular elements are not intended to mean “only one” (unless specifically stated as “only one”), but rather “one or more”. Unless otherwise specified, definite articles (e.g., “the” or “described”) subsequently used with an element (e.g., “processor”) are not intended to give that element a singular meaning (e.g., “only one”). For example, unless otherwise specified, references to elements (e.g., “processor”, “controller”, “memory”, “transceiver”, “antenna”, “the processor”, “the controller”, “the memory”, “the transceiver”, “the antenna”, etc.) should be understood to refer to one or more elements (e.g., “one or more processors”, “one or more controllers”, “one or more memories”, “a plurality of transceivers”, etc.). The terms “set” and “group” are intended to include one or more elements and may be used interchangeably with “one or more”. In the case of references to one or more elements performing a function (e.g., steps of a method), one element may perform all the functions, or more than one element may collectively perform those functions. When more than one element performs these functions together, each function does not need to be performed by every single element (e.g., different functions can be performed by different elements), and / or each function does not need to be performed by only one element as a whole (e.g., different elements can perform different sub-functions of a function). Similarly, when referring to one or more elements configured to cause another element (e.g., a device) to perform a function, one element may be configured to cause another element to perform all functions, or more than one element may be jointly configured to cause another element to perform these functions. Unless otherwise specifically stated, the term "some" means one or more. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are currently or hereafter known to those skilled in the art are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims.

Claims

1. An apparatus configured for wireless communication, the apparatus comprising: One or more memories, the one or more memories including processor-executable instructions; and One or more processors, the one or more processors being configured to execute processor-executable instructions and cause the device to: A first random access signal is transmitted on a first non-anchor carrier associated with a first non-anchor cell of a network entity to initiate a first random access channel (RACH) procedure in the first non-anchor cell. as well as Since the first RACH procedure failed to complete successfully within the time duration following the transmission of the first random access signal, a second random access signal is transmitted on the anchor carrier associated with the anchor cell of the network entity or on the second non-anchor carrier associated with the second non-anchor cell of the network entity to initiate a second RACH procedure in the anchor cell or the second non-anchor cell.

2. The apparatus of claim 1, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to: Receive one or more reference signals (RS) associated with the second non-anchor carrier; and Measure the one or more RS to determine the signal quality of the second non-anchor carrier.

3. The apparatus of claim 2, wherein, in order to transmit the second random access signal, the one or more processors are configured to execute processor-executable instructions and cause the apparatus to transmit the second random access signal on the second non-anchor carrier based on the signal quality of the second non-anchor cell satisfying a threshold signal quality, so as to initiate the second RACH procedure in the second non-anchor cell.

4. The apparatus of claim 2, wherein, in order to transmit the second random access signal, the one or more processors are configured to execute processor-executable instructions and cause the apparatus to transmit the second random access signal on the anchor carrier based on the signal quality of the second non-anchor cell not meeting a threshold signal quality, so as to initiate the second RACH procedure in the anchor cell.

5. The apparatus of claim 4, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to send an indication of the apparatus's ability to support non-anchor cell operation.

6. The apparatus of claim 5, wherein, in order to transmit the indication, the one or more processors are configured to transmit the indication via a Radio Resource Control (RRC) message after executing the processor-executable instructions and causing the apparatus to successfully complete the second RACH procedure in the anchor cell.

7. The apparatus of claim 5, wherein, in order to send the instruction, the one or more processors are configured to execute processor-executable instructions and cause the apparatus to send the instruction via a message of the second RACH procedure.

8. The apparatus of claim 7, wherein the message of the second RACH procedure includes the second random access signal.

9. The apparatus of claim 5, wherein the indication of the apparatus's ability to support the non-anchor cell operation comprises a corresponding indication of the apparatus's ability to support the non-anchor cell operation by frequency bands in one or more frequency bands or by frequency band groups in one or more frequency band groups.

10. The apparatus of claim 1, wherein the duration of time is fixed.

11. The apparatus of claim 1, wherein the one or more processors are configured to execute processor-executable instructions and to enable the apparatus to receive the time history.

12. The apparatus according to claim 1, wherein: The one or more processors are configured to execute processor-executable instructions and enable the device: Receive one or more reference signals (RS); as well as Measure the one or more RSs to determine the signal quality of the first non-anchored cell; and In order to transmit the first random access signal, the one or more processors are configured to execute processor-executable instructions and cause the device to transmit the first random access signal on the first non-anchor carrier based on the signal quality of the first non-anchor cell, so as to initiate the first RACH procedure in the first non-anchor cell.

13. The apparatus according to claim 1, wherein: The one or more processors are configured to execute processor-executable instructions and cause the device to receive instructions for performing the first RACH procedure in the first non-anchor cell; and In order to transmit the first random access signal, the one or more processors are configured to execute processor-executable instructions and cause the device to transmit the first random access signal on the first non-anchor carrier based on the instructions, so as to initiate the first RACH procedure in the first non-anchor cell.

14. A method for wireless communication by a device, the method comprising: A first random access signal is transmitted on a first non-anchor carrier associated with a first non-anchor cell of a network entity to initiate a first random access channel (RACH) procedure in the first non-anchor cell. as well as Since the first RACH procedure failed to complete successfully within the time duration following the transmission of the first random access signal, a second random access signal is transmitted on the anchor carrier associated with the anchor cell of the network entity or on the second non-anchor carrier associated with the second non-anchor cell of the network entity to initiate a second RACH procedure in the anchor cell or the second non-anchor cell.

15. The method according to claim 14, further comprising: Receive one or more reference signals (RS) associated with the second non-anchor carrier; as well as Measure the one or more RS to determine the signal quality of the second non-anchor carrier.

16. The method of claim 15, wherein transmitting the second random access signal comprises transmitting the second random access signal on the second non-anchor carrier based on the signal quality of the second non-anchor cell satisfying a threshold signal quality, to initiate the second RACH procedure in the second non-anchor cell.

17. The method of claim 15, wherein transmitting the second random access signal comprises transmitting the second random access signal on the anchor carrier based on the signal quality of the second non-anchor cell not meeting a threshold signal quality, to initiate the second RACH procedure in the anchor cell.

18. The method of claim 17, further comprising sending an indication of the device's ability to support non-anchor cell operation.

19. The method of claim 18, wherein the indication is sent via a Radio Resource Control (RRC) message after the second RACH procedure is successfully completed in the anchor cell.

20. One or more non-transitory computer-readable media, the one or more non-transitory computer-readable media comprising executable instructions that, when executed by one or more processors of the device, cause the device to perform operations, the operations including: A first random access signal is transmitted on a first non-anchor carrier associated with a first non-anchor cell of a network entity to initiate a first random access channel (RACH) procedure in the first non-anchor cell. as well as Since the first RACH procedure failed to complete successfully within the time duration following the transmission of the first random access signal, a second random access signal is transmitted on the anchor carrier associated with the anchor cell of the network entity or on the second non-anchor carrier associated with the second non-anchor cell of the network entity to initiate a second RACH procedure in the anchor cell or the second non-anchor cell.

Images