On-demand system information block type 1 transmission

Abstract

The present disclosure provides systems, apparatus, equipment, and methods, including computer programs encoded on storage media, for UL-WUS on-demand SIB1. A UE (102) receives (730) a first configuration from a first network entity (104a), the first configuration configuring an uplink wake-up signal, UL-WUS, for requesting a system information block type 1, SIB1, associated with a second network entity (104b). The UE (102) transmits (740) the UL-WUS to the first network entity (104a) based on status information of the SIB1. The UE 102 receives (750) a response from the first network entity (104a), the response indicating a second configuration for monitoring the SIB1 from the second network entity (104b).

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, and more specifically to a user equipment (UE) request for receiving System Information Block Type 1 (SIB1) requests from a network entity. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) specifies a radio interface known as Fifth Generation (5G) New Radio (NR) (5G NR). The architecture of a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), and user equipment (5G UE). Compared to previous generations of cellular communication systems, the 5G NR architecture aims to provide increased data rates, reduced latency, and / or increased capacity.

[0003] In wireless communication systems, network entities and user equipment (UEs) can implement techniques to reduce power consumption. For example, when a UE has an active radio connection with a network entity, it operates in a Radio Resource Control (RRC) connected state. During periods when the UE does not have an active radio connection with a network entity, it can enter a power-saving mode. For example, the UE transitions from an RRC connected state to an RRC idle state or an RRC inactive state. In the RRC idle state, the UE releases its RRC configuration. In the RRC inactive state, the UE suspends its RRC configuration, and the RRC configuration may remain dormant until the UE transitions back to the RRC connected state. During the RRC idle or inactive state, the UE can obtain downlink synchronization signal blocks (SSBs) and system information (SIs) (e.g., System Information Block Type 1 (SIB1)) from the network entity. The UE relies on the SIB1 from the network entity for various operations, such as initial cell access, cell reselection, returning from out-of-coverage, performing random access procedures, and transitioning to the RRC connected state, among other examples.

[0004] Reducing signaling overhead and improving network energy performance are desirable goals. Some recent improvements in wireless communication technologies are based on Network Energy Saving (NES), where network entities eliminate or reduce some uplink and downlink transmissions. For example, a network entity (e.g., an NES network entity) may avoid transmitting some of the SIB1s associated with a specific cell or beam operated by that network entity. To trigger the initial access procedure for a UE to access an NES network entity (e.g., an NES cell), the UE may need to send an uplink wake-up signal (UL-WUS) to request SIB1s from the NES cell. Summary of the Invention

[0005] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects. It neither identifies key or important elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0006] In some aspects, the UE can send a UL-WUS signal (e.g., a Physical Random Access Channel (PRACH) signal) to another network entity based on the status information of the on-demand SIB1 to request SIB1 (e.g., on-demand SIB1) from the NES network entity. Therefore, in response to this request, the other network entity can send a signal (e.g., a network entity WUS) to the NES network entity to request the NES network entity to send the on-demand SIB1 to the UE. The NES network entity can then send the on-demand SIB1 to the UE. The UE can then use the information from the SIB1 to perform an initial access procedure to access the NES network entity. In some aspects, the UE can send a UL-WUS when the status information indicates that a previously received (e.g., previous) SIB1 is no longer valid (e.g., no longer effective). For example, the previous SIB1 may have been valid for a valid period. The UE can send a UL-WUS after the valid period. Alternatively or additionally, the UE can determine (or receive an indication from a first network entity) to send a UL-WUS when the status information indicates that one or more parameters included in the SIB1 have been updated or modified. For example, the UE can perform a comparison between the value label associated with the on-demand SIB1 and the value label associated with the previous SIB1.

[0007] According to some aspects, the UE receives a first configuration from a first network entity, which configures UL-WUS for requesting SIB1 associated with a second network entity. The UE sends UL-WUS to the first network entity based on the SIB1 status information. The UE receives a response from the first network entity indicating a second configuration for monitoring SIB1 from the second network entity.

[0008] According to certain aspects, a first network entity sends a first configuration to the UE, which configures UL-WUS for requesting SIB1 associated with a second network entity. The first network entity receives UL-WUS from the UE based on the status information of SIB1. The first network entity sends a response to the UE indicating a second configuration for monitoring SIB1 from the second network entity.

[0009] According to some aspects, the second (NES) network entity sends a first SIB1 associated with the second network entity (104b) to the UE. The second network entity receives a network entity wake-up signal from the first network entity. In response to receiving the network entity wake-up signal, the second network entity sends a second SIB1 associated with the second network entity to the UE, which is different from the first SIB1. The second network entity receives a PRACH signal for initial access from the UE based on the second SIB1.

[0010] The technical benefits of this disclosure include reduced initial access latency, reduced network overhead, and reduced power consumption in network entities and / or UEs. Attached Figure Description

[0011] Figure 1 An illustration of a wireless communication system according to an embodiment is shown, the wireless communication system including multiple user equipment (UE) and network entities communicating on one or more cells.

[0012] Figure 2 A scheduling diagram for sending multiple SSBs and associated SIB1 network entities according to an embodiment is shown.

[0013] Figure 3 The example illustrates how a network entity sends SIB1 to a UE based on an SIB1 value label, according to an embodiment.

[0014] Figure 4 The example illustrates how a network entity, according to an embodiment, sends SIB1 to a UE based on the validity period of SIB1.

[0015] Figure 5 The initial access and on-demand SIB1 monitoring of network entities according to an embodiment are illustrated.

[0016] Figure 6 The diagram illustrates a scheduling method, according to an embodiment, for transmitting multiple SSBs and associated SIB1 network entities based on time slot offsets.

[0017] Figure 7 This is a signaling diagram illustrating on-demand SIB1 transmission according to an embodiment.

[0018] Figure 8 This is a signaling diagram illustrating on-demand SIB1 transmission and initial access of network entities according to an embodiment.

[0019] Figure 9 This is a flowchart of a wireless communication method at the UE according to an embodiment.

[0020] Figure 10 This is a flowchart of a wireless communication method at a first network entity according to an embodiment.

[0021] Figure 11 This is a flowchart of a method for wireless communication at a second (NES) network entity according to an embodiment.

[0022] Figure 12 This is an illustration showing a hardware implementation of an example UE device according to some embodiments.

[0023] Figure 13 This is an illustration showing a hardware implementation of one or more example network entities according to some embodiments.

[0024] exist Figures 1 to 13 In this context, similar reference numerals refer to similar features. Detailed Implementation

[0025] Figure 1 A diagram 100 illustrates a wireless communication system associated with multiple cells 190. The wireless communication system includes user equipment (UE) 102 and base station / network entity 104. Some base stations may include an aggregated base station architecture, and others may include a decomposed base station architecture. The aggregated base station architecture utilizes a radio protocol stack physically or logically integrated within a single radio access network (RAN) node. The decomposed base station architecture utilizes a protocol stack physically or logically distributed across two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, CU 110 is implemented within a RAN node, and one or more DU 108s may be located in the same location as CU 110, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RU 106s. Any of RU 106, DU 108, and CU 110 can be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). Base station / network entity 104 (e.g., an aggregated base station or a decomposed unit of a base station, such as RU 106 or DU 108) can be referred to as a transmit receiver point (TRP).

[0026] The operation and / or network design of base station 104 can be based on the aggregation characteristics of base station functionality. For example, a decomposed base station architecture can be utilized in an Integrated Access Backhaul (IAB) network, an Open Radio Access Network (O-RAN) network, or a Virtual Radio Access Network (vRAN) (which may also be referred to as a Cloud Radio Access Network (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing functionality for at least one unit, which allows for flexibility in network design. Various units in a decomposed base station architecture or a decomposed RAN architecture can be configured to communicate with at least one other unit via wired or wireless communication. For example, base stations 104d, 104e and / or RUs 106a, 106b, 106c, 106d can communicate with UEs 102a, 102b, 102c, 102d and / or 102s via one or more radio frequency (RF) access links based on a Uu interface. In the example, multiple RUs 106 and / or base stations 104 can simultaneously serve UE 102, such as through intra-cell and / or inter-cell access links between UE 102 and RUs 106 / base stations 104.

[0027] RU 106, DU 108, and CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via wired or wireless transmission media. For example, a wired interface may be configured to transmit or receive information / signals via a wired transmission medium—such as a fronthaul link 160 between RU 106d and a baseband unit (BBU) 112 of base station 104d associated with cell 190d. BBU 112 includes DU 108 and CU 110, and may also have a wired interface (e.g., a midhaul link) configured between DU 108 and CU 110 for transmitting or receiving information / signals between DU 108 and CU 110. In a further example, a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) may be configured to transmit and / or receive information / signals via a wireless transmission medium, such as information transmitted between RU 106a in cell 190a and base station 104e in cell 190e via inter-cell communication beams 136-138 of RU 106a and base station 104e.

[0028] RU 106 can be configured to implement low-level functionality. For example, RU 106 is controlled by DU 108 and can correspond to a logical node that manages RF processing functions or low-level PHY functionality, such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction, and filtering. The functionality of RU 106 can be based on functional partitioning, such as low-level functional partitioning.

[0029] RU 106 can transmit or receive over-the-air (OTA) communications with one or more UEs 102. For example, RU 106b of cell 190b communicates with UE 102b of cell 190b via a first communication beam set 132 of RU 106b and a second communication beam set 134b of UE 102b. These two communication beam sets may correspond to inter-cell communication beams or, in some examples, inter-cell communication beams. For example, UE 102b of cell 190b can communicate with RU 106a of cell 190a via a third communication beam set 134a of UE 102b and a fourth communication beam set 136 of RU 106a. DU 108 can control the real-time and non-real-time characteristics of control plane and user plane communications of RU 106.

[0030] Any combination of RU 106, DU 108, and CU 110, or a reference to them individually, may correspond to base station 104. Therefore, base station 104 may include at least one of RU 106, DU 108, or CU 110. Base station 104 provides UE 102 with access to the core network. Base station 104 may relay communication between UE 102 and the core network (not shown). Base station 104 may be associated with macro cells of high-power cellular base stations and / or small cells of low-power cellular base stations. For example, cell 190e may correspond to a macro cell, while cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network".

[0031] Transmissions from UE 102 to base station 104 / RU 106 are called uplink (UL) transmissions, while transmissions from base station 104 / RU 106 to UE 102 are called downlink (DL) transmissions. Uplink transmissions can also be called reverse link transmissions, and downlink transmissions can also be called forward link transmissions. For example, RU 106d uses the antenna of base station 104d in cell 190d to send downlink / forward link communication to UE 102d, or receive uplink / reverse link communication from UE 102d, based on the Uu interface associated with the access link between UE 102d and base station 104d / RU 106d.

[0032] The communication link between UE 102 and base station 104 / RU 106 can be based on multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be associated with one or more carriers. UE 102 and base station 104 / RU 106 can utilize up to a total of Yx Each carrier allocated in MHz carrier aggregation Y Spectral bandwidths of MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.), where x Each component carrier (CC) is used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along the spectrum. In the example, uplink and downlink carriers may be allocated asymmetrically, with more or fewer carriers allocated to the uplink or downlink. A component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be associated with a primary cell (PCell), and the secondary component carriers may be associated with secondary cells (SCells).

[0033] Some UEs, such as UEs 102a and 102s, can perform device-to-device (D2D) communication via a sidelink. For example, the sidelink / D2D communication link utilizes the spectrum of the Wireless Wide Area Network (WWAN) associated with uplink and downlink communication. Such sidelink / D2D communication can be performed by various wireless communication systems such as Wi-Fi, Bluetooth, LTE, and NR systems.

[0034] UE 102 and base station 104 / RU 106 may each include multiple antennas. These multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that facilitate beamforming operation. For example, RU 106b transmits downlink beamforming signals to UE 102b based on a first communication beamset 132 in one or more transmit directions of RU 106b. UE 102b may receive downlink beamforming signals from RU 106b based on a second communication beamset 134b in one or more receive directions of UE 102b. In a further example, UE 102b may also transmit uplink beamforming signals (e.g., sounding reference signals (SRS)) to RU 106b based on the second communication beamset 134b in one or more transmit directions of UE 102b. RU 106b may receive uplink beamforming signals from UE 102b in one or more receive directions of RU 106b. UE 102b can perform beamforming to determine the optimal reception and transmission directions for beamforming signals. The transmission and reception directions of UE 102 and base station 104 / RU 106 can be the same or different.

[0035] In a further example, the beamforming signal can be transmitted between the first base station / RU 106a and the second base station 104e. For example, base station 104e of cell 190e can transmit the beamforming signal to RU 106a based on communication beam 138 in one or more transmit directions of base station 104e. RU 106a can receive the beamforming signal from base station 104e of cell 190e based on RU communication beam 136 in one or more receive directions of RU 106a. In a further example, base station 104e transmits a downlink beamforming signal to UE 102e based on communication beam 138 in one or more transmit directions of base station 104e. UE 102e receives the downlink beamforming signal from base station 104e based on UE communication beam 130 in one or more receive directions of UE 102e. UE 102e can also transmit uplink beamforming signals to base station 104e in one or more transmission directions of UE 102e based on UE communication beam 130, so that base station 104e can receive uplink beamforming signals from UE 102e in one or more reception directions of base station 104e.

[0036] Base station 104 may include and / or be referred to as a network entity. That is, "network entity" may refer to base station 104 or at least one element of base station 104, such as RU 106, DU 108, and / or CU 110. Base station 104 may also include and / or be referred to as Next Generation Evolved Node B (ng-eNB), Next Generation NB (gNB), Evolved NB (eNB), access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network device, or other related terms. Base station 104 or the entity at base station 104 may be implemented as an IAB node, relay node, sidelink node, aggregated (monolithic) base station, or a decomposed base station including one or more RU 106, DU 108, and / or CU 110. Aggregated or decomposed base station sets may be referred to as Next Generation Radio Access Network (NG-RAN). In some examples, UE 102a operates in dual connectivity (DC) with base station 104e and base station / RU 106a. In such a case, base station 104e can be the primary node, while base station / RU 160a can be the secondary node.

[0037] Still referencing Figure 1 In some aspects, any of the UEs 102 may include an on-demand SIB1 component 140 configured to receive a first configuration from a first network entity for configuring UL-WUS for requesting SIB1 associated with a second network entity. The on-demand SIB1 component 140 is further configured to send UL-WUS to the first network entity based on SIB1 status information. The on-demand SIB1 component 140 is further configured to receive a response from the first network entity indicating a second configuration for monitoring SIB1 from the second network entity.

[0038] In some aspects, any of the base stations 104 or the network entity of the base station 104 may include an on-demand SIB1 configuration component 150 configured to send a first configuration to the UE for configuring UL-WUS for requesting SIB1 associated with the second network entity. The on-demand SIB1 configuration component 150 is further configured to receive UL-WUS from the UE based on SIB1 status information. The on-demand SIB1 configuration component 150 is further configured to send a response to the UE indicating a second configuration for monitoring SIB1 from the second network entity.

[0039] In some aspects, any of the base stations 104 or a network entity of the base station 104 may include an on-demand SIB1 configuration component 150 configured to send a first SIB1 associated with a second network entity to the UE. The on-demand SIB1 configuration component 150 is further configured to receive a network entity wake-up signal from the first network entity. The on-demand SIB1 configuration component 150 is further configured to send a second SIB1 associated with the second network entity to the UE in response to receiving the network entity wake-up signal, the second SIB1 being different from the first SIB1. The on-demand SIB1 configuration component 150 is further configured to receive a PRACH signal for initial access from the UE based on the second SIB1.

[0040] therefore, Figure 1 A wireless communication system that can be implemented in conjunction with aspects of one or more other accompanying figures described herein is described. Furthermore, although the following description may focus on 5G NR, the concepts described herein are applicable to other similar fields, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies such as 6G.

[0041] Figure 2 A scheduling diagram 200 is shown according to an embodiment for sending multiple SSB 230s and associated SIB1 network entities. Figure 2 In the example shown, there are multiple monitoring opportunities (MOs) for the UE to monitor the search space (SS) (e.g., the SS in control resource set (CORESET) 0). Network entities can broadcast multiple SSBs (e.g., SSB1 230a and / or SSB2 230b). For example, the first MO occurs in time slot 6, where PDCCH 232a schedules PDSCH 233a carrying SIB1 associated with SSB1 230a. The second MO occurs in time slot 7, where PDCCH 232b schedules PDSCH 233b carrying SIB1 associated with SSB1 230b.

[0042] In some aspects, SSB 230 includes downlink synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)) for the UE to maintain synchronization with the network entity. Each SSB 230 may include a primary information block (MIB) and other information to enable the UE to receive SIB1 via PDSCH 233. Although each cell has at least one SSB 230, the network entity may transmit multiple SSBs 230 within a cell. For example, the network entity may transmit different SSBs 230 for each of multiple beams or transmit / receive points (TRPs). Alternatively, the network entity may operate multiple cells and transmit multiple SSBs 230 for these cells. To save bandwidth and energy, the network entity may avoid transmitting some or all of the SIB1s transmitted by the network entity. For example, the network entity may transmit SSB 1 230a in time slot 1 and avoid transmitting SIB1 in the associated time slot 6 (e.g., via PDSCH 233a). As another example, a network entity may send SSB 2 230b in slot 2 and avoid sending SIB1 in the associated slot 7 (e.g., via PDSCH233b).

[0043] Due to the limited payload size in the Physical Broadcast Channel (PBCH) carrying the MIB, network entities can only transmit a portion of the common configuration in the MIB. The network entity can transmit the remaining common configuration in SIB1 via PDSCH 233. SIB1 is a minimum portion of the SI required for the UE to perform certain functions such as random access procedures or cell selection / cell reselection. The MIB may include a field indicating when PDCCH 232 is being monitored for downlink control information by the UE (e.g., ...). PDCCH-ConfigSIB1 PDCCH 232 includes scheduling of PDSCH 233, which includes SIB1. The network entity transmits PDSCH 233 based on the System Information Radio Network Temporary Identifier (SI-RNTI), which is predefined as "0xFFFF". The network entity schedules SIB1 via PDCCH 232 in search space (SS) 0 on CORESET 0. The network entity schedules SIB1 via MIB (e.g., via SSB 230). PDCCH-ConfigSIB1The monitoring timing and frequency location of SS / CORESET0 associated with SSB are configured. Network entities can transmit SSB 1 230a and PDCCH 232a / PDSCH 233a for SIB1 associated with SSB 1 230a based on the same beamforming. Network entities can transmit SSB 2 230b and PDCCH 232b / PDSCH 233b for SIB1 associated with SSB 2 230b based on the same beamforming. The beamforming of SSB 1 230a and SSB 2 230b can be different. Therefore, the UE can determine the demodulation reference signal (DMRS) for PDCCH 232 / PDSCH 233 for SIB1 and the associated quasi-co-address (QCL) for SSB 230 based on one or more parameters such as delay spread, average delay, Doppler shift, Doppler spread, spatial reception parameters, and / or antenna gain.

[0044] Figure 3 Illustrations 300, 301, and 302 show network entity 104 transmitting SIB1 308 to UE 102 based on state information (e.g., SIB1 value label) according to an embodiment. In some aspects, network entity 104 may transmit SIB1 periodically. In some aspects, network entity 104b may enter NES mode and may not transmit SIB1 for some SSBs.

[0045] In some aspects, UE 102 may have already received SIB1 from network entity 104b before network entity 104b enters NES mode. UE 102 may be in RRC idle mode or RRC inactive mode. In RRC idle mode, UE 102 may release the RRC configuration. In RRC inactive mode, UE 102 may suspend the RRC configuration and store the RRC configuration in the UE inactive access stratum (AS) context. However, after UE 102 attempts to camp on network entity 104b again (e.g., when UE 102 reselects network entity 104b from another network entity / cell and / or when UE 102 recovers from an out-of-coverage situation), UE 102 may not have information about whether the SIB1 of network entity 104b has changed. If UE 102 does not have information about whether the SIB1 has changed, UE 102 may request on-demand SIB1 from network entity 104b. However, if SIB1 has not changed, UE 102 will unnecessarily request SIB1 on demand, thus wasting energy and resources in UE 102 and network entity 104b. An aspect of this disclosure may include UE 102 sending UL-WUS to request SIB1 on demand based on state information (e.g., whether SIB1 for network entity 104b has changed).

[0046] refer to Figure 3 Figure 300 illustrates a network entity 104b (e.g., a second network entity) sending SIB1308a to UE 102 and optionally sending status information (e.g., a value tag) associated with the first SIB1308a. The value tag can be a hash function of SIB1308a or other suitable function. Network entity 104b can configure the value tag for UE 102 by sending an indicator of the value tag to UE 102 via SIB1308a, the main information block (MIB), another SIB, and / or the PDCCH of the PDSCH carrying SIB1208a. Alternatively, UE 102 can determine (e.g., calculate or deduce) the value tag of SIB1308a. For example, UE 102 can receive SIB1308a and determine its value tag by taking the entire or part of the SIB1308a message as input to a hash function, where the output of the hash function (e.g., the value tag) can be a k-bit integer X. In some aspects, network entity 104a (e.g., the first network entity not in NES mode) and / or network entity 104b can determine the value label of the on-demand SIB1 308b associated with network entity 104b by feeding the on-demand SIB1 308b into the same hash function employed by UE 102. Network entity 104a may include the value label 307 of the on-demand SIB1 in SIB1, in another SIB, and / or in the UL-WUS configuration 330. In some other implementations, the status information of SIB1 includes not only the value label but also a system information area identifier (i.e., systemInformationAreaID In this implementation, when two different SIB1s (from the same or different cells) have the same value label but different... systemInformationAreaIDs In this case, the two SIB1s should not be considered the same. In other words, only when two different SIB1s are... systemInformationAreaIDs Two different SIB1 values ​​are considered the same only if both the sum and value labels are identical. 。

[0047] In some aspects, network entity 104a can receive the on-demand value tag 307 from network entity 104b via link 311 (e.g., an X2 interface, shared memory, or other suitable link). Although the first network entity 104a and the second network entity 104b are described as different network entities, they may be the same network entity 104 operating different cells. In some aspects, the first network entity 104a is different from the second network entity 104b. For ease of description, this disclosure refers to the first network entity 104a as operating the first cell and the second network entity 104b as operating the second cell. The first network entity 104a and the second network entity 104b can coordinate with each other via link 311.

[0048] UE 102 can determine whether the value label 307 of on-demand SIB1 308b is different from or the same as the value label used for SIB1 308a. For example, UE 102 can receive the value label 307 of on-demand SIB1 308b from the first network entity 104a and compare the value label 307 with the value label of SIB1 308a. Alternatively, network entity 104a can send an indicator to UE 102 indicating whether the value label 307 of on-demand SIB1 308b is different from the value label of SIB1 308a.

[0049] As shown in Figure 301, if UE 102 determines that the value tag associated with SIB1 308a (e.g., stored in UE 102) is different from the value tag 307 of on-demand SIB1 308b, UE 102 can send UL-WUS 340a to the first network entity 104a to request on-demand SIB1 308b. Network entity 104a can send (e.g., forward) the network entity WUS and the request for on-demand SIB1 308b to the second network entity 104b via link 311. Alternatively, UE 102 can send UL-WUS 340b to the second network entity 104b to request on-demand SIB1 308b. In response to this request, network entity 104b can send on-demand SIB1 308b to UE 102. UE 102 can then perform an initial access procedure based on on-demand SIB1 308b to access network entity 104b.

[0050] As shown in Figure 302, if UE 102 determines that the value label associated with SIB1 308a is the same as the value label 307 of on-demand SIB1 308b, then UE 102 can treat the previously received SIB1 308a (e.g., a stored SIB1) as an effective (e.g., valid) SIB1 of network entity 104b, and UE 102 can avoid sending UL-WUS to network entity 104a, and perform the initial access procedure 309 to access network entity 104b based on the stored SIB1 308a. In some other implementations ( Figure 3 (not shown in the image), if UE 102 determines the value label of SIB1 308a sent by network entity 104b and systemInformationAreaID With the value label of SIB1 308b on demand and systemInformationAreaID If they are the same, then UE 102 can assume that SIB1 sent by network entity 104b is the same as on-demand SIB1 308b, and UE 102 can avoid sending UL-WUS to network entity 104a.

[0051] Figure 4 Illustration 400 shows network entity 104 transmitting SIB1 to UE 102 based on SIB1 status information (e.g., validity period 404) according to an embodiment. Validity period 404 can be the time period during which SIB1 is active. In some aspects, network entity 104b can operate in NES mode and configure validity period 404 for periodically transmitted SIB1. Network entity 104b can transmit SIB1 validity period 404b configuration to UE 102 via SIB1, another SIB, MIB, and / or PDCCH that schedules PDSCH for SIB1. Alternatively, network entity 104b can transmit SIB1 validity period 404 to network entity 104a via link 311. Network entity 104a can then transmit SIB1 validity period 404a configuration to UE 102 via another SIB1, another SIB, another MIB, and / or PDCCH that schedules PDSCH for SIB1.

[0052] In some aspects, when UE 102 receives SIB1 from network entity 104b, UE 102 can start or reset a timer based on validity period 404. While the timer is running, UE 102 can avoid sending UL-WUS 340a indicating an on-demand SIB1 request because SIB1 remains unchanged during the validity period. In some aspects, when the timer expires, UE 102 can send UL-WUS 340a to network entity 104a to request on-demand SIB1 from network entity 104b. In some other aspects, UE 102 can send UL-WUS 340b to a second network entity 104b to request on-demand SIB1 from network entity 104b. Network entity 104a can send (e.g., forward) the network entity WUS and the request for on-demand SIB1 to the second network entity 104b via link 311. In response to this request, network entity 104b can send on-demand SIB1 to UE 102. Then, UE 102 can perform an initial access procedure to access network entity 104b based on on-demand SIB1.

[0053] Figure 5 Illustration 500 shows initial access and on-demand SIB1 monitoring of network entity 104 according to an embodiment. In some aspects, UE 102 may determine whether to send UL-WUS 340a to network entity 104a to request on-demand SIB1 308 from network entity 104b, or whether to perform an initial access procedure to access network entity 104a (e.g., fallback to perform initial access). In some other aspects, UE 102 may determine whether to send UL-WUS 340b to a second network entity 104b to request on-demand SIB1 from network entity 104b, or whether to perform an initial access procedure to access network entity 104a. UE 102 may base its access on the status information of on-demand SIB1 308 (e.g., as referenced in the diagram). Figure 3 The described value labels are compared and / or as referenced. Figure 4 The SIB1 validity period (described) is used to determine whether to send UL-WUS.

[0054] In some aspects, UE 102 may determine whether to back off to perform initial access to network entity 104a based on measurement information (e.g., first measurement information associated with a first network entity 104a and / or second measurement information associated with a second network entity 104b). Measurement information may include the measured reference signal received power (RSRP) associated with network entity 104a and / or network entity 104b (e.g., Layer 1 RSRP (L1-RSRP) and / or Layer 3 RSRP (L3-RSRP)), the measured signal-to-interference-plus-noise ratio (SINR) (e.g., L1-SINR and / or L3-SINR) of network entity 104a and / or network entity 104b, and / or the measured reference signal received quality (RSRQ) of network entity 104a and / or network entity 104b. UE 102 may measure the RSRP / SINR / RSRQ of network entity 104a and / or network entity 104b based on one or more SSBs.

[0055] In some respects, UE 102 may determine the fallback to perform initial access to network entity 104a based on at least one of the following conditions: - The RSRP associated with the first network entity 104a is greater than the RSRP associated with the second network entity 104b minus the first offset; - The SINR associated with the first network entity 104a is greater than the SINR associated with the second network entity 104b minus the second offset; - The RSRQ associated with the first network entity 104a is greater than the RSRQ associated with the second network entity 104b minus the third offset; - The RSRP associated with the first network entity 104a is greater than the first threshold; - The SINR associated with the first network entity 104a is greater than the second threshold; - The RSRQ associated with the first network entity 104a is greater than the third threshold; - The RSRP associated with the second network entity 104b is less than the fourth threshold; - The SINR associated with the second network entity 104b is less than the fifth threshold; or - The RSRQ associated with the second network entity 104b is less than the sixth threshold.

[0056] In some aspects, the first / second / third offset and / or the first / second / third / fourth / fifth / sixth threshold can be predefined or configured by network entity 104a and / or network entity 104b (e.g., by SIB1 or another SIB from network entity 104a and / or network entity 104b). Measurement information used to determine the rollback operation (e.g., RSRP / SINR / RSRQ) can be predefined or configured by network entity 104a and / or network entity 104b.

[0057] If UE 102 determines not to fall back to access network entity 104a, UE 102 may trigger the On-Demand SIB1 procedure (e.g., sending UL-WUS 340 to request On-Demand SIB1 308 from network entity 104b). Network entity 104a may send (e.g., forward) network entity WUS 503 and the request for On-Demand SIB1 to the second network entity 104b via link 311. Otherwise, if UE 102 determines to fall back to access network entity 104a, UE 102 may perform an initial access procedure to access network entity 104a based on configuration 530 (e.g., a second configuration) received from network entity 104a.

[0058] In some aspects, UL-WUS 340 may be a PRACH signal (e.g., a random access (RA) preamble). Network entity 104a may configure dedicated PRACH resources for UE 102 to transmit UL-WUS 340. In some aspects, network entity 104a may connect to multiple network entities 104 operating in NES mode, including network entity 104b. Network entity 104a may configure multiple sets of dedicated PRACH resources, each of which may be associated with a different network entity 104. For example, network entity 104a may configure different PRACH resources corresponding to different carrier frequencies and / or different SSBs of the on-demand SIB1 QCL for network entity 104b. In some aspects, UE 102 may determine the PRACH resources for UL-WUS 340 based on the physical cell identifier (PCI) of network entity 104b, the requested SSB index of the on-demand SIB1 PDSCH, and / or the carrier frequency QCL of the on-demand SIB1. After receiving the UL-WUS 340 request for on-demand SIB1 from network entity 104b, network entity 104a can determine, based on the status information, whether UE 102 should fall back to perform initial access to network entity 104a or start monitoring resources from on-demand SIB1 from network entity 104b.

[0059] In response to receiving UL-WUS 340 from UE 102, network entity 104a may send a response to UE 102 indicating a configuration (e.g., a second configuration) for monitoring SIB1 from a second network entity 104b, or configuring UE 102 to initially access network entity 104a. This response may be a Random Access Response (RAR). The RAR may include a first RAR type for configuring UE 102 to monitor on-demand SIB1 from network entity 104b, or a second RAR type (e.g., as defined in 3GPP TS 38.321) for configuring UE 102 to initially access network entity 104a. The second type of RAR can provide a configuration for UE 102 to monitor on-demand SIB1 from network entity 104b.

[0060] Network entity 104a can configure the RAR type via the corresponding Media Access Control (MAC) subheading for the RAR. In one example, network entity 104a can configure a Back Off Indicator (BI) in the MAC subheading to indicate whether network entity 104a is sending a first-type RAR or a second-type RAR. In another embodiment, network entity 104a can provide a Random Access Preamble Identifier (RAPID) in the MAC subheading corresponding to one of the random access preambles configured for the on-demand SIB1 request. The MAC payload of the RAR can be appended after the MAC subheading to indicate whether a first-type RAR or a second-type RAR is being sent.

[0061] As an alternative to configuring dedicated PRACH resources for UE 102 to transmit UL-WUS 340, network entity 104a can configure non-dedicated PRACH resources for UE 102 to transmit UL-WUS 340. For example, PRACH resources can be shared by multiple network entities 104 operating in NES mode. In some aspects, non-dedicated resources can be used for different functionalities (e.g., UL-WUS or PRACH for initial access). After receiving UL-WUS 340 (e.g., PRACH) from UE 102, network entity 104a can send a RAR for a PUSCH scheduled for message 3 (Msg3) transmission. UE 102 can then send a scheduled PUSCH carrying Msg3 to network entity 104a. In some aspects, Msg3 may indicate the PCI associated with network entity 104b, one or more SSBs (e.g., SSB indexes associated with network entity 104b) associated with the PDSCH QCL carrying on-demand SIB1, measurement information associated with network entity 104a, measurement information associated with network entity 104b (e.g., to allow network entity 104a to determine whether to back off), carrier frequency associated with on-demand SIB1, and / or time window for UE 102 to monitor on-demand SIB1. The time window for UE 102 to monitor on-demand SIB1 may indicate to UE 102 a preferred or recommended time window for on-demand SIB1 reception (e.g., minimum / maximum / preferred start time and / or minimum / maximum / preferred duration for on-demand SIB1 monitoring). The recommended time window may be indicated as a slot offset and / or frame offset.

[0062] In response to Msg3, network entity 104a may send Msg4 to UE 102. Network entity 104a may send Msg4 via PDSCH in MAC-CE or via PDCCH in DCI. Msg4 may indicate to UE 102 whether to fall back to perform the initial access procedure with network entity 104a or to begin monitoring on-demand SIB1 from network entity 104b. Msg4 may include information for UE 102 to monitor on-demand SIB1 (e.g., time / frequency resources).

[0063] In some aspects, UE 102 may transmit UL-WUS 340 (e.g., PRACH signal) and Msg3 in two separate transmissions (e.g., a 4-step random access procedure). Alternatively, UE 102 may transmit UL-WUS 340 (e.g., PRACH signal) and Msg3 together in a single transmission (e.g., MsgA in a 2-step random access procedure).

[0064] In some aspects, network entity 104a may send RAR and Msg4 in two separate transmissions (e.g., a 4-step random access procedure). Alternatively, network entity 104a may send RAR and Msg4 together in a single transmission (e.g., MsgB in a 2-step random access procedure).

[0065] In some respects, UE 102 may use dedicated PRACH resources to send UL-WUS 340 corresponding to the on-demand SIB1 for network entity 104b. Otherwise, if on-demand SIB1 is configured for network entity 104b, UE 102 may fall back to use other PRACH resources (e.g., public PRACH resources) to trigger the on-demand SIB1 procedure.

[0066] In response to receiving UL-WUS 340, network entity 104a may send at least one of the following to UE 102 via RAR, Msg4, and / or MsgB: - Acknowledgment of receipt of UL-WUS 340. UL-WUS 340 acknowledgment may include a random access preamble identifier (RAPID) indicating the PRACH preamble index sent by UE 102; - Backoff indicator (BI), which indicates whether UE 102 should backoff to perform the initial access procedure to access network entity 104a; - PCI information associated with network entity 104b. The PCI information can be used as confirmation from network entity 104a that UE 102 is requesting on-demand SIB1 from network entity 104b; - The carrier frequency of SIB1 requested from network entity 104b; - One or more SSB indices for the PDCCH and / or PDSCH QCL used for On-Demand SIB1.

[0067] - On-demand SIB1 value labels (e.g., on-demand SIB1 hash functions); - Timing information for UE 102 to begin monitoring on-demand SIB1. This timing information may indicate the subframes and / or radio frames for UE 102 to begin monitoring on-demand SIB1; - Timing information for UE 102 to stop monitoring on-demand SIB1. This timing information can indicate the subframes and / or radio frames for UE 102 to stop monitoring on-demand SIB1; - The duration of the time window for UE 102 to monitor on-demand SIB1. The duration of the time window can be indicated as the number of symbols, time slots, subframes, and / or radio frames; - Configuration for UL-WUS retransmission. In some aspects, UE 102 may send UL-WUS 340 to request on-demand SIB1, but UE 102 may fail to receive on-demand SIB1. If UE 102 fails to receive on-demand SIB1, UE 102 may retransmit UL-WUS 340 based on the UL-WUS 340 retransmission configuration, which may include at least one of the following: - Duration of the retransmission prohibition timer for UL-WUS 340. To prevent frequent or premature retransmissions of UL-WUS 340, network entity 104a can configure a UL-WUS 340 retransmission prohibition timer, during which UE 102 will avoid retransmitting UL-WUS 340; - Power ramp step size for retransmissions of UL-WUS 340. UE 102 can increase the power level of each retransmission of UL-WUS 340 by this power ramp step size.

[0068] - An indicator of whether retransmission is allowed on the UL-WUS 340.

[0069] In some aspects, network entity 104a (e.g., via RAR, MSG4, and / or MSGB) sends a response to UL-WUS 340, which may include a downlink assignment for directly scheduling the PDSCH for on-demand SIB1. Enabling the response to include the downlink assignment for scheduling the PDSCH allows UE 102 to avoid monitoring and decoding the scheduled PDCCH including the downlink assignment, thereby reducing power consumption in UE 102. UE 102 monitors the PDSCH for on-demand SIB1 based on the received downlink assignment. In some aspects, the downlink assignment may include one or more of the following information: - Frequency Domain Resource Assignment (FDRA) for PDSCH; - Time-Domain Resource Assignment (TDRA) for PDSCH; - Virtual Resource Block (VRB) to Physical Resource Block (PRB) mapping. In some aspects, VRB to PRB mapping can be used for frequency hopping and / or frequency interleaving in the frequency domain; - Modulation and coding scheme (MCS) for PDSCH; - Redundant version (RV) of PDSCH; - Periodicity and / or slot offset of the reference slot for PDSCH used in on-demand SIB1; or - Number of times PDSCH is repeated. In some respects, network entity 104a may repeat the transmission of PDSCH to increase the probability that UE 102 correctly decodes PDSCH.

[0070] Figure 6 A diagram 600 is shown according to an embodiment for scheduling network entities that transmit multiple SSBs and associated SIBs based on time slot offsets.

[0071] In some aspects, the UL-WUS response from network entity 104a may not include a downlink assignment for PDSCH 633 carrying on-demand SIB1. If UE 102 does not receive a downlink assignment for directly scheduling PDSCH 633 carrying on-demand SIB1, UE 102 monitors the PDCCH scheduled for PDSCH 633 for on-demand SIB1 in the search space (SS) (e.g., SS 0) corresponding to SSB 630 of the PDCCH / PDSCH 633 QCL. UE 102 then monitors the PDSCH 633 scheduled for on-demand SIB1 by the PDCCH.

[0072] In some aspects, downlink assignment can indicate the slot offset from PDCCH to PDSCH 633. However, since downlink assignment directly schedules PDSCH 633 without PDCCH, network entity 104a and UE 102 can determine the reference slot (e.g., virtual PDCCH reference slot) for the slot offset of PDSCH 633.

[0073] exist Figure 6 In the example, network entity 104a can configure a reference slot offset x in the downlink assignment in response to UL-WUS, and configure a slot offset based on the reference slot offset y set by TDRA in the downlink assignment in response to UL-WUS. Then, network entity 104b transmits PDSCH 633 for On-Demand SIB1 in slot n+x+y, where network entity 104b transmits SSB 630 in slot n. SSB 630 is paired with PDSCH 633 QCL. Network entity 104a can configure common or separate values ​​for x and / or y for PDSCH 633 used for On-Demand SIB1 with different SSB 630 QCLs. For example, in Figure 6 In this configuration, PDSCH 633a can use slot 5 as a reference slot, and PDSCH 633b can use slot 6 as a reference slot. The reference slot can be indicated in the downlink assignment as an offset x from SSB 630. Figure 6 In this context, x is a 4-slot offset from SSB 630 within slot n. If TDRA indicates an offset of y (e.g., 1 slot), then PDSCH 633a is scheduled for slot 1+4+1=slot 6. Similarly, PDSCH 633b is scheduled for slot 2+4+1=slot 7.

[0074] In some aspects, network entity 104b can transmit PDSCH 633 for on-demand SIB1 through one or more repetitions. Network entity 104b can transmit different repetitions in different time slots and / or in different symbols. Network entity 104b can further configure the repetition type (e.g., time slot level and / or symbol level). Network entity 104b can transmit different repetitions of PDSCH 633 through the same or different redundancy versions (RVs). The RV of each repetition can be predefined or configured by network entity 104b.

[0075] In some aspects, network entity 104b may transmit PDSCH 633 for on-demand SIB1 based on an antenna port and a configured downlink assignment. Network entity 104b may also transmit PDSCH 633 for on-demand SIB1 based on a predefined Radio Network Temporary Identifier (RNTI) (e.g., SI-RNTI or a configured RNTI). In some aspects, the on-demand SI-RNTI may be configured by network entity 104b or network entity 104a via MIB, SIB, UL-WUS configuration, response to an on-demand SIB1 request, or UL-WUS. The on-demand SI-RNTI allows UE 102 to distinguish between periodic SIB1 and on-demand SIB1. If UE 102 receives an on-demand SIB1 with an on-demand SI-RNTI, the UE recognizes that the UL-WUS requesting that on-demand SIB1 was correctly received by network entity 104a. Network entity 104b can transmit PDSCH 633 with SSB 630 QCL based on one or more parameters including average delay, delay spread, Doppler shift, Doppler spread, spatial reception parameters and / or antenna gain.

[0076] Figure 7 This is signaling diagram 700 illustrating on-demand SIB1 transmission according to an embodiment. In some aspects, a second network entity 104b (e.g., an NES network entity) may send 710 SIB1 to UE 102. SIB1 may optionally include SIB1 status information. For example, SIB1 may include a value tag for SIB1 (e.g., a hash function for SIB1) and / or an expiration time for SIB1. UE 102 may enter a 720 RRC idle state or an RRC inactive state. In some aspects, the second network entity 104b may optionally send 715 SIB1 to a first network entity 104a. SIB1 may optionally include SIB1 status information (e.g., a value tag for SIB1 and / or an expiration time).

[0077] In some aspects, the first network entity 104a may send 730 to the UE 102 a configuration (e.g., a first configuration) for the UL-WUS of the second network entity 104b, which may optionally include the status information of SIB1. The UL-WUS may be used by the UE 102 to request on-demand SIB1 associated with the second network entity 104b.

[0078] In some aspects, UE 102 may send a 740 request to the first network entity 104a for UL-WUS (e.g., PRACH signal) for on-demand SIB1 from the second network entity 104b. UE 102 may send the 740 UL-WUS based on the status information of on-demand SIB1. For example, as referenced... Figure 3 The status information can be based on the difference between the value label associated with SIB1 and the value label associated with On-Demand SIB1. In some aspects, the status information is based on, as referenced... Figure 4 The effective time period of SIB1 is described. In some other aspects, UE 102 may send a UL-WUS (e.g., a PRACH signal) requesting on-demand SIB1 from the second network entity 104b to the second network entity 104b.

[0079] In some aspects, the first network entity 104a may send a 750-pair UL-WUS response to the UE 102, indicating a configuration for SIB1 monitoring or a configuration for accessing the first network entity 104a. For example, the response may indicate a configuration for on-demand SIB1 monitoring, as referenced... Figure 5 and Figure 6 As described. In some aspects, the response can indicate the configuration used to access the first network entity, as referenced. Figure 5 As described.

[0080] In some aspects, the first network entity 104a may optionally send network entity WUS 755 to the second network entity 104b. Network entity 104a may send (e.g., forward) network entity WUS and a request for on-demand SIB1 to the second network entity 104b, as shown in reference... Figure 3 and Figure 4 As described.

[0081] In some aspects, the second network entity 104b can send 760 on-demand SIB1 to the UE 102 based on the SIB1 monitoring configuration. The second network entity 104b can send 760 on-demand SIB1 in response to receiving an on-demand SIB1 request.

[0082] In some aspects, UE 102 may optionally send 770a, a PRACH for initial access to network entity 104a, to the first network entity 104a. UE 102 may optionally send 770a, a PRACH for initial access to network entity 104a, as referenced. Figure 5 As described.

[0083] In some aspects, UE 102 may optionally send 770b PRACH for initial access to network entity 104b to the second network entity 104b. UE 102 may optionally send 770b PRACH for initial access to network entity 104b based on on-demand SIB1 or based on whether SIB1 has been changed according to previously received 710 SIB1.

[0084] Figure 8 This is signaling diagram 800 illustrating on-demand SIB1 transmission and initial access to a network entity according to an embodiment. In some aspects, UE 102 may send 740 UL-WUS requesting on-demand SIB1 from a second network entity to a first network entity 104a. UL-WUS may include a PRACH signal (e.g., RA preamble). UE 102 may send 740 UL-WUS based on on-demand SIB1 status information. For example, as referenced... Figure 3 The status information may be based on the difference between the value label associated with SIB1 and the value label associated with On-Demand SIB1. In some aspects, the status information is based on the valid time period of SIB1, as referenced... Figure 4 As described.

[0085] In some respects, the first network entity 104a may send a RAR (Record Animation) to the UE 102 for scheduling the PUSCH for message 3 (Msg3) transmission. The RAR may be referred to as message 2 (Msg2).

[0086] In some aspects, UE 102 may (e.g., via a scheduled PUSCH) send 835 Msg3 to the first network entity 104a, which includes a MAC CE for an on-demand SIB1 request to the second network entity. For example, UE 102 may send 835 Msg3 to the first network entity 104a, as referenced Figure 5 As described.

[0087] In some aspects, the first network entity 104a may send 845 Msg4 to the UE 102 (e.g., via PDSCH), which includes a response to an on-demand SIB1 request instructing the UE 102 to access network entity 104a or to monitor on-demand SIB1. For example, the first network entity 104a may send 845 Msg4, as referenced Figure 5 As described.

[0088] Figures 9 to 11 The following diagram illustrates the implementation. Figures 2 to 8 One or more aspects of the method. In particular, Figure 9 This is an example of implementation by UE 102. Figures 2 to 8 One or more aspects of. Figure 10 This is shown as implemented by network entity 104. Figures 2 to 8 One or more aspects of. Figure 11 This is shown as being implemented by the second (NES) network entity 104. Figures 2 to 8 One or more aspects of.

[0089] Figure 9 A flowchart 900 illustrates a method for wireless communication at the UE. (Reference) Figures 1 to 8 This method can be performed by UE 102. In an embodiment, the UE receives 910 first SIB1 from a second network entity. For example, refer to... Figure 7 UE 102 receives a first SIB1 from the second network entity 104b, the first SIB1 optionally including an SIB1 value label or an SIB1 validity period.

[0090] In an embodiment, the UE receives a first configuration (930) from a first network entity, which is used to configure UL-WUS for requesting SIB1 associated with a second network entity. For example, refer to... Figure 7 UE 102 receives 730 configuration for UL-WUS of network entity 104b from network entity 104a, which optionally includes SIB1 status information.

[0091] In this embodiment, the UE sends 940 UL-WUS to the first network entity based on the SIB1 state information. For example, refer to... Figure 7 UE 102 sends 740 UL-WUS to the first network entity 104a to request on-demand SIB1 from the second network entity 104b.

[0092] In one embodiment, the UE receives a 950 response from a first network entity, which indicates a second configuration for monitoring SIB1 from a second network entity. For example, refer to... Figure 7 UE 102 receives 750 UL-WUS responses from network entity 104a, indicating either a configuration for SIB1 monitoring or a configuration for accessing the first network entity 104a. In an embodiment, the UE receives 960 SIB1 responses from the second network entity via the Physical Downlink Shared Channel (PDSCH) based on a second configuration. For example, refer to... Figure 7UE 102 receives 760 on-demand SIB1 from network entity 104b based on the configured SIB1 monitoring configuration.

[0093] In an embodiment, the UE may optionally send a 970 Physical Random Access Channel (PRACH) signal for initial access to a first or second network entity. For example, refer to... Figure 7 UE 102 may optionally send 770a PRACH for the initial access procedure to the first network entity 104a. For example, refer to Figure 7 UE 102 may optionally send 770b PRACH for the initial access procedure to the second network entity 104b.

[0094] Figure 9 A method is described from the UE side of the wireless communication link, while Figures 10 to 11 A method is described from the network side of this wireless communication link.

[0095] Figure 10 This is a flowchart 1000 showing the wireless communication method at the first network entity. (Reference) Figures 1 to 8 This method can be performed by one or more network entities 104, which may correspond to a base station or a unit of a base station, such as RU 106, DU 108, and / or CU 110. In an embodiment, the first network entity optionally receives 1015 SIB1 from the second network entity, the SIB1 optionally including SIB1 status information. For example, refer to... Figure 7 The first network entity 104a may optionally receive 715 SIB1 from the second network entity 104b, wherein the SIB1 may optionally include the status information of the SIB1.

[0096] In one embodiment, a first network entity sends a 1030 first configuration to the UE, which configures UL-WUS for requesting SIB1 associated with a second network entity. For example, refer to... Figure 7 The first network entity 104a sends 730 to the UE 102 for the configuration of UL-WUS for the second network entity 104b, which optionally includes the status information of SIB1.

[0097] In this embodiment, the first network entity receives 1040 UL-WUS from the UE based on SIB1 state information. For example, refer to... Figure 7 The first network entity 104a receives 740 UL-WUS from UE 102 to request on-demand SIB1 from the second network entity 104b.

[0098] In one embodiment, the first network entity sends a 1050 response to the UE, indicating a second configuration for monitoring SIB1 from the second network entity. For example, refer to... Figure 7 The first network entity 104a sends a 750 response to UL-WUS to the UE 102, which indicates the configuration for SIB1 monitoring or the configuration for accessing the first network entity 104a.

[0099] In an embodiment, the first network entity may optionally receive a PRACH signal for initial access from the UE (1070). For example, refer to... Figure 7 The first network entity 104a may optionally receive the PRACH signal 770a for initial access from the UE 102.

[0100] Figure 11 This is a flowchart 1100 of a method for wireless communication at the second network entity. (Reference) Figures 1 to 8 This method can be performed by one or more network entities 104, which may correspond to a base station or a unit of a base station, such as RU 106, DU 108, and / or CU 110. In an embodiment, the second network entity sends a first SIB1 associated with the second network entity to the UE. For example, refer to... Figure 7 The second network entity 104b sends 710 SIB1 to UE 102, which may optionally include an SIB1 value label or an SIB1 validity period.

[0101] In an embodiment, the second network entity may optionally send the status information associated with SIB1 (1115) to the first network entity. For example, refer to... Figure 7 The second network entity 104b may optionally send 715 SIB1 to the first network entity 104a, wherein the SIB1 may optionally include an SIB1 value label or an SIB1 validity period.

[0102] In one embodiment, the second network entity receives a network entity wake-up signal (1155) from the first network entity. For example, refer to... Figure 7 The second network entity 104b receives the 755 network entity wake-up signal from the first network entity 104a.

[0103] In an embodiment, in response to receiving a network entity wake-up signal, the second network entity sends a second SIB1 associated with the second network entity to the UE, which is different from the first SIB1. For example, refer to... Figure 7 The second network entity 104b sends 760 on-demand SIB1 to UE 102 based on the SIB1 monitoring configuration.

[0104] In an embodiment, the second network entity may optionally receive a PRACH signal for initial access from the UE (1170). For example, refer to... Figure 7The second network entity 104b may optionally receive the PRACH signal 770b for initial access from the UE 102.

[0105] like Figure 12 As described, UE equipment 1202 can perform Figure 9 The flowchart method. For example... Figure 13 As described herein, one or more network entities 104 can perform Figure 10 and Figure 11 The flowchart method.

[0106] Figure 12 Illustration 1200 illustrates an example of a hardware implementation of UE device 1202. UE device 1202 may be UE 102, a component of UE 102, or may implement UE functionality. UE device 1202 may include application processor 1206, which may have on-chip memory 1206'. In the example, application processor 1206 may be coupled to secure digital (SD) card 1208 and / or display 1210. Application processor 1206 may also be coupled to sensor module 1212, power supply 1214, additional memory module 1216, camera 1218, and / or other related components. For example, sensor module 1212 may control barometric pressure sensor / altimeter, motion sensors (such as inertial management unit (IMU), gyroscope, accelerometer), light detection and ranging (LIDAR) device, radio-assisted detection and ranging (RADAR) device, sound navigation and ranging (SONAR) device, magnetometer, audio device, and / or other technologies for positioning.

[0107] The UE equipment 1202 may further include a wireless baseband processor 1226, which may be referred to as a modem. The wireless baseband processor 1226 may have on-chip memory 1226'. Together with and similarly to the application processor 1206, the wireless baseband processor 1226 may also be coupled to a sensor module 1212, a power supply 1214, an additional memory module 1216, a camera 1218, and / or other related components. The wireless baseband processor 1226 may additionally be coupled to one or more Subscriber Identity Module (SIM) cards 1220 and / or one or more transceivers 1230 (e.g., wireless RF transceivers).

[0108] Within one or more transceivers 1230, the UE equipment 1202 may include a Bluetooth module 1232, a WLAN module 1234, an SPS module 1236 (e.g., a GNSS module), and / or a cellular module 1238. The Bluetooth module 1232, WLAN module 1234, SPS module 1236, and cellular module 1238 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 1232, WLAN module 1234, SPS module 1236, and cellular module 1238 may each include a dedicated antenna and / or communicate with one or more other nodes using antenna 1240. For example, UE equipment 1202 can communicate with another UE (e.g., sidelink communication) and / or with network entity 104 (e.g., uplink / downlink communication) via transceiver 1230 and antenna 1240, wherein network entity 104 may correspond to a base station or a unit of a base station (such as RU 106, DU 108 or CU 110).

[0109] The wireless baseband processor 1226 and application processor 1206 may each include computer-readable media / memory 1226' and 1206', respectively. An additional memory module 1216 may also be considered a computer-readable media / memory. Each computer-readable media / memory 1226', 1206', and 1216 may be non-transitory. The wireless baseband processor 1226 and application processor 1206 may each be responsible for general processing, including executing software stored on the computer-readable media / memory 1226', 1206', and 1216. When executed by the wireless baseband processor 1226 / application processor 1206, this software causes the wireless baseband processor 1226 / application processor 1206 to perform the various functions described herein. The computer-readable media / memory may also be used to store data manipulated by the wireless baseband processor 1226 / application processor 1206 during software execution. The wireless baseband processor 1226 / application processor 1206 may be a component of UE 102. UE equipment 1202 may be a processor chip (e.g., a modem and / or an application) and includes only the wireless baseband processor 1226 and / or the application processor 1206. In other examples, UE equipment 1202 may be the entire UE 102 and may include additional modules for equipment 1202.

[0110] like Figure 1 The discussion in the article and about Figure 9Implemented, the on-demand SIB1 component 140 is configured to receive a first configuration from a first network entity, the first configuration being used to configure UL-WUS for requesting SIB1 associated with a second network entity. The on-demand SIB1 component 140 is further configured to send UL-WUS to the first network entity based on SIB1 status information. The on-demand SIB1 component 140 is further configured to receive a response from the first network entity indicating a second configuration for monitoring SIB1 from the second network entity.

[0111] On-demand SIB1 component 140 may be within application processor 1206 (e.g., at 140a), within wireless baseband processor 1226 (e.g., at 140b), or within both application processor 1206 and wireless baseband processor 1226. On-demand SIB1 components 140a-140b may be one or more hardware components specifically configured to implement the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or a combination thereof.

[0112] Figure 13 Illustration 1300 illustrates an example of a hardware implementation of one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include or correspond to at least one of RU 106, DU 108, or CU 110. CU 110 may include a CU processor 1346, which may have on-chip memory 1346'. In some aspects, CU 110 may further include an additional memory module 1356 and / or a communication interface 1348, both of which may be coupled to the CU processor 1346. CU 110 may communicate with DU 108 via a midhaul link 162 (such as an F1 interface between the communication interface 1348 of CU 110 and the communication interface 1328 of DU 108).

[0113] DU 108 may include a DU processor 1326, which may have on-chip memory 1326'. In some aspects, DU 108 may further include an additional memory module 1336 and / or a communication interface 1328, both of which may be coupled to the DU processor 1326. DU 108 may communicate with RU 106 via a frontlink 160 between DU 108's communication interface 1328 and RU 106's communication interface 1308.

[0114] RU 106 may include an RU processor 1306, which may have on-chip memory 1306'. In some aspects, RU 106 may further include an additional memory module 1316, a communication interface 1308, and one or more transceivers 1330, all of which may be coupled to the RU processor 1306. RU 106 may further include an antenna 1340, which may be coupled to one or more transceivers 1330, enabling RU 106 to communicate with UE 102 via the antenna 1340 through one or more transceivers 1330.

[0115] On-chip memories 1306', 1326', 1346' and additional memory modules 1316, 1336, 1356 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1306, 1326, 1346 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor 1306, 1326, 1346, the software causes the processor 1306, 1326, 1346 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by processors 1306, 1326, 1346 during software execution. In the example, the on-demand SIB1 configuration component 150 may be located at any of one or more network entities 104, such as at CU 110; at both CU 110 and DU 108; at each of CU 110, DU 108 and RU 106; at DU 108; at both DU 108 and RU 106; or at RU 106.

[0116] like Figure 1 The discussion in the article and about Figure 10 Implemented, the on-demand SIB1 configuration component 150 is configured to send a first configuration to the UE, the first configuration being used to configure UL-WUS for requesting SIB1 associated with the second network entity. The on-demand SIB1 configuration component 150 is further configured to receive UL-WUS from the UE based on SIB1 status information. The on-demand SIB1 configuration component 150 is further configured to send a response to the UE indicating a second configuration for monitoring SIB1 from the second network entity.

[0117] like Figure 1 The discussion in the article and about Figure 11Implemented, the on-demand SIB1 configuration component 150 is configured to send a first SIB1 associated with a second network entity to the UE. The on-demand SIB1 configuration component 150 is further configured to receive a network entity wake-up signal from the first network entity. The on-demand SIB1 configuration component 150 is further configured to send a second SIB1 associated with the second network entity to the UE in response to receiving the network entity wake-up signal, the second SIB1 being different from the first SIB1. The on-demand SIB1 configuration component 150 is further configured to receive a PRACH signal for initial access from the UE based on the second SIB1.

[0118] On-demand SIB1 configuration component 150 may be located within one or more processors of one or more network entities 104, such as RU processor 1306 (e.g., at 150a), DU processor 1326 (e.g., at 150b), and / or CU processor 1346 (e.g., at 150c). On-demand SIB1 configuration components 150a-150c may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors 1306, 1326, 1346 configured to execute the stated process / algorithm, and stored in a computer-readable medium for use by one or more processors 1306, 1326, 1346, or a combination thereof.

[0119] The specific order or hierarchy of the boxes in the processes and flowcharts disclosed herein is illustrative of the exemplary methods. Therefore, the specific order or hierarchy of the boxes in the processes and flowcharts can be rearranged. Some boxes may also be merged or deleted. Dashed lines may indicate optional elements of the diagrams. The appended method claims present the elements of each box in the exemplary order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0120] The detailed descriptions presented herein, in conjunction with accompanying drawings, depict various configurations, but do not represent the only configurations in which the concepts described herein can be practiced. These detailed descriptions include specific details used to provide a comprehensive explanation of the various concepts. However, these concepts can be practiced without using these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0121] Various apparatuses and methods are presented with reference to aspects of wireless communication systems (such as telecommunications systems). These apparatuses and methods are described in the following detailed description and are shown in the accompanying drawings by various boxes, components, circuits, processes, call flows, systems, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

[0122] An element, or any part of an element, or any combination of elements, can be implemented as a “processing system” including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software, which may be referred to as software, firmware, middleware, microcode, hardware description languages, or others. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0123] If the functionality described herein is implemented in software, then such functionality may be stored on or encoded as one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer-readable media include computer storage media and may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer. The storage medium can be any available medium accessible to a computer.

[0124] The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, form factors, sizes, and package arrangements. For example, aspects, implementations, and / or use cases can be generated via integrated chip implementations and other devices based on non-modular components, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, devices supporting artificial intelligence (AI), devices supporting machine learning (ML), etc. The scope of aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein.

[0125] Apparatus incorporating the aspects and features described herein may also include additional components and features for implementing and practicing the claimed and described aspects and features. For example, the transmission and reception of wireless signals necessarily include numerous components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user devices, etc., in various configurations.

[0126] The description herein is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be interpreted in light of the full scope of this disclosure consistent with the language of the claims.

[0127] Unless explicitly stated otherwise, references to singular elements do not imply "one and only one," but rather "one or more." Terms such as "if," "when," and "at" do not imply an immediate temporal relationship or response. That is, phrases such as "when" do not imply an immediate action in response to or during the occurrence of an action, but simply that an action will occur if the condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The terms "may," "may," and "can" as used herein generally carry certain connotations. For example, "may" refers to a permissible feature that may or may not occur, "may" refers to a feature that is very likely to occur, and "can" refers to a capability (e.g., being able to). The phrase "for example" generally carries a similar connotation to "may," and therefore, "may" is sometimes excluded from sentences that include "for example" or other similar phrases.

[0128] Unless otherwise expressly stated, the term "some" means one or more. Combinations such as "at least one of A, B, or C" or "one or more of A, B, or C" include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiple A, multiple B, and / or multiple C, or may include only A, only B, or only C. A set should be interpreted as a set of elements having a number of one or more elements. Terms or articles such as "a," "an," and / or "the" may refer to one of the items, features, elements, etc., following that term or article, or may refer to more than one of the items, features, elements, etc., following that term or article. For example, the expression "a small component" does not exclude references to multiples of said component, because "multiple components" necessarily includes "a small component." Therefore, the expression "a small component" can be interpreted as "at least one component," or similarly, as "one or more components."

[0129] Unless otherwise explicitly indicated, ordinal terms such as “first” and “second” do not necessarily imply order in time, sequence, numerical value, etc., but are used to distinguish different instances of the term or phrase that follows each ordinal term.

[0130] As used in the specification and drawings, reference numerals are sometimes cross-referenced across drawings to indicate the same or similar features. Features that are identical in multiple drawings may be labeled with the same reference numerals in multiple drawings. Features that are similar but not identical across multiple drawings may be labeled with reference numerals that have different leading numerals but share one or more of the same trailing numerals (e.g., 206, 306, 406, etc. may refer to similar features in the drawings). Therefore, the same numerals may refer to the same action.

[0131] Structural and functional equivalents of elements of all aspects described throughout this disclosure, known or subsequently learned by those skilled in the art, are expressly incorporated herein by reference and are covered by the claims. The terms “module,” “mechanism,” “element,” “device,” etc., may not be substitutes for the term “component.” Therefore, no claim element shall be construed as means plus function unless explicitly stated using the phrase “component for…”. As used herein, the phrase “based on” should not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless expressly stated otherwise, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) shall be construed as “at least based on A”.

[0132] The following examples are illustrative only and can be combined with other examples or teachings described herein without limitation.

[0133] Example 1 is a method for wireless communication at a UE, comprising: receiving a first configuration of configuring an uplink wake-up signal UL-WUS from a first network entity, the UL-WUS being used to request a System Information Block Type 1 (SIB1) associated with a second network entity; sending the UL-WUS to the first network entity based on the status information of the SIB1; and receiving a response from the first network entity indicating a second configuration for monitoring the SIB1 from the second network entity.

[0134] Example 2 can be combined with Example 1 and includes: wherein UL-WUS includes the Physical Random Access Channel (PRACH) signal.

[0135] Example 3 may be combined with any of Examples 1 to 2, and further includes: transmitting UL-WUS includes transmitting PRACH signals via dedicated PRACH resources based on at least one of the following: a Physical Cell Identifier (PCI) associated with a second network entity; a carrier frequency associated with SIB1; or a Synchronization Signal Block (SSB) index with a Physical Downlink Shared Channel (PDSCH) Quasi-Co-located QCL carrying SIB1.

[0136] Example 4 can be combined with any of Examples 1 to 3, and further includes: transmitting UL-WUS including transmitting a PRACH signal via a non-dedicated PRACH resource, the method further including: receiving a random access response (RAR) from a first network entity in response to the PRACH signal to schedule physical uplink shared channel (PUSCH) communication; and transmitting to the first network entity a PUSCH communication indicating at least one of the following: a physical cell identifier (PCI) associated with a second network entity; one or more synchronization signal blocks (SSBs) with a physical downlink shared channel (PDSCH) quasi-co-located QCL carrying SIB1; first measurement information associated with the first network entity and second measurement information associated with the second network entity; a carrier frequency associated with SIB1; or a time window for monitoring SIB1; and receiving physical downlink shared channel (PDSCH) communication from the first network entity in response to the PUSCH communication to instruct the UE to monitor SIB1 or perform an initial access procedure with the first network entity.

[0137] Example 5 can be combined with any of Examples 1 to 4, and further includes: the SIB1 associated with the second network entity includes an on-demand SIB1, the method further including: receiving a second SIB1 from a first network entity; and obtaining an indicator indicating whether the second SIB1 is different from the on-demand SIB1, wherein the status information is based on the fact that the second SIB1 is different from the on-demand SIB1.

[0138] Example 6 can be combined with any of Examples 1 to 4, and further includes receiving SIB1 from a second network entity via the Physical Downlink Shared Channel (PDSCH) based on a second configuration.

[0139] Example 7 can be combined with any of Examples 1 to 6, and further includes receiving a synchronization signal block SSB associated with the on-demand SIB1 from a second network entity.

[0140] Example 8 can be combined with any of Examples 1 to 7, and further includes: the SIB1 associated with the second network entity includes an on-demand SIB1, the method further including: receiving a first SIB1 from the second network entity before receiving a first configuration; obtaining a value tag associated with the first SIB1; and obtaining a value tag associated with the on-demand SIB1, wherein the status information is based on the difference between the value tag associated with the first SIB1 and the value tag associated with the on-demand SIB1.

[0141] Example 9 can be combined with any of Examples 1 to 8, and further includes: avoiding sending UL-WUS, where the status information is based on the same value label associated with the first SIB1 and the value label associated with the on-demand SIB1.

[0142] Example 10 can be combined with any of Examples 1 to 9, and further includes: the value label associated with the first SIB1 includes the hash function of the first SIB1; and the value label associated with the on-demand SIB1 includes the hash function of the on-demand SIB1.

[0143] Example 11 can be combined with any of Examples 1 to 10, and further includes: receiving a first SIB1 with a valid time period from a second network entity before receiving the first configuration, wherein the status information is based on the valid time period of the first SIB1.

[0144] Example 12 may be combined with any of Examples 1 to 11, and further includes at least one of the following: receiving an indicator of a valid time period from a first network entity via a first configuration; or receiving an indicator of a valid time period from a second network entity via at least one of the following: a first SIB1; a second SIB1; a master information block (MIB); or a physical downlink control channel (PDCCH) that schedules the first SIB1.

[0145] Example 13 may be combined with any of Examples 1 to 12, and further includes: sending UL-WUS includes sending UL-WUS based on at least one of the following: first measurement information associated with a first network entity; or second measurement information associated with a second network entity.

[0146] Example 14 may be combined with any of Examples 1 to 13, and further includes: sending to a first network entity first measurement information associated with the first network entity and second measurement information associated with a second network entity; sending to the first network entity a Physical Random Access Channel (PRACH) signal for initial access; performing an initial access procedure with the first network entity based on a third configuration to access the first network entity if at least one of the following occurs: the Reference Signal Received Power (RSRP) associated with the first network entity is greater than the RSRP associated with the second network entity minus a first offset; the Signal-to-Interference-plus-Noise Ratio (SINR) associated with the first network entity is greater than the SINR associated with the second network entity minus a second offset; the Reference Signal Received Quality (RSRQ) associated with the first network entity is greater than the RSRQ associated with the second network entity minus a third offset; the RSRP associated with the first network entity is greater than a first threshold; the SINR associated with the first network entity is greater than a second threshold; the RSRQ associated with the first network entity is greater than a third threshold; the RSRP associated with the second network entity is less than a fourth threshold; the SINR associated with the second network entity is less than a fifth threshold; or the RSRQ associated with the second network entity is less than a sixth threshold.

[0147] Example 15 may be combined with any of Examples 1 to 14, and further includes: receiving a response via a Media Access Control Element (MAC-CE) associated with at least one of the following: a first Random Access Response (RAR) type for configuring the UE to monitor SIB1 from a second network entity; or a second RAR type for configuring the UE to access a first network entity.

[0148] Example 16 may be combined with any of Examples 1 to 15, and further includes: the SIB1 associated with the second network entity includes an on-demand SIB1, and the response further indicates at least one of the following: a UL-WUS reception acknowledgment; a backoff indicator for the UE to perform an initial access procedure for the first network entity; a Physical Cell Identifier (PCI) associated with the second network entity; a carrier frequency associated with the on-demand SIB1; one or more first synchronization signal blocks (SSBs) with the Physical Downlink Shared Channel (PDSCH) quasi-co-located QCL carrying the on-demand SIB1; one or more second SSBs with the Physical Downlink Control Channel (PDCCH) quasi-co-located QCL scheduling the PDSCH carrying the on-demand SIB1; a value label associated with the on-demand SIB1; timing information for monitoring the on-demand SIB1; a retransmission configuration for the UL-WUS; or a downlink assignment for the PDSCH carrying the on-demand SIB1.

[0149] Example 17 may be combined with any of Examples 1 to 16, and further includes: the UE avoiding receiving a PDCCH carrying an on-demand SIB1 PDSCH, and the downlink assignment indicating at least one of the following: a frequency domain resource assignment (FDRA) for the PDSCH; a time domain resource assignment (TDRA) for the PDSCH; a mapping from a virtual resource block (VRB) to a physical resource block (PRB) for the PDSCH; a modulation and coding scheme (MCS) for the PDSCH; a redundant version (RV) for the PDSCH; an index of a reference time slot for the PDSCH; a periodicity of a reference time slot for the PDSCH; a time slot offset from a reference time slot for the PDSCH; or a number of retransmissions for the PDSCH.

[0150] Example 18 may be combined with any of Examples 1 to 17, and further includes: receiving a first configuration including receiving a first configuration for UL-WUS when the UE is in a Radio Resource Control (RRC) idle state or an RRC inactive state; sending UL-WUS including sending UL-WUS when the UE is in an RRC idle state or an RRC inactive state; and receiving a response including receiving a response to UL-WUS when the UE is in an RRC idle state or an RRC inactive state.

[0151] Example 19 is a method for wireless communication at a first network entity, comprising: sending a first configuration to a user equipment (UE) for configuring an uplink wake-up signal UL-WUS for requesting a System Information Block Type 1 (SIB1) associated with a second network entity; receiving the UL-WUS from the UE based on the status information of the SIB1; and sending a response to the UE indicating a second configuration for monitoring the SIB1 from the second network entity.

[0152] Example 20 can be combined with Example 19 and includes: UL-WUS includes a Physical Random Access Channel (PRACH) signal.

[0153] Example 21 may be combined with any of Examples 19 to 20, and further includes: receiving UL-WUS includes receiving PRACH signals via dedicated PRACH resources based on at least one of the following: a Physical Cell Identifier (PCI) associated with a second network entity; a carrier frequency associated with SIB1; or a Synchronization Signal Block (SSB) index of a Physical Downlink Shared Channel (PDSCH) quasi-co-located QCL carrying SIB1.

[0154] Example 22 may be combined with any of Examples 19 to 21, and further includes: receiving UL-WUS including receiving PRACH signals via non-dedicated PRACH resources, the method further including: sending a random access response (RAR) to the UE in response to the PRACH to schedule physical uplink shared channel (PUSCH) communication; and receiving from the UE a PUSCH communication indicating at least one of the following: a physical cell identifier (PCI) associated with a second network entity; one or more synchronization signal blocks (SSBs) with a physical downlink shared channel (PDSCH) quasi-co-located QCL carrying SIB1; first measurement information associated with a first network entity and second measurement information associated with a second network entity; a carrier frequency associated with SIB1; or a time window for monitoring SIB1; and sending a physical downlink shared channel (PDSCH) communication to the UE in response to the PUSCH communication to instruct the UE to monitor SIB1 or perform an initial access procedure with the first network entity.

[0155] Example 23 may be combined with any of Examples 19 to 22, and further includes: the SIB1 associated with the second network entity includes an on-demand SIB1, the method further including: sending a second SIB1 associated with the first network entity to the UE; and an indicator of whether the second SIB1 is different from the on-demand SIB1, wherein the status information is based on the second SIB1 being different from the on-demand SIB1.

[0156] Example 24 may be combined with any of Examples 19 to 23, and further includes: receiving a value tag associated with SIB1 from a second network entity; and sending a value tag associated with SIB1 to the UE, wherein the status information is based on the value tag.

[0157] Example 25 can be combined with any of Examples 19 through 24, and further includes: the value label associated with SIB1 includes the hash function of SIB1.

[0158] Example 26 may be combined with any of Examples 19 to 25, and further includes: receiving a valid time period of a first SIB1 associated with a second network entity from a second network entity, wherein: a first configuration indication for UL-WUS is a valid time period; and wherein status information is based on the valid time period.

[0159] Example 27 may be combined with any of Examples 19 to 26, and further includes: receiving UL-WUS includes receiving UL-WUS based on at least one of: first measurement information associated with a first network entity; or second measurement information associated with a second network entity.

[0160] Example 28 may be combined with any of Examples 19 to 27, and further includes: receiving from the UE first measurement information associated with a first network entity and second measurement information associated with a second network entity; receiving from the UE a Physical Random Access Channel (PRACH) signal for initial access; and performing an initial access procedure for the UE to access the first network entity when at least one of the following occurs: the Reference Signal Received Power (RSRP) associated with the first network entity is greater than the RSRP associated with the second network entity minus a first offset; the Signal-to-Interference-plus-Noise Ratio (SINR) associated with the first network entity is greater than the SINR associated with the second network entity minus a second offset; the Reference Signal Received Quality (RSRQ) associated with the first network entity is greater than the RSRQ associated with the second network entity minus a third offset; the RSRP associated with the first network entity is greater than a first threshold; the SINR associated with the first network entity is greater than a second threshold; the RSRQ associated with the first network entity is greater than a third threshold; the RSRP associated with the second network entity is less than a fourth threshold; the SINR associated with the second network entity is less than a fifth threshold; or the RSRQ associated with the second network entity is less than a sixth threshold.

[0161] Example 29 may be combined with any of Examples 19 to 28, and further includes: sending a response via a Media Access Control Element (MAC-CE) associated with at least one of the following: a first Random Access Response (RAR) type for configuring the UE to monitor SIB1 from a second network entity; or a second RAR type for configuring the UE to access a first network entity.

[0162] Example 30 may be combined with any of Examples 19 to 29, and further includes: the SIB1 associated with the second network entity includes an on-demand SIB1, and the response further indicates at least one of the following: a UL-WUS reception acknowledgment; a backoff indicator for the UE to perform an initial access procedure for the first network entity; a Physical Cell Identifier (PCI) associated with the second network entity; a carrier frequency associated with the on-demand SIB1; one or more first synchronization signal blocks (SSBs) with the Physical Downlink Shared Channel (PDSCH) quasi-co-located QCL carrying the on-demand SIB1; one or more second SSBs with the Physical Downlink Control Channel (PDCCH) quasi-co-located QCL scheduling the PDSCH carrying the on-demand SIB1; a value tag associated with the on-demand SIB1; timing information for monitoring the on-demand SIB1; a retransmission configuration for the UL-WUS; or a downlink assignment for the PDSCH carrying the on-demand SIB1.

[0163] Example 31 may be combined with any of Examples 19 to 30, and further includes: a downlink assignment indicating at least one of the following: a frequency domain resource assignment (FDRA) for PDSCH; a time domain resource assignment (TDRA) for PDSCH; a mapping of virtual resource blocks (VRBs) to physical resource blocks (PRBs) for PDSCH; a modulation and coding scheme (MCS) for PDSCH; a redundant version (RV) for PDSCH; an index of a reference time slot for PDSCH; a periodicity of a reference time slot for PDSCH; a time slot offset from a reference time slot for PDSCH; or a number of retransmissions for PDSCH.

[0164] Example 32 is a method for wireless communication at a second network entity, comprising: sending a first System Information Block Type 1 (SIB1) associated with the second network entity to a user equipment (UE); receiving a network entity wake-up signal from the first network entity; in response to receiving the network entity wake-up signal, sending a second SIB1 associated with the second network entity to the UE, the second SIB1 being different from the first SIB1; and receiving a Physical Random Access Channel (PRACH) signal for initial access from the UE based on the second SIB1.

[0165] Example 33 can be combined with Example 32 and further includes: entering Network Power Saving (NES) mode after sending the first SIB1.

[0166] Example 34 may be combined with any of Examples 32 to 33, and further includes: transmitting the second SIB1 includes transmitting the second SIB1 via the Physical Downlink Shared Channel (PDSCH).

[0167] Example 35 may be combined with any of Examples 32 to 34, and further includes: sending a synchronization signal block SSB associated with the second SIB1 to the UE.

[0168] Example 36 may be combined with any of Examples 32 to 35, and further includes: sending a value tag associated with the first SIB1 to the UE; and sending a value tag associated with the second SIB1 to the first network entity, wherein sending the second SIB1 is based on the fact that the value tag associated with the first SIB1 and the value tag associated with the second SIB1 are different.

[0169] Example 37 can be combined with any of Examples 32 to 36, and further includes: the value label associated with the first SIB1 includes the hash function of the first SIB1; and the value label associated with the second SIB1 includes the hash function of the second SIB1.

[0170] Example 38 may be combined with any of Examples 32 to 37, and further includes: sending an indicator of the effective time period of the first SIB1 to the UE, wherein sending the second SIB1 includes sending the second SIB1 after the effective time period of the first SIB1.

[0171] Example 39 may be combined with any of Examples 32 to 38, and further includes: sending an indicator of the effective time period of the first SIB1 via at least one of: the first SIB1; the Master Information Block (MIB); or the Physical Downlink Control Channel (PDCCH) that schedules the first SIB1.

[0172] Example 40 is an apparatus for implementing wireless communication as described in any of Examples 1 to 39.

[0173] Example 41 is an apparatus for wireless communication, which includes components for implementing the method as described in any of Examples 1 to 39.

[0174] Example 42 is a non-transitory computer-readable medium that stores computer-executable code that, when executed by a processor, causes the processor to implement the method described in any of Examples 1 through 39.

Claims

1. A method for wireless communication by a user equipment (UE) (102), the method comprising: Receive (730) a first configuration from the first network entity (104a), the first configuration being configured to configure an uplink wake-up signal UL-WUS for requesting a System Information Block Type 1 (SIB1) associated with the second network entity (104b); Based on the status information of SIB1, send (740) the UL-WUS to the first network entity (104a); as well as A response is received (750) from the first network entity (104a), the response indicating a second configuration of the SIB1 for monitoring from the second network entity (104b).

2. The method of claim 1, wherein the UL-WUS includes a Physical Random Access Channel (PRACH) signal.

3. The method of claim 2, wherein transmitting (740) the UL-WUS comprises transmitting (740) the PRACH signal via a dedicated PRACH resource based on at least one of the following: The Physical Cell Identifier (PCI) associated with the second network entity (104b); The carrier frequency associated with the SIB1; or The synchronization signal block SSB index of the physical downlink shared channel PDSCH quasi-co-address QCL carrying the SIB1.

4. The method of claim 2, wherein transmitting (740) the UL-WUS comprises transmitting (740) the PRACH signal via a non-dedicated PRACH resource, the method further comprising: In response to the PRACH signal, receive (825) a random access response (RAR) from the first network entity (104a) to schedule physical uplink shared channel (PUSCH) communication; as well as Send (835) to the first network entity (104a) the PUSCH communication indicating at least one of the following: The Physical Cell Identifier (PCI) associated with the second network entity (104b); One or more synchronization signal blocks (SSBs) that share the physical downlink channel PDSCH quasi-co-located QCL carrying the SIB1; First measurement information associated with the first network entity (104a) and second measurement information associated with the second network entity (104b); The carrier frequency associated with the SIB1; or The time window used to monitor SIB1; and In response to the PUSCH communication, a Physical Downlink Shared Channel (PDSCH) communication is received (845) from the first network entity (104a), the PDSCH communication instructing the UE (102) to monitor the SIB1 or perform an initial access procedure with the first network entity (104a).

5. The method of any one of claims 1 to 4, wherein the SIB1 associated with the second network entity includes an on-demand SIB1, the method further comprising: Receive the second SIB1 from the first network entity (104a); as well as Obtain an indicator that indicates whether the second SIB1 is different from the on-demand SIB1, wherein the status information is based on the fact that the second SIB1 is different from the on-demand SIB1.

6. The method according to any one of claims 1 to 5, further comprising: Based on the second configuration, SIB1 is received (760) from the second network entity (104b) via the Physical Downlink Shared Channel (PDSCH).

7. The method of any one of claims 1 to 6, wherein the SIB1 associated with the second network entity includes an on-demand SIB1, the method further comprising: Before receiving the first configuration, a first SIB1 is received (710) from the second network entity (104b); Obtain the value label associated with the first SIB1; and Obtain the value tag associated with the on-demand SIB1, wherein the status information is based on the difference between the value tag associated with the first SIB1 and the value tag associated with the on-demand SIB1.

8. The method of claim 7, further comprising: Avoid sending the UL-WUS, where the status information is based on the same value tag associated with the first SIB1 and the value tag associated with the on-demand SIB1.

9. The method of any one of claims 1 to 8, further comprising: Before receiving the first configuration, a first SIB1 with a valid time period is received (710) from the second network entity (104b), wherein the status information is based on the valid time period of the first SIB1.

10. The method of any one of claims 1 to 9, further comprising: The response is received (750) via a Media Access Control-Control Element (MAC-CE) associated with at least one of the following: A first random access response (RAR) type, wherein the first RAR type configures the UE (102) to monitor the SIB1 from the second network entity (104b); or The second RAR type configures the UE (102) to access the first network entity (104a).

11. The method according to any one of claims 1 to 10, wherein: Receiving (730) the first configuration includes: receiving (730) the first configuration of UL-WUS when the UE (102) is in a Radio Resource Control (RRC) idle state or an RRC inactive state; Sending (740) the UL-WUS includes sending (740) the UL-WUS when the UE (102) is in the RRC idle state or the RRC inactive state; and Receiving (750) the response includes receiving (750) the response to the UL-WUS when the UE (102) is in the RRC idle state or the RRC inactive state.

12. A method for wireless communication by a first network entity (104a), the method comprising: Send (730) a first configuration to the user equipment (UE) (102), the first configuration being configured to configure an uplink wake-up signal UL-WUS for requesting a system information block type 1 SIB1 associated with a second network entity (104b); The UL-WUS is received (740) from the UE (102) based on the status information of the SIB1; as well as A (750) response is sent to the UE (102), the response indicating a second configuration of the SIB1 for monitoring the second network entity (104b).

13. The method of claim 12, further comprising: Receive (715) a value label associated with the SIB1 from the second network entity (104b); as well as The value tag associated with the SIB1 is sent to the UE (102), wherein the status information is based on the value tag.

14. The method of any one of claims 12 to 13, further comprising: Receive (715) a valid time period of the first SIB1 associated with the second network entity (104b) from the second network entity (104b), wherein: The first configuration of UL-WUS indicates the effective time period; and The status information mentioned therein is based on the valid time period.

15. A method for wireless communication performed by a second network entity (104b), the method comprising: Send (710) a first system information block type 1 (SIB1) associated with the second network entity (104b) to the user equipment (UE) (102); Receive (755) network entity wake-up signal from the first network entity (104a); In response to receiving the network entity wake-up signal, a second SIB1 associated with the second network entity (104b) is sent (760) to the UE (102), the second SIB1 being different from the first SIB1; as well as The UE (102) receives the Physical Random Access Channel (PRACH) signal for initial access based on the second SIB1.

16. The method of claim 15, further comprising: Send (710) a value tag associated with the first SIB1 to the UE (102); as well as Send a value tag associated with the second SIB1 to a first network entity (104a), wherein sending (760) the second SIB1 is based on the fact that the value tag associated with the first SIB1 and the value tag associated with the second SIB1 are different.

17. The method of any one of claims 15 to 16, further comprising: Send (710) an indicator of the effective time period of the first SIB1 to the UE (102), wherein sending (760) the second SIB1 includes sending (760) the second SIB1 after the effective time period of the first SIB1.

18. An apparatus for wireless communication, comprising a transceiver, a memory, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement the method as claimed in any one of claims 1 to 17.

Images