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

Abstract

Embodiments disclosed herein provide a method and system for performing procedures to support on demand – system information block type-1 (OD-SIB1). The present disclosure comprises a new class 1 procedure which may be initiated by NES Cell towards Cell A to request the broadcast of the UL WUS Configuration. The method involves transmitting, by NES Cell, operating in a first mode, to at least one Cell A, operating in first mode, a request message. The request message comprises setup configuration information relating to the NES cell. The request message pertains to broadcasting, upon first network entity transitioning to a second mode, setup configuration information to one or more user equipment (UE) associated with the Cell A. Further, NES cell receives a response based on the request message from the Cell A. Furthermore, NES cell selectively transitioning into the second mode based on the response.

Description

PROCEDURES TO SUPPORT ON DEMAND - SYSTEM INFORMATION BLOCKTYPE-1 (OD-SIB1)CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to India Provisional Patent Application No. 202441086281, filed on November 8, 2024, and India Non-Provisional Patent Application No. 202441086281, 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).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] Deployment of fifth generation (5G) networks presents significant challenges regarding energy efficiency. With networks becoming denser and requiring more antennas, wider bandwidths, and additional frequency bands to support advanced services like extended reality (XR), the demand for energy has escalated. Effectively managing this energy consumption is essential not only to mitigate environmental impact but also to optimize operational costs associated with running these networks efficiently. Finding solutions to enhance energy efficiency in this context is paramount for ensuring sustainable growth and minimizing the ecological footprint of 5G infrastructure.

[0005] Cells associated with the Network Energy Saving (NES) features (also termed as NES cells) stay in dormant state or sleep state to save energy. The NES cells stay in a dormant state until a wake-up signal is received. Existing technologies provide on-demand SIB1 (OD-SIB1) transmission by enabling NES cells to selectively broadcast SIB1 based on specific UE triggers via uplink wake-up signals (UL WUS) using existing channels. The NES cells transmit SystemInformation Blockl (SIB1) to the user terminals on receiving the wake-up signal. Therefore, in existing methods OD-SIB1 is specifically requested by UEs in IDLE / INACTIVE mode on an individual basis. The configuration details for OD-SIB1 transmission, such as frequency of OD- SIB1, SIB 1 burst parameters, burst pattern, duration, etc., are configuration details available in the wake-up signal (WUS) configuration obtained by the UE from either the anchor cell (Cell A) or the NES cell. These configuration details may be changed at any time by the NES cell.SUMMARY

[0006] Typically, when a first network entity decides to transition to a first mode, for example NES mode, it needs the support of the neighboring network entities like second network entity. However, if there is no coordination between the first network entity, and the second network entity this could lead to inefficient energy utilization. The present disclosure relates to a method comprising the steps of transmitting, by a first network entity, operating in a first mode, to at least one second network entity, operating in the first mode, a request message. The request message comprises setup configuration information relating to the first network entity. The request message pertains to broadcasting, upon the first network entity transitioning to a second mode, the setup configuration information to one or more user equipment (UE) associated with the second network entity. Further, the first network entity receives, from the at least one second network entity, a response based on the request message. Furthermore, the method comprises selectively transitioning, by the first network entity based on the response, into the second mode.

[0007] The present disclosure also relates to an apparatus configured to transmit, by a first network entity, operating in a first mode, to at least one second network entity, operating in the first mode, a request message. The request message comprises setup configuration information relating to the first network entity. The request message pertains to broadcasting, upon the first network entity transitioning to a second mode, the setup configuration information to one or more user equipment (UE) associated with the second network entity. The apparatus is also configured to receive, by the first network entity from the at least one second network entity, a response based on the request message. The apparatus is further configured to selectively transition, by the first network entity based on the response, into the second mode.

[0008] 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 at least one second network entity, operating in the first mode, a request message. Therequest message comprises setup configuration information relating to the first network entity. The request message pertains to broadcasting, upon the first network entity transitioning to a second mode, the setup configuration information to one or more user equipment (UE) associated with the second network entity. Further, the first network entity receives, from the at least one second network entity, a response based on the request message. Furthermore, the at least one processor also performs operations of selectively transitioning, by the first network entity based on the response, into the second mode.

[0009] 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

[0010] 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:

[0011] 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-S1B 1) by relevant Cell A in wireless communication networks, in accordance with some embodiments of the present disclosure.

[0012] FIG. 2 illustrates an exemplary call flow diagram of managing communication between NES cell and Cell A in case of a successful operation of transition to NES mode by the NES Cell, in accordance with an embodiment of the present disclosure.

[0013] FIG. 3 illustrates an exemplary call flow diagram of managing communication between NES cell and Cell A in case of an unsuccessful operation of transition to NES mode by the NES Cell, in accordance with an embodiment of the present disclosure.

[0014] FIG. 4 illustrates an exemplary call flow diagram of managing communication between NES cell and Cell A in case of a deactivation of NES Mode triggered by the NES Cell, in accordance with an embodiment of the present disclosure.

[0015] FIG. 5 illustrates an exemplary call flow diagram of managing communication between NES cell and Cell A in case of a deactivation of NES Mode triggered by the Cell A, in accordance with an embodiment of the present disclosure.

[0016] FIG. 6 illustrates a flowchart of a method for managing triggering of activation and deactivation of the NES mode of the NES cell, according to the embodiments as disclosed herein.

[0017] FIG. 7 illustrates an embodiment of a device wherein the method for managing triggering of activation and deactivation of the NES mode of the NES cell, may be implemented, in accordance with an embodiment of the present disclosure.

[0018] 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 DESCRIPTON

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

[0020] 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).

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

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

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

[0024] 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 operates in a low-power or sleep mode during periods of low network usage, reducing energy usage without compromising the overall network performance. The NES cell offers enhanced capabilities and features compared to traditional cells, enabling improved performance, capacity, and quality of service. 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.

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

[0026] UL WUS Configuration from NES Cell to Cell A

[0027] It is known that the uplink wake-up signal (UL WUS) configuration may be decided by the NES Cell gNB -Distributed Unit (DU), and it may send the UL WUS Configuration to the NES Cell gNB-Central Unit (CU) and that may be forwarded to Cell A gNB-CU. It is also known that the UL WUS Configuration may be transmitted over Xn interface using a new class 1 procedure. The present disclosure proposes the new class 1 procedure to follow the design principles of the existing basic procedures defined in 38.423, which is as follows:

[0028] UL WUS Config Transmission:

[0029] When a source Next Generation Radio Access Network (NG RAN) node may decide to transition to a NES mode, it may need the support of the neighboring NG RAN nodes. The source NG RAN (NES Cell) node may send its UL WUS Configuration to the target NG RAN (Cell A) node to broadcast to User Equipment (UE) in IDLE / INACTIVE state in the target NG RAN node. This makes the NES NG RAN node discoverable by the UEs in the target NG RAN node. The procedure of the present disclosure may use non-UE-associated signaling.

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

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

[0032] 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. According to an embodiment of the present disclosure, the second network entity 104 may be a cell A in the non-energy saving mode.

[0033] 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 setupconfiguration 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 setup configuration information to one or more user equipment (UE) (not shown) associated with the second network entity 104. 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. In some embodiment, the first network entity 102 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 first network entity 102 may be a centralized network controller for managing communication, synchronization, and dynamic configuration of mapping information and wake-up signaling parameters across network entities.

[0034] The second network entity 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 second network entity 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. In some embodiment, the second network entity 104 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.

[0035] 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 second network entity 104 for supporting the UE for seamless operation of the communication network 106, as disclosed in the present disclosure.

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

[0037] In an embodiment, the first network entity 102, operating in the first mode, transmits a request message to at least one second network entity 104, operating in the first mode. Therequest message may comprise setup 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 setup configuration information to one or more user equipment (UE) associated with the second network entity 104. In an example, the one or more UE, associated with the second network entity 104, is in an idle state. The setup 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 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.

[0038] In an example, the setup 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 second network entity 104, ensuring efficient resource utilization and effective communication in the network environment 106.

[0039] In an example, the first network entity 102 may receive a response from the at least one second network entity 104 based on the request message. Upon receiving the response, the first network entity 102 may selectively transition into the second mode based on the response.

[0040] In an embodiment, the response comprises a first response and a second response. In an example, upon receiving the first response, the first network entity 102 transitions from the first mode into the second mode. For example, the first response is indicative of availability of the at least one second network entity 104 for broadcasting the setup configuration information. In an example, upon receiving the second response, the first network entity 102 continues operating in the first mode. For example, the second response is indicative of unavailability of the at least one second network entity 104 for broadcasting the setup configuration information.

[0041] In an embodiment, upon the first network entity 102 transitioning into the second mode, the first network entity 102 receives, from the at least one second network entity 104, a stop broadcasting intimation message. Further, the first network entity 102 selectively transitions into the first mode upon receiving the stop broadcasting intimation message.

[0042] In an embodiment, upon receiving the stop broadcasting intimation message, the first network entity 102 continues to operate in the second mode, upon receiving the first response from one of the at least one second network entity 104.

[0043] In an embodiment, upon transitioning into the second mode, the first network entity 102 determines a requirement to transition into the first mode from the second mode. Further, the first network entity 102, operating in the second mode, transmits, to the at least one second network entity 104, a stop broadcasting request message pertaining to stopping the broadcasting of the setup configuration information to the one or more user equipment (UE). Upon transmitting the stop broadcasting request message, the first network entity 102 transitions into the first mode.

[0044] At the RAN3 125 meeting, the following was agreed:

[0045] Case 2 can be supported with the below details:• UL WUS configuration is decided by NES Cell DU.• UL WUS configuration transmission from NES Cell DU to NES Cell CU. NES gNB-CU sends UL WUS configuration to Cell A gNB-CU over Xn Interface.• Upon the reception of the UL WUS configuration, Cell A can provide feedback to NES Cell on whether the WUS configuration Transmission for NES Cell is accepted in Cell A (e.g., confirm, reject).

[0046] FFS if Cell A broadcasts it right away or not.

[0047] From RAN3#125-bis, the following agreements are provided for On Demand S1B1 :• The UL WUS configuration will be transferred over Xn via a new class 1 defined procedure.• Cell A gNB can decide and signal to NES Cell gNB that it stops the UL WUS configuration broadcast in its SIB.

[0048] UL WUS Configuration from NES Cell to Cell A:

[0049] It has been agreed in the previous meetings that the UL WUS Configuration is decided by the NES Cell gNB-DU, and it sends the UL WUS Configuration to the NES Cell gNB-CU and that is forwarded to Cell A gNB-CU. It has also been agreed that the UL WUS Configuration will be transmitted over Xn using a new class 1 procedure. The present subject matter proposes the new class 1 procedure to follow the design principles of the existing basic procedures defined in 38.423.

[0050] UL WUS Config Transmission:

[0051] When a source NG RAN node decides to transition to a NES mode, it needs the support of the neighboring NG RAN nodes. The source NG RAN node sends its UL WUS Configuration to the target NG RAN node to broadcast to UEs in IDLE / INACTIVE state in the target NG RAN node. This makes the NES NG RAN node discoverable by the UEs in the target NG RAN node. The procedure uses non-UE-associated signalling.

[0052] Fig. 2 refers to a Successful Operation. As per Fig. 2, UL WUS Config Transmission Request procedure is used by source NG RAN node (NES Cell) to determine whether the target NG RAN node (Cell A) is willing to broadcast UL WUS Configuration to the UEs camped on the target NG RAN node (Cell A gNB). If the target NG RAN node is willing to the transmit the UL WUS Configuration of the source NG RAN node, it responds with UL WUS Config Transmission Acknowledgement.

[0053] Fig. 3 refers to an Unsuccessful Operation. As per Fig. 3, if the target NG RAN node (Cell A) is unable or unwilling to broadcast UL WUS Configuration to the UEs camped on the target NG RAN node, the target NG-RAN node shall send the UL WUS CONFIGURATION TRANSMISSION FAILURE message to the source NG-RAN node.

[0054] NES Mode Update of NES Cell to Cell A:

[0055] When the NES Cell receives a UL WUS Config Transmission Acknowledgement, there is no guarantee that it will transition to the NES mode. The actual execution of transitioning to NES mode depends on the logic implemented at the NES gNB-DU.

[0056] However, it is important for Cell A to know whether the NES Cell has actually transitioned to the NES mode or not.

[0057] One, Cell A can stop broadcasting the UL WUS Config to the UEs camped on it if NES Cell has not transitioned to the NES mode. Secondly, if Cell A decides to top supporting the NES mode of the NES cell, then it can send the UL WUS Transmission Cancel to the NES cell (If the NES cell is in the NES mode), otherwise this signal may be avoided.

[0058] For accurate bookkeeping, the present subject matter proposes that any time the NES cell activates or deactivates the NES mode, it sends a class 2 procedure to Cell A to inform of its current NES status.

[0059] Proposal: RAN3 to agree on the new class 2 procedure initiated by the NES Cell towardsCell A to indicate the latest NES state of the NES cell whenever NES mode is activated ordeactivated. The NES Cell sends this message to all the Cell A’s. It is configured with irrespective of whether a given Cell A is supporting the NES mode of the NES Cell or not.

[0060] Activation / Deactivation of NES mode:

[0061] In RAN3#125-bis, it was agreed that Cell A gNB can decide and signal to NES Cell gNB that it wants to stop the UL WUS configuration broadcast in its SIB.

[0062] Based on the agreement, it is stated that:• NES Cell can decide when to start / stop NES mode.• Cell A can decide when to start / stop broadcasting UL WUS Configuration of the NES Cell

[0063] Observation 1 : The trigger to activate NES mode of a NES cell comes from NES Cell only. The trigger to deactivate NES mode of a NES cell can come from either NES Cell or Cell A.

[0064] This leads us to the following possible scenarios:• Scenario la: Activation of NES mode triggered by NES Cell and supported by Cell A• Scenario lb: Deactivation of NES mode triggered by NES Cell

[0065] In this case, the NES Cell sends a UL WUS Config Transmission Stop procedure to the target NG RAN node. On receiving this, the target NG RAN node may stop broadcasting the UL WUS configuration of the source NG RAN node to the UEs camped on target NG RAN node.• Scenario 2a: Activation of NES mode triggered by NES Cell and supported by Cell A• Scenario 2b: Deactivation of NES mode triggered by Cell A: Cell A stops broadcasting UL WUS Configuration; therefore, the NES Cell is forced to transition out of NES mode

[0066] In this case, the source NG RAN node decides to stop the transmission of the UL WUS Configuration of the target NG RAN node. The source NG RAN node sends a UL WUS Config Transmission Cancel procedure to the target NG RAN node. On receiving this procedure, the target NG RAN node may choose to transition out of the NES mode.

[0067] It is possible that one Cell A has stopped broadcasting the UL WUS configuration of the NES Cell, but another Cell A continues to broadcast the UL WUS configuration of the NES. Itis up to the implementation at the NES Cell to decide when and under what conditions it should deactivate the NES mode after receiving the UL WUS Configuration Transmission Cancel from a Cell A.

[0068] Conclusion:

[0069] The present subject matter have the following observations and proposals:• Proposal 1: RAN3 to agree on the new class 1 procedure initiated by the NES Cell towards Cell A to request the broadcast of its UL WUS Configuration.• Observation 1: The trigger to activate NES mode of a NES cell comes from NES Cell only. The trigger to deactivate NES mode of a NES cell can come from either NES Cell or Cell A.• Proposal 2: RAN3 to agree on the new class 2 procedure initiated by the NES Cell towards Cell A to stop the broadcast of its UL WUS Configuration.• Proposal 3: RAN3 to agree on the new class 1 procedure initiated by Cell A towards NES Cell to indicate its cancelation of the broadcast of the UL WUS Configuration of the NES Cell.

[0070] FIG. 2 illustrates an exemplary call flow diagram 200 of managing communication between NES cell 202 and Cell A 204 (successful operation of transition to NES mode by NES Cell), in accordance with an embodiment of the present disclosure.

[0071] FIG. 2 shows an interaction between an NES Cell (gNB2) 202 and a Cell A (gNBl) 204. The NES Cell (gNB2) 202 (also referred hereinafter as the NES cell 202) is similar to the first network entity 102, as described in FIG. 1, and Cell A (gNBl) 204 (also referred hereinafter as Cell A 204) is similar in structure and function to the second network entity 104, as described in FIG. 1.

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

[0073] 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. Referring to FIG. 2, at S201, the NES Cell 202 may decide to transition to the NES mode.

[0074] At S202, UL WUS Config Transmission Request procedure may be used by source NG RAN node (NES Cell (gNB2) 202) to determine whether the target NG RAN node (Cell A (gNBl) 204) is willing to broadcast UL WUS Configuration to the UEs (not shown) camped on the target NG RAN node (Cell A (gNBl) 204).

[0075] At step S203, if the Cell A (gNBl) 204 is willing to the transmit the UL WUS Configuration of the NES Cell (gNB2) 202, it may respond with UL WUS Config Transmission Acknowledgement.

[0076] Upon receiving the UL WUS Config Transmission Acknowledgement, the NES Cell (gNB2) 202 may transition into an NES mode.

[0077] FIG. 3 illustrates an exemplary call flow diagram 300 of managing communication between NES cell 202 and Cell A 204 in case of an unsuccessful operation of transition to NES mode by the NES Cell 202, in accordance with an embodiment of the present disclosure.

[0078] FIG. 3 shows an interaction between the NES Cell (gNB2) 202 (also referred hereinafter as the NES cell 202) and the Cell A (gNBl) 204 (also referred hereinafter as the Cell A 204).

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

[0080] 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. Referring to FIG. 3, at S301, the NES Cell 202 may decide to transition to NES mode.

[0081] At S302, UL WUS Config Transmission Request procedure may be used by the NES Cell 202 to determine whether the Cell A 204 is willing to broadcast UL WUS Configuration to the UEs (not shown) camped on the Cell A 204.

[0082] At step S303, if the Cell A 204 is unable or unwilling to broadcast the UL WUS Configuration of the NES Cell 202, to the UEs camped on the Cell A 204, the Cell A 204 shall send the UL WUS configuration transmission failure message to the NES Cell 202. In one nonlimiting embodiment, the above message may comprise an information element (IE).

[0083] Upon receiving the UL WUS configuration transmission failure message, the NES Cell 202 may continue operating in an active state and refrain from transitioning into an NES mode.

[0084] Thus, as mentioned above, the new class 1 procedure, as disclosed in the present disclosure, may be initiated by the NES Cell 202 towards the Cell A 204 to request the broadcast of its UL WUS Configuration.

[0085] Activation / Deactivation of NES mode:

[0086] As per RAN3#125-bis, the Cell A gNB (the Cell A 204) can decide and signal to NES Cell gNB (the NES Cell 202) that it wants to stop the UL WUS configuration broadcast in its SIB.

[0087] Based on the above agreement, the following observation is made:• NES Cell can decide when to start / stop NES mode.• Cell A can decide when to start / stop broadcasting UL WUS Configuration of the NES Cell.

[0088] Observation: The trigger to activate NES mode of a NES cell may come from NES Cell only. The trigger to deactivate NES mode of a NES cell can come from either NES Cell or Cell A.

[0089] The above observation leads to the following possible scenarios:• Scenario la: Activation of NES mode triggered by NES Cell and supported by Cell A.• Scenario lb: Deactivation of NES mode triggered by NES Cell.

[0090] FIG. 4 illustrates an exemplary call flow diagram 400 of managing communication between NES cell 202 and Cell A 204 in case of a deactivation of NES Mode triggered by the NES Cell, in accordance with an embodiment of the present disclosure.

[0091] FIG. 4 shows an interaction between the NES Cell (gNB2) 202 (also referred hereinafter as the NES cell 202) and the Cell A (gNBl) 204 (also referred hereinafter as the Cell A 204).

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

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

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

[0095] At S402, UL WUS Config Transmission Request procedure may be used by the NES Cell 202 to determine whether the Cell A 204 is willing to broadcast UL WUS Configuration to the UEs (not shown) camped on the Cell A 204.

[0096] At step S403, if the Cell A 204 is willing to the transmit the UL WUS Configuration of the NES Cell 202, it may respond with UL WUS Config Transmission Acknowledgement.

[0097] At step S404, the NES Cell 202 may activate the NES mode upon receiving the UL WUS Config Transmission Acknowledgement from the Cell A 204.

[0098] At step S405, the Cell A 204 may broadcast UL WUS configurations of the NES Cell 202 to the associated UEs camped on the Cell A 204.

[0099] At step S406, the NES Cell 202 may decide to transition out of NES mode.

[0100] At step S407, the NES Cell 202 may transmit a UL WUS configuration transmission stop message to the Cell A 204.

[0101] At step S408, the NES Cell 202 may deactivate the NES mode upon transmission of the UL WUS configuration transmission stop message to the Cell A 204.

[0102] At step S409, the Cell A 204 may stop broadcasting the UL WUS configurations of the NES Cell 202 to the associated UEs.

[0103] Thus, as mentioned above, the new class 2 procedure, as disclosed in the present disclosure, may be initiated by the NES Cell 202 towards the Cell A 204 to stop the broadcast of its UL WUS Configuration.• Scenario 2a: Activation of NES mode triggered by the NES Cell 202 and supported by the Cell A 204.• Scenario 2b: Deactivation of NES mode triggered by the Cell A 204: the Cell A 204 stops broadcasting UL WUS Configuration; therefore, the NES Cell 202 is forced to transition out of NES mode.

[0104] FIG. 5 illustrates an exemplary call flow diagram 500 of managing communication between NES cell 202 and Cell A 204 in case of a deactivation of NES Mode triggered by the Cell A, in accordance with an embodiment of the present disclosure.

[0105] FIG. 5 shows an interaction between the NES Cell (gNB2) 202 (also referred hereinafter as the NES cell 202) and the Cell A (gNBl) 204 (also referred hereinafter as the Cell A 204).

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

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

[0108] Referring to FIG. 5, at S501, the NES Cell 202 may decide to transition to NES mode.

[0109] At S502, UL WUS Config Transmission Request procedure may be used by the NES Cell 202 to determine whether the Cell A 204 is willing to broadcast UL WUS Configuration to the UEs (not shown) camped on the Cell A 204.

[0110] At step S503, if the Cell A 204 is willing to the transmit the UL WUS Configuration of the NES Cell 202, it may respond with UL WUS Config Transmission Acknowledgement.[OHl] At step S504, the NES Cell 202 may activate the NES mode upon receiving the UL WUS Config Transmission Acknowledgement from the Cell A 204.

[0112] At step S505, the Cell A 204 may broadcast UL WUS configurations of the NES Cell 202 to the associated UEs camped on the Cell A 204.

[0113] The Cell A 204 may decide to stop broadcasting UL WUS configurations of the NES Cell 202 to the associated UEs camped on the Cell A 204. In an embodiment, the decision of the Cell A 204 to stop broadcasting UL WUS configurations may depend on traffic parameters, such as current traffic conditions, traffic load, bandwidth requirement, and the likes.

[0114] At step S506, upon deciding to stop broadcasting UL WUS configurations, the Cell A 204 may transmit a UL WUS configuration transmission cancel message to the NES Cell 202.

[0115] At step S507, the Cell A 204 may stop broadcasting the UL WUS configurations of the NES Cell 202 to the associated UEs camped on the Cell A 204.

[0116] At step S508, the NES Cell 202 may deactivate the NES mode upon reception of the UL WUS configuration transmission cancel message from the Cell A 204.

[0117] In an embodiment, it may be possible that one Cell A has stopped broadcasting the UL WUS configuration of the NES Cell 202, but another Cell A continues to broadcast the UL WUS configuration of the NES Cell 202. It may be up to the implementation at the NES Cell 202 to decide when and under what conditions it may deactivate the NES mode after receiving the UL WUS Configuration Transmission Cancel from a Cell A.

[0118] Thus, as mentioned above, the new class 1 procedure disclosed in the present disclosure may be initiated by the Cell A 204 towards the NES Cell 202 to indicate its cancelation of the broadcast of the UL WUS Configuration of the NES Cell 202.

[0119] FIG. 6 illustrates a flowchart of a method for managing triggering of activation and deactivation of the NES mode of the NES cell, according to the embodiments as disclosed herein.

[0120] As illustrated in FIG. 6, the method 600 may comprise one or more steps. The method 600 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.

[0121] The order in which the method 600 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement 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.

[0122] At step 602, a request message is transmitted, by a first network entity 102, operating in a first mode, to at least one second network entity 104, operating in the first mode. The request message may comprise setup 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 setup configuration information to one or more user equipment (UE) associated with the second network entity 104. In an example, the one or more UE, associated with the second network entity 104, is in an idle state. The setup 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 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.

[0123] At step 604, the first network entity 102 may receive a response based on the request message from the at least one second network entity 104.

[0124] At step 606, the first network entity 102 may selectively transition into the second mode based on the response.

[0125] In an embodiment, the response comprises a first response and a second response. In an example, upon receiving the first response, the method comprises transitioning, by the first network entity 102, from the first mode into the second mode. For example, the first response is indicative of availability of the at least one second network entity 104 for broadcasting the setup configuration information. In an example, upon receiving the second response, the method comprises continuing to keep the first network entity 102 in the first mode. For example, the second response is indicative of unavailability of the at least one second network entity 104 for broadcasting the setup configuration information.

[0126] In an embodiment, upon the first network entity 102 transitioning into the second mode, the first network entity 102 receives, from the at least one second network entity 104, a stop broadcasting intimation message. Further, the first network entity 102 selectively transitions into the first mode upon receiving the stop broadcasting intimation message.

[0127] In an embodiment, upon receiving the stop broadcasting intimation message, the first network entity 102 continues to operate in the second mode, upon receiving the first response from one of the at least one second network entity 104.

[0128] In an embodiment, upon transitioning into the second mode, the first network entity 102 determines a requirement to transition into the first mode from the second mode. Further, the first network entity 102, operating in the second mode, transmits, to the at least one second network entity 104, a stop broadcasting request message pertaining to stopping the broadcasting of the setup configuration information to the one or more user equipment (UE). Upon transmitting the stop broadcasting request message, the first network entity 102 transitions into the first mode.

[0129] FIG. 7 illustrates an embodiment of a device wherein the method for managing triggering of activation and deactivation of the NES mode of the NES cell, may be implemented, in accordance with an embodiment of the present disclosure.

[0130] It will be appreciated that the device 700 is associated with the first network entity 102. In some embodiments, the device 700 may be associated with the second network entity 104. In some embodiments, the device 700 may be selectively associated with the first network entity 102 and the second network entity 104. As shown in FIG. 7, the device 700 includes a processor 710, a memory 720, a storage component 730, an input component 740, an output component 750, a communication interface 760, and a bus 770.

[0131] The processor 710, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 710 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 710 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.

[0132] Memory 702 includes a non-transitory computer readable medium. Memory 720 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 710. The memory 720 comprises machine-readable instructions which are executable by the processor 710. These machine-readable instructions when executed by the processor 710 cause the processor 710 to perform one or more method steps of an embodiment described above.

[0133] Storage component 730 stores information and / or software related to the operation and use of the device 700. For example, storage component 730 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.

[0134] Input component 740 is configured to receive information, such as user input. For example, the input component 740 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 740 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0135] Output component 750 is configured to provide output information from the device 700. For example, the output component 750 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).

[0136] Communication interface 760 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 760 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 700 and other devices. In other words, the standard of the communication interface 760 is not limited.

[0137] The bus 770 acts as an interconnect between the processor 710, the memory 720, the storage component 730, the input component 740, the output component 750, and the communication interface 760 of the device 700. The bus 770 may include a wired interconnection or a wireless interconnection.

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

[0139] In an embodiment [1], a method comprising: transmitting, by a first network entity, operating in a first mode, to at least one second network entity, operating in the first mode, arequest message, wherein the request message comprises setup configuration information relating to the first network entity, wherein the request message pertains to broadcasting, upon the first network entity transitioning to a second mode, the setup configuration information to one or more user equipment (UE) associated with the second network entity; receiving, by the first network entity from the at least one second network entity, a response based on the request message; and selectively transitioning, by the first network entity based on the response, into the second mode.

[0140] In an embodiment [2], in the method, described in the embodiment [1], wherein the response comprises a first response and a second response, wherein, upon receiving the first response, the method comprises transitioning, by the first network entity, from the first mode into the second mode, the first response being indicative of availability of the at least one second network entity for broadcasting the setup configuration information; and wherein, upon receiving the second response, the method comprises continuing to keep the first network entity in the first mode, the second response, indicative of unavailability of the at least one second network entity for broadcasting the setup configuration information.

[0141] In an embodiment [3], in the method, described in the embodiment [2], further comprises: upon transitioning, by the first network entity, into the second mode, receiving, by the first network entity, operating in the second mode, from the at least one second 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.

[0142] In an embodiment [4], in the method, described in the embodiment [3], further comprises: upon receiving the stop broadcasting intimation message, continue operating, by the first network entity, in the second mode, upon receiving the first response from one of the at least one second network entity.

[0143] In an embodiment [5], in the method, described in the embodiment [1], further comprises: upon transitioning, by the first network entity, into the second mode, determining, by the first network entity, a requirement to transition into the first mode from the second mode; transmitting, by the first network entity, operating in the second mode, to the at least one second network entity, a stop broadcasting request message pertaining to stopping the broadcasting of the setup configuration information to the one or more user equipment (UE); and transitioning, by the first network entity upon transmitting the stop broadcasting request message, into the first mode.

[0144] In an embodiment [6], in the method, described in the embodiment [1], wherein the transmitting of the request message is based on a determination that the first network entity is to transition into the second mode.

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

[0146] In an embodiment [8], in the method, described in the embodiment [1], the setup configuration information comprises of: a plurality of uplink (UL) wake-up signal (WUS) parameters.

[0147] In an embodiment [9], in the method, described in the embodiment [8], 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.

[0148] In an embodiment

[0010] , an apparatus is configured to: transmit, by a first network entity, operating in a first mode, to at least one second network entity, operating in the first mode, a request message, wherein the request message comprises setup configuration information relating to the first network entity, wherein the request message pertains to broadcasting, upon the first network entity transitioning to a second mode, the setup configuration information to one or more user equipment (UE) associated with the second network entity; receive, by the first network entity from the at least one second network entity, a response based on the request message; and selectively transition, by the first network entity based on the response, into the second mode.

[0149] In an embodiment

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

[0010] , wherein the response comprises a first response and a second response, wherein, upon receiving the first response, the first network entity transitions from the first mode into the second mode, the first response being indicative of availability of the at least one second network entity for broadcasting the setup configuration information; and wherein, upon receiving the second response, the first network entity continues operating in the first mode, the second response being indicative of unavailability of the at least one second network entity for broadcasting the setup configuration information.

[0150] In an embodiment

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

[0011] , further configured to: upon transitioning, by the first network entity, into the second mode, receive, by the first network entity, operating in the second mode, from the at least one second networkentity, a stop broadcasting intimation message; and selectively transition, by the first network entity upon receiving the stop broadcasting intimation message, into the first mode

[0151] In an embodiment

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

[0012] , further configured to: upon transitioning, by the first network entity, into the second mode, receive, by the first network entity, operating in the second mode, from the at least one second 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.

[0152] In an embodiment

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

[0010] , further configured to: upon transitioning, by the first network entity, into the second mode, determine, by the first network entity, a requirement to transition into the first mode from the second mode; transmit, by the first network entity, operating in the second mode, to the at least one second network entity, a stop broadcasting request message pertaining to stopping the broadcasting of the setup configuration information to the one or more user equipment (UE); and transition, by the first network entity upon transmitting the stop broadcasting request message, into the first mode.

[0153] In an embodiment

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

[0010] , wherein the apparatus is configured to transmit the request message based on a determination that the first network entity is to transition into the second mode.

[0154] In an embodiment

[0016] , the apparatus, described in the embodiment

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

[0155] In an embodiment

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

[0010] , wherein the setup configuration information comprises of: a plurality of uplink (UL) wake-up signal (WUS) parameters.

[0156] In an embodiment

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

[0010] , 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.

[0157] In an embodiment

[0019] , 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 at least one second network entity, operating in the first mode, a request message, wherein the request message comprises setup configuration information relating to the firstnetwork entity, wherein the request message pertains to broadcasting, upon the first network entity transitioning to a second mode, the setup configuration information to one or more user equipment (UE) associated with the second network entity; receiving, by the first network entity from the at least one second network entity, a response based on the request message; and selectively transitioning, by the first network entity based on the response, into the second mode.

[0158] 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 720) 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 710, including instructions for causing the at least one processor 710 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 comprise Random 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.

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

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

[0161] 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 modifyor 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 at least one second network entity, operating in the first mode, a request message, wherein the request message comprises setup configuration information relating to the first network entity; receiving, by the first network entity from the at least one second network entity, a response based on the request message; and selectively transitioning, by the first network entity based on the response, into the second mode.

2. The method as claimed in claim 1, wherein the response comprises a first response and a second response, wherein, upon receiving the first response, the method comprises transitioning, by the first network entity, from the first mode into the second mode, the first response being indicative of availability of the at least one second network entity for broadcasting the setup configuration information; and wherein, upon receiving the second response, the method comprises continuing to keep the first network entity in the first mode, the second response, indicative of unavailability of the at least one second network entity for broadcasting the setup configuration information.

3. The method as claimed in claim 2, further comprises: upon transitioning, by the first network entity, into the second mode, receiving, by the first network entity, operating in the second mode, from the at least one second 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.

4. The method as claimed in claim 3, further comprises: upon receiving the stop broadcasting intimation message, continue operating, by the first network entity, in the second mode, upon receiving the first response from one of the at least one second network entity.

5. The method as claimed in claim 1, further comprises: upon transitioning, by the first network entity, into the second mode, determining, by the first network entity, a requirement to transition into the first mode from the second mode; transmitting, by the first network entity, operating in the second mode, to the at least one second network entity, a stop broadcasting request message pertaining to stopping the broadcasting of the setup configuration information to the one or more user equipment (UE); and transitioning, by the first network entity upon transmitting the stop broadcasting request message, into the first mode.

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

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

8. The method as claimed in claim 1, wherein the setup configuration information comprises of a plurality of uplink (UL) wake-up signal (WUS) parameters.

9. The method as claimed in claim 8, 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.

10. An apparatus configured to: transmit, by a first network entity, operating in a first mode, to at least one second network entity, operating in the first mode, a request message, wherein the request message comprises setup configuration information relating to the first network entity, wherein the request message pertains tobroadcasting, upon the first network entity transitioning to a second mode, the setup configuration information to one or more user equipment (UE) associated with the second network entity; receive, by the first network entity from the at least one second network entity, a response based on the request message; and selectively transition, by the first network entity based on the response, into the second mode.

11. The apparatus as claimed in claim 10, wherein the response comprises a first response and a second response, wherein, upon receiving the first response, the first network entity transitions from the first mode into the second mode, the first response being indicative of availability of the at least one second network entity for broadcasting the setup configuration information; and wherein, upon receiving the second response, the first network entity continues operating in the first mode, the second response being indicative of unavailability of the at least one second network entity for broadcasting the setup configuration information.

12. The apparatus as claimed in claim 11, further configured to: upon transitioning, by the first network entity, into the second mode, receive, by the first network entity, operating in the second mode, from the at least one second 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.

13. The apparatus as claimed in claim 12, further configured to: upon receiving the stop broadcasting intimation message, continue to operate, by the first network entity, in the second mode, upon receiving the first response from one of the at least one second network entity.

14. The apparatus as claimed in claim 10, further configured to: upon transitioning, by the first network entity, into the second mode, determine, by the first network entity, a requirement to transition into the first mode from the second mode;transmit, by the first network entity, operating in the second mode, to the at least one second network entity, a stop broadcasting request message pertaining to stopping the broadcasting of the setup configuration information to the one or more user equipment (UE); and transition, by the first network entity upon transmitting the stop broadcasting request message, into the first mode.

15. The apparatus as claimed in claim 10, wherein the apparatus is configured to transmit the request message based on a determination that the first network entity is to transition into the second mode, and wherein the request message pertains to broadcasting, upon the first network entity transitioning to a second mode, the setup configuration information to one or more user equipment (UE) associated with the second network entity.

16. The apparatus as claimed in claim 10, wherein the one or more UE, associated with the second network entity, is in an idle state.

17. The apparatus as claimed in claim 10, wherein the setup configuration information comprises of: a plurality of uplink (UL) wake-up signal (WUS) parameters.

18. The apparatus as claimed in claim 17, 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.

19. 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 at least one second network entity, operating in the first mode, a request message, wherein the request message comprises setup configuration information relating to the first network entity, wherein the request message pertains to broadcasting, upon the first network entity transitioning to a second mode, the setup configuration information to one or more user equipment (UE) associated with the second network entity;receiving, by the first network entity from the at least one second network entity, a response based on the request message; and selectively transitioning, by the first network entity based on the response, into the second mode.

Images