CN120113288A - Provides system information associated with non-anchor cells - Google Patents

Abstract

Aspects of the present disclosure relate generally to wireless communications. In some aspects, a User Equipment (UE) is capable of receiving first System Information (SI) associated with an anchor cell and proxy information associated with obtaining a second SI from a first network node associated with the anchor cell. The UE can obtain the second SI based on the proxy information. The UE is capable of communicating with the non-anchor cell based on the second SI. Numerous other aspects are provided.

Description

Providing system information associated with non-anchor cells

Cross Reference to Related Applications

This patent application claims priority from U.S. provisional patent application No. 63/382,283 entitled "PROVIDING SYSTEM INFORMATION ASSOCIATED WITH NON-ANCHOR CELLS (providing system information associated with non-ANCHOR CELLS)" filed on month 11, 2022, and U.S. non-provisional patent application No. 18/465,637 entitled "PROVIDING SYSTEM INFORMATION ASSOCIATED WITH NON-ANCHOR CELLS (providing system information associated with non-ANCHOR CELLS)" filed on month 9, 2023, which applications are hereby expressly incorporated herein by reference.

Technical Field

Aspects of the present disclosure relate generally to wireless communications and, in particular, relate to techniques and apparatus for cell access associated with non-anchor cells.

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth or transmit power). Examples of such multiple-access techniques include Code Division Multiple Access (CDMA) systems, time Division Multiple Access (TDMA) systems, frequency Division Multiple Access (FDMA) systems, orthogonal Frequency Division Multiple Access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE/LTE-advanced is an enhanced set of Universal Mobile Telecommunications System (UMTS) mobile standards promulgated by the third generation partnership project (3 GPP).

The above multiple access techniques have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region or global level. The New Radio (NR), which may be referred to as 5G, is an enhanced set of LTE mobile standards promulgated by 3 GPP. NR is designed to better support mobile broadband internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with cyclic prefix (CP-OFDM) on the downlink, CP-OFDM or single carrier frequency division multiplexing (SC-FDM) on the uplink (also known as discrete fourier transform spread OFDM (DFT-s-OFDM) and support beamforming, multiple Input Multiple Output (MIMO) antenna technology and carrier aggregation to improve spectral efficiency, reduce cost, improve services, utilize new spectrum, and integrate better with other open standards.

In some deployments, an anchor cell (also referred to as an "anchor carrier") may be a cell that provides initial network access (e.g., in addition to providing data communications) to the UE, while a non-anchor cell (also referred to as a "non-anchor carrier") may be a cell that does not provide initial network access but only provides data communications. In some cases, the anchor cell may operate in a "normal" non-power save mode. In some such deployments, the non-anchor cell may operate in a power saving mode. Any number of additional anchor cells and/or non-anchor cells may be deployed. In some cases, the Synchronization Signal Block (SSB) and the System Information (SI) may be transmitted on the anchor cell instead of the non-anchor cell. SSBs and SIs sent on the anchor cell may provide time and frequency synchronization information and SIs for non-anchor cells as well as for anchor cells. However, in some examples, management and/or coordination of SI between the anchor cell and the non-anchor cell may be inadequate, thereby negatively impacting the opportunity for efficient cell access procedures.

Disclosure of Invention

Some aspects described herein relate to a User Equipment (UE) for wireless communication. The user equipment may include a processing system including a processor circuit and a memory circuit coupled with the processor circuit. The processing system may be configured to cause the UE to receive, from a first network node associated with an anchor cell, first System Information (SI) associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell. The at least one processor may be operable to cause the user equipment to obtain the second SI based on the proxy information. The processing system may be configured to cause the UE to communicate with the non-anchor cell based on the second SI.

Some aspects described herein relate to a network node for wireless communication. The network node may include a processing system including a processor circuit and a memory circuit coupled to the processor circuit. The processing system may be configured to cause the network node to receive a proxy indication associated with a second network node associated with a non-anchor cell, the first network node being associated with an anchor cell. The processing system may be configured to cause the network node to send, based on receiving the proxy indication, a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with the non-anchor cell.

Some aspects described herein relate to a method of wireless communication performed by a device at a UE. The method may include receiving, from a first network node associated with an anchor cell, a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell. The method may include obtaining the second SI based on the proxy information. The method may include communicating with the non-anchor cell based on the second SI.

Some aspects described herein relate to a method of wireless communication performed by an apparatus at a first network node. The method may include receiving a proxy indication associated with a second network node associated with a non-anchor cell, the first network node being associated with an anchor cell. The method may include transmitting a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with the non-anchor cell based on receiving the proxy indication.

Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to receive, from a first network node associated with an anchor cell, a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to obtain the second SI based on the proxy information. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to communicate with the non-anchor cell based on the second SI.

Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by the one or more processors of the network node, may cause the network node to receive a proxy indication associated with a second network node associated with a non-anchor cell, the first network node being associated with an anchor cell. The set of instructions, when executed by the one or more processors of the network node, may cause the network node to transmit a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with the non-anchor cell based on receiving the proxy indication.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a first network node associated with an anchor cell, a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell. The apparatus may include means for obtaining the second SI based on the proxy information. The apparatus may include means for communicating with the non-anchor cell based on the second SI.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a proxy indication associated with a network node associated with a non-anchor cell with which the apparatus is associated. The apparatus may include means for transmitting a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with the non-anchor cell based on receiving the proxy indication.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer readable medium, user equipment, base station, network node, network entity, wireless communication device, or processing system as substantially described with reference to and as illustrated by the accompanying drawings and description.

The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The concepts and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein, both as to their organization and method of operation, together with the associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for purposes of illustration and description, and is not intended as a definition of the limits of the claims.

Drawings

So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only some typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

Fig. 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

Fig. 2 is a diagram illustrating an example network node in a wireless network in accordance with the present disclosure in communication with a User Equipment (UE).

Fig. 3 is a diagram illustrating an example split base station architecture according to this disclosure.

Fig. 4 is a diagram illustrating an example associated with network access and communication associated with an anchor cell and a non-anchor cell in accordance with the present disclosure.

Fig. 5 is a diagram illustrating an example associated with obtaining System Information (SI) associated with a non-anchor cell based on proxy information provided by the anchor cell in accordance with the present disclosure.

Fig. 6 is a flowchart illustrating an example process performed, for example, by a UE supporting communication with a non-anchor cell in accordance with the present disclosure.

Fig. 7 is a flowchart illustrating an example process performed, for example, by a network node supporting communication with a non-anchor cell in accordance with the present disclosure.

Fig. 8 is an illustration of an example apparatus for wireless communication supporting communication with a non-anchor cell in accordance with the present disclosure.

Fig. 9 is an illustration of an example apparatus for wireless communication supporting communication with a non-anchor cell in accordance with the present disclosure.

Detailed Description

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently or in combination with any other aspect of the disclosure. For example, an apparatus may be implemented or a method practiced using any number of the aspects set forth herein. Furthermore, the scope of the present disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or both in addition to and other than the various aspects of the disclosure set forth herein. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

Several aspects of the telecommunications system will now be presented with reference to various apparatus and techniques. These devices and techniques will be described in the following detailed description and illustrated in the figures by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, "elements"). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

Various aspects relate generally to providing and obtaining System Information (SI) associated with cells operating in a power save mode (referred to herein as "non-anchor cells"). Some aspects relate more particularly to a User Equipment (UE) receiving proxy information associated with obtaining SI associated with a non-anchor cell from a network node associated with the anchor cell. In some aspects, proxy information may be sent in an SI associated with the anchor cell. In some aspects, the proxy information may include SI associated with the non-anchor cell and/or may include scheduling information to facilitate obtaining SI associated with the non-anchor cell. In some aspects, the proxy information may indicate one or more anchor cells from which the UE may obtain SI associated with the non-anchor cell. In some aspects, the anchor cell and/or the non-anchor cell may provide SI updates associated with the non-anchor cell. In some aspects, the anchor cell and/or the non-anchor cell may provide an indication of the SI update.

Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the described techniques may be used to facilitate providing information to a UE from which the UE may obtain SI associated with a non-anchor cell, which may facilitate a cell access procedure for the non-anchor cell while allowing the non-anchor cell to operate in a power saving mode at least prior to the cell access procedure. In some examples, the described techniques may be used to facilitate deployment of non-anchor cells, which may improve secondary cell (Scell) activation efficiency and/or network power saving.

Fig. 1 is a diagram illustrating an example of a wireless network according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., long Term Evolution (LTE)) network, among other examples. Wireless network 100 may include one or more network nodes 110 (shown as Network Node (NN) 110a, network node 110b, network node 110c, and network node 110 d), one UE 120, or a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120 e), and/or other network entities. Network node 110 is an entity in communication with UE 120. As shown, network node 110 may include one or more network nodes. For example, the network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, network node 110 may be a split network node (sometimes referred to as a split base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes, such as one or more Central Units (CUs), one or more Distributed Units (DUs), or one or more Radio Units (RUs).

In some examples, network node 110 is or includes a network node, such as an RU, that communicates with UE 120 via a radio access link. In some examples, network node 110 is or includes a network node, such as a DU, that communicates with other network nodes 110 via a forward link or an intermediate link. In some examples, the network node 110 is or includes a network node, such as a CU, that communicates with other network nodes 110 via an intermediate link or with the core network via a backhaul link. In some examples, network node 110 (such as an aggregation network node 110 or an break-up network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, or one or more DUs. The network node 110 may include, for example, an NR network node, an LTE network node, a node B, eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point or a transmission-reception point (TRP), a DU, RU, CU, a mobility element of a network, a core network node, a network element, network equipment, and/or a RAN node. In some examples, network nodes 110 may be interconnected with each other or to one or more other network nodes 110 in wireless network 100 through various types of forward, mid, or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

Network node 110 may include one or more chips, systems on a chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. A processing system includes processor (or "processing") circuitry in the form of one or more processors, microprocessors, processing units, such as Central Processing Units (CPUs), graphics Processing Units (GPUs), neural Processing Units (NPUs), and/or Digital Signal Processors (DSPs), processing blocks, application Specific Integrated Circuits (ASICs), programmable Logic Devices (PLDs), such as Field Programmable Gate Arrays (FPGAs), or other discrete gate or transistor logic elements or circuits (all of which may be referred to herein, generally, individually, as "processors", or collectively, as "processors" or "processor circuits"). One or more of these processors may be individually or collectively configurable or configured to perform the various functions or operations described herein. A group of processors collectively configurable or configured to perform a set of functions may comprise a first processor configurable or configured to perform a first function in the set and a second processor configurable or configured to perform a second function in the set, or may comprise the group of processors all configurable or configurable to perform the set of functions.

The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic or circuitry, each of which may include a tangible storage medium, such as Random Access Memory (RAM) or Read Only Memory (ROM) or a combination thereof (all of which may be referred to herein, generally, individually, as "memory" or collectively, "memory" or "memory circuitry"). One or more of these memories may be coupled (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors and may store processor-executable code (such as software) individually or collectively that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally or alternatively, in some examples, one or more of the processors may be preconfigured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled with one or more modems, such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3gpp 4G LTE, 5G, or 6G compliant) modems. In some implementations, the one or more processors of the processing system include or implement one or more of the modems. The processing system may also include or be coupled with a plurality of radio components (collectively, "radio components"), a plurality of Radio Frequency (RF) chains, or a plurality of transceivers, each of which may in turn be coupled with one or more of a plurality of antennas. In some implementations, the one or more processors of the processing system include or implement one or more of a radio, an RF chain, or a transceiver. Network node 110 may include or may be included in a housing that houses components (including processing systems) associated with network node 110.

Each network node 110 may provide communication coverage for a particular geographic area. In the third generation partnership project (3 GPP), the term "cell" can refer to a coverage area of a network node 110 or a network node subsystem serving the coverage area, depending on the context in which the term is used.

The network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, or another type of cell. A macrocell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscription. The pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs 120 associated with the femto cell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). The network node 110 for a macro cell may be referred to as a macro network node. The network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node.

The wireless network 100 may be a heterogeneous network comprising different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different effects on interference in the wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts). In the example shown in fig. 1, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102 c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile network node 110 (e.g., a mobile network node).

In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an Integrated Access and Backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, DU, RU, near real-time (near RT) RAN Intelligent Controller (RIC), and/or a non-real-time (non-RT) RIC. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in connection with network node 110. In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or different geographic locations) may be configured to perform, or repeat the performance of, at least a portion of the functionality, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions, but not the other. In this way, a single device may include more than one base station.

The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network node 110 via a backhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via wireless or wired backhaul communication links. In some aspects, the network controller 130 may be a CU or a core network device, or the network controller 130 may include a CU or a core network device.

In some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of the mobile network node 110 (e.g., a mobile network node). In some examples, network nodes 110 may be interconnected with each other or to one or more other network nodes 110 or network nodes (not shown) in wireless network 100 through various types of backhaul interfaces (such as direct physical connections or virtual networks) using any suitable transport network.

The wireless network 100 may include one or more relay stations. A relay station is an entity that may receive data transmissions from an upstream station (e.g., network node 110 or UE 120) and communicate the data transmissions to a downstream station (e.g., UE 120 or network node 110). The relay station may be a UE 120 capable of relaying transmissions for other UEs 120. In the example shown in fig. 1, network node 110d (e.g., a relay network node) may communicate with network node 110a (e.g., a macro network node) and UE 120d in order to facilitate communications between network node 110a and UE 120 d. The network node 110 relaying the communication may be referred to as a relay station, a relay network node or a relay.

UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a mobile station, or a subscriber unit. UE 120 may be a cellular telephone (e.g., a smart phone), a Personal Digital Assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a Wireless Local Loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, a super book, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smartwristband, smart jewelry (e.g., a smartring or smartband)), an entertainment device (e.g., a music device, a video device, or a satellite radio), a vehicle component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device configured to communicate via a wireless medium.

UE 120 may include one or more chips, socs, chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or "processing") circuitry in the form of one or more processors, microprocessors, processing units (such as CPU, GPU, NPU and/or DSPs), processing blocks, ASICs, PLDs (such as FPGAs), or other discrete gate or transistor logic elements or circuits (all of which may be referred to herein, generally, individually, or collectively, as "processor" or "processor circuitry"). One or more of these processors may be individually or collectively configurable or configured to perform the various functions or operations described herein. A group of processors collectively configurable or configured to perform a set of functions may comprise a first processor configurable or configured to perform a first function in the set and a second processor configurable or configured to perform a second function in the set, or may comprise the group of processors all configurable or configurable to perform the set of functions.

The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic or circuitry, each of which may include a tangible storage medium such as RAM or ROM, or a combination thereof (all of which may be referred to herein, generally, individually, or collectively, as "memory" or "memory circuitry"). One or more of these memories may be coupled (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors and may store processor-executable code (such as software) individually or collectively that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally or alternatively, in some examples, one or more of the processors may be preconfigured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled with one or more modems, such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3gpp 4G LTE, 5G, or 6G compliant) modems. In some implementations, the one or more processors of the processing system include or implement one or more of the modems. The processing system may also include or be coupled with a plurality of radio components (collectively, "radio components"), a plurality of RF chains, or a plurality of transceivers, each of which may in turn be coupled with one or more of a plurality of antennas. In some implementations, the one or more processors of the processing system include or implement one or more of a radio, an RF chain, or a transceiver. UE 120 may include or may be included in a housing that houses components (including a processing system) associated with UE 120.

Some UEs 120 may be considered Machine Type Communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, robots, drones, remote devices, sensors, gauges, monitors, or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered internet of things (IoT) devices, or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premise equipment. UE 120 may be included within a housing that houses components of UE 120, such as processor components or memory components. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) are operably coupled, communicatively coupled, electronically coupled, or electrically coupled.

In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. The RAT may be referred to as a radio technology or an air interface. The frequency may be referred to as a carrier or frequency channel. Each frequency in a given geographic region may support a single RAT to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

In some examples, two or more UEs 120 (e.g., shown as UE120 a and UE120 e) may communicate directly using one or more side link channels (e.g., without using network node 110 as an intermediary in communicating with each other). For example, UE120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, a vehicle-to-vehicle (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), or a mesh network. In such examples, UE120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

Devices of wireless network 100 may communicate using electromagnetic spectrum, which may be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices of wireless network 100 may communicate using one or more operating frequency bands. In 5G NR, two initial operating bands have been identified as frequency range designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. Similar naming problems sometimes occur in connection with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in various documents and articles, although it is different from the Extremely High Frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Recent 5G NR studies have identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency band falling within FR3 may inherit the FR1 characteristic or the FR2 characteristic, and thus the characteristics of FR1 or FR2 may be effectively extended into the mid-band frequency. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6GHz. For example, three higher operating bands have been identified as frequency range designation FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF frequency band.

In view of the above examples, unless specifically stated otherwise, if the term "below 6 GHz" is used herein, it may broadly represent frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, if the term "millimeter wave" is used herein, it may broadly mean frequencies that may include mid-band frequencies, may be within FR2, FR4-a, or FR4-1 or FR5, or may be within the EHF band. It is contemplated that frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4-a, FR4-1, or FR 5) may be modified, and that the techniques described herein are applicable to those modified frequency ranges.

In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 can receive, from a first network node associated with an anchor cell, a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell, obtain the second SI based on the proxy information, and communicate with the non-anchor cell based on the second SI. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

In some aspects, network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a proxy indication associated with a second network node associated with a non-anchor cell, the first network node being associated with an anchor cell, and send a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with the non-anchor cell based on receiving the proxy indication. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

Fig. 2 is a diagram illustrating an example network node in a wireless network in accordance with the present disclosure in communication with a UE. The network node may correspond to the network node 110 of fig. 1. Similarly, the UE may correspond to UE 120 of fig. 1. Network node 110 may be equipped with a set of antennas 234a through 234T, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a through 252R, such as R antennas (r≡1). The network node 110 depicted in fig. 2 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, network node 110 may include an interface, a communication component, or another component that facilitates communication with UE 120 or another network node. Some network nodes 110 may not include radio frequency components, such as one or more CUs or one or more DUs, that facilitate direct communication with UE 120.

At network node 110, transmit processor 220 may receive data intended for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more Modulation and Coding Schemes (MCSs) for UE 120 based at least in part on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-Static Resource Partitioning Information (SRPI)) and control information (e.g., CQI requests, grants, or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary Synchronization Signals (PSS) or Secondary Synchronization Signals (SSS)). A Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232T). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 may process a respective output symbol stream (e.g., for OFDM) using a respective modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. Modems 232 a-232T may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234 a-234T).

At UE 120, a set of antennas 252 (shown as antennas 252a through 252R) may receive downlink signals from network node 110 or other network nodes 110 and a set of received signals (e.g., R received signals) may be provided to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254R). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may condition (e.g., filter, amplify, downconvert, or digitize) a received signal using a corresponding demodulator component to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. MIMO detector 256 may obtain the received symbols from modem 254, may perform MIMO detection on the received symbols, if applicable, and may provide detected symbols. Receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for UE 120 to a data sink 260, and may provide decoded control information and system information to controller/processor 280. The term "controller/processor" may refer to one or more controllers and/or one or more processors. The channel processor may determine a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, or a CQI parameter, among others. In some examples, one or more components of UE 120 may be included in housing 284.

The network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292. The network controller 130 may comprise, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via a communication unit 294.

The one or more antennas (e.g., antennas 234a through 234t or antennas 252a through 252 r) may include or be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. An antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled to one or more transmit or receive components (such as one or more components of fig. 2).

On the uplink, at UE 120, transmit processor 264 may receive and process data from data source 262 and control information from controller/processor 280 (e.g., for reports including RSRP, RSSI, RSRQ or CQI). Transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be pre-decoded, if applicable, by a TX MIMO processor 266, further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, modem 254 of UE 120 may include a modulator and a demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modems 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller/processor 280) and memory 282 to perform aspects of any of the methods described herein.

At network node 110, uplink signals from UE 120 or other UEs may be received by antennas 234, processed by modems 232 (e.g., the demodulator components of modems 232, shown as DEMODs), detected by MIMO detector 236 if applicable, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240. The network node 110 may comprise a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. Network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some examples, modem 232 of network node 110 may include a modulator and a demodulator. In some examples, network node 110 includes a transceiver. The transceiver may include any combination of antennas 234, modems 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller/processor 240) and memory 242 to perform aspects of any of the methods described herein.

Controller/processor 240 of network node 110, controller/processor 280 of UE 120, or any other component of fig. 2 may perform one or more techniques associated with system information associated with non-anchor cells, as described in more detail elsewhere herein. For example, controller/processor 240 of network node 110, controller/processor 280 of UE 120, or any other component of fig. 2 may perform or direct operations such as process 600 of fig. 6, process 700 of fig. 7, or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 or UE 120 (e.g., directly, or after compilation, conversion, or interpretation), may cause the one or more processors, UE 120, or network node 110 to perform or direct operations such as process 600 of fig. 6, process 700 of fig. 7, or other processes as described herein. In some examples, the execution instructions may include execution instructions, conversion instructions, compilation instructions, or interpretation instructions, among others.

The terms "processor," "controller," or "controller/processor" may refer to one or more controllers and/or one or more processors. For example, references to "a/the processor," "a/the controller/processor," etc. (in the singular) should be understood to refer to any one or more of the processors described in connection with fig. 2, such as a single processor or a combination of multiple different processors. References to "one or more processors" should be understood to refer to any one or more of the processors described in connection with fig. 2. For example, the one or more processors of network node 110 may include a transmit processor 220, a TX MIMO processor 230, a MIMO detector 236, a receive processor 238, and/or a controller/processor 240. Similarly, the one or more processors of UE 220 may include a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, and/or a controller/processor 280.

In some aspects, a single processor may perform all operations described as being performed by one or more processors. In some aspects, a first set of processor(s) of the one or more processors may perform a first function described as being performed by the one or more processors, and a second set of processor(s) of the one or more processors may perform a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. References to "one or more memories" should be understood to refer to any one or more memories of a corresponding device, such as the memories described in connection with fig. 2. For example, functions described as being performed by one or more memories may be performed by the same subset of the one or more memories or a different subset of the one or more memories.

In some aspects, a UE (e.g., UE 120) includes means for receiving a first SI associated with an anchor cell from a first network node associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell, means for obtaining the second SI based on the proxy information, and/or means for communicating with the non-anchor cell based on the second SI. Means for a UE to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller/processor 280, or the memory 282.

In some aspects, a network node (e.g., network node 110) includes means for receiving a proxy indication associated with a second network node associated with a non-anchor cell, the first network node being associated with an anchor cell, and/or means for transmitting a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with the non-anchor cell based on receiving the proxy indication. Means for a network node to perform the operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

Deployment of a communication system, such as a 5G NR system, may be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, RAN nodes, core network nodes, network elements, base stations, or network equipment may be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access Point (AP), TRP or cell, etc.) or one or more units (or one or more components) performing base station functionality may be implemented as an aggregated base station (also referred to as a standalone base station or a monolithic base station) or a decomposed base station. A "network entity" or "network node" may refer to an exploded base station or one or more units of an exploded base station (such as one or more CUs, one or more DUs, and/or one or more RUs).

An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A disaggregated base station (e.g., a disaggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more CUs, one or more DUs, or one or more RUs. In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as virtual units, such as Virtual Central Units (VCUs), virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), among others.

Base station type operation or network design may take into account the aggregate nature of the base station functionality. For example, the split base station may be utilized in an IAB network, an open radio access network (O-RAN such as network configuration advocated by the O-RAN alliance), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that may be individually deployed. The decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Each unit of the base station may be configured for wired or wireless communication with at least one other unit of the base station.

Fig. 3 is a diagram illustrating an example split base station architecture 300 according to this disclosure. The split base station architecture 300 may include a CU 310 that may communicate directly with the core network 320 via a backhaul link or indirectly with the core network 320 through one or more split control units, such as a near RT RIC 325 via an E2 link, or a non RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both. CU 310 may communicate with one or more DUs 330 via respective intermediate links, such as through an F1 interface. Each of DUs 330 may be in communication with one or more RUs 340 via a respective forward link. Each of RUs 340 may communicate with one or more UEs 120 via a respective RF access link. In some implementations, UE 120 may be served by multiple RUs 340 simultaneously.

Each of the units (including CU 310, DU 330, RU 340) and near RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled with 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 units, or an associated processor or controller that provides instructions to one or more communication interfaces of the respective unit, may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface configured to receive signals over a wired transmission medium or to transmit signals to one or more of the other units, and a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals over a wireless transmission medium or to transmit signals to one or more of the other units, or both.

In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include a Radio Resource Control (RRC) function, a Packet Data Convergence Protocol (PDCP) function, or a Service Data Adaptation Protocol (SDAP) function, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality) and/or control plane functionality (e.g., central unit-control plane (CU-CP) functionality). In some implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bi-directionally with the CU-CP unit via an interface, such as an E1 interface. CU 310 may be implemented to communicate with DU 330 for network control and signaling, as desired.

Each DU 330 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DUs 330 may host one or more of a Radio Link Control (RLC) layer, a MAC layer, and one or more high Physical (PHY) layers, at least in part, according to a functional split, such as that defined by 3 GPP. In some aspects, one or more of the high PHY layers may be implemented by one or more modules for Forward Error Correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among others. In some aspects, the DU 330 may also host one or more low PHY layers, such as implemented by one or more modules for Fast Fourier Transform (FFT), inverse FFT (iFFT), digital beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, and so forth. Each layer (which may also be referred to as a module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

Each RU 340 may implement lower layer functionality. In some deployments, RU 340 controlled by DU 330 may correspond to a logical node that hosts RF processing functions or lower PHY layer functions based on a functional split (e.g., a functional split defined by 3 GPP), such as a lower layer functional split, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, and so forth. In such an architecture, each RU 340 may be operable to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, the real-time and non-real-time aspects of control plane communication and user plane communication with RU 340 may be controlled by corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as vRAN architecture).

SMO framework 305 may be configured to support RAN deployment and deployment of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, SMO framework 305 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via operation and maintenance interfaces (such as O1 interfaces). For virtualized network elements, SMO framework 305 may be configured to interact with a Cloud computing platform, such as open Cloud (O-Cloud) platform 390, to perform network element lifecycle management (such as instantiating virtualized network elements) via a Cloud computing platform interface, such as an O2 interface. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near RT RIC 325. In some implementations, SMO framework 305 may communicate with hardware aspects of the 4G RAN, such as open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations SMO framework 305 may communicate directly with each of one or more RUs 340 via a respective O1 interface. SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of SMO framework 305.

The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence/machine learning (AI/ML) workflows including model training and updating, or policy-based guidance of applications/features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with a near-RT RIC 325 (such as via an A1 interface). Near RT RIC 325 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and an O-eNB with near RT RIC 325.

In some implementations, to generate the AI/ML model to be deployed in the near RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by near RT RIC 325 and may be received at SMO framework 305 or non-RT RIC 315 from a non-network data source or from a network function. In some examples, the non-RT RIC 315 or near-RT RIC 325 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI/ML models to perform error correction actions through SMO framework 305 (such as reconfiguration via O1 interfaces) or through creation of RAN management policies (such as A1 interface policies).

Fig. 4 is a diagram illustrating an example 400 associated with network access and communication associated with an anchor cell and a non-anchor cell in accordance with the present disclosure. The example 400 illustrates a UE 402 that may communicate with one or more network nodes ("NNs") 404, 406, 408, and 410. In some aspects, the UE 402 may be, be similar to, include, or be included in the UE 120 described in connection with fig. 1-3. In some aspects, network nodes 404, 406, 408, and/or 410 may be, be similar to, include, or be included in one or more components of network node 110 described in connection with fig. 1 and 2 and/or split base station architecture 300 described in connection with fig. 3.

As shown, network node 404 may be associated with an anchor cell 412 and network node 406 may be associated with a non-anchor cell 414. In some aspects, an anchor cell (also referred to as an "anchor carrier") may be a cell that provides initial network access (e.g., in addition to providing data communications) to a UE, while a non-anchor cell (also referred to as a "non-anchor carrier") may be a cell that does not provide initial network access but only provides data communications. For example, the network node 404 associated with the anchor cell 412 may provide a cell access procedure and/or may transmit SI including, for example, minimum System Information (MSI) (e.g., a Master Information Block (MIB) and/or a Synchronization Signal Block (SSB)), remaining system information (RMSI) (e.g., system information block 1 (SIB 1)) and/or Other SI (OSI), and/or the like. In some aspects, the network node 404 may send paging messages and/or other short messages, etc.

In contrast, network node 406 associated with non-anchor cell 414 may be operable to not provide a cell access procedure, deactivate one or more components of network node 406, and/or refrain from performing one or more operations executable by the network node associated with the anchor cell. In some cases, a cell may be configured as an anchor cell or a non-anchor cell. For example, a cell may be a non-anchor cell based on an associated network node operating in a power save mode in conjunction with at least the non-anchor cell. For example, in a power saving mode, network node 406 may deactivate one or more antenna panels, receive chains, and/or transmit chains, etc. In some examples, in the power saving mode, network node 406 may refrain from transmitting one or more types of SI (e.g., MIB, SSB, SIB a and/or OSI, etc.), paging messages and/or short messages, etc. An example of a non-anchor cell is an SSB-free cell. SSB-free cells are cells that do not transmit SSBs. For example, network node 406 may refrain from transmitting any broadcast transmissions (e.g., SSB, SI, and/or paging messages) on the SSB-free carrier. In some examples, the anchor cell 412 may be a primary cell (Pcell) and the non-anchor cell 414 may be a secondary cell (SCell).

In some aspects, any number of additional anchor cells and/or non-anchor cells may be deployed. As shown, for example, network node 408 may be associated with anchor cell 416 and network node 410 may be associated with anchor cell 418. In some aspects, any number of network nodes 404, 406, 408, and 410 may be associated with multiple anchor cells and/or non-anchor cells. For example, in some cases, two or more of network nodes 404, 406, 408, and 410 may be co-located (e.g., as components of a base station and/or DU, etc.), in which case carrier aggregation may be used to aggregate two or more of cells 412, 414, 416, and 418.

In some aspects, network node 404 may send SSB and SI on anchor cell 412 while network node 406 does not send SSB and SI on non-anchor cell 414. SSBs and SIs sent on anchor cell 412 may provide time and frequency synchronization information and SIs for non-anchor cell 414 (and/or any number of additional non-anchor cells) as well as for anchor cell 412. In some cases, sending SSBs on the anchor cell 412 (e.g., pcell) but not on the non-anchor cells (e.g., scells) may improve Scell activation latency (e.g., because the UE 402 does not receive a respective SSB on each Scell). Such improved Scell activation latency may facilitate efficient Scell activation and/or deactivation depending on the actual traffic associated with UE 402, which may result in network power savings. Furthermore, not transmitting SSBs and/or SIs on non-anchor cells (e.g., scells) may improve resource utilization by reducing downlink overhead. This may allow deeper network sleep to improve power savings. However, in some examples, management and/or coordination of SI between the anchor cell and the non-anchor cell may be inadequate, thereby negatively impacting the opportunity for efficient cell access procedures.

Various aspects relate generally to providing SI associated with non-anchor cells. Some aspects relate more particularly to a UE receiving proxy information associated with obtaining SI associated with a non-anchor cell from a network node associated with the anchor cell. In some aspects, proxy information may be sent in an SI associated with the anchor cell. In some aspects, the proxy information may include SI associated with the non-anchor cell and/or may include scheduling information to facilitate obtaining SI associated with the non-anchor cell. In some aspects, the proxy information may indicate one or more anchor cells from which the UE may obtain SI associated with the non-anchor cell. In some aspects, the anchor cell and/or the non-anchor cell may provide SI updates associated with the non-anchor cell. In some aspects, the anchor cell and/or the non-anchor cell may provide an indication of the SI update.

Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the described techniques may be used to facilitate providing information to a UE from which the UE may obtain SI associated with a non-anchor cell, which may facilitate a cell access procedure for the non-anchor cell while allowing the non-anchor cell to operate in a power saving mode at least prior to the cell access procedure. In some examples, the described techniques may be used to facilitate deployment of non-anchor cells, which may improve Scell activation efficiency and/or network power saving.

Fig. 5 is a diagram illustrating an example 500 associated with obtaining SI associated with a non-anchor cell based on proxy information provided by the anchor cell in accordance with the present disclosure. As shown in fig. 5, a UE 502 may communicate with a network node 504 and a network node 506. In some aspects, UE 502 may be, similar to, include, or be included in UE 402 depicted in fig. 4 and/or UE 120 depicted in fig. 1-3. In some aspects, network node 504 may be associated with an anchor cell 508 and network node 506 may be associated with a non-anchor cell 510. In some aspects, the network node 504 may be, be similar to, include, or be included in one or more components of the network nodes 404, 408, and/or 410 depicted in fig. 4, the network node 110 depicted in fig. 1 and 2, and/or the split base station architecture depicted in fig. 3. In some aspects, the network node 506 may be, be similar to, include, or be included in one or more components of the network node 406 depicted in fig. 4, the network node 110 depicted in fig. 1 and 2, and/or the split base station architecture depicted in fig. 3.

In a first operation 512, the network node 504 may send a first SI associated with the anchor cell 508 and proxy information associated with obtaining a second SI associated with the non-anchor cell 510, and the UE 502 may receive the first SI and the proxy information. In some aspects, the first SI may include a first SIB1. The first SIB1 may include scheduling information associated with a second SIB1 associated with the non-anchor cell 510. The first SIB1 may include an SI type indication indicating that the first SIB1 is to be used as the second SIB1. In some aspects, SIB1 for non-anchor cell 510 may be provided in a similar manner as other SIs on anchor cell 508. In some aspects, SIB1 associated with anchor cell 508 may include "SI-SchedulingInfo" to provide information (such as periodicity) needed to acquire SIB1 associated with non-anchor cell 510.

In some aspects, SIB1 may indicate a cell ID associated with non-anchor cell 510. The first SIB1 may indicate any number of other cell IDs and/or area IDs for which the first SIB1 provides proxy information. In some aspects, the first SIB1 may include scheduling information indicating a cell ID. In some aspects, the first SIB1 may include an SI type indication that indicates a cell ID. SIB1 may indicate a region ID associated with a region associated with non-anchor cell 510. For example, "systemInformationAreaID" (or a dedicated Information Element (IE), such as "systemInformationAreaID _sib1" or "systemInformationAreaID _ nonAcnhor") may be indicated as being associated with the provided SIB1. In some examples, the area ID may not represent the anchor cell 508 itself. The region ID may be associated with one or more associated SIB1 s. In some aspects, the first SIB1 may include a second SIB1 associated with the non-anchor cell 510. In some aspects, the proxy information may include an indication of a difference between the first SIB1 and a second SIB1 associated with the non-anchor cell 510.

In some aspects, the second SI may comprise an on-demand SI. In operation 514, the UE 502 may send a request for the second SI and the network node 504 may receive the request. In some aspects, the UE 502 may send the request for the second SI based on sending a Random Access Channel (RACH) message indicating the request for the second SI. In some aspects, the proxy information may indicate at least one of a request configuration associated with a request for on-demand SI associated with the non-anchor cell 510 or a resource allocation associated with the request, and the UE 502 may send the request. In some aspects, the UE 502 may send the request based on sending a RACH message indicating the request. In operation 516, the UE 502 may send a request for other SIs and the network node 506 may receive the request.

In operation 518, the network node 506 may transmit the second SI and the UE 502 may receive the second SI. The network node 506 may send a second SI based on the proxy information, wherein the second SI is an on-demand SI. In operation 520, the network node 504 may send at least one of a monitoring configuration or a resource allocation, and the UE 502 may receive at least one of the monitoring configuration or the resource allocation. The UE 502 may receive the on-demand SI based on at least one of a monitoring configuration or resource allocation.

In some aspects, the proxy information may indicate at least one of a configuration associated with a second SIB1 associated with the non-anchor cell 510 or a resource allocation associated with the second SIB 1. In some aspects, the UE 502 may obtain the second SI based on at least one of a configuration associated with the second SIB1 or a resource allocation associated with the second SIB 1. In some aspects, the UE 502 may receive proxy information based on receiving a first SIB1 associated with the anchor cell 508. The first SIB1 may indicate proxy information. In some aspects, receiving proxy information may include receiving a dedicated SI transmission from the first network node 504. In some aspects, receiving the proxy information may include receiving an RRC message from the network node 504.

In some aspects, at least one of the first SI or the second SI may indicate scheduling information associated with other SIs associated with the non-anchor cell 510. In operation 522, the network node 504 may transmit other SI and the UE 502 may receive the other SI. In operation 524, the network node 506 may send other SI and the UE 502 may receive the other SI. In some aspects, the other SIs may include on-demand SIs. In some aspects, the first SI may indicate scheduling information associated with other SIs. In some aspects, the scheduling information may indicate the one of the anchor cell 508 and the non-anchor cell 510 on which to send requests for other SIs.

In some aspects, at least one of the first SI or the second SI may indicate a region ID associated with the non-anchor cell 510, and the UE 502 may obtain other SIs associated with the non-anchor cell 510 based on the region ID. In some aspects, the first SI may indicate SIB1 associated with non-anchor cell 510 and the first SI may indicate whether non-anchor cell 510 is associated with a region ID associated with anchor cell 508. In some aspects, the UE 502 may obtain the second SI based on receiving SIB1 associated with the non-anchor cell 510 from the network node 506. SIB1 may indicate an additional network node associated with an additional cell associated with a region ID associated with network node 506. In some aspects, the region ID may be associated with other SIs associated with the non-anchor cell 510.

In some aspects, the UE 502 may obtain the second SI based on receiving SIB1 associated with the non-anchor cell 510 from the network node 506. SIB1 may indicate additional network nodes associated with additional cells associated with other SIs that are associated with non-anchor cell 510. In some aspects, other SIs may be common to non-anchor cell 510 and the additional cells.

In some aspects, the UE 502 may monitor the SI update indication on the non-anchor cell 510. The UE 502 may receive the SI update indication and obtain updated SI associated with the non-anchor cell 510 from the network node 504 based on receiving the SI update indication. In some aspects, the UE 502 may monitor on at least one of the anchor cell 508 or the non-anchor cell 510. In some aspects, the UE 502 may monitor the paging message on the anchor cell 508 or the non-anchor cell 510. In some aspects, the UE 502 may monitor the anchor cell 508 for SI update indications associated with the non-anchor cell 510.

In some aspects, the network node 504 may send a short message including an SI update indication, and the UE 502 may obtain the first SIB1 associated with the anchor cell 508 based on receiving the short message. The first SIB1 may indicate a change in a second SIB1 associated with the non-anchor cell 510. In some aspects, the UE 502 may receive a non-anchor cell indication indicating at least one of an SI update change associated with at least one non-anchor cell, a cell ID associated with at least one non-anchor cell, or a region ID associated with at least one non-anchor cell.

In some aspects, the UE 502 may receive the non-anchor cell indication based on receiving a short message including the non-anchor cell indication. In some aspects, the UE 502 may monitor for non-anchor cell indications. In some aspects, the UE 502 may receive a non-anchor cell indication based on receiving a Physical Downlink Shared Channel (PDSCH) communication including the non-anchor cell indication. In some aspects, the UE 502 may receive the non-anchor cell indication based on receiving a Permanent Equipment Identifier (PEI) that includes the non-anchor cell indication.

In some aspects, the second SI may be associated with an SI specific region ID. In some aspects, the UE 502 may receive a communication including an indication of at least one neighbor cell ID associated with a region ID associated with the anchor cell 508. In some aspects, the communication may include at least one of SIB1, other SI, or RRC messages.

In some aspects, the UE 502 may receive a Physical Broadcast Channel (PBCH) communication including cell information indicating the anchor cell 508, and the UE 502 may monitor the first SI based on the PBCH communication. In some aspects, the cell information may indicate one or more frequency resources associated with the anchor cell 508. The cell information may indicate a cell ID associated with the anchor cell 508 and/or a region ID associated with the anchor cell 508.

Fig. 6 is a flowchart illustrating an example process 600 performed, for example, by a UE supporting communication with a non-anchor cell in accordance with the present disclosure. The example process 600 is an example in which a UE (e.g., the UE 502) performs operations associated with SI associated with a cell operating in a power save mode.

As shown in fig. 6, in some aspects, process 600 may include receiving a first SI associated with an anchor cell from a first network node associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell (block 610). For example, the UE (such as by using the communication manager 808 or receiving component 802 depicted in fig. 8) may receive a first SI associated with an anchor cell from a first network node associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell associated with a power save mode of operation, as described above.

As further shown in fig. 6, in some aspects, the process 600 may include obtaining a second SI based on the proxy information (block 620). For example, the UE (such as by using the communication manager 808 or receiving component 802 depicted in fig. 8) may obtain the second SI based on the proxy information, as described above.

As further shown in fig. 6, in some aspects, process 600 may include communicating with a non-anchor cell based on a second SI (block 630). For example, the UE (such as by using the communication manager 808, receiving component 802, or transmitting component 804 depicted in fig. 8) may communicate with the non-anchor cell based on the second SI, as described above.

Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.

In a first additional aspect, the first SI includes a first SIB1. In a second additional aspect, alone or in combination with the first aspect, the first SIB1 includes scheduling information associated with a second SIB1 associated with the non-anchor cell. In a third additional aspect, alone or in combination with one or more of the first and second aspects, the first SIB1 includes an SI type indication indicating that the first SIB1 is to be used as the second SIB1. In a fourth additional aspect, SIB1 indicates a cell ID associated with the non-anchor cell, alone or in combination with one or more of the first to third aspects. In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, the first SIB1 includes scheduling information indicating a cell ID. In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the first SIB1 includes an SI type indication indicating a cell ID.

In a seventh additional aspect, alone or in combination with one or more of the first through sixth aspects, SIB1 indicates a region ID associated with a region associated with the non-anchor cell. In an eighth additional aspect, the first SIB1 includes a second SIB1 associated with the non-anchor cell, alone or in combination with one or more of the first through seventh aspects. In a ninth additional aspect, the proxy information comprises an indication of a difference between the first SIB1 and a second SIB1 associated with the non-anchor cell, alone or in combination with one or more of the first to eighth aspects.

In a tenth additional aspect, alone or in combination with one or more of the first through ninth aspects, the second SI comprises an on-demand SI, and the process 600 comprises sending a request for the second SI to the first network node. In an eleventh additional aspect, alone or in combination with one or more of the first through tenth aspects, sending the request for the second SI includes sending a RACH message indicating the request for the second SI. In a twelfth additional aspect, alone or in combination with one or more of the first through eleventh aspects, the proxy information indicates at least one of a request configuration associated with a request for on-demand SI associated with a non-anchor cell or a resource allocation associated with the request, the process 600 comprising sending the request. In a thirteenth additional aspect, alone or in combination with one or more of the first to twelfth aspects, the sending the request includes sending a RACH message indicating the request.

In a fourteenth additional aspect, alone or in combination with one or more of the first to thirteenth aspects, sending the request includes sending the request to the anchor cell. In a fifteenth additional aspect, alone or in combination with one or more of the first through fourteenth aspects, sending the request includes sending the request to a non-anchor cell. In a sixteenth additional aspect, alone or in combination with one or more of the first through fifteenth aspects, obtaining the second SI based on the proxy information includes receiving an on-demand SI from the non-anchor cell based on the request. In a seventeenth additional aspect, alone or in combination with one or more of the first through sixteenth aspects, the process 600 includes receiving at least one of a monitoring configuration or a resource allocation from the first network node, wherein receiving the on-demand SI includes receiving the on-demand SI based on the at least one of the monitoring configuration or the resource allocation.

In an eighteenth additional aspect, alone or in combination with one or more of the first through seventeenth aspects, the proxy information indicates at least one of a configuration associated with a second SIB1 associated with the non-anchor cell or a resource allocation associated with the second SIB1, wherein obtaining the second SI includes receiving the second SIB1 based on at least one of the configuration associated with the second SIB1 or the resource allocation associated with the second SIB1. In a nineteenth additional aspect, alone or in combination with one or more of the first through eighteenth aspects, receiving the proxy information includes receiving a first SIB1 associated with the anchor cell, the first SIB1 indicating the proxy information. In a twenty-eighth aspect, alone or in combination with one or more of the first to nineteenth aspects, the method further comprises receiving a dedicated SI transmission from the first network node. In a twenty-first additional aspect, alone or in combination with one or more of the first to twentieth aspects, receiving the proxy information comprises receiving an RRC message from the first network node.

In a twenty-second additional aspect, alone or in combination with one or more of the first to twenty-first aspects, at least one of the first or second SI indicates scheduling information associated with other SI associated with the non-anchor cell. In a twenty-third additional aspect, alone or in combination with one or more of the first through twenty-second aspects, the process 600 includes receiving other SIs. In a twenty-fourth additional aspect, alone or in combination with one or more of the first to twenty-third aspects, receiving the other SI comprises receiving the other SI from the first network node. In a twenty-fifth additional aspect, alone or in combination with one or more of the first to twenty-fourth aspects, receiving the other SI comprises receiving the other SI from a second network node associated with the non-anchor cell. In a twenty-sixth additional aspect, alone or in combination with one or more of the first through twenty-fifth aspects, the other SI comprises an on-demand SI. In a twenty-seventh additional aspect, alone or in combination with one or more of the first through twenty-sixth aspects, the first SI indicates scheduling information associated with other SIs. In a twenty-eighth additional aspect, alone or in combination with one or more of the first through twenty-seventh aspects, the scheduling information indicates a cell of the anchor cell and the non-anchor cell on which to send requests for other SIs.

In a twenty-ninth additional aspect, alone or in combination with one or more of the first through twenty-eighth aspects, at least one of the first SI or the second SI indicates a region ID associated with the non-anchor cell, the process 600 includes obtaining other SIs associated with the non-anchor cell based on the region ID. In a thirty-third additional aspect, alone or in combination with one or more of the first through twenty-ninth aspects, the first SI indicates SIB1 associated with the non-anchor cell and the first SI indicates whether the non-anchor cell is associated with a region ID associated with the anchor cell. In a thirty-first additional aspect, alone or in combination with one or more of the first through thirty-first aspects, obtaining the second SI comprises receiving a SIB1 associated with the non-anchor cell from a second network node associated with the non-anchor cell, wherein the SIB1 indicates an additional network node associated with an additional cell associated with a region ID, wherein the region ID is associated with the second network node. In a thirty-second additional aspect, alone or in combination with one or more of the first through thirty-first aspects, the region ID is associated with other SIs associated with non-anchor cells.

In a thirty-third additional aspect, alone or in combination with one or more of the first through thirty-second aspects, obtaining the second SI comprises receiving SIB1 associated with the non-anchor cell from a second network node associated with the non-anchor cell, wherein the SIB1 indicates additional network nodes associated with additional cells associated with other SIs, wherein the other SIs are associated with the non-anchor cell. In a thirty-fourth additional aspect, other SIs are common to the non-anchor cell and the additional cell, alone or in combination with one or more of the first through thirty-third aspects.

In a thirty-fifth additional aspect, alone or in combination with one or more of the first through thirty-fourth aspects, the process 600 comprises monitoring SI update indications on non-anchor cells. In a thirty-sixth additional aspect, alone or in combination with one or more of the first through thirty-fifth aspects, the process 600 includes receiving an SI update indication and obtaining updated SI associated with the non-anchor cell from the first network node based on receiving the SI update indication. In a thirty-seventh additional aspect, alone or in combination with one or more of the first through thirty-sixth aspects, the process 600 comprises monitoring for paging messages on at least one of an anchor cell or a non-anchor cell. In a thirty-eighth additional aspect, alone or in combination with one or more of the first through thirty-seventh aspects, the process 600 includes monitoring, on the anchor cell, an SI update indication associated with the non-anchor cell. In a thirty-ninth additional aspect, alone or in combination with one or more of the first through thirty-eighth aspects, the process 600 includes receiving a short message including an SI update indication from a first network node, and obtaining a first SIB1 associated with an anchor cell based on receiving the short message, wherein the first SIB1 indicates a change in a second SIB1 associated with a non-anchor cell. In a fortieth additional aspect, alone or in combination with one or more of the first through thirty-ninth aspects, the process 600 includes receiving a non-anchor cell indication indicating at least one of a SI update change associated with at least one non-anchor cell, a cell ID associated with at least one non-anchor cell, or a region ID associated with at least one non-anchor cell. In a forty-additional aspect, alone or in combination with one or more of the first through fortieth aspects, receiving the non-anchor cell indication comprises receiving a short message comprising the non-anchor cell indication.

In a forty-second additional aspect, alone or in combination with one or more of the first through fortieth aspects, the process 600 includes monitoring for non-anchor cell indications. In a forty-third additional aspect, alone or in combination with one or more of the first through forty-second aspects, receiving the non-anchor cell indication comprises receiving PDSCH communications including the non-anchor cell indication. In a fortieth additional aspect, alone or in combination with one or more of the first through fortieth aspects, receiving the non-anchor cell indication comprises receiving a permanent equipment identifier comprising the non-anchor cell indication.

In a forty-fifth additional aspect, alone or in combination with one or more of the first through forty-fourth aspects, the second SI is associated with an SI specific region identifier. In a forty-sixth additional aspect, alone or in combination with one or more of the first through forty-fifth aspects, the process 600 includes receiving a communication including an indication of at least one neighbor cell ID associated with a region ID, wherein the region ID is associated with an anchor cell. In a forty-seventh additional aspect, alone or in combination with one or more of the first through forty-sixth aspects, the communication includes at least one of SIB1, other SI, or RRC messages. In a forty-eighth additional aspect, alone or in combination with one or more of the first through forty-seventh aspects, the process 600 includes receiving a PBCH communication including cell information indicating an anchor cell, and monitoring the first SI based on the PBCH communication.

In a forty-ninth additional aspect, alone or in combination with one or more of the first through forty-eighth aspects, the cell information indicates one or more frequency resources associated with the anchor cell. In a fifty-additional aspect, the cell information indicates a cell ID associated with the anchor cell, alone or in combination with one or more of the first through fortieth aspects. In a fifty-first additional aspect, alone or in combination with one or more of the first through fifty aspects, the cell information indicates a region ID associated with the anchor cell.

In a fifty-second additional aspect, the non-anchor cell is associated with a power saving mode of operation, alone or in combination with one or more of the first through fifty aspects.

While fig. 6 shows example blocks of the process 600, in some aspects, the process 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than the blocks depicted in fig. 6. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

Fig. 7 is a flow chart illustrating an example process 700 performed, for example, by a network node supporting communication with a non-anchor cell in accordance with the present disclosure. Example process 700 is an example in which a network node (e.g., network node 110) performs operations associated with an SI associated with a cell operating in a power save mode.

As shown in fig. 7, in some aspects, process 700 may include receiving a proxy indication associated with a second network node associated with a non-anchor cell associated with a power save mode of operation, the first network node associated with an anchor cell (block 710). For example, a network node (such as by using the communication manager 908 or receiving component 902 depicted in fig. 9) may receive a proxy indication associated with a second network node associated with a non-anchor cell associated with a power save mode of operation, the first network node associated with an anchor cell, as described above.

As further shown in fig. 7, in some aspects, process 700 may include transmitting a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with the non-anchor cell based on receiving the proxy indication (block 720). For example, the network node (such as by using the communication manager 908 or the sending component 904 depicted in fig. 9) may send the first SI associated with the anchor cell and proxy information associated with obtaining the second SI associated with the non-anchor cell based on receiving the proxy indication, as described above.

Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.

In a first additional aspect, the first SI includes a first SIB1. In a second additional aspect, alone or in combination with the first aspect, the first SIB1 includes scheduling information associated with a second SIB1 associated with the non-anchor cell. In a third additional aspect, alone or in combination with one or more of the first and second aspects, the first SIB1 includes an SI type indication indicating that the first SIB1 is to be used as the second SIB1. In a fourth additional aspect, SIB1 indicates a cell ID associated with the non-anchor cell, alone or in combination with one or more of the first to third aspects. In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, the first SIB1 includes scheduling information indicating a cell ID. In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the first SIB1 includes an SI type indication indicating a cell ID. In a seventh additional aspect, alone or in combination with one or more of the first through sixth aspects, SIB1 indicates a region ID associated with a region associated with the non-anchor cell. In an eighth additional aspect, the first SIB1 includes a second SIB1 associated with the non-anchor cell, alone or in combination with one or more of the first through seventh aspects. In a ninth additional aspect, the proxy information comprises an indication of a difference between the first SIB1 and a second SIB1 associated with the non-anchor cell, alone or in combination with one or more of the first to eighth aspects.

In a tenth additional aspect, alone or in combination with one or more of the first through ninth aspects, the second SI comprises an on-demand SI, and the process 700 comprises receiving a request for the second SI. In an eleventh additional aspect, alone or in combination with one or more of the first through tenth aspects, receiving the request for the second SI includes receiving a RACH message indicating the request for the second SI. In a twelfth additional aspect, alone or in combination with one or more of the first through eleventh aspects, the proxy information indicates at least one of a request configuration associated with a request for on-demand SI associated with a non-anchor cell or a resource allocation associated with the request, the process 700 comprising receiving the request. In a thirteenth additional aspect, alone or in combination with one or more of the first to twelfth aspects, receiving the request includes receiving a RACH message indicating the request. In a fourteenth additional aspect, alone or in combination with one or more of the first through thirteenth aspects, the process 700 includes transmitting at least one of a monitoring configuration for obtaining the second SI from the non-anchor cell or a resource allocation for obtaining the second SI from the non-anchor cell. In a fifteenth additional aspect, alone or in combination with one or more of the first through fourteenth aspects, the proxy information indicates at least one of a configuration associated with a second SIB1 associated with the non-anchor cell or a resource allocation associated with the second SIB 1.

In a sixteenth additional aspect, alone or in combination with one or more of the first through fifteenth aspects, transmitting the proxy information includes transmitting a first SIB1 associated with the anchor cell, the first SIB1 indicating the proxy information. In a seventeenth additional aspect, alone or in combination with one or more of the first through sixteenth aspects, transmitting the proxy information includes transmitting a dedicated SI transmission including the proxy information. In an eighteenth additional aspect, alone or in combination with one or more of the first through seventeenth aspects, transmitting the proxy information includes transmitting an RRC message including the proxy information. In a nineteenth additional aspect, alone or in combination with one or more of the first through eighteenth aspects, at least one of the first or second SI indicates scheduling information associated with other SIs associated with non-anchor cells. In a twenty-eighth aspect, alone or in combination with one or more of the first through nineteenth aspects, the process 700 includes transmitting a second SI.

In a twenty-first additional aspect, alone or in combination with one or more of the first through twentieth aspects, the other SI comprises an on-demand SI. In a twenty-second additional aspect, alone or in combination with one or more of the first to twenty-first aspects, the scheduling information indicates a cell of the anchor cell and the non-anchor cell on which to send requests for other SIs. In a twenty-third additional aspect, alone or in combination with one or more of the first to twenty-second aspects, at least one of the first SI or the second SI indicates a region ID associated with the non-anchor cell. In a twenty-fourth additional aspect, alone or in combination with one or more of the first to twenty-third aspects, the first SI indicates SIB1 associated with the non-anchor cell and the first SI indicates whether the non-anchor cell is associated with a region ID associated with the anchor cell. In a twenty-fifth additional aspect, alone or in combination with one or more of the first through twenty-fourth aspects, the process 700 includes sending updated SI associated with the non-anchor cell.

In a twenty-sixth additional aspect, alone or in combination with one or more of the first through twenty-fifth aspects, the process 700 includes sending an SI update indication associated with the non-anchor cell. In a twenty-seventh additional aspect, alone or in combination with one or more of the first through twenty-sixth aspects, transmitting the SI update indication comprises transmitting a short message comprising the SI update indication, and process 700 comprises transmitting a first SIB1 associated with the anchor cell, wherein the first SIB1 indicates a change in a second SIB1 associated with the non-anchor cell. In a twenty-eighth additional aspect, alone or in combination with one or more of the first through twenty-seventh aspects, the second SI is associated with an SI-specific region ID. In a twenty-ninth additional aspect, alone or in combination with one or more of the first through twenty-eighth aspects, the process 700 includes transmitting a communication including an indication of at least one neighbor cell ID associated with a region ID, wherein the region ID is associated with an anchor cell. In a thirty-third additional aspect, the communication comprises at least one of SIB1, other SI, or RRC messages, alone or in combination with one or more of the first through twenty-ninth aspects.

In a thirty-first additional aspect, alone or in combination with one or more of the first through thirty-first aspects, the process 700 includes transmitting a PBCH communication including cell information indicating an anchor cell. In a thirty-second additional aspect, alone or in combination with one or more of the first through thirty-first aspects, the cell information indicates one or more frequency resources associated with the anchor cell. In a thirty-third additional aspect, alone or in combination with one or more of the first through thirty-second aspects, the cell information indicates a cell identifier associated with the anchor cell. In a thirty-fourth additional aspect, alone or in combination with one or more of the first to thirty-third aspects, the cell information indicates a region identifier associated with the anchor cell.

In a thirty-fifth additional aspect, the non-anchor cell is associated with a power saving mode of operation, alone or in combination with one or more of the first to thirty-fourth aspects.

While fig. 7 shows example blocks of process 700, in some aspects process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than the blocks depicted in fig. 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

Fig. 8 is an illustration of an example apparatus 800 for wireless communication supporting SI associated with a cell operating in a power save mode in accordance with the present disclosure. The apparatus 800 may be a UE, or the UE may include the apparatus 800. In some aspects, the apparatus 800 includes a receiving component 802, a transmitting component 804, and a communication manager 808 that can communicate with one another (e.g., via one or more buses). As shown, apparatus 800 can communicate with another apparatus 806 (such as a UE, a network node, or another wireless communication device) using a receiving component 802 and a transmitting component 804.

In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with fig. 5. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 600 of fig. 6. In some aspects, apparatus 800 may comprise one or more components of the UE described above in connection with fig. 2.

The receiving component 802 can receive communications, such as reference signals, control information, and/or data communications, from the device 806. The receiving component 802 can provide the received communication to one or more other components of the apparatus 800, such as the communication manager 140. In some aspects, the receiving component 802 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components. In some aspects, the receive component 802 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers/processors, and/or memories of the UE described above in connection with fig. 2.

The transmitting component 804 can transmit communications, such as reference signals, control information, and/or data communications, to the device 806. In some aspects, the communication manager 140 can generate a communication and can send the generated communication to the sending component 804 for sending to the device 806. In some aspects, the transmitting component 804 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping or encoding, etc.) on the generated communication and can transmit the processed signal to the device 806. In some aspects, the transmit component 804 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers/processors, and/or memories of the UE described above in connection with fig. 2. In some aspects, the sending component 804 may be co-located with the receiving component 802 in a transceiver.

The communication manager 808 may receive from a first network node associated with an anchor cell or may cause the receiving component 802 to receive from the first network node associated with the anchor cell a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell associated with a power saving mode of operation. The communication manager 808 may obtain the second SI based on the proxy information. The communication manager 808 may communicate with the non-anchor cell based on the second SI. In some aspects, the communication manager 808 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 140.

The communication manager 808 may include a controller/processor and/or memory of the UE described above in connection with fig. 2. In some aspects, the communication manager 808 includes a collection of components. Alternatively, the set of components may be separate and distinct from the communication manager 808. In some aspects, one or more components of the set of components may include, or may be implemented within, the controller/processor and/or memory of the UE described above in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be at least partially implemented as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform functions or operations of the component.

The receiving component 802 can receive, from a first network node associated with an anchor cell, a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell. The receiving component 802 may obtain the second SI based on the proxy information. The receiving component 802 and/or the transmitting component 804 can communicate with the non-anchor cell based on the second SI.

The receiving component 802 can receive at least one of a monitoring configuration or a resource allocation from a first network node, wherein receiving the on-demand SI comprises receiving the on-demand SI based on the at least one of the monitoring configuration or the resource allocation. The receiving component 802 may receive other SIs. The receiving component 802 may monitor SI update indications on non-anchor cells. The receiving component 802 may receive the SI update indication. The receiving component 802 may obtain updated SI associated with the non-anchor cell from the first network node based on receiving the SI update indication. The receiving component 802 can monitor for paging messages on at least one of an anchor cell or a non-anchor cell. The receiving component 802 may monitor the SI update indication associated with the non-anchor cell on the anchor cell. The receiving component 802 may receive a short message comprising an SI update indication from the first network node. The receiving component 802 can obtain a first SIB1 associated with the anchor cell based on receiving the short message, wherein the first SIB1 indicates a change in a second SIB1 associated with the non-anchor cell.

The receiving component 802 can receive a non-anchor cell indication indicating at least one of an SI update change associated with at least one non-anchor cell, a cell ID associated with at least one non-anchor cell, or a region ID associated with at least one non-anchor cell. The receiving component 802 can monitor for non-anchor cell indications. The receiving component 802 can receive a communication comprising an indication of at least one neighbor cell ID associated with a region ID, wherein the region ID is associated with an anchor cell. The receiving component 802 can receive PBCH communications that include cell information indicating an anchor cell. The receiving component 802 may monitor the first SI based on the PBCH communication.

The number and arrangement of components shown in fig. 8 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged in a different manner than the components shown in fig. 8. Further, two or more components shown in fig. 8 may be implemented within a single component, or a single component shown in fig. 8 may be implemented as multiple distributed components. Additionally or alternatively, the set of component(s) shown in fig. 8 may perform one or more functions described as being performed by another set of components shown in fig. 8.

Fig. 9 is an illustration of an example apparatus 900 for wireless communication supporting SI associated with a cell operating in a power save mode in accordance with the present disclosure. The apparatus 900 may be a network node or the network node may comprise the apparatus 900. In some aspects, the apparatus 900 includes a receiving component 902, a transmitting component 904, and a communication manager 908 that can communicate with one another (e.g., via one or more buses). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a network node, or another wireless communication device) using a receiving component 902 and a transmitting component 904.

In some aspects, apparatus 900 may be configured to perform one or more operations described herein in connection with fig. 5. Additionally or alternatively, apparatus 900 may be configured to perform one or more processes described herein, such as process 700 of fig. 7. In some aspects, apparatus 900 may comprise one or more components of a network node described above in connection with fig. 2.

The receiving component 902 can receive communications, such as reference signals, control information, and/or data communications, from the device 906. The receiving component 902 can provide the received communication to one or more other components of the apparatus 900, such as the communication manager 150. In some aspects, the receiving component 902 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components. In some aspects, the receiving component 902 can include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers/processors, and/or memories of the network node described above in connection with fig. 2.

The transmitting component 904 can transmit communications, such as reference signals, control information, and/or data communications, to the device 906. In some aspects, the communication manager 150 can generate a communication and can send the generated communication to the sending component 904 for sending to the device 906. In some aspects, the transmitting component 904 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping or encoding, etc.) on the generated communication and can transmit the processed signal to the device 906. In some aspects, the transmit component 904 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers/processors, and/or memories of the network node described above in connection with fig. 2. In some aspects, the sending component 904 may be co-located with the receiving component 902 in a transceiver.

The communication manager 908 can receive or can cause the receiving component 902 to receive a proxy indication associated with a second network node associated with a non-anchor cell, the first network node being associated with an anchor cell. The communication manager 908 may transmit based on receipt of the proxy indication or may cause the transmitting component 904 to transmit the first SI associated with the anchor cell and proxy information associated with obtaining the second SI associated with the non-anchor cell based on receipt of the proxy indication. In some aspects, the communication manager 908 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 150.

The communication manager 908 may include a controller/processor, memory, scheduler, and/or communication unit of the network node described above in connection with fig. 2. In some aspects, the communication manager 908 comprises a collection of components. Alternatively, the collection of components may be separate and distinct from the communication manager 908. In some aspects, one or more components of the set of components may include, or may be implemented within, the controller/processor, memory, scheduler, and/or communication unit of the network node described above in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be at least partially implemented as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform functions or operations of the component.

The receiving component 902 can receive a proxy indication associated with a second network node associated with a non-anchor cell associated with a power save mode of operation, the first network node associated with an anchor cell. The sending component 904 can send a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with the non-anchor cell based on receiving the proxy indication. The transmitting component 904 may transmit at least one of a monitoring configuration for obtaining the second SI from the non-anchor cell or a resource allocation for obtaining the second SI from the non-anchor cell. The sending component 904 may send other SIs. The sending component 904 can send the updated SI associated with the non-anchor cell. The sending component 904 can send an SI update indication associated with the non-anchor cell. The transmitting component 904 can transmit a communication comprising an indication of at least one neighbor cell ID associated with a region ID, wherein the region ID is associated with an anchor cell. The transmitting component 904 can transmit PBCH communications that include cell information indicating an anchor cell.

The number and arrangement of components shown in fig. 9 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged in a different manner than the components shown in fig. 9. Further, two or more components shown in fig. 9 may be implemented within a single component, or a single component shown in fig. 9 may be implemented as multiple distributed components. Additionally or alternatively, the set of component(s) shown in fig. 9 may perform one or more functions described as being performed by another set of components shown in fig. 9.

The following provides an overview of some aspects of the disclosure:

aspect 1a method of wireless communication performed by an apparatus at a User Equipment (UE), the method comprising receiving, from a first network node associated with an anchor cell, first System Information (SI) associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell, obtaining the second SI based on the proxy information, and communicating with the non-anchor cell based on the second SI.

Aspect 2 the method of aspect 1, wherein the first SI comprises a first SI block 1 (SIB 1).

Aspect 3 the method of aspect 2, wherein the first SIB1 includes scheduling information associated with a second SIB1 associated with the non-anchor cell.

Aspect 4 the method of aspect 3, wherein the first SIB1 includes an SI type indication indicating that the first SIB1 is to be used as the second SIB 1.

Aspect 5 the method of any one of aspects 2 to 4, wherein the SIB1 indicates a cell Identifier (ID) associated with the non-anchor cell.

Aspect 6 the method of aspect 5, wherein the first SIB1 includes scheduling information indicating the cell ID.

Aspect 7 the method of any one of claims 5 or 6, wherein the first SIB1 includes an SI type indication indicating the cell ID.

Aspect 8 the method of any one of aspects 2 to 7, wherein the SIB1 indicates a region Identifier (ID) associated with a region associated with the non-anchor cell.

Aspect 9 the method of any one of aspects 2 to 8, wherein the first SIB1 includes a second SIB1 associated with the non-anchor cell.

Aspect 10 the method of any one of aspects 2 to 9, wherein the proxy information includes an indication of a difference between the first SIB1 and a second SIB1 associated with the non-anchor cell.

Aspect 11 the method of aspect 1, wherein the second SI comprises an on-demand SI, the method further comprising sending a request for the second SI to the first network node.

Aspect 12 the method of aspect 11, wherein transmitting the request for the second SI comprises transmitting a Random Access Channel (RACH) message indicating a request for the second SI.

Aspect 13 the method of any one of aspects 1-12, wherein the proxy information indicates at least one of a request configuration associated with a request for on-demand SI associated with the non-anchor cell or a resource allocation associated with the request, the method further comprising sending the request.

Aspect 14 the method of aspect 13, wherein transmitting the request includes transmitting a Random Access Channel (RACH) message indicating the request.

Aspect 15 the method of any one of claims 13 or 14, wherein sending the request comprises sending the request to the anchor cell.

Aspect 16 the method of any one of claims 13 or 14, wherein sending the request comprises sending the request to the non-anchor cell.

Aspect 17 the method of any one of aspects 13-16, wherein obtaining the second SI based on the proxy information includes receiving the on-demand SI from the non-anchor cell based on the request.

Aspect 18 the method of aspect 17, further comprising receiving at least one of a monitoring configuration or a resource allocation from the first network node, wherein receiving the on-demand SI comprises receiving the on-demand SI based on the at least one of the monitoring configuration or the resource allocation.

The method of any one of aspects 1-18, wherein the proxy information indicates at least one of a configuration associated with a second SI block 1 (SIB 1) associated with the non-anchor cell or a resource allocation associated with the second SIB1, wherein obtaining the second SI includes receiving the second SIB1 based on the at least one of the configuration associated with the second SIB1 or the resource allocation associated with the second SIB1.

Aspect 20 the method of aspect 19, wherein receiving the proxy information comprises receiving a first SIB1 associated with the anchor cell, the first SIB1 indicating the proxy information.

Aspect 21 the method of any one of aspects 19 to 20, wherein receiving the proxy information comprises receiving a dedicated SI transmission from the first network node.

Aspect 22 the method according to any one of aspects 19 to 21, wherein receiving the proxy information comprises receiving a radio resource control message from the first network node.

Aspect 23 the method of any one of aspects 1-22, wherein at least one of the first SI or the second SI indicates scheduling information associated with other SIs associated with the non-anchor cell.

Aspect 24 the method of aspect 23, further comprising receiving the other SI.

Aspect 25 the method of aspect 24, wherein receiving the other SI comprises receiving the other SI from the first network node.

Aspect 26 the method of aspect 24, wherein receiving the other SI comprises receiving the other SI from a second network node associated with the non-anchor cell.

Aspect 27 the method of any one of aspects 23 to 26, wherein the other SI comprises an on-demand SI.

Aspect 28 the method of any one of aspects 23 to 27, wherein the first SI indicates scheduling information associated with the other SI.

Aspect 29 the method of aspect 28, wherein the scheduling information indicates a cell of the anchor cell and the non-anchor cell on which to send the request for the other SI.

Aspect 30 the method according to any one of aspects 1 to 29, wherein at least one of the first SI or the second SI indicates a region Identifier (ID) associated with the non-anchor cell, the method further comprising obtaining other SIs associated with the non-anchor cell based on the region ID.

Aspect 31 the method of any one of aspects 1 to 30, wherein the first SI indicates a system information block 1 (SIB 1) associated with the non-anchor cell, and wherein the first SI indicates whether the non-anchor cell is associated with a region Identifier (ID) associated with the anchor cell.

Aspect 32 the method of any one of aspects 1-31, wherein obtaining the second SI comprises receiving a system information block 1 (SIB 1) associated with the non-anchor cell from a second network node associated with the non-anchor cell, wherein the SIB1 indicates an additional network node associated with an additional cell associated with a region Identifier (ID), wherein the region ID is associated with the second network node.

Aspect 33 is the method of aspect 32, wherein the region ID is associated with other SIs associated with the non-anchor cell.

Aspect 34 the method of any one of aspects 1-33, wherein obtaining the second SI comprises receiving a system information block 1 (SIB 1) associated with the non-anchor cell from a second network node associated with the non-anchor cell, wherein the SIB1 indicates additional network nodes associated with additional cells associated with other SIs, wherein the other SIs are associated with the non-anchor cell.

Aspect 35 the method of aspect 34, wherein the other SI is common to the non-anchor cell and the additional cell.

Aspect 36 the method according to any one of aspects 1 to 35, further comprising monitoring SI update indications on the non-anchor cells.

Aspect 37 the method of aspect 36, further comprising receiving the SI update indication and obtaining updated SI associated with the non-anchor cell from the first network node based on receiving the SI update indication.

Aspect 38 the method of any one of claims 36 or 37 further comprising monitoring paging messages on at least one of the anchor cell or the non-anchor cell.

Aspect 39 the method according to any one of aspects 1 to 38, further comprising monitoring, on the anchor cell, an SI update indication associated with the non-anchor cell.

Aspect 40 the method of aspect 39, further comprising receiving a short message from the first network node comprising the SI update indication, and obtaining a first SI block 1 (SIB 1) associated with the anchor cell based on receiving the short message, wherein the first SIB1 indicates a change in a second SIB1 associated with the non-anchor cell.

Aspect 41 the method of any one of aspects 1 to 40, the method further comprising receiving a non-anchor cell indication indicating at least one of an SI update change associated with at least one non-anchor cell, a cell Identifier (ID) associated with the at least one non-anchor cell, or a region ID associated with the at least one non-anchor cell.

Aspect 42 the method of aspect 41, wherein receiving the non-anchor cell indication comprises receiving a short message comprising the non-anchor cell indication.

Aspect 43 the method according to any one of claims 41 or 42 further comprising monitoring the non-anchor cell indication.

Aspect 44 is the method of any one of aspects 41-43, wherein receiving the non-anchor cell indication includes receiving a Physical Downlink Shared Channel (PDSCH) communication including the non-anchor cell indication.

Aspect 45 the method of any one of aspects 41-44, wherein receiving the non-anchor cell indication includes receiving a permanent equipment identifier that includes the non-anchor cell indication.

Aspect 46 the method according to any one of aspects 1 to 45, wherein the second SI is associated with an SI specific region identifier.

Aspect 47 the method of any one of aspects 1-46, further comprising receiving a communication comprising an indication of at least one neighbor cell ID associated with a region Identifier (ID), wherein the region ID is associated with the anchor cell.

Aspect 48 the method of aspect 47, wherein the communication comprises at least one of a system information block 1 (SIB 1), other SI, or a radio resource control message.

Aspect 49 the method of any one of aspects 1-48, further comprising receiving a Physical Broadcast Channel (PBCH) communication including cell information indicating the anchor cell, and monitoring the first SI based on the PBCH communication.

Aspect 50 the method of aspect 49, wherein the cell information indicates one or more frequency resources associated with the anchor cell.

Aspect 51 is a method according to any one of claims 49 or 50, wherein the cell information indicates a cell identifier associated with the anchor cell.

Aspect 52 the method according to any one of aspects 49 to 51, wherein the cell information indicates a region identifier associated with the anchor cell.

Aspect 53 is a method of wireless communication performed by an apparatus at a first network node, the method comprising receiving a proxy indication associated with a second network node associated with a non-anchor cell, the first network node being associated with an anchor cell, and transmitting first System Information (SI) associated with the anchor cell and proxy information associated with obtaining the second SI associated with the non-anchor cell based on receiving the proxy indication.

Aspect 54 the method of aspect 53, wherein the first SI comprises a first SI block 1 (SIB 1).

Aspect 55 the method of aspect 54, wherein the first SIB1 includes scheduling information associated with a second SIB1 associated with the non-anchor cell.

Aspect 56 the method of aspect 55, wherein the first SIB1 includes an SI type indication indicating that the first SIB1 is to be used as the second SIB 1.

Aspect 57 the method of any one of aspects 54-56, wherein the SIB1 indicates a cell Identifier (ID) associated with the non-anchor cell.

Aspect 58 the method of aspect 57, wherein the first SIB1 includes scheduling information indicating the cell ID.

Aspect 59 the method of any one of claims 57 or 58 wherein the first SIB1 includes an SI type indication that indicates the cell ID.

Aspect 60 the method of any one of aspects 54 to 59, wherein the SIB1 indicates a region Identifier (ID) associated with a region associated with the non-anchor cell.

Aspect 61 the method of any one of aspects 54 to 60, wherein the first SIB1 includes a second SIB1 associated with the non-anchor cell.

Aspect 62 is the method of any of aspects 54 to 61, wherein the proxy information includes an indication of a difference between the first SIB1 and a second SIB1 associated with the non-anchor cell.

Aspect 63 the method of any one of aspects 53-62, wherein the second SI comprises an on-demand SI, the method further comprising receiving a request for the second SI.

Aspect 64 the method of aspect 63, wherein receiving the request for the second SI comprises receiving a Random Access Channel (RACH) message indicating a request for the second SI.

Aspect 65 the method of any of aspects 53-64, wherein the proxy information indicates at least one of a request configuration associated with a request for on-demand SI associated with the non-anchor cell or a resource allocation associated with the request, the method further comprising receiving the request.

Aspect 66 the method of aspect 65, wherein receiving the request comprises receiving a Random Access Channel (RACH) message indicating the request.

Aspect 67 the method of any one of aspects 53-66, further comprising sending at least one of a monitoring configuration for obtaining the second SI from the non-anchor cell or a resource allocation for obtaining the second SI from the non-anchor cell.

Aspect 68 the method of any one of aspects 53-67, wherein the proxy information indicates at least one of a configuration associated with a second SI block 1 (SIB 1) associated with the non-anchor cell or a resource allocation associated with the second SIB 1.

Aspect 69 the method of aspect 68, wherein transmitting the proxy information comprises transmitting a first SIB1 associated with the anchor cell, the first SIB1 indicating the proxy information.

Aspect 70 the method of any one of aspects 53-69, wherein transmitting the proxy information includes transmitting a dedicated SI transmission including the proxy information.

Aspect 71 the method of any one of aspects 53-69, wherein transmitting the proxy information includes transmitting a radio resource control message including the proxy information.

Aspect 72 is the method of any one of aspects 53-71, wherein at least one of the first SI or the second SI indicates scheduling information associated with other SIs associated with the non-anchor cell.

Aspect 73 the method according to aspect 72, further comprising transmitting the other SI.

Aspect 74 the method of any one of claims 72 or 73, wherein the other SI comprises an on-demand SI.

Aspect 75 the method according to any one of aspects 72 to 74, wherein the scheduling information indicates a cell of the anchor cell and the non-anchor cell on which to send the request for the other SI.

Aspect 76 the method of any one of aspects 53-75, wherein at least one of the first SI or the second SI indicates a region Identifier (ID) associated with the non-anchor cell.

Aspect 77 is the method of any one of aspects 53-76, wherein the first SI indicates a system information block 1 (SIB 1) associated with the non-anchor cell, and wherein the first SI indicates whether the non-anchor cell is associated with a region Identifier (ID) associated with the anchor cell.

Aspect 78 the method of any one of aspects 53-77, further comprising sending updated SI associated with the non-anchor cell.

Aspect 79 the method according to any one of aspects 53 to 78, further comprising sending an SI update indication associated with the non-anchor cell.

Aspect 80 the method of aspect 79, wherein transmitting the SI update indication comprises transmitting a short message comprising the SI update indication, the method further comprising transmitting a first SI block 1 (SIB 1) associated with the anchor cell, wherein the first SIB1 indicates a change in a second SIB1 associated with the non-anchor cell.

Aspect 81 the method according to any of aspects 53 to 80, wherein the second SI is associated with an SI specific area identifier.

Aspect 82 the method of any one of aspects 53-81, further comprising transmitting a communication comprising an indication of at least one neighbor cell ID associated with a region Identifier (ID), wherein the region ID is associated with the anchor cell.

Aspect 83 the method of aspect 82, wherein the communication comprises at least one of a system information block 1 (SIB 1), other SI, or a radio resource control message.

Aspect 84 the method according to any one of aspects 53 to 83, further comprising transmitting a Physical Broadcast Channel (PBCH) communication comprising cell information indicating the anchor cell.

Aspect 85 the method of aspect 84, wherein the cell information indicates one or more frequency resources associated with the anchor cell.

Aspect 86 the method of any one of claims 84 or 85, wherein the cell information indicates a cell identifier associated with the anchor cell.

Aspect 87 the method according to any of aspects 84 to 86, wherein the cell information indicates a region identifier associated with the anchor cell.

Aspect 88 the method of any one of aspects 1 to 52 and/or the method of any one of aspects 53 to 87, wherein the non-anchor cell is associated with an energy saving mode of operation.

Aspect 89 an apparatus for wireless communication at a device, the apparatus comprising a processor, a memory coupled with the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1-52 and 88.

Aspect 90 an apparatus for wireless communication comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1-52 and 88.

Aspect 91 an apparatus for wireless communication comprising at least one means for performing the method according to one or more of aspects 1-52 and aspect 88.

Aspect 92 a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1-52 and aspect 88.

Aspect 93 is a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 1-52 and 88.

Aspect 94 an apparatus for wireless communication at a device, the apparatus comprising a processor, a memory coupled with the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 53-88.

Aspect 95 an apparatus for wireless communication comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 53-88.

Aspect 96 is an apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 53-88.

Aspect 97 is a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 53-88.

Aspect 98 is a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 53-88.

The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of various aspects.

As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and software. "software" should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures or functions, etc., whether described in software, firmware, middleware, microcode, hardware description language, or other terminology. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the system or method described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual specialized control hardware or software code used to implement the systems or methods is not limiting of the aspects. Thus, the operation and behavior of the systems or methods were described herein without reference to the specific software code-since one of ordinary skill in the art would understand that software and hardware could be designed to implement the systems or methods based at least in part on the description herein.

As used herein, a "meeting a threshold" may refer to a value greater than a threshold, greater than or equal to a threshold, less than or equal to a threshold, not equal to a threshold, etc., depending on the context.

Although specific combinations of features are expressed in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of the various aspects includes each dependent claim combined with each other claim in the set of claims. As used herein, a phrase referring to "at least one of a list of items" refers to any combination of these items (which includes a single member). As an example, "at least one of: a, b, or c" is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combinations with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Furthermore, as used herein, the article "a" is intended to include one or more items and may be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more items recited in connection with the article "the" and may be used interchangeably with "one or more. Furthermore, as used herein, the terms "set" and "group" are intended to include one or more items, and may be used interchangeably with "one or more". If only one item is intended, the phrase "only one" or similar terms will be used. Also, as used herein, the terms "having," "containing," "including," and the like are intended to be open ended terms that do not limit the element they modify (e.g., the element "comprising" a may also contain B). Furthermore, the phrase "based on" is intended to mean "based, at least in part, on" unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used serially is intended to be inclusive and interchangeable with "and/or" unless explicitly stated otherwise (e.g., if used in combination with "either of the two" or "only one of the two").

Claims (30)

1. A User Equipment (UE) for wireless communication, the User Equipment (UE) comprising:

a processing system comprising a processor circuit and a memory circuit coupled with the processor circuit, the processing system configured to cause the UE to:

receiving, from a first network node associated with an anchor cell, first System Information (SI) associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell;

obtaining the second SI based on the proxy information, and

And communicating with the non-anchor cell based on the second SI.

2. The UE of claim 1, wherein the first SI comprises a first SI block 1 (SIB 1).

3. The UE of claim 2, wherein the first SIB1 includes scheduling information associated with a second SIB1 associated with the non-anchor cell.

4. The UE of claim 2, wherein the SIB1 indicates a cell Identifier (ID) associated with the non-anchor cell.

5. The UE of claim 2, wherein the SIB1 indicates a region Identifier (ID) associated with a region associated with the non-anchor cell.

6. The UE of claim 2, wherein the first SIB1 comprises a second SIB1 associated with the non-anchor cell.

7. The UE of claim 2, wherein the proxy information includes an indication of a difference between the first SIB1 and a second SIB1 associated with the non-anchor cell.

8. The UE of claim 1, wherein the second SI comprises an on-demand SI, and wherein the processing system is further configured to cause the UE to send a request for the second SI to the first network node.

9. The UE of claim 8, wherein to cause the UE to transmit the request for the second SI, the processing system is configured to cause the UE to transmit a Random Access Channel (RACH) message indicating the request for the second SI.

10. The UE of claim 1, wherein the proxy information indicates at least one of a request configuration associated with a request for on-demand SI associated with the non-anchor cell or a resource allocation associated with the request, and wherein the processing system is further configured to cause the UE to send the request.

11. The UE of claim 10, wherein to cause the UE to transmit the request, the processing system is configured to cause the UE to transmit a Random Access Channel (RACH) message indicating the request.

12. The UE of claim 10, wherein to cause the UE to obtain the second SI based on the proxy information, the processing system is configured to cause the UE to receive the on-demand SI from the non-anchor cell based on the request.

13. The UE of claim 1, wherein the proxy information indicates at least one of a configuration associated with a second SI block 1 (SIB 1) associated with the non-anchor cell or a resource allocation associated with the second SIB1, wherein to cause the UE to obtain the second SI, the processing system is configured to cause the UE to receive the second SIB1 based on the at least one of the configuration associated with the second SIB1 or the resource allocation associated with the second SIB1.

14. The UE of claim 13, wherein to cause the UE to receive the proxy information, the processing system is configured to cause the UE to receive a first SIB1 associated with the anchor cell, the first SIB1 indicating the proxy information, a dedicated SI transmission from the first network node, or a radio resource control message from the first network node.

15. The UE of claim 1, wherein at least one of the first SI or the second SI indicates scheduling information associated with other SIs associated with the non-anchor cell.

16. The UE of claim 15, wherein the processing system is further configured to cause the UE to receive the other SI from the first network node or from a second network node associated with the non-anchor cell.

17. The UE of claim 1, wherein at least one of the first SI or the second SI indicates a region Identifier (ID) associated with the non-anchor cell, and wherein processing system is further configured to cause the UE to obtain other SIs associated with the non-anchor cell based on the region ID.

18. The UE of claim 1, wherein the first SI indicates a system information block 1 (SIB 1) associated with the non-anchor cell, and wherein the first SI indicates whether the non-anchor cell is associated with a region Identifier (ID) associated with the anchor cell.

19. The UE of claim 1, wherein to cause the UE to obtain the second SI, the processing system is configured to cause the UE to receive a system information block 1 (SIB 1) associated with the non-anchor cell from a second network node associated with the non-anchor cell, wherein the SIB1 indicates an additional network node associated with an additional cell associated with a region Identifier (ID), wherein the region ID is associated with the second network node.

20. The UE of claim 1, wherein to cause the UE to obtain the second SI, the processing system is configured to cause the UE to receive a system information block 1 (SIB 1) associated with the non-anchor cell from a second network node associated with the non-anchor cell, wherein the SIB1 indicates additional network nodes associated with additional cells associated with other SIs, wherein the other SIs are associated with the non-anchor cell.

21. The UE of claim 1, wherein the processing system is further configured to cause the UE to monitor SI update indications on the non-anchor cell.

22. The UE of claim 1, wherein the processing system is further configured to cause the UE to monitor, on the anchor cell, SI update indications associated with the non-anchor cell.

23. The UE of claim 1, wherein the processing system is further configured to cause the UE to receive a non-anchor cell indication indicating at least one of an SI update change associated with at least one non-anchor cell, a cell Identifier (ID) associated with the at least one non-anchor cell, or a region ID associated with the at least one non-anchor cell.

24. The UE of claim 1, wherein the second SI is associated with an SI-specific region identifier.

25. The UE of claim 1, wherein the processing system is further configured to cause the UE to receive a communication comprising an indication of at least one neighbor cell ID associated with a region Identifier (ID), wherein the region ID is associated with the anchor cell.

26. The UE of claim 1, wherein the processing system is further configured to cause the UE to:

receiving Physical Broadcast Channel (PBCH) communications including cell information indicating the anchor cell, and

27. A first network node for wireless communication, the first network node comprising:

A processing system comprising a processor circuit and a memory circuit coupled with the processor circuit, the processing system configured to cause the first network node to:

Receiving a proxy indication associated with a second network node associated with a non-anchor cell, the first network node being associated with an anchor cell, and

First System Information (SI) associated with the anchor cell and proxy information associated with obtaining a second SI associated with the non-anchor cell are sent based on receiving the proxy indication.

28. The first network node of claim 27, wherein the first SI comprises a first SI block 1 (SIB 1).

29. A method of wireless communication performed by an apparatus at a User Equipment (UE), the method comprising:

receiving, from a first network node associated with an anchor cell, first System Information (SI) associated with the anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell;

obtaining the second SI based on the proxy information, and

And communicating with the non-anchor cell based on the second SI.

30. The method of claim 29, wherein the first SI comprises a first SI block 1 (SIB 1).