Providing system information associated with non-anchor cells

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) can 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. 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

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 382,283, filed on November 3, 2022, entitled “PROVIDING SYSTEM INFORMATION ASSOCIATED WITH NON-ANCHOR CELLS,” and U.S. Non-Provisional Patent Application No. 18 / 465,637, filed on September 12, 2023, entitled “PROVIDING SYSTEM INFORMATION ASSOCIATED WITH NON-ANCHOR CELLS,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and particularly to techniques and apparatuses for cell access associated with a non-anchor cell. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth or transmit power). Examples of such multiple access technologies 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 a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] The above multiple access technologies 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. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using CP-OFDM or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful.

[0006] In some deployments, an anchor cell (also referred to as an "anchor carrier") may be a cell that provides initial network access to a UE (e.g., in addition to providing data communications), 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, an anchor cell may operate in a "normal" non-energy-saving mode. In some such deployments, a non-anchor cell may operate in an energy-saving mode. Any number of additional anchor cells and / or non-anchor cells may also be deployed. In some cases, synchronization signal blocks (SSBs) and system information (SI) may be sent on an anchor cell rather than on a non-anchor cell. The SSBs and SI sent on the anchor cell may provide time and frequency synchronization information and SI for the non-anchor cell as well as for the anchor cell. However, in some examples, the management and / or coordination of SI between the anchor cell and the non-anchor cell may be insufficient, thereby negatively affecting the opportunity for an efficient cell access process. Summary of the invention

[0007] 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 to 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.

[0008] Some aspects described herein relate to a network node for wireless communication. The network node may include a processing system, the 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 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.

[0009] Some aspects described herein relate to a method of wireless communication performed by an apparatus at a UE. The method may include receiving, from a first network node associated with an anchor cell, first SI associated with the anchor cell and proxy information associated with obtaining 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.

[0010] 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 sending first SI associated with the anchor cell and proxy information associated with obtaining second SI associated with the non-anchor cell based on receiving the proxy indication.

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

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by 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 instruction set, when executed by one or more processors of the network node, may cause the network node to 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.

[0013] 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, first SI associated with the anchor cell and proxy information associated with obtaining 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.

[0014] 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, the apparatus being associated with an anchor cell. The apparatus may include means for sending first SI associated with the anchor cell and proxy information associated with obtaining second SI associated with the non-anchor cell based on receiving the proxy indication.

[0015] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices, or processing systems as fully described with reference to the accompanying drawings and the specification and as illustrated in the accompanying drawings and the specification.

[0016] The foregoing has broadly outlined the features and technical advantages of examples according to the present disclosure in an effort to make the following specific embodiments better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily utilized as the basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood according to the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to be able to understand the above features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only some typical aspects of the present disclosure and should not be considered to limit its scope, as the description may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0019] Figure 2 is a diagram illustrating communication between an example network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0020] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0021] Figure 4 is a diagram illustrating an example associated with network access and communication associated with an anchor cell and a non-anchor cell according to the present disclosure.

[0022] Figure 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 an anchor cell according to the present disclosure.

[0023] Figure 6 is a flow chart illustrating an example process performed, for example, by a UE supporting communications with a non-anchor cell in accordance with the present disclosure.

[0024] Figure 7 is a flow chart illustrating an example process performed, for example, by a network node supporting communications with a non-anchor cell in accordance with the present disclosure.

[0025] Figure 8 is a diagram of an example apparatus for wireless communications that supports communications with non-anchor cells in accordance with the present disclosure.

[0026] Fig. 9 is a diagram of an example apparatus for wireless communications that supports communications with non-anchor cells in accordance with the present disclosure. DETAILED DESCRIPTION

[0027] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, the aspect of any amount set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. Any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0028] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as "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 on the specific application and the design constraints imposed on the overall system.

[0029] Various aspects are generally related to providing and obtaining system information (SI) associated with a cell operating in an energy-saving mode (referred to herein as a "non-anchor cell"). Some aspects are more specifically related to a user equipment (UE) receiving proxy information associated with obtaining SI associated with a non-anchor cell from a network node associated with an anchor cell. In some aspects, the proxy information may be sent in the 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 can 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 SI updates.

[0030] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques may be used to facilitate providing information to a UE by which the UE may obtain SI associated with a non-anchor cell, which may facilitate a cell access procedure with the non-anchor cell while allowing the non-anchor cell to operate in an energy-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 energy saving.

[0031] Figure 1 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, as well as other examples. The 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 110d), one UE 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The network node 110 is an entity that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged 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, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), which means that the 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)).

[0032] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed 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, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point or a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, and / or a RAN node. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul interfaces, midhaul interfaces, or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0033] The network node 110 may include one or more chips, systems on chips (SoCs), chipsets, packages or devices that individually or collectively constitute or include a processing system. The processing system includes a processor (or "processing") circuit 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 components or circuits (all of which may be generally referred to as "processors" individually or collectively as "processors" or "processor circuits" herein). One or more of these processors may be individually or collectively configurable or configured to perform various functions or operations described herein. A processor group that is collectively configurable or configured to perform a set of functions may include a first processor that is configurable or configured to perform a first function in the set, and a second processor that is configurable or configured to perform a second function in the set, or may include all of the processor groups that are configured or configurable to perform the set of functions.

[0034] 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 components or circuits, each of which may include a tangible storage medium, such as a random access memory (RAM) or a read-only memory (ROM), or a combination thereof (all of which may be generally referred to herein as "memory" 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) to one or more of the processors, and may individually or collectively store processor executable code (such as software) 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 various functions or operations described herein without being configured by software. The processing system may also include, or be coupled to, one or more modems, such as a Wi-Fi (e.g., IEEE compliant) modem or a cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modem. In some implementations, 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 to a plurality of radios (collectively, "radios"), a plurality of radio frequency (RF) chains, or a plurality of transceivers, each of which in turn may be coupled to one or more of the plurality of antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains, or transceivers. The network node 110 may include or may be included in a housing that houses components associated with the network node 110, including the processing system.

[0035] Each network node 110 may provide communication coverage for a particular geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" may 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.

[0036] The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several thousand meters) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or a home network node.

[0037] The wireless network 100 may be a heterogeneous network that includes 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, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts). Figure 1 In the example shown in , 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 102c. The network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0038] In some aspects, the term "base station" or "network node" may refer to a converged 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, a DU, a RU, a 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 conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple 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 in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, 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.

[0039] 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 the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. 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.

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

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

[0042] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 may be a cellular phone (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, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an 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.

[0043] 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 a processor (or "processing") circuit in the form of one or more processors, microprocessors, processing units (such as CPUs, GPUs, NPUs, and / or DSPs), processing blocks, ASICs, PLDs (such as FPGAs), or other discrete gate or transistor logic components or circuits (all of which may be generally referred to herein as "processors" individually, or collectively as "processors" or "processor circuits"). One or more of these processors may be individually or collectively configurable or configured to perform various functions or operations described herein. A processor group that is collectively configurable or configured to perform a set of functions may include a first processor that is configurable or configured to perform a first function in the set, and a second processor that is configurable or configured to perform a second function in the set, or may include the processor group that is all configured or configurable to perform the set of functions.

[0044] 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 components or circuits, each of which may include a tangible storage medium, such as RAM or ROM, or a combination thereof (all of which may be generally referred to herein as "memory" 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) to one or more of the processors, and may individually or collectively store processor executable code (such as software) 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 various functions or operations described herein without being configured by software. The processing system may also include, or be coupled to, one or more modems, such as a Wi-Fi (e.g., IEEE compliant) modem or a cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modem. In some implementations, 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 to a plurality of radios (collectively, "radios"), a plurality of RF chains, or a plurality of transceivers, each of which in turn may be coupled to one or more of the plurality of antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains, or transceivers. UE 120 may include or may be included in a housing that houses components associated with UE 120, including the processing system.

[0045] Some UEs 120 may be considered as 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, meters, 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 as Internet of Things (IoT) devices, or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component or a memory component. 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., a memory) may be operably coupled, communicatively coupled, electronically coupled, or electrically coupled.

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

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

[0048] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, or channels by frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. Similar naming issues sometimes arise in conjunction 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 as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0049] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics or FR2 characteristics, and thus the features of FR1 or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

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

[0051] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive, from a 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; obtain the second SI based on the proxy information; and communicate with the non-anchor cell based on the second SI. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0052] In some aspects, the 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 based on receiving the proxy indication, send a first SI associated with the anchor cell and proxy information associated with obtaining a second SI associated with the non-anchor cell. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

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

[0054] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The 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)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, where 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 to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 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 234a to 234t).

[0055] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 or other network nodes 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal 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. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the 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 other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

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

[0057] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or may 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 (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or coupled to one or more transmit or receive components (such as Figure 2 One or more antenna elements of one or more components).

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

[0059] At the network node 110, uplink signals from the UE 120 or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232, shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 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.

[0060] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 2Any other component of the network node 110 may perform one or more techniques associated with system information associated with non-anchor cells, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 2 Any other component of the Figure 6 The process of 600 Figure 7 10 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 (e.g., directly, or after compilation, conversion, or interpretation) by one or more processors of network node 110 or UE 120, may cause the one or more processors, UE 120, or network node 110 to perform or direct, for example, Figure 6 The process of 600 Figure 7 The operations of process 700 or other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, or interpreting instructions, etc.

[0061] The term "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 the combination of Figure 2 Any one or more processors described herein, such as a single processor or a combination of multiple different processors. References to "one or more processors" should be understood to refer to the combination of Figure 2 Any one or more of the described processors. For example, the one or more processors of the 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 the 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.

[0062] 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 (one or more) processors of the one or more processors may perform first functions described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform second functions 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 the corresponding device, such as in conjunction with Figure 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 by a different subset of the one or more memories.

[0063] In some aspects, a UE (e.g., UE 120) includes: a component 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; a component for obtaining the second SI based on the proxy information; and / or a component for communicating with the non-anchor cell based on the second SI. The components for the 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.

[0064] In some aspects, a network node (e.g., network node 110) includes: a component 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 a component for sending a first SI associated with the anchor cell and a proxy information associated with obtaining a second SI associated with the non-anchor cell based on receiving the proxy indication. The components for the network node to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0065] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs and / or one or more RUs).

[0066] 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 decomposed base station (e.g., a decomposed 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 across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0067] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known 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 can be deployed separately. A 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. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0068] Figure 33 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed 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). The CU 310 may communicate with one or more DUs 330 via respective midhaul links (such as via an F1 interface). Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective RF access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0069] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as 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 corresponding 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 and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or to do both.

[0070] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The 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 specific implementations, the 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 bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0071] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 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 a functional split defined by 3GPP). In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0072] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as lower layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 340 may be controlled by the 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 a vRAN architecture).

[0073] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an 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-RTRIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0074] 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 the near-RT RIC 325 (such as via an A1 interface). The 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 the O-eNB with the near-RT RIC 325.

[0075] In some implementations, in order to generate an 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 the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to regulate 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 corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0076] Figure 4 4 is a diagram illustrating an example 400 associated with network access and communication associated with an anchor cell and a non-anchor cell according to the present disclosure. Example 400 illustrates a UE 402 that can communicate with one or more network nodes ("NN") 404, 406, 408, and 410. In some aspects, UE 402 can be, be similar to, include, or be combined with Figures 1 to 3 120, or included in the UE. In some aspects, the network nodes 404, 406, 408, and / or 410 may be, similar to, or include a combination of Figure 1 and Figure 2 The described network node 110 and / or in combination Figure 3 One or more components of the described decomposed base station architecture 300 may be included in the network node and / or the one or more components.

[0077] As shown, the network node 404 may be associated with an anchor cell 412, and the 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 to a UE (e.g., in addition to providing data communications), 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 send 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 (SIB1)), and / or other SI (OSI), etc. In some aspects, the network node 404 may send a paging message and / or other short message, etc.

[0078] In contrast, the network node 406 associated with the non-anchor cell 414 may be operable to not provide a cell access procedure, deactivate one or more components of the network node 406, and / or refrain from performing one or more operations that may be performed 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 the associated network node operating in an energy-saving mode at least in conjunction with the non-anchor cell. For example, in energy-saving mode, the network node 406 may deactivate one or more antenna panels, receive chains, and / or transmit chains, etc. In some examples, in energy-saving mode, the network node 406 may refrain from sending one or more types of SI (e.g., MIB, SSB, SIB1, and / or OSI, etc.), paging messages, and / or short messages, etc. An example of a non-anchor cell is a non-SSB cell. A non-SSB cell is a cell that does not send SSB. For example, the network node 406 may refrain from sending any broadcast transmissions (e.g., SSB, SI, and / or paging messages) on a non-SSB 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).

[0079] 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.

[0080] In some aspects, the network node 404 may send SSBs and SI on the anchor cell 412, while the network node 406 does not send SSBs and SI on the non-anchor cell 414. The SSBs and SI sent on the anchor cell 412 may provide time and frequency synchronization information and SI for the non-anchor cell 414 (and / or any number of additional non-anchor cells) and for the anchor cell 412. In some cases, sending SSBs on the anchor cell 412 (e.g., Pcell) but not on the non-anchor cell (e.g., Scell) may improve Scell ​​activation latency (e.g., because the UE 402 does not receive the corresponding SSB on each Scell). This improved Scell ​​activation latency may facilitate efficient Scell ​​activation and / or deactivation based on the actual traffic associated with the UE 402, which may result in network power savings. In addition, not sending SSBs and / or SI on the non-anchor cell (e.g., Scell) 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 anchor cells and non-anchor cells may be insufficient, negatively impacting the chances of an efficient cell access procedure.

[0081] Various aspects are generally related to providing SI associated with non-anchor cells. Some aspects more specifically relate to a UE receiving proxy information associated with obtaining SI associated with a non-anchor cell from a network node associated with an anchor cell. In some aspects, the proxy information may be sent in the 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 can obtain SI associated with the non-anchor cell. In some aspects, the anchor cell and / or the non-anchor cell may provide an SI update associated with the non-anchor cell. In some aspects, the anchor cell and / or the non-anchor cell may provide an indication of an SI update.

[0082] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques may be used to facilitate providing information to a UE by which the UE may obtain SI associated with a non-anchor cell, which may facilitate a cell access procedure with the non-anchor cell while allowing the non-anchor cell to operate in an energy-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 energy saving.

[0083] Figure 5 is a diagram illustrating an example 500 associated with obtaining SI associated with a non-anchor cell based on proxy information provided by an anchor cell according to the present disclosure. Figure 5 As shown, UE 502 can communicate with network node 504 and network node 506. In some aspects, UE 502 can be, be similar to, or include Figure 4 UE 402 and / or Figures 1 to 3 In some aspects, the network node 504 may be associated with the anchor cell 508, and the network node 506 may be associated with the non-anchor cell 510. In some aspects, the network node 504 may be, similar to, or include Figure 4 The network nodes 404, 408 and / or 410 depicted in Figure 1 and Figure 2 The network node 110 and / or Figure 3 In some aspects, the network node 506 may be, be similar to, or include one or more components of the decomposed base station architecture depicted in FIG. Figure 4 The network node 406 depicted in Figure 1 and Figure 2 The network node 110 and / or Figure 3 One or more components of the decomposed base station architecture depicted in, or are included in these network nodes and / or the one or more components.

[0084] 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 the 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, the SIB1 of the non-anchor cell 510 may be provided in a manner similar to other SI on the anchor cell 508. In some aspects, the SIB1 associated with the anchor cell 508 may include "SI-SchedulingInfo" to provide information (such as periodicity) required to obtain the SIB1 associated with the non-anchor cell 510.

[0085] In some aspects, the SIB1 may indicate a cell ID associated with the 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 the cell ID. In some aspects, the first SIB1 may include an SI type indication indicating the cell ID. The SIB1 may indicate an area ID associated with an area associated with the 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 area ID may be associated with one or more associated SIB1s. 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 the difference between the first SIB1 and the second SIB1 associated with the non-anchor cell 510.

[0086] In some aspects, the second SI may include 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 a 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 SI, and the network node 506 may receive the request.

[0087] In operation 518, the network node 506 may send a second SI, and the UE 502 may receive the second SI. The network node 506 may send the 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 the monitoring configuration or the resource allocation.

[0088] 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 SIB1. 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 SIB1. In some aspects, the UE 502 may receive the proxy information based on receiving a first SIB1 associated with the anchor cell 508. The first SIB1 may indicate the proxy information. In some aspects, receiving the 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.

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

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

[0091] 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 other SI associated with the non-anchor cell 510. In some aspects, the other SI may be common to the non-anchor cell 510 and the additional cell.

[0092] In some aspects, the UE 502 may monitor the non-anchor cell 510 for an SI update indication. 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 on the anchor cell 508 or the non-anchor cell 510 for a paging message. In some aspects, the UE 502 may monitor on the anchor cell 508 for an SI update indication associated with the non-anchor cell 510.

[0093] In some aspects, the network node 504 may send a short message including an SI update indication, and the UE 502 may, based on receiving the short message, obtain a first SIB1 associated with the anchor cell 508. The first SIB1 may indicate a change of 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 an area ID associated with at least one non-anchor cell.

[0094] 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 the non-anchor cell indication. In some aspects, the UE 502 may receive the 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) including the non-anchor cell indication.

[0095] In some aspects, the second SI may be associated with an SI-specific regional ID. In some aspects, the UE 502 may receive a communication including an indication of at least one neighboring cell ID associated with a regional ID, wherein the regional ID is associated with the anchor cell 508. In some aspects, the communication may include at least one of SIB1, other SI, or an RRC message.

[0096] 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 an area ID associated with the anchor cell 508.

[0097] Figure 6 is a flow chart illustrating an example process 600 performed, for example, by a UE supporting communications with a non-anchor cell in accordance with the present disclosure. Example process 600 is an example of operations in which a UE (eg, UE 502) performs SI associated with a cell operating in an energy saving mode.

[0098] like Figure 6 As shown, in some aspects, process 600 may include receiving, from a first network node associated with an anchor cell, first SI associated with the anchor cell and proxy information associated with obtaining second SI associated with a non-anchor cell (block 610). For example, a UE (such as by using Figure 8 The communication manager 808 or receiving component 802 depicted in the figure 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 non-anchor cell being associated with an energy-saving operation mode, as described above.

[0099] like Figure 6 As further shown, in some aspects, process 600 may include obtaining a second SI based on the proxy information (block 620). Figure 8 The communication manager 808 or the receiving component 802 depicted in can obtain the second SI based on the proxy information, as described above.

[0100] like Figure 6 As further shown, in some aspects, process 600 may include communicating with a non-anchor cell based on the second SI (block 630). Figure 8 The communication manager 808, receiving component 802, or sending component 804 depicted in FIG. 8 may communicate with the non-anchor cell based on the second SI, as described above.

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

[0102] 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 a 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 a second SIB1. In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, the SIB1 indicates a cell ID associated with a non-anchor cell. 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 to fifth aspects, the first SIB1 includes an SI type indication indicating a cell ID.

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

[0104] In a tenth additional aspect, alone or in combination with one or more of the first to ninth aspects, the second SI includes on-demand SI, and the process 600 includes 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 to 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 to 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, and the process 600 includes sending the request. In a thirteenth additional aspect, alone or in combination with one or more of the first to twelfth aspects, sending the request includes sending a RACH message indicating the request.

[0105] In a fourteenth additional aspect, alone or in combination with one or more of the first to thirteenth aspects, sending the request comprises sending the request to an anchor cell. In a fifteenth additional aspect, alone or in combination with one or more of the first to fourteenth aspects, sending the request comprises sending the request to a non-anchor cell. In a sixteenth additional aspect, alone or in combination with one or more of the first to fifteenth aspects, obtaining the second SI based on the proxy information comprises receiving 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 to sixteenth aspects, process 600 comprises receiving 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 at least one of the monitoring configuration or the resource allocation.

[0106] In an eighteenth additional aspect, alone or in combination with one or more of the first to seventeenth aspects, the proxy information indicates at least one of a configuration associated with a second SIB1 associated with a non-anchor cell or a resource allocation associated with the second SIB1, wherein obtaining the second SI comprises 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 to eighteenth aspects, receiving the proxy information comprises receiving a first SIB1 associated with an anchor cell, the first SIB1 indicating the proxy information. In a twentieth additional aspect, alone or in combination with one or more of the first to nineteenth aspects, receiving the proxy information comprises receiving a dedicated SI transmission from a 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.

[0107] 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 SI or the second SI indicates scheduling information associated with other SI associated with a non-anchor cell. In a twenty-third additional aspect, alone or in combination with one or more of the first to twenty-second aspects, the process 600 includes receiving other SI. In a twenty-fourth additional aspect, alone or in combination with one or more of the first to twenty-third aspects, receiving other SI includes receiving other SI from a 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 other SI includes receiving other SI from a second network node associated with a non-anchor cell. In a twenty-sixth additional aspect, alone or in combination with one or more of the first to twenty-fifth aspects, the other SI includes on-demand SI. In a twenty-seventh additional aspect, alone or in combination with one or more of the first to twenty-sixth aspects, the first SI indicates scheduling information associated with other SI. In a twenty-eighth additional aspect, alone or in combination with one or more of the first to twenty-seventh aspects, the scheduling information indicates a cell among the anchor cell and the non-anchor cell on which the request for the other SI is to be sent.

[0108] In a twenty-ninth additional aspect, alone or in combination with one or more of the first to twenty-eighth aspects, at least one of the first SI or the second SI indicates an area ID associated with the non-anchor cell, and the process 600 includes obtaining other SI associated with the non-anchor cell based on the area ID. In a thirtieth additional aspect, alone or in combination with one or more of the first to twenty-ninth aspects, the first SI indicates a SIB1 associated with the non-anchor cell, and the first SI indicates whether the non-anchor cell is associated with an area ID associated with the anchor cell. In a thirty-first additional aspect, alone or in combination with one or more of the first to thirtieth aspects, obtaining the second SI includes 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 an area ID, wherein the area 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 to thirty-first aspects, the area ID is associated with other SI associated with the non-anchor cell.

[0109] In a thirty-third additional aspect, alone or in combination with one or more of the first to thirty-second 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 the additional cell associated with other SI, wherein the other SI is associated with the non-anchor cell. In a thirty-fourth additional aspect, alone or in combination with one or more of the first to thirty-third aspects, the other SI is common to the non-anchor cell and the additional cell.

[0110] In a thirty-fifth additional aspect, alone or in combination with one or more of the first to thirty-fourth aspects, the process 600 includes monitoring an SI update indication on a non-anchor cell. In a thirty-sixth additional aspect, alone or in combination with one or more of the first to thirty-fifth aspects, the process 600 includes receiving an SI update indication, and obtaining updated SI associated with the non-anchor cell from a 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 to thirty-sixth aspects, the process 600 includes monitoring a paging message 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 to thirty-seventh aspects, the process 600 includes monitoring an SI update indication associated with a non-anchor cell on an anchor cell. In a thirty-ninth additional aspect, alone or in combination with one or more of the first to thirty-eight 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 of 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 to thirty-ninth aspects, the process 600 includes 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 ID associated with at least one non-anchor cell, or an area ID associated with at least one non-anchor cell. In a forty-first additional aspect, alone or in combination with one or more of the first to fortieth aspects, receiving the non-anchor cell indication includes receiving a short message including the non-anchor cell indication.

[0111] In a 42nd additional aspect, alone or in combination with one or more of the first to forty-first aspects, process 600 includes monitoring a non-anchor cell indication. In a 43rd additional aspect, alone or in combination with one or more of the first to forty-second aspects, receiving the non-anchor cell indication includes receiving a PDSCH communication including the non-anchor cell indication. In a 44th additional aspect, alone or in combination with one or more of the first to forty-third aspects, receiving the non-anchor cell indication includes receiving a permanent equipment identifier including the non-anchor cell indication.

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

[0113] In a 49th additional aspect, alone or in combination with one or more of the first to forty-eight aspects, the cell information indicates one or more frequency resources associated with the anchor cell. In a 50th additional aspect, alone or in combination with one or more of the first to forty-ninth aspects, the cell information indicates a cell ID associated with the anchor cell. In a 51st additional aspect, alone or in combination with one or more of the first to fiftieth aspects, the cell information indicates an area ID associated with the anchor cell.

[0114] In a fifty-second additional aspect, alone or in combination with one or more of the first to fiftieth aspects, the non-anchor cell is associated with an energy-saving mode of operation.

[0115] although Figure 6 An example block diagram of process 600 is shown, but in some aspects, process 600 may include Figure 6 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 600. Additionally or alternatively, two or more of the blocks in the process 600 may be performed in parallel.

[0116] Figure 7 is a flow chart illustrating an example process 700 performed, for example, by a network node supporting communications with a non-anchor cell in accordance with the present disclosure. Example process 700 is an example of operations in which a network node (e.g., network node 110) performs SI associated with a cell operating in an energy saving mode.

[0117] like Figure 7 As shown, in some aspects, process 700 may include receiving a proxy indication associated with a second network node associated with a non-anchor cell, the non-anchor cell being associated with an energy-saving mode of operation, the first network node being associated with the anchor cell (block 710). For example, the network node (such as by using Fig. 9 The communication manager 908 or receiving component 902 depicted in can receive a proxy indication associated with a second network node associated with a non-anchor cell, the non-anchor cell being associated with an energy-saving mode of operation, the first network node being associated with the anchor cell, as described above.

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

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

[0120] 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 a 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 a second SIB1. In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, the SIB1 indicates a cell ID associated with a non-anchor cell. 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 to 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 to sixth aspects, the SIB1 indicates an area ID associated with an area associated with a non-anchor cell. In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, the first SIB1 includes a second SIB1 associated with the non-anchor cell. In a ninth additional aspect, alone or in combination with one or more of the first to eighth aspects, the proxy information includes an indication of a difference between the first SIB1 and the second SIB1 associated with the non-anchor cell.

[0121] In a tenth additional aspect, either alone or in combination with one or more of the first to ninth aspects, the second SI includes an on-demand SI, and process 700 includes receiving a request for the second SI. In an eleventh additional aspect, either alone or in combination with one or more of the first to 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, either alone or in combination with one or more of the first to 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, and process 700 includes receiving the request. In a thirteenth additional aspect, either 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 to thirteenth aspects, the process 700 includes sending at least one of a monitoring configuration for obtaining a second SI from a 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 to 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 SIB1.

[0122] In a sixteenth additional aspect, alone or in combination with one or more of the first to fifteenth aspects, sending the proxy information comprises sending a first SIB1 associated with an 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 to sixteenth aspects, sending the proxy information comprises sending a dedicated SI transmission comprising the proxy information. In an eighteenth additional aspect, alone or in combination with one or more of the first to seventeenth aspects, sending the proxy information comprises sending an RRC message comprising the proxy information. In a nineteenth additional aspect, alone or in combination with one or more of the first to eighteenth aspects, at least one of the first SI or the second SI indicates scheduling information associated with other SI associated with a non-anchor cell. In a twentieth additional aspect, alone or in combination with one or more of the first to nineteenth aspects, process 700 comprises sending other SI.

[0123] In a twenty-first additional aspect, either alone or in combination with one or more of the first to twentieth aspects, the other SI includes on-demand SI. In a twenty-second additional aspect, either alone or in combination with one or more of the first to twenty-first aspects, the scheduling information indicates a cell in the anchor cell and the non-anchor cell on which the request for the other SI is to be sent. In a twenty-third additional aspect, either 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 an area ID associated with the non-anchor cell. In a twenty-fourth additional aspect, either 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 an area ID associated with the anchor cell. In a twenty-fifth additional aspect, either alone or in combination with one or more of the first to twenty-fourth aspects, the process 700 includes sending an updated SI associated with the non-anchor cell.

[0124] In a twenty-sixth additional aspect, alone or in combination with one or more of the first to twenty-fifth aspects, the process 700 includes sending an SI update indication associated with a non-anchor cell. In a twenty-seventh additional aspect, alone or in combination with one or more of the first to twenty-sixth aspects, sending the SI update indication includes sending a short message including the SI update indication, and the process 700 includes sending 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 to twenty-seventh aspects, the second SI is associated with an SI-specific area ID. In a twenty-ninth additional aspect, alone or in combination with one or more of the first to twenty-eighth aspects, the process 700 includes sending a communication including an indication of at least one neighboring cell ID associated with an area ID, wherein the area ID is associated with the anchor cell. In a thirtieth additional aspect, either alone or in combination with one or more of the first to twenty-ninth aspects, the communication comprises at least one of SIB1, other SI or RRC messages.

[0125] In a thirty-first additional aspect, either alone or in combination with one or more of the first to thirtieth aspects, process 700 includes sending a PBCH communication including cell information indicating an anchor cell. In a thirty-second additional aspect, either alone or in combination with one or more of the first to thirty-first aspects, the cell information indicates one or more frequency resources associated with the anchor cell. In a thirty-third additional aspect, either alone or in combination with one or more of the first to thirty-second aspects, the cell information indicates a cell identifier associated with the anchor cell. In a thirty-fourth additional aspect, either alone or in combination with one or more of the first to thirty-third aspects, the cell information indicates an area identifier associated with the anchor cell.

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

[0127] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more of the blocks in the process 700 may be performed in parallel.

[0128] Figure 8 8 is a diagram of an example apparatus 800 for wireless communication that supports SI associated with a cell operating in an energy saving mode according to 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 sending component 804, and a communication manager 808 that may communicate with each other (e.g., via one or more buses). As shown, the apparatus 800 may communicate with another apparatus 806 (such as a UE, a network node, or another wireless communication device) using the receiving component 802 and the sending component 804.

[0129] In some aspects, the apparatus 800 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 In some aspects, the apparatus 800 may include the above-mentioned process 600. Figure 2 One or more components of a UE are described.

[0130] The receiving component 802 may receive communications, such as reference signals, control information, and / or data communications, from the apparatus 806. The receiving component 802 may provide the received communications to one or more other components of the apparatus 800, such as the communications manager 140. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 802 may include the above in combination with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, and / or memories of a UE are described.

[0131] The transmission component 804 may transmit communications, such as reference signals, control information, and / or data communications, to the device 806. In some aspects, the communication manager 140 may generate communications and may transmit the generated communications to the transmission component 804 for transmission to the device 806. In some aspects, the transmission component 804 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 806. In some aspects, the transmission component 804 may include the above in combination with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, and / or memories of the described UE. In some aspects, the transmit component 804 can be co-located with the receive component 802 in a transceiver.

[0132] The communication manager 808 may receive or 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, the non-anchor cell being associated with the energy-saving operation mode. 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.

[0133] The communication manager 808 may include the above combined Figure 2 In some aspects, the communication manager 808 includes a collection of components. Alternatively, the collection of components may be separate and distinct from the communication manager 808. In some aspects, one or more components in the collection of components may include the above-mentioned combination Figure 2The controller / processor and / or memory of the described UE may be implemented therein or may be implemented therein. Additionally or alternatively, one or more components in the set of components may be at least partially implemented as software stored in the memory. For example, a component (or a portion of a component) may be implemented as an instruction or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0134] The receiving component 802 may receive, from a 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 the non-anchor cell. The receiving component 802 may obtain the second SI based on the proxy information. The receiving component 802 and / or the sending component 804 may communicate with the non-anchor cell based on the second SI.

[0135] The receiving component 802 may receive 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 at least one of the monitoring configuration or the resource allocation. The receiving component 802 may receive other SI. The receiving component 802 may monitor the SI update indication on the non-anchor cell. 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 may monitor the paging message on at least one of the anchor cell or the 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 including the SI update indication from the first network node. The receiving component 802 may 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.

[0136] The receiving component 802 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 an area ID associated with at least one non-anchor cell. The receiving component 802 may monitor the non-anchor cell indication. The receiving component 802 may receive a communication including an indication of at least one neighboring cell ID associated with an area ID, wherein the area ID is associated with an anchor cell. The receiving component 802 may receive a PBCH communication including cell information indicating the anchor cell. The receiving component 802 may monitor the first SI based on the PBCH communication.

[0137] Figure 8 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 8The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Figure 8 Two or more components shown in may be implemented in a single component, or Figure 8 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The collection of (one or more) components shown in can perform the operations described by Figure 8 One or more functions performed by a collection of another component shown in FIG.

[0138] Fig. 9 is a diagram of an example apparatus 900 for wireless communication that supports SI associated with a cell operating in an energy saving mode according to the present disclosure. The apparatus 900 may be a network node, or a network node may include the apparatus 900. In some aspects, the apparatus 900 includes a receiving component 902, a sending component 904, and a communication manager 908 that may communicate with each other (e.g., via one or more buses). As shown, the apparatus 900 may communicate with another apparatus 906 (such as a UE, a network node, or another wireless communication device) using the receiving component 902 and the sending component 904.

[0139] In some aspects, the apparatus 900 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 In some aspects, the apparatus 900 may include the above-mentioned process 700. Figure 2 One or more components of a described network node.

[0140] The receiving component 902 may receive communications, such as reference signals, control information, and / or data communications, from the device 906. The receiving component 902 may provide the received communications to one or more other components of the device 900, such as the communications manager 150. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 902 may include the above in combination with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors and / or memories of the described network nodes.

[0141] The transmission component 904 may transmit communications, such as reference signals, control information, and / or data communications, to the device 906. In some aspects, the communication manager 150 may generate communications and may transmit the generated communications to the transmission component 904 for transmission to the device 906. In some aspects, the transmission component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 906. In some aspects, the transmission component 904 may include the above in combination with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, and / or memories of the described network nodes. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0142] The communication manager 908 may receive or may 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 the anchor cell. The communication manager 908 may send or may cause the sending component 904 to 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. 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.

[0143] The communication manager 908 may include the above combined Figure 2 The controller / processor, memory, scheduler, and / or communication unit of the network node described herein. In some aspects, the communication manager 908 includes 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 in the collection of components may include the components described above in conjunction with Figure 2 The controller / processor, memory, scheduler and / or communication unit of the described network node may be implemented in or may be implemented therein. Additionally or alternatively, one or more components in the set of components may be at least partially implemented as software stored in the memory. For example, a component (or a portion of a component) may be implemented as an instruction or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0144] The receiving component 902 may receive a proxy indication associated with a second network node associated with a non-anchor cell, the non-anchor cell being associated with an energy-saving operation mode, and the first network node being associated with the anchor cell. The sending component 904 may 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 sending component 904 may send 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 SI. The sending component 904 may send an updated SI associated with the non-anchor cell. The sending component 904 may send an SI update indication associated with the non-anchor cell. The sending component 904 may send a communication including an indication of at least one neighboring cell ID associated with an area ID, wherein the area ID is associated with the anchor cell. The sending component 904 may send a PBCH communication including cell information indicating the anchor cell.

[0145] Fig. 9 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig. 9 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig. 9 Two or more components shown in may be implemented in a single component, or Fig. 9 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The collection of (one or more) components shown in can perform the operations described by Fig. 9 One or more functions performed by a collection of another component shown in FIG.

[0146] The following provides an overview of some aspects of the disclosure:

[0147] Aspect 1: A method of wireless communication performed by a device at a user equipment (UE), the method comprising: receiving first system information (SI) associated with an anchor cell and proxy information associated with obtaining a second SI associated with a non-anchor cell from a first network node associated with the anchor cell; obtaining the second SI based on the proxy information; and communicating with the non-anchor cell based on the second SI.

[0148] Aspect 2: The method according to aspect 1, wherein the first SI comprises a first SI block 1 (SIB1).

[0149] Aspect 3: The method according to aspect 2, wherein the first SIB1 includes scheduling information associated with a second SIB1 associated with the non-anchor cell.

[0150] Aspect 4: The method according to aspect 3, wherein the first SIB1 includes an SI type indication indicating that the first SIB1 is to be used as the second SIB1.

[0151] Aspect 5: The method according to any one of aspects 2 to 4, wherein the SIB1 indicates a cell identifier (ID) associated with the non-anchor cell.

[0152] Aspect 6: The method according to aspect 5, wherein the first SIB1 includes scheduling information indicating the cell ID.

[0153] Aspect 7: The method according to any one of claims 5 or 6, wherein the first SIB1 includes an SI type indication indicating the cell ID.

[0154] Aspect 8: The method according to any one of aspects 2 to 7, wherein the SIB1 indicates an area identifier (ID) associated with an area associated with the non-anchor cell.

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

[0156] Aspect 10: The method according to any one of aspects 2 to 9, wherein the proxy information comprises an indication of a difference between the first SIB1 and a second SIB1 associated with the non-anchor cell.

[0157] Aspect 11: The method according to aspect 1, wherein the second SI comprises on-demand SI, and the method further comprises sending a request for the second SI to the first network node.

[0158] Aspect 12: The method according to aspect 11, wherein sending the request for the second SI includes sending a random access channel (RACH) message indicating the request for the second SI.

[0159] Aspect 13: A method according to any one of Aspects 1 to 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, and the method further comprises sending the request.

[0160] Aspect 14: The method according to aspect 13, wherein sending the request includes sending a random access channel (RACH) message indicating the request.

[0161] Aspect 15: The method according to any one of claims 13 or 14, wherein sending the request comprises sending the request to the anchor cell.

[0162] Aspect 16: The method according to any one of claims 13 or 14, wherein sending the request comprises sending the request to the non-anchor cell.

[0163] Aspect 17: The method according to any one of aspects 13 to 16, wherein obtaining the second SI based on the proxy information comprises receiving the on-demand SI from the non-anchor cell based on the request.

[0164] Aspect 18: According to the method of aspect 17, the method also 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.

[0165] Aspect 19: A method according to any one of Aspects 1 to 18, wherein the proxy information indicates at least one of a configuration associated with a second SI block 1 (SIB1) associated with the non-anchor cell or a resource allocation associated with the second SIB1, and wherein obtaining the second SI includes receiving the second SIB1 based on the configuration associated with the second SIB1 or the at least one of the resource allocation associated with the second SIB1.

[0166] Aspect 20: The method according to aspect 19, wherein receiving the proxy information comprises receiving a first SIB1 associated with the anchor cell, the first SIB1 indicating the proxy information.

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

[0168] 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.

[0169] Aspect 23: The method according to any one of aspects 1 to 22, wherein at least one of the first SI or the second SI indicates scheduling information associated with other SI associated with the non-anchor cell.

[0170] Aspect 24: According to the method of Aspect 23, the method also includes receiving the other SI.

[0171] Aspect 25: The method according to aspect 24, wherein receiving the other SI comprises receiving the other SI from the first network node.

[0172] Aspect 26: The method according to aspect 24, wherein receiving the other SI comprises receiving the other SI from a second network node associated with the non-anchor cell.

[0173] Aspect 27: A method according to any one of Aspects 23 to 26, wherein the other SI comprises an on-demand SI.

[0174] Aspect 28: The method according to any one of aspects 23 to 27, wherein the first SI indicates scheduling information associated with the other SI.

[0175] Aspect 29: The method according to aspect 28, wherein the scheduling information indicates a cell among the anchor cell and the non-anchor cell on which the request for the other SI is to be sent.

[0176] Aspect 30: A method according to any one of Aspects 1 to 29, wherein at least one of the first SI or the second SI indicates an area identifier (ID) associated with the non-anchor cell, and the method also includes obtaining other SI associated with the non-anchor cell based on the area ID.

[0177] Aspect 31: A method according to any one of Aspects 1 to 30, wherein the first SI indicates a system information block 1 (SIB1) associated with the non-anchor cell, and wherein the first SI indicates whether the non-anchor cell is associated with an area identifier (ID) associated with the anchor cell.

[0178] Aspect 32: A method according to any one of Aspects 1 to 31, wherein obtaining the second SI includes receiving a system information block 1 (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 an area identifier (ID), wherein the area ID is associated with the second network node.

[0179] Aspect 33: The method according to aspect 32, wherein the area ID is associated with other SI associated with the non-anchor cell.

[0180] Aspect 34: A method according to any one of Aspects 1 to 33, wherein obtaining the second SI includes receiving a system information block 1 (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 other SI, wherein the other SI is associated with the non-anchor cell.

[0181] Aspect 35: The method according to aspect 34, wherein the other SI is common to the non-anchor cell and the additional cell.

[0182] Aspect 36: According to any one of aspects 1 to 35, the method further comprises monitoring an SI update indication on the non-anchor cell.

[0183] Aspect 37: The method according to aspect 36, the method 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.

[0184] Aspect 38: The method according to any one of claims 36 or 37, the method further comprising monitoring a paging message on at least one of the anchor cell or the non-anchor cell.

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

[0186] Aspect 40: According to the method according to Aspect 39, the method also includes: receiving a short message including the SI update indication from the first network node; and obtaining a first SI block 1 (SIB1) associated with the anchor cell based on receiving the short message, wherein the first SIB1 indicates a change of a second SIB1 associated with the non-anchor cell.

[0187] Aspect 41: According to any one of Aspects 1 to 40, the method also includes 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 an area ID associated with the at least one non-anchor cell.

[0188] Aspect 42: The method according to aspect 41, wherein receiving the non-anchor cell indication comprises receiving a short message including the non-anchor cell indication.

[0189] Aspect 43: The method according to any one of claims 41 or 42, further comprising monitoring the non-anchor cell indication.

[0190] Aspect 44: The method according to any one of aspects 41 to 43, wherein receiving the non-anchor cell indication comprises receiving a physical downlink shared channel (PDSCH) communication including the non-anchor cell indication.

[0191] Aspect 45: The method according to any one of aspects 41 to 44, wherein receiving the non-anchor cell indication comprises receiving a permanent equipment identifier including the non-anchor cell indication.

[0192] Aspect 46: A method according to any one of Aspects 1 to 45, wherein the second SI is associated with an SI specific area identifier.

[0193] Aspect 47: A method according to any one of Aspects 1 to 46, the method also includes receiving a communication including an indication of at least one neighboring cell ID associated with an area identifier (ID), wherein the area ID is associated with the anchor cell.

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

[0195] Aspect 49: According to the method described in any one of Aspects 1 to 48, the method further includes: receiving a physical broadcast channel (PBCH) communication including cell information indicating the anchor cell; and monitoring the first SI based on the PBCH communication.

[0196] Aspect 50: The method according to aspect 49, wherein the cell information indicates one or more frequency resources associated with the anchor cell.

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

[0198] Aspect 52: A method according to any one of aspects 49 to 51, wherein the cell information indicates an area identifier associated with the anchor cell.

[0199] Aspect 53: A method of wireless communication performed by a device 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 sending first system information (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.

[0200] Aspect 54: The method according to aspect 53, wherein the first SI comprises a first SI block 1 (SIB1).

[0201] Aspect 55: The method according to aspect 54, wherein the first SIB1 includes scheduling information associated with a second SIB1 associated with the non-anchor cell.

[0202] Aspect 56: The method according to aspect 55, wherein the first SIB1 includes an SI type indication indicating that the first SIB1 is to be used as the second SIB1.

[0203] Aspect 57: A method according to any one of aspects 54 to 56, wherein the SIB1 indicates a cell identifier (ID) associated with the non-anchor cell.

[0204] Aspect 58: The method according to aspect 57, wherein the first SIB1 includes scheduling information indicating the cell ID.

[0205] Aspect 59: The method according to any one of claims 57 or 58, wherein the first SIB1 includes an SI type indication indicating the cell ID.

[0206] Aspect 60: A method according to any one of aspects 54 to 59, wherein the SIB1 indicates an area identifier (ID) associated with an area associated with the non-anchor cell.

[0207] Aspect 61: A method according to any one of aspects 54 to 60, wherein the first SIB1 comprises a second SIB1 associated with the non-anchor cell.

[0208] Aspect 62: The method according to any one of aspects 54 to 61, wherein the proxy information comprises an indication of a difference between the first SIB1 and a second SIB1 associated with the non-anchor cell.

[0209] Aspect 63: The method according to any one of aspects 53 to 62, wherein the second SI comprises on-demand SI, and the method further comprises receiving a request for the second SI.

[0210] Aspect 64: The method according to aspect 63, wherein receiving the request for the second SI includes receiving a random access channel (RACH) message indicating the request for the second SI.

[0211] Aspect 65: A method according to any one of Aspects 53 to 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, and the method further includes receiving the request.

[0212] Aspect 66: The method according to aspect 65, wherein receiving the request includes receiving a random access channel (RACH) message indicating the request.

[0213] Aspect 67: According to any one of Aspects 53 to 66, the method also includes 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.

[0214] Aspect 68: A method according to any one of aspects 53 to 67, wherein the proxy information indicates at least one of a configuration associated with a second SI Block 1 (SIB1) associated with the non-anchor cell or a resource allocation associated with the second SIB1.

[0215] Aspect 69: The method according to aspect 68, wherein sending the proxy information comprises sending a first SIB1 associated with the anchor cell, the first SIB1 indicating the proxy information.

[0216] Aspect 70: The method according to any one of aspects 53 to 69, wherein sending the proxy information comprises sending a dedicated SI transmission including the proxy information.

[0217] Aspect 71: A method according to any one of aspects 53 to 69, wherein sending the proxy information comprises sending a radio resource control message including the proxy information.

[0218] Aspect 72: A method according to any one of aspects 53 to 71, wherein at least one of the first SI or the second SI indicates scheduling information associated with other SI associated with the non-anchor cell.

[0219] Aspect 73: According to the method of Aspect 72, the method also includes sending the other SI.

[0220] Aspect 74: The method according to any one of claims 72 or 73, wherein the other SI comprises an on-demand SI.

[0221] Aspect 75: The method according to any one of aspects 72 to 74, wherein the scheduling information indicates a cell among the anchor cell and the non-anchor cell on which the request for the other SI is to be sent.

[0222] Aspect 76: A method according to any one of aspects 53 to 75, wherein at least one of the first SI or the second SI indicates an area identifier (ID) associated with the non-anchor cell.

[0223] Aspect 77: A method according to any one of Aspects 53 to 76, wherein the first SI indicates a system information block 1 (SIB1) associated with the non-anchor cell, and wherein the first SI indicates whether the non-anchor cell is associated with an area identifier (ID) associated with the anchor cell.

[0224] Aspect 78: The method according to any one of aspects 53 to 77, the method also includes sending updated SI associated with the non-anchor cell.

[0225] Aspect 79: The method according to any one of aspects 53 to 78, the method also includes sending an SI update indication associated with the non-anchor cell.

[0226] Aspect 80: A method according to Aspect 79, wherein sending the SI update indication includes sending a short message including the SI update indication, and the method also includes sending a first SI block 1 (SIB1) associated with the anchor cell, wherein the first SIB1 indicates a change of a second SIB1 associated with the non-anchor cell.

[0227] Aspect 81: A method according to any one of Aspects 53 to 80, wherein the second SI is associated with an SI specific area identifier.

[0228] Aspect 82: A method according to any one of aspects 53 to 81, the method also includes sending a communication including an indication of at least one neighboring cell ID associated with an area identifier (ID), wherein the area ID is associated with the anchor cell.

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

[0230] Aspect 84: The method according to any one of aspects 53 to 83, the method also includes sending a physical broadcast channel (PBCH) communication including cell information indicating the anchor cell.

[0231] Aspect 85: The method according to aspect 84, wherein the cell information indicates one or more frequency resources associated with the anchor cell.

[0232] Aspect 86: The method according to any one of claims 84 or 85, wherein the cell information indicates a cell identifier associated with the anchor cell.

[0233] Aspect 87: A method according to any one of aspects 84 to 86, wherein the cell information indicates an area identifier associated with the anchor cell.

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

[0235] Aspect 89: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 52 and Aspect 88.

[0236] Aspect 90: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of Aspects 1 to 52 and Aspect 88.

[0237] Aspect 91: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 52 and aspect 88.

[0238] 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 according to one or more of aspects 1 to 52 and aspect 88.

[0239] Aspect 93: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method according to one or more of aspects 1 to 52 and aspect 88.

[0240] Aspect 94: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 53 to 88.

[0241] Aspect 95: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 53 to 88.

[0242] Aspect 96: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 53 to 88.

[0243] Aspect 97: 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 to 88.

[0244] Aspect 98: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 53 to 88.

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

[0246] As used herein, the term "component" is intended to be widely interpreted as a combination of hardware or hardware and software. "Software" should be widely interpreted as meaning an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software module, an application, a software application, a software package, a routine, a subroutine, an object, an executable program, a thread of execution, a process or a function, etc., whether it is described in software, firmware, middleware, microcode, hardware description language or other terms. As used herein, a "processor" is implemented with a combination of hardware or hardware and software. It will be obvious that the system or method described herein can be implemented in different forms of hardware or a combination of hardware and software. The actual dedicated control hardware or software code for implementing these systems or methods does not limit various aspects. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement these systems or methods based at least in part on the description herein.

[0247] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0248] Although the specific combination of features is stated in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of the following: a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, 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).

[0249] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the terms "having", "containing", "comprising" and similar terms are intended to be open terms, which do not limit the elements they modify (for example, the element "comprising" A can also contain B). In addition, the phrase "based on" is intended to represent "based at least in part", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used consecutively is intended to be inclusive and used interchangeably with "and / or" unless expressly stated otherwise (e.g., if used in conjunction with "either one of" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) include: A processing system, the processing system comprising a processor circuit and a memory circuit coupled to the processor circuit, the processing system being 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 second SI associated with a non-anchor cell; obtaining the second SI based on the proxy information; and Communicate with the non-anchor cell based on the second SI. 2 . The UE according to claim 1 , wherein the first SI comprises a first SI block 1 (SIB1). 3 . The UE of claim 2 , wherein the first SIB1 comprises 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 an area identifier (ID) associated with an area associated with the non-anchor cell. 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 comprises 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 in order for the UE to send the request for the second SI, the processing system is configured to cause the UE to send 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 in order for the UE to send the request, the processing system is configured to cause the UE to send a random access channel (RACH) message indicating the request.

12. The UE of claim 10, wherein in order for 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 according to claim 1, wherein the proxy information indicates at least one of a configuration associated with a second SI block 1 (SIB1) associated with the non-anchor cell or a resource allocation associated with the second SIB1, wherein in order for the UE to obtain the second SI, the processing system is configured to enable 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 according to claim 13, wherein, in order for 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 SI 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 an area identifier (ID) associated with the non-anchor cell, and wherein the processing system is further configured to enable the UE to obtain other SI associated with the non-anchor cell based on the area ID.

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

19. The UE of claim 1, wherein in order for the UE to obtain the second SI, the processing system is configured to cause the UE to receive a system information block 1 (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 an area identifier (ID), wherein the area ID is associated with the second network node.

20. The UE according to claim 1, wherein in order for the UE to obtain the second SI, the processing system is configured to cause the UE to receive a system information block 1 (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 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 an SI update indication on the non-anchor cell.

22. The UE of claim 1, wherein the processing system is further configured to cause the UE to monitor the anchor cell for an SI update indication 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 an area 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 area identifier.

25. The UE of claim 1, wherein the processing system is further configured to cause the UE to receive a communication including an indication of at least one neighbor cell ID associated with a regional identifier (ID), wherein the regional 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 a physical broadcast channel (PBCH) communication including cell information indicative of the anchor cell; and 27. A first network node for wireless communication, the first network node include: a processing system comprising a processor circuit and a memory circuit coupled to the processor circuit, the processing system being 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 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 (SIB1).

29. A method of wireless communication performed by a device at a user equipment (UE), the method include: 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 second SI associated with a non-anchor cell; obtaining the second SI based on the proxy information; and Communicate 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 (SIB1).

Images