Wake-up signal (WUS) configuration coordination for requesting on-demand system information block 1 (SIB1)

Abstract

According to certain embodiments, a method is performed by a user equipment. The method comprises receiving information from a first cell configured to transmit a SIB1 of the first cell on demand. The information comprises an updated WUS configuration of the first cell or an updated SIB1 of the first cell. The method comprises using the information to perform an operation of the user equipment.

Description

Wake-up signal (WUS) configuration coordination for requesting on-demand system information block 1 (SIB1) BACKGROUND

[0001] A user equipment (UE) receives minimum system information (SI) in a master information block (MIB) and a system information block 1 (SIB1) transmitted by a network. The minimum SI provides the minimum amount of system information required for the UE to camp on a cell or to initiate random access (RA). A UE can acquire the MIB by appropriately receiving a synchronization signal block (SSB). Upon decoding of the MIB, the UE has the required information to acquire the SIB1, as well as, e.g., a Control Resource Set #0 (CORESET#0) configuration. The MIB can indicate that the cell does not transmit the SIB1 and an appropriate SIB1 can be received by listening to an associated SSB.

[0002] The 3rd Generation Partnership Project (3GPP) has provided a work item description (WID) to support an on-demand SIB1, for example:See 3GPP RP-234065, New WID: Enhancements of network energy savings for NR, 3GPP TSG RAN Meeting #102, Dec.11-15, 2024.

[0003] The outcome of this objective is the standardization of cells with on-demand SIB1 transmission. The purpose of such a feature is to assist the cell to save power, contributing to the network energy saving (NES) gains of the work item. A cell implementing the on-demand SIB1 transmission may be termed an NES cell. The feature can be significantly facilitated if the NES cell is related with some other coverage cell that acts as an anchor cell, for example, by taking care of part of the required signaling. That is, the NES cell provides periodic SSB transmission and, hence, a UE can receive this SSB and decode the associated MIB. However, if the SIB1 is to be provided on-demand by the NES cell or the coverage cell, a wake-up signal (WUS) must be used by the UE to request the on-demand SIB1. Further, the UE must be informed on the configuration of the WUS signal by either the NES cell or the anchor cell.

[0004] Figures 1A-1B illustrate a scenario A in which a UE 112 in RRC_IDLE mode is simultaneously within the coverage of a first cell 10a associated with a first network node 110a (e.g., gNB1) and within the coverage of a second cell 10b associated with a second network node 110b (e.g., NES network node). In the example, the first cell 10a corresponds to an anchor cell and the second cell 10b corresponds to an NES cell. In scenario A, the UE 112 is expected to receive the SSB transmitted by the NES cell 10b. Figure 1A shows the anchor cell 10a provides the UE 112 with the WUS configuration of the second network node 110b / second cell 10b, which is the WUS configuration needed by the UE 112 to request transmission of the on- demand SIB1 by the NES cell 10b. Figure 1B illustrates communication between the UE 112 and the NES cell 10b after reception of the WUS configuration from the anchor cell 10a. The UE 112 can initiate a physical random access channel (PRACH)-based transmission to the NES cell 10b to request the on-demand SIB1. After receiving the SIB1 from the NES cell 10b, the UE 112 can proceed to camp on the NES cell 10b, to initiate a random access procedure to transition to connected mode at the NES cell 10b, or to start a cell (re-)selection procedure.

[0005] As long as the NES cell 10b is selected as a candidate cell by the UE 112 to camp or connect, the UE 112 has to regularly switch between the carrier of the NES cell 10b and the carrier of the anchor cell 10a. On the NES cell 10b, the UE 112 can receive the SSB, transmit the on-demand SIB1 request, and receive the on-demand SIB1. On the carrier of the anchor cell 10a, the UE 112 can receive the WUS configuration or updates of this configuration.

[0006] In terms of communication between the anchor cell 10a and the NES cell 10b, a mechanism must be in place to ensure that the WUS configuration provided by the anchor cell 10a to the UE 112 is consistent with the WUS configuration that the NES cell 10b expects. This mechanism includes an update procedure from the NES cell 10b to the anchor cell 10a (e.g., performed when the WUS configuration has changed). Figure 1A illustrates this exchange via the Xn interface connecting gNB1 (the network node 110a associated with the anchor cell 10a) and the NES network node (the network node 110b associated with the NES cell 10b).

[0007] In scenario B (shown in Figure 2), the UE 112 in RRC_IDLE mode is expected to receive the SSB by the NES cell 10b, and the UE 112 is simultaneously in the coverage of an anchor cell 10a. The anchor cell 10a provides the configuration of the wake-up signal (WUS) required by the UE 112 so that the UE 112 can request from the anchor cell 10a the on-demand SIB1 for the NES cell 10b. After reception of the WUS configuration, the UE can initiate a PRACH-based transmission to the anchor cell 10a to request the on-demand SIB1. After the UE 112 receives the SIB1 (e.g., the UE 112 receives, via the anchor cell 10a, the SIB1 of NESnetwork node 110b / NES cell 10b), the UE 112 can proceed to camp on the NES cell 10b, to initiate a random access procedure to transition to connected mode at the NES cell 10b, or to start a cell (re-)selection procedure. In a related scenario, the anchor cell 10a continuously transmits the SIB1 of the NES cell 10b rather than requiring the UE 112 to use the WUS procedure to request the anchor cell 10a to transmit the SIB1 of the NES cell 10b on demand.

[0008] For reasons analogous to scenario A, the UE 112 in scenario B must also switch between carriers of the NES cell 10b and the anchor cell 10a on a regular basis to be up-to-date with potential changes of the SIB1 contents. Regarding the communication between the anchor cell 10a and the NES cell 10b, the mechanism in scenario B extends the mechanism in scenario A to include the contents of the on-demand SIB1. Given that the contents of the on-demand SIB1 are likely to change more often than the WUS configuration for the on-demand SIB1 request, the communication overhead is substantially increased in scenario B (compared to scenario A). Figure 2 illustrates an example where the SIB1 update is communicated via the Xn interface between gNB1 (the network node 110a associated with the anchor cell 10a) and the NES network node (the network node 110b associated with the NES cell 10b). SUMMARY

[0009] There currently exist certain challenge(s). When an anchor cell assists in providing the UE with the SIB1 for an NES cell, for example, by providing the appropriate configuration of WUS, the UE must switch between the carrier of the anchor cell and the NES cell at regular intervals (see, e.g., scenario A and scenario B discussed above). This switching between cells creates synchronization issues and forces the UE to keep synchronizing with an anchor cell (which typically is on another carrier), which could lead to increased UE power consumption, loss of timely updates, increased access latency, etc.

[0010] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The methods disclosed here provide mechanisms so that any of the procedures related to NES SIB1 provision, either constant provision via the anchor cell, or on- demand SIB1 via anchor transmission, and potential updates of the WUS configuration for the on demand SIB1 request can be seamlessly performed by the NES cell without the UE having to constantly track the anchor cell as intermediary.

[0011] In certain embodiments, while the anchor cell may regularly (e.g., on a periodic basis) transmit information (e.g., SIB1 or WUS configuration) related to an NES cell, the NES cell also provides this information for a limited duration upon updates.

[0012] In certain embodiments, a method performed by a user equipment comprises receiving information from a first cell configured to transmit a SIB1 of the first cell on demand. The information comprises an updated WUS configuration of the first cell or an updated SIB1 of the first cell. The method comprises using the information to perform an operation of the user equipment.

[0013] In certain embodiments, a user equipment comprises processing circuitry configured to receive information from a first cell, the first cell configured to transmit a SIB1 of the first cell on demand. The information received from the first cell comprises an updated WUS configuration of the first cell or an updated SIB1 of the first cell. The processing circuitry is configured to use the information to perform an operation of the user equipment.

[0014] In certain embodiments, a method in a network node associated with a first cell comprises obtaining information comprising an updated WUS configuration of the first cell or an updated SIB1 of the first cell, wherein the first cell is configured to transmit a SIB1 of the first cell on demand. The method comprises transmitting the information via the first cell.

[0015] In certain embodiments, a network node is associated with a first cell configured to transmit a SIB1 of the first cell on demand. The network node comprises processing circuitry configured to obtain information comprising an updated WUS configuration of the first cell or an updated SIB1 of the first cell and to transmit the information via the first cell.

[0016] Certain embodiments may provide one or more of the following technical advantage(s). Certain embodiments assist the UE to receive all the required information of the NES cell and avoid the switching between the carriers of the anchor cell to obtain up-to-date WUS configuration information and the NES (camping) cell to monitor the cell quality.

[0017] Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the drawings, in which:

[0019] Figures 1A-1B illustrates block diagrams showing an example of a first scenario (scenario A) in which a user equipment (UE) can request an on-demand system information block 1 (SIB1).

[0020] Figure 2 illustrates a block diagram showing an example of a second scenario (scenario B) in which a UE can request an on-demand SIB1.

[0021] Figure 3 illustrates a flow diagram showing an example of a method that may be performed by a UE in accordance with some embodiments.

[0022] Figure 4 illustrates a flow diagram showing an example of a method that may be performed by a network node in accordance with some embodiments.

[0023] Figure 5 illustrates a block diagram showing an example of a communication system in accordance with some embodiments.

[0024] Figure 6 illustrates a block diagram showing an example of a UE in accordance with some embodiments.

[0025] Figure 7 illustrates a block diagram showing an example of a network node in accordance with some embodiments.

[0026] Figure 8 illustrates a block diagram showing an example of a virtualization environment in accordance with some embodiments.

[0027] Figure 9 illustrates a block diagram showing an example in which a UE receives an updated WUS configuration or an updated SIB1 in accordance with some embodiments. DETAILED DESCRIPTION

[0028] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0029] Certain embodiments alleviate one or more UEs camping on a first cell (NES cell) from having to constantly keep track of two cells (both the first cell / NES cell and a second cell / anchor cell) for the sake of potential updates of the NES cell’s information. Either a validity procedure is defined, and the UE then knows when (rather than constantly) to update itself on the information provided from the second cell or another method based on which both cells cooperate in the information update procedure. According to the second procedure, while the second cell (anchor cell) may regularly (e.g., on a periodic basis) transmit the NES cell’s information (e.g., SIB1 or WUS configuration for the first cell / NES cell) and associated update notifications, the NES cell also provides this information (the update notifications and / or the configuration itself) for a limited duration upon updates. As such: the second (anchor) cell regularly / periodically provides the up-to-date information (based on received up-to-date information via backhaul from the NES cell) to its camping UEs.the first (NES) cell temporarily (upon updates) provides the updated information to its camping UEs.

[0030] When it comes to the first procedure, based on validity, either a timer-based solution is identified as described further below, or a validity procedure is defined which is based on lack of response to the UE’s WUS transmission. For example, either according to a prespecified number of WUS transmissions defined in the specifications, or according to a network (NW) provided WUS configuration, the UE camping on the first cell understands that upon one or more lack of WUS responses (i.e., lack of SIB1 provision after WUS), the UE needs to update itself on the WUS configuration. In other words, the UE determines that the WUS currently used by the UE is not valid anymore and / or that the UE needs to update the WUS configuration, for example, based on (1) a number of WUS transmissions lacking a response (e.g., SIB1 not received after WUS) exceeding (2) a maximum value (where the maximum value can be pre-configured by signaling or pre-defined in a standard, for example).

[0031] In scenario A, after the UE has acquired the WUS configuration from the anchor cell, it can request on-demand SIB1 from the NES cell. Given that the UE is not in connected mode, the request for on-demand SIB1 is preamble / PRACH based random access (RA) procedure. Upon correct completion of the RA procedure, the UE can camp on the NES cell or proceed with connection establishment.

[0032] The UE needs to know which time / frequency resources to use when transmitting the wake-up signal, e.g., preamble, in the NES cell. But this information is typically provided in SIB1, so in one embodiment an anchor cell informs the NES cell to start transmitting SIB1 after receiving the wake-up signal, e.g., preamble, from a UE. This information can be conveyed via, e.g., Xn. In another embodiment, it is the NES cell that informs the anchor cell which WUS configuration it (the anchor) needs to signal to the requesting UEs along with the time / frequency resources on the NES cell where the said WUS can be transmitted. In yet another embodiment, the WUS configuration and the associated time / frequency resources on the NES cell are decided by the network and signaled towards the anchor and NES cells. Note that in certain embodiments, communication described as being communicated to / from the anchor cell may encompass communication to / from an anchor base station (i.e., a base station / network node, such as a gNB, configured with the anchor cell). Similarly, in certain embodiments, communication described as being communicated to / from the NES cell may encompass communication to / from an NES base station (i.e., a base station / network node, such as a gNB, configured with the NES cell).

[0033] In another embodiment time / frequency resources for wake-up signal, e.g., preamble, transmission in the NES cell is provided by the anchor cell in addition to the configuration of the wake-up signal, e.g., which preamble, to be used to request SIB1 transmission in NES cell. Once acquired, the UE uses this information to transmit the signal, e.g., preamble, to wake-up SIB1 transmission in the NES cell. In a dependent embodiment, in the anchor cell time / frequency resource allocation for the wake-up signal can be mapped to the physical cell identity (PCI) of the NES cell so that a UE can differentiate between different time / frequency resource allocations in case there are multiple NES cells associated with the anchor cell. Instead of PCI, this mapping can also be provided with an identifier (ID) provided as part of physical broadcast channel (PBCH) block associated with SSB in the NES cell, i.e., in the anchor cell the UE uses the ID / PCI to find out the configuration for the wake-up signal.

[0034] In one embodiment, the indication about the WUS / SIB1 updates of the first cell is repeated to a specific UE by the first cell. When the UE requests SIB1 via WUS but receives no response, i.e., a UE is informed of a reserved periodic uplink (UL) resource and a specific preamble when it for the first time received the WUS response from the second cell. When a UE requests SIB1 from the first cell again but fails, the UE can send the preamble to request for a reannouncement of WUS configuration.

[0035] In one embodiment, the NES cell informs the UE that updates on WUS configuration will be provided by the NES cell. In one embodiment this indication is included in the payload of message 4 (msg4) of the RA procedure. In another embodiment the information about an update in WUS configuration is provided during a paging occasion. In yet another embodiment this information is provided to a UE in connected mode via downlink control information (DCI). The provision of WUS configuration updates may stop after a determined number of updates, after the expiration of a timer, after a measurement in a report by the UE exceeds or is below a threshold, etc.

[0036] For a UE in connected mode, the NES cell can inform the UE of an update in the WUS configuration via a DCI. As examples, the new WUS configuration could be valid upon reception of the DCI, after a fixed offset, after the expiration of a timer, or after a specified system frame number (SFN). For a UE in connected mode discontinuous reception (DRX), the update can be valid after a specified number of DRX cycles or after an offset during a specified DRX cycle.

[0037] Validity information during configuration provision

[0038] In one group of embodiments, the UE may obtain validity duration information associated with a WUS configuration. As an example, in certain embodiments, the UE obtainsthe validity duration information at the time when the WUS configuration is provided / obtained. No additional future WUS configuration change indication signaling is then needed. The UE may assume that the WUS configuration is valid during the indicated time, and it does not need to monitor indication signaling, including possibly switch to second (anchor) cell monitoring, to verify the current WUS configuration. When the validity time ends, e.g., a timer expires, the UE may obtain an updated WUS configuration the same way it obtained the original configuration for the second cell, or it may obtain it from the first cell.

[0039] In one embodiment, the WUS configuration is provided to the UE by the second (anchor) cell via a SI broadcast signaling and the SI broadcast includes a WUS configuration validity timer. Upon the expiration of the timer, the UE obtains updated WUS configuration, together with a new associated validity timer, by reading SI from the second cell, or from the first cell that is now transmitting its SIB1 and optionally other SIBs.

[0040] In one embodiment, the WUS configuration is provided to the UE in connected mode by the second (anchor) cell via a dedicated radio resource control (RRC) signaling and the RRC signaling includes a configuration validity timer. Upon the expiration of the timer, the UE connects and performs a new WUS configuration request towards the second cell and receives updated WUS configuration and a new associated validity timer. Alternatively, it may connect and perform a new WUS configuration request towards the first cell that now is transmitting its SIB1 and receive updated WUS configuration and a new associated validity timer.

[0041] In some scenarios, multiple UEs may connect to the second or first NW when the timer expires, i.e., when the WUS configuration change occurs. To avoid a scheduling / resource bottleneck during the critical time instant, both configurations may be valid for a limited duration, so UEs that have not yet received the WUS configuration update can also send a WUS.

[0042] Paging messages

[0043] When a UE is camped in a NES cell and the network needs to update the configuration for the wake-up signal (request for SIB1 broadcast) for the NES cell, e.g., allocating a different preamble and / or time / frequency resources to use when requesting SIB1 transmission: in one embodiment the update notification can be indicated with a bit in the DCI in the physical downlink control channel (PDCCH) message transmitted at a paging occasion (PO) in the NES cell, i.e., similar to how system information update notification or Commercial Mobile Alert System (CMAS) / Earthquake andTsunami Warning System (ETWS) notifications are provided in legacy. The new configuration for the wake-up signal is then provided in the NES cell as part of the system information broadcast in the next modification period. in another embodiment, the update notification can be indicated with a bit in the DCI in the PDCCH message transmitted at a paging occasion (PO) in the NES cell, i.e., similar to how system information update notification or CMAS / ETWS notifications are provided in legacy, but the new configuration is then provided in the anchor cell from next modification period on. The reference for the next modification period can either be the NES cell or the anchor cell. in another embodiment a bit in the DCI in the PDCCH message transmitted at a paging occasion (PO) in the NES cell can indicate that the paging message carried in the associated physical downlink shared channel (PDSCH) message contains the new configuration for the wake-up signal, e.g., preamble and / or time / frequency resources to be used. in another embodiment a bit in the medium access control (MAC) payload, e.g., MAC control element (CE), of the PDSCH message that contains the new configuration for the wake-up signal, e.g., preamble and / or time / frequency resources to be used, indicates that the RRC message in the PDSCH message contain the new configuration for the wake-up signal. in another embodiment the new configuration for the wake-up signal is provided as part of MAC payload, e.g., MAC CE, of the PDSCH message associated with the PDCCH message transmitted at a paging occasion (PO).

[0044] Figure 3 illustrates an example of a method 30 that may be performed by a UE, in accordance with some embodiments. The method 30 begins at step 32 with receiving information from a first cell. The information comprises an updated WUS configuration of the first cell or an updated SIB1 of the first cell (or both). The first cell from which the information is received is configured to transmit a SIB1 of the first cell on demand. For example, the first cell configured to transmit its SIB1 on demand may transmit its SIB1 for a limited duration for a specific purpose, such as on request from the UE (e.g., in which case the first cell may respond with an on-demand SIB1) or when the SIB1 has recently been changed / updated (e.g., in which case the first cell may be configured to transmit an updated SIB1 for a limited duration). The first cell may be configured to transmit its SIB1 on demand because the first cell is notconfigured to transmit its SIB1 on a regular basis. A configuration for transmitting SIB1 on demand may be used when the first cell is configured for network energy savings, for example. Configuration of an NES cell may differ from configuration of an anchor cell. For example, an anchor cell may transmit its SIB1 (i.e., the anchor cell’s SIB1) regularly / on a periodic basis, whereas an NES cell may transmit its SIB1 (i.e., the NES cell’s SIB1) on demand, such as on request from the UE and / or for a limited duration upon updates. Limiting the NES cell’s transmission of its SIB1 in this manner may facilitate efficient updating of the SIB1 to the UE while saving energy that would otherwise be needed to regularly transmit the SIB1.

[0045] The method 30 proceeds to step 34 with using the information received in step 32 to perform an operation of the user equipment. As an example, an updated WUS configuration received in step 32 may be used to appropriately format a WUS in order to facilitate requesting on-demand minimum system information, such as SIB1, from the first cell. As another example, an updated SIB1 received in step 32 may be used to camp on the first cell or to perform an RA procedure with the first cell.

[0046] In an embodiment, the first cell is a NES cell, the second cell is an anchor cell, and the UE is simultaneously within coverage of both cells. The NES cell does not transmit any SIB1 to the UE on a regular / ordinary basis, but it can transmit its SIB1 occasionally on demand, such as on request from a UE or for a limited duration to update its SIB1. The anchor cell can transmit its own SIB1 to the UE on a regular / ordinary basis and can also transmit the SIB1 of the NES cell to the UE (e.g., on a regular / ordinary basis or on demand). The UE can receive an updated WUS configuration of the NES cell from either the NES cell or from the anchor cell. The UE can use the updated WUS configuration to transmit a WUS to the NES cell, for example, to obtain system information on demand from the NES cell. Examples of system information that the UE can request on demand from the NES cell include the SIB1 of the NES cell and / or other remaining minimum system information of the NES cell. The SIB1 of the NES cell (whether received, e.g., during an update by the NES cell or in response to a request from the UE) may be used by the UE to camp on the NES cell or to perform an RA procedure with the NES cell.

[0047] The method 30 of Figure 3 may further include any suitable features, such as those described in the paragraphs above and / or those described with respect to the Group A embodiments in the Example Embodiments section below.

[0048] Figure 4 illustrates an example of a method 40 that may be performed by a network node associated with a first cell, in accordance with some embodiments. The method 40 begins at step 42 with obtaining information comprising an updated WUS configuration of the firstcell or an updated SIB1 of the first cell. The first cell is configured to transmit a SIB1 of the first cell on demand. For example, the first cell (e.g., NES cell) does not transmit the information on a regular basis. In other words, while the first cell may be configured such that it does not transmit a WUS configuration and / or a SIB1 on a regular basis, the first cell may transmit an updated WUS configuration and / or an updated SIB1 for a limited duration. For example, while an anchor cell may regularly (e.g., on a periodic basis) transmit information (e.g., SIB1 or WUS configuration) related to itself and / or related to the NES cell, the NES cell also provides its information (e.g., SIB1 or WUS configuration) on demand, such as in response to a request from a UE and / or for a limited duration upon updates, for example, to facilitate efficient updating of the information to the UE.

[0049] The network node may obtain the information in step 42 in any suitable manner. As non-limiting examples, in certain embodiments, the network node obtains at least some of the information in step 42 by one or more of: obtaining the information from memory associated with the network node, obtaining the information based on input from another network node, obtaining the information based on input from the operator via e.g. an Operation and Maintenance (O&M) system, obtaining the information based on a standard specification, obtaining the information using a function or formula, or otherwise obtaining (e.g., determining) the information by the network node, for example, in response to detecting an indication or a need to update the WUS configuration and / or to update the SIB1.

[0050] The method 40 proceeds to step 44 with transmitting the information obtained in step 42 via the first cell. As an example, transmitting the updated WUS configuration facilitates a UE in requesting minimum system information, such as SIB1, on demand. As another example, transmitting the updated SIB1 facilitates a UE in camping on the first cell or performing an RA procedure with the first cell without having to constantly monitor transmissions in a second cell, e.g., an anchor cell.

[0051] The method 40 of Figure 4 may further include any suitable features, such as those described in the paragraphs above and / or those described with respect to the Group B embodiments in the Example Embodiments section below.

[0052] Note that throughout the disclosure, a cell may be associated with a network node. In other words, the network node may be configured to provide the cell that is associated with the network node (see, e.g., Fig. 1A associating cell 10a with network node 110a and associating cell 10b with network node 110b). Accordingly, signaling described as being to / from the cell may correspond to signaling to / from the network node associated with the cell and may therefore be transmitted, received, processed, etc. using circuitry of the network node.As an example, with respect to Figures 3 and 4, the first cell may be associated with a first network node, such as an NES network node configured to provide the first cell as an NES cell. Similarly, the second cell may be associated with a second network node, such as a gNB configured to provide the second cell as an anchor cell. Signaling described as being to / from the first cell may correspond to signaling to / from the first network node, and signaling described as being to / from the second cell may correspond to signaling to / from the second network node.

[0053] Figure 5 shows an example of a communication system 100 in accordance with some embodiments.

[0054] In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 102, including one or more network nodes 110 and / or core network nodes 108.

[0055] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN accessnode may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0056] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0057] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0058] In the depicted example, the core network 106 connects the network nodes 110 to one or more host computing systems, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and MobilityManagement Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0059] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0060] As a whole, the communication system 100 of Figure 5 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0061] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive IoT services to yet further UEs.

[0062] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by aninternal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC).

[0063] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.

[0064] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to a machine-to-machine (M2M) service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub – that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In other embodiments, the hub 114 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0065] Figure 6 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0066] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0067] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 6. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0068] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0069] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0070] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0071] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes oneor more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0072] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.

[0073] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0074] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-basedcommunication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0075] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0076] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0077] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor formonitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 200 shown in Figure 6.

[0078] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0079] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0080] Figure 7 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0081] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node)and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0082] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0083] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0084] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logicoperable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0085] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0086] The memory 304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer- executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0087] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signalhaving the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0088] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0089] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0090] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0091] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source suppliespower to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0092] Embodiments of the network node 300 may include additional components beyond those shown in Figure 7 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

[0093] Figure 8 is a block diagram illustrating a virtualization environment 400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0094] Applications 402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0095] Hardware 404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 406(also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 408a and 408b (one or more of which may be generally referred to as VMs 408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 406 may present a virtual operating platform that appears like networking hardware to the VMs 408.

[0096] The VMs 408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 406. Different embodiments of the instance of a virtual appliance 402 may be implemented on one or more of VMs 408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0097] In the context of NFV, a VM 408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 408, and that part of hardware 404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 408 on top of the hardware 404 and corresponds to the application 402.

[0098] Hardware 404 may be implemented in a standalone network node with generic or specific components. Hardware 404 may implement some functions via virtualization. Alternatively, hardware 404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 410, which, among others, oversees lifecycle management of applications 402. In some embodiments, hardware 404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 412 which may alternatively be used for communication between hardware nodes and radio units.

[0099] The methods / steps / functionality described throughout the disclosure as being performed by a UE may be performed by any UE described herein, such as the UE describedwith respect to Figures 1-2, UE 112 of Figure 5, or UE 200 of Figure 6. As an example, in certain embodiments, the UE comprises at least one processor (such as processing circuitry 202) configured to perform any one or more steps of a method performed by a UE. In certain embodiments, the UE comprises a computer-readable medium (such as memory 210) comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform any one or more steps of a method performed by a UE. For example, Figure 3 above and the Group A embodiments below describe examples of methods that may be performed by a UE.

[0100] The methods / steps / functionality described throughout this disclosure as being performed by a cell / base station / gNB / network node (e.g., NES or anchor) may be performed by any network node described herein, such as a network node (e.g., gNB) described with respect to Figures 1-2, network node 110 of Figure 5, or network node 300 of Figure 7. As an example, in certain embodiments, the network node comprises at least one processor (such as processing circuitry 302) configured to perform any one or more steps of a method performed by a cell / base station / gNB / network node (e.g., NES or anchor). In certain embodiments, the network node comprises a computer-readable medium (such as memory 304) comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform any one or more steps of a method performed by a cell / base station / gNB / network node (e.g., NES or anchor). For example, Figure 4 above and the Group B embodiments below describe examples of methods that may be performed by a network node.

[0101] In certain embodiments, a UE and a network node (e.g., anchor or NES cell / base station / gNB) may perform reciprocal operations. For example, a message sent from a UE to a network node may be received by the network node from the UE, and vice versa. Similarly, an anchor cell and a NES cell may perform reciprocal operations. For example, a message sent from an anchor cell to an NES cell may be received by the NES cell from the anchor cell, and vice versa. Thus, a method performed by one entity (e.g., UE, anchor cell, or NES cell) may include any suitable steps or features to support another entity in performing a reciprocal method.

[0102] Modifications, additions, or omissions may be made to the systems and apparatuses described herein without departing from the scope of the disclosure. Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform thetasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. Thus, the components of the systems and apparatuses may be integrated or separated in any suitable manner, and the operations of the systems and apparatuses may be performed by more, fewer, or other components.

[0103] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0104] Figure 9 illustrates a block diagram showing an example in which a UE 112 receives an updated WUS configuration or an updated SIB1 in accordance with some embodiments. As an example, a UE 112 in Figure 9 may perform the method 30 in Figure 3 and a network node 110b / cell 10b in Figure 9 may perform the method 40 in Figure 4. In an embodiment, the network node 110b / cell 10b is configured to transmit cell 10b’s SIB1 on demand, e.g., for NES purposes (which may save energy that would otherwise be required totransmit cell 10b’s SIB1 on a regular basis). In an embodiment, the UE 112 may be simultaneously within the coverage of another network node 110a / cell 10a (e.g., gNB1 / anchor cell).

[0105] In the example shown in Figure 9, the UE 112 may receive information 902 from the network node 110b / cell 10b. The UE 112 may use the received information 902 to perform an operation of the UE, which may optionally involve sending signaling 904 to the network node 110b / cell 10b. As an example, in an embodiment, the information 902 received by the UE comprises an updated WUS configuration and the operation of the UE comprises sending a WUS configured according to the updated WUS configuration in signaling 904 to the network node 110b / cell 10b. Sending the WUS facilitates the UE in obtaining the SIB1 on-demand from the network node 110b / cell 10b. As another example, in an embodiment, the information 902 received by the UE comprises an updated SIB1 and the signaling 904 sent by the UE comprises signaling that initiates RA to the network node 110b / cell 10b. As another example, in an embodiment, the information 902 received by the UE comprises the updated SIB1 and the operation of the UE comprises using the SIB1 to camp on the cell 10b.

[0106] EXAMPLE EMBODIMENTS

[0107] Group A Embodiments:

[0108] In an embodiment A1, a method performed by a user equipment. The method comprises receiving (32) information from a first cell configured to transmit a SIB1 of the first cell on demand. The information comprises an updated WUS configuration of the first cell or an updated SIB1 of the first cell. The method comprises using (34) the information to perform an operation of the user equipment.

[0109] In an embodiment A2, the method of embodiment A1, wherein using the information to perform the operation of the user equipment comprises: configuring a WUS according to the updated WUS configuration received from the first cell; and transmitting the WUS to the first cell to request an on-demand SIB1.

[0110] In an embodiment A3, the SIB1 (e.g., on-demand SIB1 or updated SIB1) is used for camping on the first cell and / or for initiating RA to the first cell. As an example of embodiment A3, the method of embodiment A2 further comprises: receiving the on-demand SIB1 from the first cell; and using the on-demand SIB1 for camping on the first cell and / or for initiating RA to the first cell. As another example of embodiment A3, the method of embodiment A1 or A2, wherein using the information to perform the operation of the user equipment comprises one or more of: camping on the first cell using the updated SIB1 receivedfrom the first cell; or initiating RA to the first cell using the updated SIB1 received from the first cell.

[0111] In an embodiment A4, the method of any one of embodiments A1-A3, the method further comprising one or more of: (a) receiving a synchronization signal from the first cell; (b) receiving remaining minimum system information of the first cell from a second cell; (c) transmitting a WUS to the first cell, the WUS configured according to the updated WUS configuration received from the first cell, wherein transmitting the WUS to the first cell facilitates receiving the remaining minimum system information of the first cell on-demand from the first cell; (d) receiving, from the second cell, one of either the updated SIB1 of the first cell or the updated WUS configuration of the first cell; (e) transmitting the WUS to the first cell, the WUS configured according to the updated WUS configuration, the updated WUS configuration received from the second cell, wherein transmitting the WUS to the first cell facilitates receiving the remaining minimum system information of the first cell on-demand from the first cell; (f) receiving, from a network, the updated WUS configuration of the first cell or the updated SIB1 of the first cell; and / or (g) receiving information indicating one or more resources allocated by the first cell for a future WUS configuration update. As an example, for option (b), in some embodiments the remaining minimum system information of the first cell is received from the second cell because the first cell is not configured to regularly transmit the remaining minimum system information. As another example, in certain embodiments option (c) facilitates receiving the remaining minimum system information from the first cell on an on-demand basis because the first cell is not configured to regularly transmit the remaining minimum system information. As another example, in certain embodiments, the synchronization signal comprises a 5G SSB and / or the remaining minimum system information comprises a 5G SIB1.

[0112] In an embodiment A5, the method of any one of embodiments A1-A4, further comprising: receiving an indication about a future WUS configuration update via a network response during a random access procedure.

[0113] In an embodiment A6, the method of any one of embodiments A1-A5, further comprising: receiving an indication about a future WUS configuration update, the indication received from the first cell, a second cell, or both.

[0114] In an embodiment A7, the method of any one of embodiments A1-A6, wherein the updated WUS configuration is received both in the first cell and a second cell.

[0115] In an embodiment A8, the method of any one of embodiments A1-A7, wherein the updated WUS configuration is received via a SIB.

[0116] In an embodiment A9, the method of any one of embodiments A1-A8, wherein the information received from the first cell is accompanied by a duration of validity, the duration of validity indicating how long the updated WUS configuration will remain valid and / or how long the updated SIB1 will remain valid.

[0117] In an embodiment A10, the method of embodiment A9, wherein the duration of validity is based on expiry of a timer. As an example, timer expiration may be expressed in seconds, milliseconds, number of symbols / frames, SFN, etc. As another example, timer expiration may be related with some other signal or measurement or report.

[0118] In an embodiment A11, the method of embodiment A9, wherein the duration of validity corresponds to: a fixed number of WUS periods with respect to the updated WUS configuration; or a fixed number of SIB1 periods with respect to the updated SIB1.

[0119] In an embodiment A12, the method of any one of embodiments A9-A11, wherein the duration of validity is determined after a measurement in a report by the UE crosses a predetermined threshold. The measurement in the report may cross the predetermined threshold either by exceeding the threshold or by falling below the threshold, for example, depending on the type of threshold.

[0120] In an embodiment A13, the method of any one of embodiments A9-A12, wherein the duration of validity is terminated if the UE is handed over to another cell.

[0121] In an embodiment A14, the method of any of embodiments A1-A13, wherein the updated WUS configuration is accompanied by information indicating a number of WUS attempts for which if the UE fails to receive any WUS response to transmitting the number of WUS attempts according to the updated WUS configuration, then the UE determines that the updated WUS configuration is not valid. As an example, if the UE identifies a lack of WUS response due to the UE not receiving any response to a given number of WUS attempts, the UE determines that its current WUS configuration is no longer valid and updates its WUS configuration via the first cell or the second cell. The number of WUS attempts / lack of WUS responses associated with WUS configuration validity can be configurable or predefined in a standard, for example. The number of WUS attempts / lack of WUS responses can be configured as any suitable number (e.g., 1, 2, … n).

[0122] In an embodiment A15, the method of any one of embodiments A1-A14, wherein validity information associated with the updated WUS configuration is provided by the first cell together with the updated WUS configuration. In certain embodiments, the updated WUS configuration and the validity information associated with the updated WUS configuration are also provided by a second cell.

[0123] In an embodiment A16, the method of any one of embodiments A1-A15, wherein the updated WUS configuration is received via RRC signaling and the RRC signaling comprises a configuration for a validity timer associated with the updated WUS configuration.

[0124] In an embodiment A17, the method of embodiment A16 further comprises: requesting a new WUS configuration in response to an expiration of the validity timer associated with the updated WUS configuration; and receiving the new WUS configuration and a configuration for a validity timer associated with the new WUS configuration.

[0125] In an embodiment A18, the method of any one of embodiments A1-A15, wherein the updated WUS configuration is received via SI broadcast signaling and the SI broadcast comprises a configuration for a validity timer associated with the updated WUS configuration.

[0126] In an embodiment A19, the method of embodiment A18 further comprises: reading SI after an expiration of the validity timer associated with the updated WUS configuration to obtain a new WUS configuration and a configuration for a validity timer associated with the new WUS configuration.

[0127] In an embodiment A20, the method of any one of embodiments A1-A19, wherein the first cell from which the information is received is configured as a NES cell that does not transmit the information on a regular basis. E.g., the NES cell does not transmit the updated WUS configuration or the updated SIB1 on a regular basis. In certain embodiments, the UE is simultaneously within the coverage of the NES cell as the first cell and within the coverage of a second cell (e.g., an anchor cell or a cell provided by a gNB).

[0128] In an embodiment A21, the method of any one of embodiments A1-A20, wherein the updated WUS configuration (or the indication about a future WUS configuration update) is received via a paging occasion.

[0129] In an embodiment A22, the method of any one of embodiments A1-A21, wherein the first cell from which the information is received is configured to repeat the information (the updated WUS configuration and / or the updated SIB1) to the UE.

[0130] In an embodiment A23, the method of any one of embodiments A1-A22, wherein the first cell from which the information is received is configured to broadcast the information (the updated WUS configuration and / or the updated SIB1) to a group of UEs in the first cell. In certain embodiments, the information of the first cell (the updated WUS configuration of the first cell and / or the updated SIB1 of the first cell) is also broadcast to a group of UEs in the second cell.

[0131] In an embodiment A24, the method of any one of embodiments A1-A23, wherein the update is received via DCI when the UE is in connected mode.

[0132] Group B Embodiments:

[0133] In an embodiment B1, a method in a network node associated with a first cell comprises obtaining (42) information comprising an updated WUS configuration of the first cell or an updated SIB1 of the first cell, wherein the first cell is configured to transmit a SIB1 of the first cell on demand. The method comprises transmitting (44) the information via the first cell.

[0134] In an embodiment B2, the information transmitted via the first cell in embodiment B1 includes the updated WUS configuration and the updated WUS configuration facilitates a UE in requesting an on-demand SIB1.

[0135] In an embodiment B3, the information transmitted via the first cell in any one of embodiments B1 or B2 includes the updated SIB1 and the updated SIB1 facilitates a UE camping on the first cell or initiating RA to the first cell.

[0136] In an embodiment B4, the method of any one of embodiments B1-B3, the method further comprising one or more of: transmitting a synchronization signal; receiving, from a UE, a WUS configured according to the updated WUS configuration and, in response, transmitting remaining minimum system information on-demand to the UE; and / or transmitting information indicating one or more resources allocated by the first cell for a future WUS configuration update. As an example, in certain embodiments the synchronization signal comprises a 5G SSB. As another example, in certain embodiments the remaining minimum system information comprises a 5G SIB1.

[0137] In an embodiment B5, the method of embodiment B4, wherein transmitting the information indicating the one or more resources allocated by the first cell for the future WUS configuration update is done via a network response during a random access procedure.

[0138] In an embodiment B6, the method of any one of embodiments B1-B5, further comprising transmitting an indication about a future WUS configuration update.

[0139] In an embodiment B7, the method of any one of embodiments B1-B6, wherein the updated WUS configuration is provided both in the first cell and in a second cell.

[0140] In an embodiment B8, the method of any one of embodiments B1-B7, wherein the updated WUS configuration is transmitted via a SIB.

[0141] In an embodiment B9, the method of any one of embodiments B1-B8, further comprising transmitting a duration of validity via the first cell, the duration of validity indicating how long the updated WUS configuration will remain valid and / or how long the updated SIB1 will remain valid.

[0142] In an embodiment B10, the method of embodiment B9, wherein the duration of validity is based on expiry of a timer. As an example, expiry of the timer may be expressed in seconds, milliseconds, number of symbols / frames, SFN, etc. As another example, expiry of the timer may be related with some other signal or measurement or report.

[0143] In an embodiment B11, the method of embodiment B9, wherein the duration of validity corresponds to: a fixed number of WUS periods with respect to the updated WUS configuration; or a fixed number of SIB1 periods with respect to the updated SIB1.

[0144] In an embodiment B12, the method of any one of embodiments B9-B11, wherein the duration of validity is determined after a measurement in a report by the UE crosses a predetermined threshold. As an example, a maximum threshold may be crossed by exceeding the maximum. As another example, a minimum threshold may be crossed by falling below the minimum.

[0145] In an embodiment B13, the method of any one of embodiments B9-B12, wherein the duration of validity is terminated if the UE is handed over to another cell.

[0146] In an embodiment B14, the method of any of embodiments B1-B13, further comprising transmitting information indicating a number of WUS attempts for which if the UE fails to receive any WUS response to transmitting the number of WUS attempts according to the updated WUS configuration, then the UE determines that the updated WUS configuration is not valid. (See analogous embodiment A14 for further explanation.)

[0147] In an embodiment B15, the method of any one of embodiments B1-B14, wherein validity information associated with the updated WUS configuration is provided together with the updated WUS configuration.

[0148] In an embodiment B16, the embodiment of B15 wherein the updated WUS configuration is provided via RRC signaling and the RRC signaling comprises a configuration for a validity timer associated with the updated WUS configuration.

[0149] In an embodiment B17, the method of embodiment of B17 further comprises receiving, from the UE, a request for a new WUS configuration from the UE, the request based on an expiration of the validity timer associated with the updated WUS configuration; and in response to the request, providing the UE with the new WUS configuration.

[0150] In an embodiment B18, the method of embodiment B17 further comprises providing the UE with a configuration for a validity timer associated with the new WUS configuration.

[0151] In an embodiment B19, the method of embodiment B15, wherein the updated WUS configuration is provided via SI broadcast signaling and the SI broadcast comprises a configuration for a validity timer associated with the updated WUS configuration.

[0152] In an embodiment B20, the method of embodiment B19, further comprising in response to expiration of the configuration for the validity timer associated with the updated WUS configuration, updating the SI broadcast with a new WUS configuration and a configuration for a validity timer associated with the new WUS configuration.

[0153] In an embodiment B21, the method of any one of embodiments B1-B20, wherein the first cell via which the information comprising the updated WUS configuration or the updated SIB1 is transmitted is configured as a NES cell that does not transmit the information on a regular basis.

[0154] In an embodiment B22, the method of any one of embodiments B1-B21, wherein the updated WUS configuration is transmitted via a paging occasion.

[0155] In an embodiment B23, the method of any one of embodiments B1-B22, wherein the update is repeated to the UE by the first cell.

[0156] In an embodiment B24, the method of any one of embodiments B1-B23, wherein the update of the first cell is broadcasted to a group of UEs in the first cell.

[0157] In an embodiment B25, the method of any one of embodiments B1-B24, wherein the update is transmitted to a UE via DCI when the UE is in connected mode.

[0158] In an embodiment B26, the method of any one of embodiments B1-B25 further comprises performing one or more steps in the network node to facilitate any of methods A1- A24 in the UE (e.g., performing reciprocal steps in the network node).

[0159] Group C Embodiments:

[0160] In an embodiment C1, a user equipment comprises processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0161] In an embodiment C2, a network node comprises processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0162] In an embodiment C3, a UE comprises: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interfaceconnected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE. The processing circuitry is configured to perform any of the steps of any of the Group A embodiments.

[0163] Various embodiments of the present disclosure can be implemented via any of: a computer-readable medium, a tangible and non-transitory computer readable medium, a computer program product, a computer program, or a carrier containing a computer program. Any one of the preceding comprises instructions that, when executed on at least one processor, cause the at least one processor to perform operations comprising the steps of any of the methods of the Group A embodiments or the Group B embodiments.

[0164] Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of the disclosure. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

[0165] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure.

Claims

CLAIMS 1. A method performed by a user equipment, the method comprising: receiving (32) information from a first cell configured to transmit a system information block 1 (SIB1) of the first cell on demand, the information comprising an updated wake-up signal (WUS) configuration of the first cell or an updated SIB1 of the first cell; and using (34) the information to perform an operation of the user equipment.

2. The method of claim 1, wherein using the information to perform the operation of the user equipment comprises: configuring a WUS according to the updated WUS configuration received from the first cell; and transmitting the WUS to the first cell to request an on-demand SIB1.

3. The method of claim 2, the method further comprising: receiving the on-demand SIB1 from the first cell; and using the on-demand SIB1 for camping on the first cell and / or for initiating random access (RA) to the first cell.

4. The method of any one of claims 1-3, wherein using the information to perform the operation of the user equipment comprises one or more of: camping on the first cell using the updated SIB1 received from the first cell; or initiating random access (RA) to the first cell using the updated SIB1 received from the first cell.

5. The method of any one of claims 1-4, the method further comprising one or more of: receiving a synchronization signal from the first cell; receiving remaining minimum system information of the first cell from a second cell; transmitting a WUS to the first cell, the WUS configured according to the updated WUS configuration received from the first cell, wherein transmitting the WUS to the first cell facilitates receiving the remaining minimum system information of the first cell on-demand from the first cell; receiving, from the second cell, one of either the updated SIB1 of the first cell or the updated WUS configuration of the first cell;transmitting the WUS to the first cell, the WUS configured according to the updated WUS configuration, the updated WUS configuration received from the second cell, wherein transmitting the WUS to the first cell facilitates receiving the remaining minimum system information of the first cell on-demand from the first cell; receiving, from a network, the updated WUS configuration of the first cell or the updated SIB1 of the first cell; and / or receiving information indicating one or more resources allocated by the first cell for a future WUS configuration update.

6. The method of any one of claims 1-5, further comprising: receiving an indication about a future WUS configuration update via a network response during a random access procedure.

7. The method of any one of claims 1-6, further comprising: receiving an indication about a future WUS configuration update, the indication received from the first cell, a second cell, or both.

8. The method of any one of claims 1-7, wherein the updated WUS configuration is received both in the first cell and a second cell.

9. The method of any one of claims 1-8, wherein the updated WUS configuration is received via a system information block (SIB).

10. The method of any one of claims 1-9, further comprising receiving a duration of validity from the first cell, the duration of validity indicating how long the updated WUS configuration will remain valid and / or how long the updated SIB1 will remain valid.

11. The method of claim 10, wherein the duration of validity is based on expiry of a timer.

12. The method of claim 10, wherein the duration of validity corresponds to: a fixed number of WUS periods with respect to the updated WUS configuration; or a fixed number of SIB1 periods with respect to the updated SIB1.

13. The method of any one of claims 10-12, wherein the duration of validity is determined after a measurement in a report by the UE crosses a predetermined threshold.

14. The method of any one of claims 10-13, wherein the duration of validity is terminated if the UE is handed over to another cell.

15. The method of any one of claims 1-14, further comprising receiving information indicating a number of WUS attempts for which if the UE fails to receive any WUS response to transmitting the number of WUS attempts according to the updated WUS configuration, then the UE determines that the updated WUS configuration is not valid.

16. The method of any one of claims 1-15, wherein validity information associated with the updated WUS configuration is received from the first cell together with the updated WUS configuration.

17. The method of any one of claims 1-16, wherein the updated WUS configuration is received via radio resource control (RRC) signaling and the RRC signaling comprises a configuration for a validity timer associated with the updated WUS configuration.

18. The method of claim 17, further comprising: requesting a new WUS configuration in response to an expiration of the validity timer associated with the updated WUS configuration; and receiving the new WUS configuration and a configuration for a validity timer associated with the new WUS configuration.

19. The method of any one of claims 1-16, wherein the updated WUS configuration is received via system information (SI) broadcast signaling and the SI broadcast comprises a configuration for a validity timer associated with the updated WUS configuration.

20. The method of claim 19, further comprising: reading system information (SI) after an expiration of the validity timer associated with the updated WUS configuration to obtain a new WUS configuration and a configuration for a validity timer associated with the new WUS configuration.

21. The method of any one of claims 1-20, wherein the first cell from which the information comprising the updated WUS configuration or the updated SIB1 is received is configured as a network energy saving (NES) cell that does not transmit the information on a regular basis.

22. A user equipment (112, 200), comprising: processing circuitry (202); and power supply circuitry (208) configured to supply power to the processing circuitry; the processing circuitry configured to: receive information from a first cell configured to transmit a system information block 1 (SIB1) of the first cell on demand, the information comprising an updated wake-up signal (WUS) configuration of the first cell or an updated SIB1 of the first cell; and use the information to perform an operation of the user equipment.

23. The user equipment of claim 22, the processing circuitry further configured to perform the steps of any one of claims 2-21.

24. A method performed by a network node associated with a first cell, the method comprising: obtaining (42) information comprising an updated wake-up signal (WUS) configuration of the first cell or an updated system information block 1 (SIB1) of the first cell, wherein the first cell is configured to transmit a SIB1 of the first cell on demand; and transmitting (44) the information via the first cell.

25. The method of claim 24, wherein the information transmitted via the first cell includes the updated WUS configuration, wherein the updated WUS configuration facilitates a UE in requesting an on-demand SIB1.

26. The method of any one of claims 24-25, wherein the information transmitted via the first cell includes the updated SIB1, wherein the updated SIB1 facilitates a UE camping on the first cell or initiating random access (RA) to the first cell.

27. The method of any one of claims 24-26, the method further comprising one or more of: transmitting a synchronization signal;receiving, from a UE, a WUS configured according to the updated WUS configuration and, in response, transmitting remaining minimum system information on-demand to the UE; and / or transmitting information indicating one or more resources allocated by the first cell for a future WUS configuration update.

28. The method of claim 27, wherein transmitting the information indicating the one or more resources allocated by the first cell for the future WUS configuration update is done via a network response during a random access procedure.

29. The method of any one of claims 24-28, further comprising: transmitting an indication about a future WUS configuration update.

30. The method of any one of claims 24-29, wherein the updated WUS configuration is provided both in the first cell and in a second cell.

31. The method of any one of claims 24-30, wherein the updated WUS configuration is transmitted via a system information block (SIB).

32. The method of any one of claims 24-31, further comprising transmitting a duration of validity via the first cell, the duration of validity indicating how long the updated WUS configuration will remain valid and / or how long the updated SIB1 will remain valid.

33. The method of claim 32, wherein the duration of validity is based on expiry of a timer.

34. The method of claim 32, wherein the duration of validity corresponds to: a fixed number of WUS periods with respect to the updated WUS configuration; or a fixed number of SIB1 periods with respect to the updated SIB1.

35. The method of any one of claims 32-34, wherein the duration of validity is determined after a measurement in a report by the UE crosses a predetermined threshold.

36. The method of any one of claims 32-35, wherein the duration of validity is terminated if the UE is handed over to another cell.

37. The method of any one of claims 24-36, further comprising transmitting information indicating a number of WUS attempts for which if the UE fails to receive any WUS response to transmitting the number of WUS attempts according to the updated WUS configuration, then the UE determines that the updated WUS configuration is not valid.

38. The method of any one of claims 24-37, wherein validity information associated with the updated WUS configuration is provided together with the updated WUS configuration.

39. The method of claim 38, wherein the updated WUS configuration is provided via radio resource control (RRC) signaling and the RRC signaling comprises a configuration for a validity timer associated with the updated WUS configuration.

40. The method of claim 39, further comprising: receiving, from the UE, a request for a new WUS configuration from the UE, the request based on an expiration of the validity timer associated with the updated WUS configuration; and in response to the request, providing the UE with the new WUS configuration.

41. The method of claim 40, further comprising providing the UE with a configuration for a validity timer associated with the new WUS configuration.

42. The method of claim 38, wherein the updated WUS configuration is provided via system information (SI) broadcast signaling and the SI broadcast comprises a configuration for a validity timer associated with the updated WUS configuration.

43. The method of claim 42, further comprising: in response to expiration of the configuration for the validity timer associated with the updated WUS configuration, updating the SI broadcast with a new WUS configuration and a configuration for a validity timer associated with the new WUS configuration.

44. The method of any one of claims 24-43, wherein the first cell via which the information comprising the updated WUS configuration or the updated SIB1 is transmitted is configured as a network energy saving (NES) cell that does not transmit the information on a regular basis.

45. A network node (110, 300), the network node comprising: processing circuitry (302); and power supply circuitry (308) configured to supply power to the processing circuitry; the processing circuitry configured to: obtain information comprising an updated wake-up signal (WUS) configuration of the first cell or an updated system information block 1 (SIB1) of the first cell, wherein the first cell is configured to transmit a SIB1 of the first cell on demand; and transmit the information via the first cell.

46. The network node of claim 45, the processing circuitry further configured to perform the steps of any one of claims 24-44.

Images