Procedures to support on demand–system information block type-1 (OD-SIB1) in wireless networks

Abstract

Embodiments disclosed herein provide a method and system for performing procedures to support on demand – system information block type-1 (OD-SIB1) in wireless networks. The present disclosure comprises transmitting, by a first network entity, operating in a first mode, to one or more second network entities, operating in the first mode, a request message. Further, the request message comprises cell access configuration information relating to the first network entity. Furthermore, based on receiving a response in reply to the request message, the first network entity selectively transitions into the second mode. The response indicates that at least one of the one or more second network entities is available to support broadcasting of the cell access configuration information to one or more user equipment (UE) associated with the first network entity.

Description

PROCEDURES TO SUPPORT ON DEMAND-SYSTEM INFORMATION BLOCK TYPE-1 (OD-SIB1) IN WIRELESS NETWORKSCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to Indian provisional patent application- 202441086274, filed on November 08, 2024, and Indian non-provisional patent application- 202441086274, filed on February 28, 2025, the entire contents of which are incorporated herein by reference.TECHNICAL FIELD

[0002] The present disclosure generally relates to procedures to support On-demand-System Information Block Type-1 (OD-SIB1) in wireless network.BACKGROUND

[0003] The information disclosed in this background section is only for enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0004] Network energy efficiency is a performance requirement in wireless networks. Consequently, Third Generation Partnership Project (3GPP) standards are designed to enable low energy consumption, not only in user terminals, but also in network equipment. New features for energy savings (also termed as Network Energy Saving (NES) features) are introduced. For example, much longer durations and higher ratio of discontinuous transmission (DTX) is supported in New Radio (NR) compared to the 3GPP Long Term Evolution (LTE) standard. Also, the feature of transmitting System Information Blocks (SIBs) only on-demand is supported. SIBs are broadcast messages from a base station or a gNodeB (gNB) to the UEs that contain relevant information related to the UEs. Further, SIB1 is a type of SIB which provides network access parameters along with scheduling information about all other system information. Network energy saving is of great importance for environmental sustainability, to reduce environmental impact (greenhouse gas emissions), and for operational cost savings. Cells associated with the NES features (also termed as NES cells) may not transmit a default SIB1, periodically, to save energy. The NES cells may not transmit default SIB1 until a wake-up signal is received. The NES cells transmit SIBs to User Equipment (UEs) on receiving the wake-up signal.

[0005] The relevant information included in the SIBs may include, without limitation, cell selection information, information required to perform cell re-selection by the UE, and defines the scheduling of other system information. The SIB is a downlink broadcast information blocktransmitted periodically by the gNB. The SIB is very critical information for the UE to connect to the gNB. The UE needs SIB for cell camping when it is powered on, and for cell selection and cell re-selection when the UE is in Radio Resource Control (RRC) IDLE / inactive mode. The SIB provides all necessary details, including, but limited to, system frame number, system bandwidth, Public Land Mobile Network (PLMN), cell selection and re-selection thresholds, and the like, to access the network. 3GPP Release 19 has a work item for Network Energy Savings with an objective to provide on-demand SIB1 (OD-SIB 1) transmission to UEs by enabling NES cells to selectively broadcast SIB 1 based on specific trigger via uplink wake-up signals using existing channels.SUMMARY

[0006] Typically, when a network entity decides to transition to a first mode, for example the NES mode, the network entity requires support of one or more neighboring network entities to transmit periodic SIB1 to UEs. However, lack of coordination between the network entity and the one or more neighboring network entities could lead to inefficient resource utilization and ineffective communication in the network environment.

[0007] The present disclosure relates to a method comprising the steps of transmitting, by a first network entity, operating in a first mode, to one or more second network entities, operating in the first mode, a request message. The request message comprises cell access configuration information relating to the first network entity. Further, the method comprises selectively transitioning, by the first network entity, based on receiving a response in reply to the request message, into the second mode. The response indicates that at least one of the one or more second network entities is available to support broadcasting of the cell access configuration information to one or more user equipment (UE). The one or more UE is associated with the first network entity.

[0008] The present disclosure also relates to an apparatus configured to transmit, by a first network entity, operating in a first mode, to one or more second network entities, operating in the first mode, a request message. The request message comprises cell access configuration information relating to the first network entity. The apparatus is also configured to selectively transition, by the first network entity based on receiving a response in reply to the request message, into the second mode. The response indicates that at least one of the one or more second network entities is available to support broadcasting of the cell access configuration information to one or more user equipment (UE). The one or more UE is associated with the first network entity.

[0009] In an embodiment, there is a non-transitory computer readable medium including instructions stored thereon that when processed by at least one processor, cause the at least one processor to perform operations of transmitting, by a first network entity, operating in a first mode, to one or more second network entities, operating in the first mode, a request message. The request message comprises cell access configuration information relating to the first network entity. Further, the at least one processor also performs operations of selectively transitioning, by the first network entity, based on receiving a response in reply to the request message, into the second mode. The response indicates that at least one of the one or more second network entities is available to support broadcasting of the cell access configuration information to one or more user equipment (UE). The one or more UE is associated with the first network entity.

[0010] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Features, aspects, and advantages of embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:

[0012] FIG. 1 illustrates an exemplary environment for managing triggering of activation and deactivation of a Network Energy Saving (NES) mode of an NES cell and supporting of On- demand system information block type-1 (OD-SIB 1) by relevant Cell A in wireless communication networks, in accordance with some embodiments of the present disclosure.

[0013] FIG. 2 illustrates an exemplary call flow diagram of indicating positive acknowledgement to support the NES mode of the NES Cell, in accordance with an embodiment of the present disclosure.

[0014] FIG. 3 illustrates an exemplary call flow diagram indicating failure message to support the NES mode of the NES Cell, in accordance with an embodiment of the present disclosure.

[0015] FIG. 4 illustrates an exemplary call flow diagram of indicating outcome when at least one Cell A responds to the UL WUS Config Transmission Request with a positive acknowledgement, in accordance with an embodiment of the present disclosure.

[0016] FIG. 5 illustrates an exemplary call flow diagram of indicating outcome when at least one Cell A responds to the UL WUS Config Transmission Request with a failure message, in accordance with an embodiment of the present disclosure.

[0017] FIG. 6 illustrates an exemplary call flow diagram of indicating change in NES Cell UL WUS configuration, in accordance with an embodiment of the present disclosure.

[0018] FIGS. 7A-7C illustrate flowcharts of a method for handling OD-SIB1 in the wireless networks, according to the embodiments as disclosed herein.

[0019] FIG. 8 illustrates an embodiment of a device wherein the method for handling OD-SIB1 in the wireless networks, may be implemented, in accordance with an embodiment of the present disclosure.

[0020] It should be appreciated by those skilled in the art that any block diagram herein represents conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.DETAILED DESCRIPTION

[0021] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” (in other words, nouns not mentioned in the plural) are intended to include one or more items and may be used interchangeably with “one or more.” Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B],” “[A] and / or [B],” or “at least one of [A] or [B]” are to be understood as including only A, only B, or both A and B.

[0022] The following detailed description of example embodiments refers to the accompanying drawings. The present disclosure provides illustrations and descriptions but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the present disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flow chart and description of operations provided below relate to at least one of the embodiments in the present disclosure. It should be noted that it is possible to make other embodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or moreoperations may be added, one or more operations may be performed simultaneously (at least in part).

[0023] It will be apparent that systems and / or methods described herein, may be implemented in different forms of hardware, software, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods should not limit their implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0024] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, the particular combinations are not intended to limit the disclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Even if a dependent claim directly depends on only one claim, the present disclosure may indicate that the dependent claim is dependent on other claims in the claim set.

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

[0026] In wireless communication systems, such as those employing New Radio (NR) technology, Network Energy Saving (NES) cell plays a crucial role in providing advanced services to users. The NES cell optimizes energy consumption by dynamically transitioning between active and inactive states based on traffic demand. The NES cell offers enhanced capabilities and features compared to traditional cells, enabling improved performance, capacity, and quality of service. For example, the NES features, such as discontinuous transmission (DTX) and on-demand System Information Block 1 (SIB1) transmission are supported. Cell A is a primary or anchor cell in network that maintains continuous connectivity and handles critical signaling and control functions. The cell A ensures seamless communication for user devices and coordinates with other cells, including NES cells, to manage data traffic and handovers efficiently. The cell A always remains operational to ensure stable network performance and acts as a control anchor.

[0027] The NES cell often has multiple neighboring cells relevant / associated with the NES cell. To enable on-demand system information block 1 (OD-SIB1) operations, it is essential for theNES cell to transmit the NES cells information to neighboring cells with overlapping coverage, specifically cell As.

[0028] The NES cell may transmit OD-SIB1 transmission in response to UL WUS from a UE. The NES cell need not transmit periodic SIB1 (default transmission) all the time. For example, cells associated with the NES features (also termed as NES cells) may not transmit default SIB1, periodically, to save energy. In an example, the NES cells may not transmit default SIB1 until a wake-up signal is received. For example, the wake-up signal may be received from the UEs. The NES cells transmit SIB1 to the UEs on receiving the wake-up signal.

[0029] 3 GPP Release 19 has a work item WI on enhancements of network energy savings for NR (RP-234065).

[0030] The objectives of 3GPP Release 19 related to NES are reproduced below:

[0031] 1. Specify procedures and signaling method(s) to support on-demand SIB1 for UEs in idle / inactive mode, including: [RAN1 / 2 / 3]

[0032] • Triggering method by uplink wake-up-signal using an existing signal / channel.

[0033] • Wake-up-signal configuration provisioning to UE.

[0034] • Note: No modification of SSB will be discussed under this objective.

[0035] • Information exchange between gNBs at least for the configuration of wake-up signal, if necessary.

[0036] • Checkpoint for normative work in RAN# 105 Specify triggering method(s) (select from UE uplink wake-up-signal using an existing signal / channel, cell on / off indication via backhaul, Scell activation / deactivation signaling).

[0037] A concept of a non-anchor NES cell without periodic SIB1 is introduced in 3 GPP, where the UE is in coverage of one or more anchor cells and one or multiple non-anchor NES cell(s).

[0038] FIG. 1 illustrates an exemplary environment for managing triggering of activation and deactivation of a Network Energy Saving (NES) mode of an NES cell and supporting of On- demand system information block type-1 (OD-SIB1) by relevant Cell A in wireless communication networks, in accordance with some embodiments of the present disclosure.

[0039] As shown in FIG. 1, the exemplary environment 100 includes a first network entity 102, communicatively coupled with one or more second network entities 104 via a communication network 106.

[0040] In one non-limiting example, the first network entity 102 may be an NES cell capable of operating in an active mode (non-energy saving mode) and an energy-saving mode. Accordingto an embodiment of the present disclosure, the one or more second network entity 104 may be a one or more cell A in the non-energy saving mode.

[0041] As a non-limiting example, the first network entity 102 includes devices or systems for transmitting a request message. The first network entity 102 may be configured to operate in a first mode and a second mode. In an embodiment, the first mode may be a non-energy saving mode and the second mode may be an energy saving mode. The request message comprises cell access configuration information relating to the first network entity 102, wherein the request message pertains to broadcasting, upon the first network entity 102 transitioning to the second mode, the cell access configuration information to one or more user equipment (UE) (not shown) associated with the first network entity 102. The first network entity 102 may be but not limited to a Next Generation Node B (gNB), an evolved Node B (eNB), a femtocell, a relay node, a picocell, an loT gateway, or any other suitable network infrastructure component or system capable of wired or wireless communication.

[0042] The one or more second network entities 104 may be implemented as network infrastructure like a central gNB, the eNB, a macrocell, or a high-capacity access point, and the like. In an embodiment, the one or more second network entities 104 may be a centralized network controller for managing communication, synchronization, and dynamic configuration of mapping information and wake-up signaling parameters across network entities.

[0043] Further, the first network entity 102 may include a processor (not shown in FIG. 1), a I / O interface (not shown in FIG. 1), and the memory (not shown in FIG. 1). In some embodiments, the memory is communicatively coupled to the processor. The memory stores instructions, executable by the processor, which, on execution, may cause the first network entity 102 to trigger transmission of the request message to the one or more second network entities 104 for supporting the UE for seamless operation of the communication network 106, as disclosed in the present disclosure.

[0044] In an embodiment the communication network 106 may include, without limitation, NR- based networks, a direct interconnection, Local Area Network (LAN), Wide Area Network (WAN), Controller Area Network (CAN), wireless network (e.g., using a Wireless Application Protocol), the Internet, and the like.

[0045] In an embodiment, the first network entity 102 is a Network Energy Saving (NES) cell, and each of the one or more second network entities is a Cell A. The first network entity 102 is one of an NES Distributed Unit (DU) and an NES Central Unit (CU), and each of the one or more second network entities is one of a Cell A DUs and Cell A CUs.In an embodiment, the first network entity 102, operating in the first mode, transmits a request message to one or more second network entities, operating in the first mode. The request message may comprise cell access configuration information relating to the first network entity 102. The request message pertains to broadcasting, upon the first network entity 102 transitioning to the second mode, the cell access configuration information to one or more user equipment (UE) associated with the first network entity 102. In an example, the one or more UE, associated with the first network entity, is in an idle state. The cell access configuration information may include information pertaining to a plurality of uplink (UL) wake-up signal (WUS) parameters of the first network entity 102. In an example, the plurality of UL WUS parameters comprises at least one of uplink wake-up signal configuration, uplink wake-up timers, wake-up trigger conditions, access parameters, response configurations, and a scheduled mode of operation. The plurality of wake-up signaling parameters may include wake-up signaling (WUS) configurations necessary for managing transitions in energy-saving modes efficiently. In an example, the one or more second network entities 104 comprises mapping information relating to the first network entity 102. For example, the mapping information comprises a plurality of wake-up signaling parameters of the first network entity 102. In an example, the mapping parameters comprises information of the one or more second network entities 104 in the first mode associated with the first network entity 102. In an embodiment, the mapping information of the first network entity 102 comprises a list of the one or more second network entities 104 corresponding to the first network entity 102. The first network entity 102 maintains the list of the one or more second network entities 104 along with information about a current support for the second mode of the first network entity 102. In an embodiment, the mapping information of each of the one or more second network entities 104 comprises a list of one or more first network entities (not shown) for which the respective second network entity, from the one or more second network entities 104, provides support for the second mode. For example, each of the one or more second network entities 104 maintain the list of the one or more first network entities along with information about a corresponding uplink wake up signal (UL WUS) configurations and a current second mode status of the one or more first network entities. In an example, the request message is transmitted by the first network entity 102 based on a determination that the first network entity 102 is to transition into the second mode.

[0046] In an example, the cell access configuration information includes configurations relevant for energy-saving operations and communication coordination of the first network entity 102. In an example, the request message facilitates seamless configuration, coordination, and optimized operation between the first network entity 102 and the one or more second network entities 104,ensuring efficient resource utilization and effective communication in the network environment 106.

[0047] In an example, the first network entity 102 may receive a response from the at least one of the one or more second network entities 104 based on the request message. In an example, the first network entity 102 may receive a response from the at least one second network entity 104 through NES cell Central Unit (CU). The first network entity 102 may selectively transition into the second mode based on receiving a response in reply to the request message. The response may indicate that at least one of the one or more second network entities 104 is available to support broadcasting of the cell access configuration information to one or more user equipment (UE). In an example, the one or more UE is associated with the first network entity 102.

[0048] In an embodiment, the first network entity 102 receives an indication message based on the request message. For example, the indication message comprises an indication that one or more second network entities 104 are unavailable to support broadcasting of the cell access configuration information to the one or more UE. Subsequently, based on the indication message, the first network entity 102 continues to operate into the first mode.

[0049] In an embodiment, the first network entity 102, upon transitioning into the second mode, based on the response, receives a stoppage of broadcasting intimation message. Further, the first network entity 102 selectively transitions, upon receiving the stop broadcasting intimation message, into the first mode.

[0050] In an embodiment, the stop broadcasting intimation message is indicative that the one or more second network entities 104 are unavailable to support broadcasting of the cell access configuration information to the one or more UE.

[0051] FIG. 2 illustrates an exemplary call flow diagram of indicating positive acknowledgement to support the NES mode of the NES Cell, in accordance with an embodiment of the present disclosure.

[0052] FIG. 2 shows an interaction between an NES Cell (gNB2-DU) 202, an NES Cell (gNB2- Central Unit (CU)) 204, and a Cell A (gNBl-CU) 206. The NES Cell (gNB2-DU) 202 is similar to the first network entity 102, as described in FIG. 1, and the Cell A (gNBl-CU) 206 is similar in structure and function to the one or more second network entities 104, as described in FIG. 1.

[0053] The sequence diagram may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, units, and functions, which perform specific functions or implement specific abstract data types.

[0054] The order in which the steps of the sequence diagram are described are not intended to be construed as a limitation, and any number of the described blocks of the sequence diagram can be combined in any order to implement the method illustrated in the sequence diagram. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method illustrated in the sequence diagram can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0055] Referring to FIG. 2, at S201, the NES Cell (gNB2-DU) 202 (also referred hereinafter as NES cell DU 202) decides to transition to NES mode.

[0056] At step S202, the NES cell DU 202 transmits a NES Activation Request to NES Cell (gNB2-CU) 204 (also referred hereinafter as NES cell CU 204). In an example, the NES Cell ID and Uplink Wake-up signal (UL WUS) configuration.

[0057] At step S203, the NES cell CU 204 transmits an UL WUS config transmission request to the Cell A (gNBl -CU) 206.

[0058] At step S204, the Cell A (gNBl-CU) 206 transmits a UL WUS config transmission Acknowledgement to the NES cell CU 204 indicating that the Cell A (gNBl-CU) 206 is available to transmit the UL WUS Configurations of NES cell DU 202 to the one or more UEs.

[0059] At step S205, the NES cell CU 204 transmits an NES Activation Response to the NES cell DU 202 indicating that the Cell A (gNBl-CU) 206 is available to transmit the UL WUS Configurations of NES cell DU 202 to the one or more UEs.

[0060] At step S206, the Cell A (gNBl-CU) 206 broadcasts UL WUS Configurations of the NES cell DU 202 to the one or more UE.

[0061] At step S207, the NES cell DU 202 activates NES mode.

[0062] At step S208, the NES cell DU 202 transmits an NES Activated Notification to the NES cell CU 204.

[0063] At step S209, the NES cell CU 204 transmits an NES Activated Notification to the Cell A (gNB l-CU) 206.

[0064] FIG. 3 illustrates an exemplary call flow diagram indicating failure message to support the NES mode of the NES Cell, in accordance with an embodiment of the present disclosure.

[0065] FIG. 3 shows an interaction between an NES Cell (gNB2-DU) 202, an NES Cell (gNB2- CU) 204, and a Cell A (gNBl-CU) 206. The NES Cell (gNB2-DU) 202 is similar to the first network entity 102, as described in FIG. 1, and the Cell A (gNBl-CU) 206 is similar in structure and function to the one or more second network entities 104, as described in FIG. 1 .

[0066] The sequence diagram may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, units, and functions, which perform specific functions or implement specific abstract data types.

[0067] The order in which the steps of the sequence diagram are described are not intended to be construed as a limitation, and any number of the described blocks of the sequence diagram can be combined in any order to implement the method illustrated in the sequence diagram. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method illustrated in the sequence diagram can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0068] Referring to FIG. 3, at S301, the NES Cell 202 may decide to transition to NES mode.

[0069] At step S302, the NES cell DU 202 transmits a NES Activation Request to NES Cell (gNB2-CU) 204 (also referred hereinafter as NES cell CU 204). In an example, the NES Cell ID and Uplink Wake-up signal (UL WUS) configuration.

[0070] At step S303, the NES cell CU 204 transmits an UL WUS config transmission request to the Cell A (gNBl-CU) 206.

[0071] At step S304, the Cell A (gNBl-CU) 206 transmits an UL WUS config transmission failure message to the NES cell CU 204 indicating that the Cell A (gNB l-CU) 206 is unavailable to transmit the UL WUS Configurations of NES cell DU 202 to the one or more UEs.

[0072] At step S305, upon receiving the UL WUS config transmission failure message, the NES cell CU 204 may transmit an NES Activation Response indicating that the Cell A (gNBl-CU) 206 is not available to broadcast the UL WUS Configurations of NES cell DU 202 to the one or more UEs.

[0073] At step S306, upon receiving the UL WUS config transmission failure, the NES cell DU 202 does not activate NES mode.

[0074] FIG. 4 illustrates an exemplary call flow diagram of indicating outcome when at least one Cell A responds to the UL WUS Config Transmission Request with a positive acknowledgement, in accordance with an embodiment of the present disclosure.

[0075] FIG. 4 shows an interaction between an NES Cell (gNB2-DU) 202, an NES Cell (gNB2- CU) 204, a Cell A (gNBl-CU) 206, and another Cell A (gNB3-CU) 402.

[0076] The sequence diagram may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs,objects, components, data structures, procedures, units, and functions, which perform specific functions or implement specific abstract data types.

[0077] The order in which the steps of the sequence diagram are described are not intended to be construed as a limitation, and any number of the described blocks of the sequence diagram can be combined in any order to implement the method illustrated in the sequence diagram. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method illustrated in the sequence diagram can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0078] Referring to FIG. 4, at S401, the NES Cell 202 may decide to transition to NES mode.

[0079] At S402, the NES cell DU 202 transmits a NES Activation Request to NES Cell (gNB2- CU) 204 (also referred hereinafter as NES cell CU 204). In an example, the NES Cell ID and Uplink Wake-up signal (UL WUS) configuration.

[0080] At step S403, the NES cell CU 204 transmits an UL WUS config transmission request to the Cell A (gNBl-CU) 206.

[0081] At step S404, the NES cell CU 204 transmits a UL WUS config transmission request to the Cell A (gNB3-CU) 402.

[0082] At step S405, the Cell A (gNB3-CU) 402 transmits a UL WUS config transmission Acknowledgement to the NES cell CU 204 indicating that the Cell A (gNB3-CU) 402 is available to transmit the UL WUS Configurations of NES cell DU 202 to the one or more UEs.

[0083] At step S406, the Cell A (gNB3-CU) 402 broadcasts UL WUS Configurations of the NES cell DU 202 to the one or more UE.

[0084] At step S407, the Cell A (gNBl-CU) 206 transmits a UL WUS config transmission failure message to the NES cell CU 204 indicating that the Cell A (gNB l-CU) 206 is unavailable to transmit the UL WUS Configurations of NES cell DU 202 to the one or more UEs.

[0085] At step S408, the NES cell CU 204 checks if at least one Cell A supports the NES mode of NES cell S408. For example, the NES cell CU 204 checks if at least one of the Cell A (gNBl- CU) 206 or Cell A (gNB3-CU) 402 supports the NES mode of the NES cell DU 202.

[0086] At step S409, the NES cell CU 204 transmits the NES activation response to the NES cell DU 202.

[0087] At step S410, the NES cell DU 202 activates NES mode.

[0088] At step S411, the NES cell DU 202 transmits an NES Activated Notification to the NES cell CU 204.

[0089] At step S412, the NES cell CU 204 transmits an NES Activated Notification to the Cell A (gNBl-CU) 206.

[0090] At step S413, the NES cell CU 204 transmits an NES Activated Notification to the Cell A (gNB3-CU) 402.

[0091] In an example, the NES cell CU 204 may transmit the NES Activated Notification to the Cell A (gNBl-CU) 206 and Cell A (gNB3-CU) 402, simultaneously.

[0092] FIG. 5 illustrates an exemplary call flow diagram of indicating outcome when at least one Cell A responds to the UL WUS Config Transmission Request with a failure message, in accordance with an embodiment of the present disclosure.

[0093] FIG. 5 shows an interaction between an NES Cell (gNB2-DU) 202, an NES Cell (gNB2- CU) 204, a Cell A (gNBl-CU) 206, and another Cell A (gNB3-CU) 402.

[0094] The sequence diagram may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, units, and functions, which perform specific functions or implement specific abstract data types.

[0095] The order in which the steps of the sequence diagram are described are not intended to be construed as a limitation, and any number of the described blocks of the sequence diagram can be combined in any order to implement the method illustrated in the sequence diagram. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method illustrated in the sequence diagram can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0096] Referring to FIG. 5, at S501, the Cell A (gNB3-CU) 402 broadcasts UL WUS Configurations of the NES cell DU 202 to the one or more UE.

[0097] At step S502, the Cell A (gNBl-CU) 206 broadcasts UL WUS Configurations of the NES cell DU 202 to the one or more UE.

[0098] At step S503, the NES cell DU 202 activates the NES mode.

[0099] At step S504, the Cell A (gNBl-CU) 206 transmits a UL WUS config transmission cancel message to NES cell CU 204.

[0100] At step S505, the Cell A (gNBl-CU) 206 stops broadcast of UL WUS configuration of the NES cell DU 202.

[0101] At step S506, the NES cell CU 204 checks if at least one Cell A supports the NES mode of NES cell S408. For example, the NES cell CU 204 checks if at least one of the Cell A (gNBl- CU) 206 or Cell A (gNB3-CU) 402 supports the NES mode of the NES cell DU 202.

[0102] At step S507, the Cell A (gNB3-CU) 402 transmits a UL WUS config transmission cancel message to NES cell CU 204.

[0103] At step S508, the NES cell CU 204 checks if at least one Cell A supports the NES mode of NES cell S408. For example, the NES cell CU 204 checks if at least one of the Cell A (gNBl- CU) 206 or Cell A (gNB3-CU) 402 supports the NES mode of the NES cell DU 202.

[0104] At step S509, the Cell A (gNB3-CU) 402 stops broadcast of UL WUS configuration of the NES cell DU 202.

[0105] At step S510, the NES cell CU 204 sends command to the NES cell DU 202 to deactivate the NES mode, upon determining that none of the cell As are available to support NES mode of the NES Cell 202.

[0106] At step S511, the NES cell DU 202 deactivates the NES mode.

[0107] At step S512, the NES cell DU 202 transmits a NES Deactivation Notification to the NES cell CU 204.

[0108] At step S513, the NES cell CU 204 transmits a NES Deactivation Notification to the Cell A (gNBl-CU) 206.

[0109] At step S514, the NES cell CU 204 transmits a NES Deactivation Notification to the Cell A (gNB3-CU) 402.

[0110] In an example, the NES cell CU 204 may transmit the NES Deactivation Notification to the Cell A (gNBl-CU) 206 and Cell A (gNB3-CU) 402, simultaneously.[OHl] FIG. 6 illustrates an exemplary call flow diagram of indicating change in NES Cell UL WUS configuration, in accordance with an embodiment of the present disclosure.

[0112] FIG. 6 shows an interaction between an NES Cell (gNB2-DU) 202, an NES Cell (gNB2- Central Unit (CU)) 204, and a Cell A (gNBl-CU) 206.

[0113] The sequence diagram may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, units, and functions, which perform specific functions or implement specific abstract data types.

[0114] The order in which the steps of the sequence diagram are described are not intended to be construed as a limitation, and any number of the described blocks of the sequence diagram can be combined in any order to implement the method illustrated in the sequence diagram.Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method illustrated in the sequence diagram can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0115] Referring to FIG. 6, at S601, the Cell A (gNB l-CU) 206 transmits a UL WUS config transmission Acknowledgement to the NES cell CU 204 indicating that the Cell A (gNBl-CU) 206 is available to transmit the UL WUS Configurations of NES cell DU 202 to the one or more UEs..

[0116] At step S602, the NES cell CU 204 sends command to the NES cell DU 202 to activate the NES mode.

[0117] At step S603, the NES cell DU 202 activates NES mode.

[0118] At step S604, the Cell A (gNBl-CU) 206 broadcasts UL WUS Configurations of the NES cell DU 202 to the one or more UE.

[0119] At step S605, the NES cell DU 202 transmits an NES Activated Notification to the NES cell CU 204.

[0120] At step S606, the NES cell CU 204 transmits an NES Activated Notification to the Cell A (gNBl-CU) 206.

[0121] At step S607, the NES cell DU 202 updates the UL WUS Configuration.

[0122] At step S608, the NES cell DU 202 transmits a UL WUS Configuration updated Notification to the NES cell CU 204.

[0123] At step S609, the NES cell CU 204 transmits a UL WUS Configuration updated Notification, received from the NES cell DU 202, to the Cell A (gNBl-CU) 206.

[0124] At step S610, the Cell A (gNBl-CU) 206 broadcasts updated UL WUS Configurations of the NES cell DU 202 to the one or more UE.

[0125] FIGS. 7A-7C illustrate flowcharts of a method for handling OD-SIB1 in the wireless networks, according to the embodiments as disclosed herein.

[0126] As illustrated in FIGS. 7A-7C, the respective methods 700A-700C may comprise one or more steps. The methods 700A-700C may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.

[0127] The order in which the methods 700A-700C are described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order toimplement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0128] Referring to method 700A of FIG. 7A, at step 702A, a request message is transmitted, by a first network entity 102, operating in a first mode, to one or more second network entities 104, operating in the first mode. The request message may comprise cell access configuration information relating to the first network entity 102. For example, the request message pertains to broadcasting, upon the first network entity 102 transitioning to a second mode, the cell access configuration information to one or more user equipment (UE) associated with the first network entity 102. In an example, the one or more UE, associated with the first network entity, is in an idle state. The cell access configuration information may include information pertaining to a plurality of uplink (UL) wake-up signal (WUS) parameters of the first network entity 102. In an example, the plurality of UL WUS parameters comprises at least one of uplink wake-up signal confi uration, uplink wake-up timers, wake-up trigger conditions, access parameters, response configurations, and a scheduled mode of operation. The plurality of wake-up signaling parameters may include wake-up signaling (WUS) configurations necessary for managing transitions in energy-saving modes efficiently. In an example, the one or more second network entities 104 comprises mapping information relating to the first network entity 102. For example, the mapping information comprises a plurality of wake-up signaling parameters of the first network entity 102. In an example, the mapping parameters comprises information of the one or more second network entities 104 in the first mode associated with the first network entity 102. In an embodiment, the mapping information of the first network entity 102 comprises a list of the one or more second network entities 104 corresponding to the first network entity 102. The first network entity 102 maintains the list of the one or more second network entities 104 along with information about a current support for the second mode of the first network entity 102. In an embodiment, the mapping information of each of the one or more second network entities 104 comprises a list of one or more first network entities (not shown) for which the respective second network entity, from the one or more second network entities 104, provides support for the second mode. For example, each of the one or more second network entities 104 maintain the list of the one or more first network entities along with information about a corresponding uplink wake up signal (UL WUS) configurations and a current second mode status of the one or more first network entities. In an example, the request message is transmitted by the first network entity 102 based on a determination that the first network entity is to transition into the second mode.

[0129] In an embodiment, the first network entity 102 is a Network Energy Saving (NES) cell, and each of the one or more second network entities is a Cell A. The first network entity 102 is one of an NES Distributed Unit (DU) and an NES Central Unit (CU), and each of the one or more second network entities is one of a Cell A DUs and Cell A CUs.

[0130] At step 704A, the first network entity 102 may selectively transition, based on receiving a response in reply to the request message, into the second mode. The response indicates that at least one of the one or more second network entities is available to support broadcasting of the cell access configuration information to one or more user equipment (UE). The one or more UE is associated with the first network entity.

[0131] In an embodiment, the stop broadcasting intimation message is indicative that the one or more second network entities 104 are unavailable to support broadcasting of the cell access configuration information to the one or more UE.

[0132] Referring to method 700B of FIG. 7B, at step 702B, the first network entity 102 receives an indication message based on the request message. The indication message comprises an indication that one or more second network entities 104 are unavailable to support broadcasting of the cell access configuration information to the one or more UE.

[0133] At step 704B, upon receiving the indication message that the one or more second network entities 104 are unavailable, the first network entity 102 continues to operate into the first mode based on the indication message.

[0134] Referring to method 700C of FIG. 7C, step 702C indicates about further steps being performed upon transitioning, by the first network entity based on the response, into the second mode

[0135] At step 704C, the first network entity 102 receives a stop broadcasting intimation message.

[0136] At step 706C, upon receiving the stop broadcasting intimation message, the first network entity 102 selectively transitions into the first mode.

[0137] Introduction:

[0138] The Rel-19 WI on enhancements of network energy savings for NR (RP-234065), with the objective to study on-demand SIB 1 for idle / inactive UEs as highlighted below:

[0139] Study procedures and signalling method(s) to support on-demand S1B1 for UEs in idle / inactive mode, including: [RAN1 / 2 / 3]• Triggering method by uplink wake-up-signal using an existing signal / channel.• Wake-up-signal configuration provisioning to UE• Note: No modification of SSB will be discussed under this objective• Information exchange between gNBs at least for the configuration of wake-up signal, if necessary.• Checkpoint for normative work in RAN# 105

[0140] NES activation at the NES cell;

[0141] The NES cell is a cell that may transmit On Demand SIB1 (OD-SIB1) transmission in response to UL WUS from a UE. It need not transmit periodic SIB1 (default transmission) all the time.

[0142] When the NES Cell gNB-DU decides to transition to the NES mode, it sends a NES Activation Request to the NES Cell gNB-DU over F1AP. This request carries the NES Cell ID and the corresponding UL WUS configuration.

[0143] On receiving the request, the NES Cell gNB-CU sends a UL WUS Config Transmission Request to Cell A (as proposed in R3 -247426), and it forwards the response received from Cell A to the NES Cell gNB-DU. If the NES Cell gNB-CU has received a positive acknowledgement from Cell A, then NES Cell gNB-DU can proceed with transitioning to the NES mode. Similarly, if the NES Cell gNB-CU has received a failure response from Cell A, then NES Cell gNB-DU is informed of the same by NES Cell gNB-CU. And in that case, the NES Cell gNB-DU does not transition to the NES mode. This is applicable when there is only one Cell A for the NES Cell.

[0144] Proposal 1: NES Cell gNB-DU decides to transition to the NES mode, and it informs the NES Cell gNB-CU along with NES Cell ID and the corresponding UL WUS Configuration.

[0145] Support for multiple Cell As for a NES Cell and multiple NES Cells for Cell A;

[0146] It has been agreed in the previous meetings of RAN1 / 2, that a single NES Cells can have multiple Cell As and a single Cell A can have multiple NES cells. With this agreement in place, there is a need for NES cell gNB-CU to know the list of Cell As corresponding to the NES cell. And similarly, there is a need for Cell A gNB-CU to have the list of NES cells, their corresponding UL WUS Configurations and their current NES mode status.

[0147] The present subject matter proposes that the 0AM configures to the NES gNB-CU a list of Cell As corresponding to the NES Cell. Furthermore, NES Cell gNB-CU maintains this list along with information about the current support for the NES mode of the NES cell.

[0148] The present subject matter also propose that the 0AM configures to the Cell A gNB-CU a list of NES cells for which is acts as Cell A. Furthermore, Cell A gNB-CU maintains this listalong with information about the corresponding UL WUS configurations and the current NES mode status.

[0149] Observation 1: A single NES Cell can have multiple Cell As associated with it and a single Cell A can have multiple NES cells associated with it.

[0150] Proposal 2: A NES Cell gNB-CU needs to be configured with a list of all Cell As associated with the NES Cell and the Cell A gNB-CU needs to be configured with a list of all NES cells associated with it.

[0151] The behavior of the NES mode activation of the NES cell remains the same as discussed in the above section, if all the Cell As of the NES cell respond similarly to the request of transmitting UL WUS Configuration of the NES Cell.

[0152] The present subject matter proposes that when the NES Cell decides to transition to the NES mode, the NES Cell gNB-CU sends the UL WUS Config Transmission Request to all the Cell As that are corresponding to the NES Cell. Then the NES Cell can transition to the NES mode when at least one of the Cell As corresponding to it has responded with a positive acknowledgement. The present subject matter further proposes that it is the responsibility of NES Cell gNB-CU to monitor if there is support from at least one Cell A for the NES mode of the NES Cell.

[0153] The present subject matter presents the call flow of the outcome when at least one Cell A responds to the UL WUS Config Transmission Request with a positive acknowledgement and at least one Cell A responds to the UL WUS Config Transmission Request with a failure message.

[0154] Proposal 3: The present subject matter proposes that when the NES Cell decides to transition to the NES mode, the NES Cell gNB-CU sends the UL WUS Config Transmission Request to all the Cell As that correspond to the NES Cell. The NES Cell can transition to the NES mode if at least one of the Cell As corresponding to it has responded with a positive acknowledgement.

[0155] Proposal 4: The present subject matter proposes that it is the responsibility of the NES Cell gNB-CU to monitor if there is support from at least one Cell A for the NES mode of the NES Cell.

[0156] The present subject matter presents the call flow of the outcome when at least one Cell A sends a UL WUS Config Transmission Cancel procedure to the NES Cell gNB-CU with the intent to stop broadcasting UL WUS Configuration of the NES cell. The present subject matter proposes that when NES Cell gNB-CU receives a UL WUS Config Transmission Cancel, it checks whether any Cell A currently supports the NES mode of the NES cell. If all Cell As ofthe NES Cell have either sent a failure response for request to transmit the UL WUS configuration, or sent the UL WUS Config Transmission Cancel message, then the NES Cell gNB-CU can deduce that there is no support for NES Cell to continue to operate in the NES mode. In this case, it sends a NES mode deactivation message to the NES Cell gNB-DU.

[0157] Proposal 5: The present subject matter proposes that when all the Cell As corresponding to a NES cell either send a UL WUS Config Transmission failure response to the request for UL WUS Config transmission, or decide to stop broadcasting UL WUS Configuration of the NES Cell and send UL WUS Config Transmission Cancel message to the NES Cell gNB-CU, then the NES gNB-CU sends a Deactivate NES Mode message over F1AP to the NES Cell gNB-DU. Therefore, when even one Cell A continues to support the NES mode of the NES Cell by transmitting UL WUS configuration of the NES cell to its UEs, then the NES Cell can continue to operate in the NES mode. It is the responsibility of the NES Cell gNB-CU to keep track of the support from all the Cell As corresponding to the NES Cell.

[0158] Change in NES Cell UL WUS Configuration:

[0159] If there is any change in the UL WUS configuration at the NES Cell, then NES Cell gNB-DU informs the NES Cell gNB-CU of the update over Fl interface. The updated UL WUS configuration is then sent to Cell A gNB-CU over the Xn interface using UL WUS Configuration Update Notification which is a class 2 procedure. The NES Cell gNB-CU sends the UL WUS Configuration Update procedure to all the Cell As from which it has previously received a positive acknowledgment to support the NES mode of the NES cell, and not received any cancelation of transmission of UL WUS configuration.

[0160] If there is any change in the UL WUS configuration at the NES Cell, then NES Cell gNB-DU informs the NES Cell gNB-CU of the update over Fl interface. The updated UL WUS configuration is then sent to Cell A gNB-CU over the Xn interface.

[0161] Conclusion:

[0162] The present subject matter has the following observations and proposals:

[0163] Proposal 1: NES Cell gNB-DU decides to transition to the NES mode, and it informs the NES Cell gNB-CU along with NES Cell ID and the corresponding UL WUS Configuration.

[0164] Observation 1: A single NES Cell can have multiple Cell As associated with it and a single Cell A can have multiple NES cells associated with it.

[0165] Proposal 2: A NES Cell gNB-CU needs to be configured with a list of all Cell As associated with the NES Cell and the Cell A gNB-CU needs to be configured with a list of all NES cells associated with it.

[0166] Proposal 3: The present subject matter proposes that when the NES Cell decides to transition to the NES mode, the NES Cell gNB-CU sends the UL WUS Config Transmission Request to all the Cell As that correspond to the NES Cell. The NES Cell can transition to the NES mode if at least one of the Cell As corresponding to it has responded with a positive acknowledgement.

[0167] Proposal 4: The present subject matter proposes that it is the responsibility of the NES Cell gNB-CU to monitor if there is support from at least one Cell A for the NES mode of the NES Cell

[0168] Proposal 5: The present subject matter proposes that when all the Cell As corresponding to a NES cell either send a UL WUS Config Transmission failure response to the request for UL WUS Config transmission, or decide to stop broadcasting UL WUS Configuration of the NES Cell and send UL WUS Config Transmission Cancel message to the NES Cell gNB-CU, then the NES gNB-CU sends a Deactivate NES Mode message over F1AP to the NES Cell gNB-DU

[0169] Proposal 6 If there is any change in the UL WUS configuration at the NES Cell, then NES Cell gNB-DU informs the NES Cell gNB-CU of the update over Fl interface. The updated UL WUS configuration is then sent to Cell A gNB-CU over the Xn interface.

[0170] FIG. 8 illustrates an embodiment of a device wherein the method for handling OD-SIB1 in the wireless networks, may be implemented, in accordance with an embodiment of the present disclosure.

[0171] It will be appreciated that the device 800 is associated with the first network entity 102. As shown in FIG. 8, the device 800 includes a processor 810, a memory 820, a storage component 830, an input component 840, an output component 850, a communication interface 860, and a bus 870.

[0172] The processor 810, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 810 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or the like. The processor 810 may be a Central Processing Unit (CPU), a graphics processing unit (GPU),an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.

[0173] The memory 820 includes a non-transitory computer readable medium. Memory 820 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 810. The memory 820 comprises machine-readable instructions which are executable by the processor 810. These machine-readable instructions when executed by the processor 810 cause the processor 810 to perform one or more method steps of an embodiment described above.

[0174] Storage component 830 stores information and / or software related to the operation and use of the device 800. For example, storage component 830 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer- readable medium, along with a corresponding drive.

[0175] Input component 840 is configured to receive information, such as user input. For example, the input component 840 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 840 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0176] Output component 850 is configured to provide output information from the device 800. For example, the output component 850 may be, but not limited to, a display, a speaker, an instruction device to an external device, and / or one or more light-emitting diodes (LEDs).

[0177] Communication interface 860 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 860 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the device 800 and other devices. In other words, the standard of the communication interface 860 is not limited.

[0178] The bus 870 acts as an interconnect between the processor 810, the memory 820, the storage component 930, the input component 840, the output component 850, and the communication interface 860 of the device 800. The bus 870 may include a wired interconnection or a wireless interconnection.

[0179] The number and arrangement of components shown in FIG. 8 are provided as an example. In practice, device 800 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 8. Additionally, or alternatively, a set of components (e.g., one or more components) of device 800 may perform one or more functions described as being performed by another set of components of device 800. Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of devices 800 in communication with one another.

[0180] In an embodiment [1], a method comprising: transmitting, by a first network entity, operating in a first mode, to one or more second network entities, operating in the first mode, a request message, wherein the request message comprises cell access configuration information relating to the first network entity; and selectively transitioning, by the first network entity, based on receiving a response in reply to the request message, into the second mode, wherein the response indicates that at least one of the one or more second network entities is available to support broadcasting of the cell access configuration information to one or more user equipment (UE), wherein the one or more UE is associated with the first network entity.

[0181] In an embodiment [2], in the method, described in the embodiment [1], wherein the request message pertains to broadcasting, upon the first network entity transitioning to a second mode, the cell access configuration information to one or more user equipment (UE) associated with the first network entity, and wherein the transmitting of the request message is based on a determination that the first network entity is to transition into the second mode.

[0182] In an embodiment [3], in the method, described in the embodiment [1], further comprises: receiving, by the first network entity, an indication message based on the request message, wherein the indication message comprises an indication that one or more second network entities are unavailable to support broadcasting of the cell access configuration information to the one or more UE; and continuing, by the first network entity based on the indication message, to operate into the first mode.

[0183] In an embodiment [4], in the method, described in the embodiment [1], further comprises: upon transitioning, by the first network entity based on the response, into the second mode, receiving, by the first network entity, a stop broadcasting intimation message; and selectively transitioning, by the first network entity upon receiving the stop broadcasting intimation message, into the first mode.

[0184] In an embodiment [5], in the method, described in the embodiment [1], wherein the each of the first network entity, and each of the one or more second network entities comprise mappinginformation relating to the one or more second network entry and the first network entity, respectively, wherein, the mapping information of the first network entity comprises: a list of the one or more second network entities corresponding to the first network entity, wherein the first network entity maintains the list of the one or more second network entities along with information about a current support for the second mode of the first network entity; and the mapping information of each of the one or more second network entities comprises: a list of one or more first network entities for which the respective second network entity, from the one or more second network entities, provides support for the second mode, wherein each of the one or more second network entities maintain the list of the one or more first network entities along with information about a corresponding uplink wake up signal (UL WUS) configurations and a current second mode status of the one or more first network entities.

[0185] In an embodiment [6], in the method, described in the embodiment [4], wherein the stop broadcasting intimation message is indicative that the one or more second network entities are unavailable to support broadcasting of the cell access configuration information to the one or more UE.

[0186] In an embodiment [7], in the method, described in the embodiment [1], wherein the first network entity is a Network Energy Saving (NES) cell, and each of the one or more second network entities is a Cell A.

[0187] In an embodiment [8], in the method, described in the embodiment [1], wherein the first network entity is one of a Network Energy Saving (NES) Distributed Unit (DU) and an NES Central Unit (CU), and each of the one or more second network entities is one of a Cell A DUs and Cell A CUs.

[0188] In an embodiment [9], in the method, described in the embodiment [1], wherein the one or more UE, associated with the first network entity, is in an idle state.

[0189] In an embodiment

[0010] , in the method, described in the embodiment [1], wherein the cell access configuration information comprises of: a plurality of uplink (UL) wake-up signal (WUS) parameters, wherein the plurality of UL WUS parameters comprises at least one of uplink wakeup signal configuration, uplink wake-up timers, wake-up trigger conditions, access parameters, response configurations, and a scheduled mode of operation.

[0190] In an embodiment

[0011] , an apparatus is configured to: transmit, by a first network entity, operating in a first mode, to one or more second network entities, operating in the first mode, a request message, wherein the request message comprises cell access configuration information relating to the first network entity; and selectively transition, by the first network entity based onreceiving a response in reply to the request message, into the second mode, wherein the response indicates that at least one of the one or more second network entities is available to support broadcasting of the cell access configuration information to one or more user equipment (UE), wherein the one or more UE is associated with the first network entity.

[0191] In an embodiment

[0012] , in the apparatus, described in the embodiment

[0011] , wherein the request message pertains to broadcasting, upon the first network entity transitioning to a second mode, the cell access configuration information to one or more user equipment (UE) associated with the first network entity, and wherein the transmitting of the request message is based on a determination that the first network entity is to transition into the second mode.

[0192] In an embodiment

[0013] , in the apparatus, described in the embodiment

[0011] , further configured to: receive, by the first network entity, an indication message based on the request message, wherein the indication message comprises an indication that one or more second network entities are unavailable to support broadcasting of the cell access configuration information to the one or more UE; and continue, by the first network entity based on the indication message, to operate into the first mode.

[0193] In an embodiment

[0014] , in the apparatus, described in the embodiment

[0011] , further configured to: upon transitioning, by the first network entity based on the response, into the second mode, receive, by the first network entity, a stop broadcasting intimation message; and selectively transition, by the first network entity upon receiving the stop broadcasting intimation message, into the first mode.

[0194] In an embodiment

[0015] , in the apparatus, described in the embodiment

[0011] , wherein the each of the first network entity, and each of the one or more second network entities comprise mapping information relating to the one or more second network entry and the first network entity, respectively, wherein, the mapping information of the first network entity comprises: a list of the one or more second network entities corresponding to the first network entity, wherein the first network entity maintains the list of the one or more second network entities along with information about a current support for the second mode of the first network entity; and the mapping information of each of the one or more second network entities comprises: a list of one or more first network entities for which the respective second network entity, from the one or more second network entities, provides support for the second mode, wherein each of the one or more second network entities maintain the list of the one or more first network entities along with information about a corresponding uplink wake up signal (UL WUS) configurations and a current second mode status of the one or more first network entities.

[0195] In an embodiment

[0016] , in the apparatus, described in the embodiment

[0014] , wherein the stop broadcasting intimation message is indicative that the one or more second network entities are unavailable to support broadcasting of the cell access configuration information to the one or more UE.

[0196] In an embodiment

[0017] , in the apparatus, described in the embodiment

[0011] , wherein the first network entity is a Network Energy Saving (NES) cell, and each of the one or more second network entities is a Cell A.

[0197] In an embodiment

[0018] , the apparatus, described in the embodiment

[0011] , wherein the one or more UE, associated with the first network entity, is in an idle state.

[0198] In an embodiment

[0019] , in the apparatus, described in the embodiment

[0011] , wherein the cell access configuration information comprises of: a plurality of uplink (UL) wake-up signal (WUS) parameters, wherein the plurality of UL WUS parameters comprises at least one of uplink wake-up signal configuration, uplink wake-up timers, wake-up trigger conditions, access parameters, response configurations, and a scheduled mode of operation.

[0199] In an embodiment

[0020] , a non-transitory computer-readable medium having program instructions stored thereon, executed by an apparatus for wireless communication, is disclosed. The program instructions may comprise: transmitting, by a first network entity, operating in a first mode, to one or more second network entities, operating in the first mode, a request message, wherein the request message comprises cell access configuration information relating to the first network entity; and selectively transitioning, by the first network entity, based on receiving a response in reply to the request message, into a second mode, wherein the response indicates that at least one of the one or more second network entities is available to support broadcasting of the cell access configuration information to one or more user equipment (UE), wherein the one or more UE is associated with the first network entity.

[0200] In a non-limiting embodiment of the present disclosure, one or more non-transitory computer-readable media may be utilized for implementing the embodiments consistent with the present disclosure. A computer-readable medium refers to any type of physical memory (such as memory 820) on which information or data readable by a processor may be stored. Thus, a computer-readable media may store one or more instructions for execution by the at least one processor 810, including instructions for causing the at least one processor 810 to perform steps or stages consistent with the embodiments described herein. The term “computer-readable media” should be understood to include tangible items and exclude carrier waves and transient signals. By way of example, and not limitation, such computer-readable media can compriseRandom Access Memory (RAM), Read-Only Memory (ROM), volatile memory, non-volatile memory, hard drives, Compact Disc (CD) ROMs, Digital Video Disc (DVDs), flash drives, disks, and any other known physical storage media.

[0201] Thus, certain aspects may comprise a computer program product for performing the operations presented herein. For example, such a computer program product may comprise a computer readable media having instructions stored (and / or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein. For certain aspects, the computer program product may include packaging material.

[0202] The various illustrative logical blocks, units, and operations described in connection with the present disclosure may be implemented or performed with a general-purpose processor, discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein. A general-purpose processor may include a microprocessor, but in the alternative, the processor may include any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a plurality of microprocessors, or any other such configuration.

[0203] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

We Claim:

1. A method comprising: transmitting, by a first network entity, operating in a first mode, to one or more second network entities, operating in the first mode, a request message, wherein the request message comprises cell access configuration information relating to the first network entity; and selectively transitioning, by the first network entity, based on receiving a response in reply to the request message, into a second mode, wherein the response indicates that at least one of the one or more second network entities is available to support broadcasting of the cell access configuration information to one or more user equipment (UE), wherein the one or more UE is associated with the first network entity.

2. The method as claimed in claim 1, wherein the request message pertains to broadcasting, upon the first network entity transitioning to the second mode, the cell access configuration information to one or more user equipment (UE) associated with the first network entity, and wherein the transmitting of the request message is based on a determination that the first network entity is to transition into the second mode.

3. The method as claimed in claim 1, further comprises: receiving, by the first network entity, an indication message based on the request message, wherein the indication message comprises an indication that one or more second network entities are unavailable to support broadcasting of the cell access configuration information to the one or more UE; and continuing, by the first network entity based on the indication message, to operate into the first mode.

4. The method as claimed in claim 1, further comprises: upon transitioning, by the first network entity based on the response, into the second mode, receiving, by the first network entity, a stoppage broadcasting intimation message; and selectively transitioning, by the first network entity upon receiving the stoppage of broadcasting intimation message, into the first mode.

5. The method as claimed in claim 1, wherein the each of the first network entity, and each of the one or more second network entities comprise mapping information relating to the one or more second network entry and the first network entity, respectively, wherein, the mapping information of the first network entity comprises: a list of the one or more second network entities corresponding to the first network entity, wherein the first network entity maintains the list of the one or more second network entities along with information about a current support for the second mode of the first network entity; and the mapping information of each of the one or more second network entities comprises: a list of one or more first network entities for which the respective second network entity, from the one or more second network entities, provides support for the second mode, wherein each of the one or more second network entities maintain the list of the one or more first network entities along with information about a corresponding uplink wake up signal (UL WUS) configurations and a current second mode status of the one or more first network entities.

6. The method as claimed in claim 4, wherein the stop broadcasting intimation message is indicative that the one or more second network entities are unavailable to support broadcasting of the cell access configuration information to the one or more UE.

7. The method as claimed in claim 1 , wherein the first network entity is a Network Energy Saving (NES) cell, and each of the one or more second network entities is a Cell A.

8. The method as claimed in claim 1, wherein the first network entity is one of a Network Energy Saving (NES) Distributed Unit (DU) and an NES Central Unit (CU), and each of the one or more second network entities is one of a Cell A DUs and Cell A CUs.

9. The method as claimed in claim 1, wherein the one or more UE, associated with the first network entity, is in an idle state.

10. The method as claimed in claim 1, wherein the cell access configuration information comprises of: a plurality of uplink (UL) wake-up signal (WUS) parameters, wherein the plurality of UL WUS parameters comprises at least one of uplink wake-up signal configuration, uplink wake-up timers,wake-up trigger conditions, access parameters, response configurations, and a scheduled mode of operation.

11. An apparatus configured to: transmit, by a first network entity, operating in a first mode, to one or more second network entities, operating in the first mode, a request message, wherein the request message comprises cell access configuration information relating to the first network entity; and selectively transition, by the first network entity based on receiving a response in reply to the request message, into a second mode, wherein the response indicates that at least one of the one or more second network entities is available to support broadcasting of the cell access configuration information to one or more user equipment (UE), wherein the one or more UE is associated with the first network entity.

12. The apparatus as claimed in claim 11, wherein the request message pertains to broadcasting, upon the first network entity transitioning to the second mode, the cell access configuration information to one or more user equipment (UE) associated with the first network entity, and wherein the transmitting of the request message is based on a determination that the first network entity is to transition into the second mode.

13. The apparatus as claimed in claim 11, further configured to: receive, by the first network entity, an indication message based on the request message, wherein the indication message comprises an indication that one or more second network entities are unavailable to support broadcasting of the cell access configuration information to the one or more UE; and continue, by the first network entity based on the indication message, to operate into the first mode.

14. The apparatus as claimed in claim 11, further configured to: upon transitioning, by the first network entity based on the response, into the second mode, receive, by the first network entity, a stop broadcasting intimation message; and selectively transition, by the first network entity upon receiving the stop broadcasting intimation message, into the first mode.

15. The apparatus as claimed in claim 11, wherein the each of the first network entity, and each of the one or more second network entities comprise mapping information relating to the one or more second network entry and the first network entity, respectively, wherein, the mapping information of the first network entity comprises: a list of the one or more second network entities corresponding to the first network entity, wherein the first network entity maintains the list of the one or more second network entities along with information about a current support for the second mode of the first network entity; and the mapping information of each of the one or more second network entities comprises: a list of one or more first network entities for which the respective second network entity, from the one or more second network entities, provides support for the second mode, wherein each of the one or more second network entities maintain the list of the one or more first network entities along with information about a corresponding uplink wake up signal (UL WUS) configurations and a current second mode status of the one or more first network entities.

16. The apparatus as claimed in claim 14, wherein the stop broadcasting intimation message is indicative that the one or more second network entities are unavailable to support broadcasting of the cell access configuration information to the one or more UE.

17. The apparatus as claimed in claim 11, wherein the first network entity is a Network Energy Saving (NES) cell, and each of the one or more second network entities is a Cell A.

18. The apparatus as claimed in claim 11, wherein the one or more UE, associated with the first network entity, is in an idle state.

19. The apparatus as claimed in claim 11, wherein the cell access configuration information comprises of: a plurality of uplink (UL) wake-up signal (WUS) parameters, wherein the plurality of UL WUS parameters comprises at least one of uplink wake-up signal configuration, uplink wake-up timers, wake-up trigger conditions, access parameters, response configurations, and a scheduled mode of operation.

20. A non-transitory computer-readable medium having program instructions stored thereon, executed by an apparatus for wireless communication, for: transmitting, by a first network entity, operating in a first mode, to one or more second network entities, operating in the first mode, a request message, wherein the request message comprises cell access configuration information relating to the first network entity; and selectively transitioning, by the first network entity, based on receiving a response in reply to the request message, into a second mode, wherein the response indicates that at least one of the one or more second network entities is available to support broadcasting of the cell access configuration information to one or more user equipment (UE), wherein the one or more UE is associated with the first network entity.

Images