User equipment monitoring for system information block- before and after requesting on demand system information block

Abstract

A method (400) performed by a wireless device (712, 800) for requesting on-demand SIB1, OD-SIB1, includes receiving, from a first network node (710A, 900), an uplink wake-up signal, UL-WUS, configuration for requesting OD-SIB1 from a second network node (710B, 900). The UL-WUS includes assistance data for SIB1 acquisition from the second 5 network node, and the assistance data includes at least SIB1 periodicity.

Description

[0001] USER EQUIPMENT MONITORING FOR SYSTEM INFORMATION BLOCK- BEFORE AND AFTER REQUESTING ON DEMAND SYSTEM INFORMATION BLOCK

[0002] TECHNICAL FIELD

[0003] The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for User Equipment (UE) monitoring for System Information Block-1 (SIB-1) before and after requesting On-Demand SIB-1 (OD-SIB1).

[0004] BACKGROUND

[0005] Energy consumption is a considerable challenge of 5thGeneration (5G) systems today where a major contributor to the energy consumption is the radio unit of Radio Access Network (RAN) system. The Network (NW) power consumption for New Radio (NR) is said to be less compared to Long Term Evolution (LTE) because of its lean design, i.e., no Cell-specific Reference Signal (CRS) and the Synchronization Signal Block (SSB) periodicity is by default 20 ms. However, in the current implementation, NR may consume more energy compared to LTE, partly due to higher bandwidths (BWs), shorter transmission time intervals (TTIs), and massive number of antennas. This is still evident even at times when cells and beams are lightly loaded or serve no traffic or no users at all.

[0006] SIB1

[0007] SIB1 refers to System Information Block-1 in 5G NR. It is transmitted by a cell to provide User Equipments (UEs) essential information to access the network. The Master Information Block (MIB) is provided on Physical Broadcast Channel (PBCH) (in SSB). The MIB provides the UE with parameters (e.g., CORESET#0 and searchSpaceZero configuration) for monitoring TypeO-Physical Downlink Control Channel (PDCCH) Common Search Space (CSS) for scheduling Physical Downlink Shared Channel (PDSCH) that carries SIB1. These parameters provide time- and frequency location of TypeO-PDCCH CSS as offsets with respect to the SSB. See, 3GPPTS 38.213, Physical layer procedures for control (Release 18), V18.4.0, September 2024.

[0008] SIB1 is transmitted on the Downlink-Shared Channel (DL-SCH) with a periodicity of 160 ms and variable transmission repetition periodicity within 160 ms as specified in Clause 13 of 3GPP TS 38.213. The default transmission repetition periodicity of SIB1 is 20 ms, but the actual transmission repetition periodicity is up to network implementation.The UE is unaware of the actual repetition periodicity of SIB1 and may, therefore, have to search for it every 20 ms until it successfully finds and decodes SIB1. For example, a cell with SSB periodicity of 20ms may transmit SIB1 in connection with every second SSB and, thus, with a 40ms periodicity. A UE doing initial access may begin to monitor TypeO-PDCCH CSS occasions for SIB1-PDCCH associated with a first SSB where in fact no SIB1 PDCCH is provided. In the subsequent TypeO-PDCCH CSS occasion associated with the next SSB, the UE continues to monitor and finds SIB 1 -PDCCH and receives SIB1.

[0009] 3GPP Release 19 Work-Item Objective for OD-SIB

[0010] In order to enable an energy efficient NW, Third Generation Partnership Project (3 GPP) first initiated a study item (SI) on Network energy savings in NR, which was concluded with the outcome captured in TR 38.864. See, TR 38.864, Study on network energy savings for NR (Release 18), Version ilO, Mar. 2023. Following the SI phase, a Work Item (WI) on Network energy savings for NR was approved at RAN#98 and concluded with the outcomes captured in TS 38.331 and, TS 38.304. See, RP-223540, New WID: Network energy savings for NR; TS 38.331 Rel-18 v 18.0.0; TS 38.304 Rel-18 v 18.0.0.

[0011] In order to further enhance network energy savings techniques, 3GPP approved at RAN#102 a new WI on Enhancements of network energy savings for NR. See, 3GPP Work Item Description: New WID: Enhancements of network energy savings for NR, RP-234065, December 2023. This new WI includes the following objective for on-demand SIB1 provisioning:

[0012] Specify support for on-demand SIB1 for UEs in idle / inactive mode [RAN1 / 2 / 3]

[0013] • Specify procedures and signaling method(s) for Case 2 [RAN1 / 2] Case 2: UE obtains UL WUS configuration from Cell A, UE transmits UL WUS on NES Cell, UE receives on-demand SIB1 from NES Cell

[0014] Triggering method by UL WUS using PRACH

[0015] • Specify inter NG-RAN node signalling at least for the configuration of UL WUS [RAN3]

[0016] • Note 1: No modification of SSB will be discussed under this objective

[0017] • Note 2:UL WUS: Uplink wake-up signal

[0018] Cell A: A cell that is periodically transmitting at least its own SIB1

[0019] NES Cell: A cell that may transmit SIB1 transmission in response to UL WUS from a UE

[0020] • Note 3:

[0021] RANI strives to minimize impact to legacy UE

[0022] RANI specification impact to support this feature should be minimized The purpose of on-demand SIB1 is to assist the cell to save on power, contributing to the network energy saving (NES) gains of the work item. Herein, a cell implementing the on-demand SIB1 transmission is called a NES cell. A NES cell may not provide SIB1 transmission in idle state, and a UE can’t proceed to camp on the NES cell, initiate random access procedure to transition to connected mode at the NES cell, or start a cell (re-)selection procedure, unless SIB1 is provided as request. The feature can be significantly facilitated if the NES cell is related with some other coverage cell, which takes care of part of the required signaling, i.e., acts as an anchor cell (Cell A). That is, the NES cell provides periodic SSB transmission and, thus, a UE can receive this SSB and decode the associated MIB. The UE can request the on-demand SIB 1 from the NES cell where the configuration should be informed by either the NES cell or the anchor cell.

[0023] FIGURE 1 illustrates a NES cell transmitting SIB1 once requested by the UE. The UE obtains the Uplink-Wake Up Signal (UL-WUS) configuration from a Cell A. The WUS configuration is provided to Cell A by the NES cell via the network internal interface Xn.

[0024] A number of agreements regarding the objective for on-demand SIB1 provisioning has already been reached. Some aspects which are relevant for this invention are the following:

[0025] • In Release 18, a NR cell broadcast SIB1 periodically. A Release 19 on- demand SIB1 capable cell can be configured to

[0026] o NOT broadcast SIB1 periodically, but

[0027] o instead provide SIB1 in response to a request from a UE.

[0028] In the following, such a cell is referred to as a “NES cell”.

[0029] • A UE can request SIB1 transmission from an on-demand SIB1 capable cell by sending an uplink wake-up signal (UL WUS).

[0030] • A UL WUS uses a dedicated Physical Random Access Channel (PRACH) resource.• A UL WUS is specific for one or more explicitly listed NES cells.

[0031] • The UE can get the UL WUS configuration (or SIB1 request configuration) applicable to a NES cell from another cell, which is an assisting cell.

[0032] • Before sending UL WUS, the UE should first check if SIB1 is currently being broadcasted or provided on demand for that cell.

[0033] • If the UE does not find SIB1, the UE can send UL WUS. When the NES cell receives the UL WUS, it responds with a random access response (RAR) and with SIB1.

[0034] The UL WUS configuration includes parameters that the UE needs for monitoring the response of the cell, that is, to read RAR and SIB1. In particular, the following parameters are included in an UL WUS configuration:

[0035] • Specified Time Period. The UE should monitor for on-demand SIB1 for a specified time-period. The starting time for the monitoring window is defined by an offset with regard to the RAR window and the duration of the SIB1 monitoring window is given by the UL WUS configuration (see agreements cited below).

[0036] • pdcch-ConfigSIB 1 including searchSpaceZero and ontrolResourceSet- Zero\ In a cell that provides periodic SIB1 transmission, the UE can acquire these parameters from the MIB. However, a cell providing SIB 1 on-demand will not include them in the MIB, instead they will be a part of the UL WUS configuration.

[0037] • K SSB: In a cell that provides periodic SIB1 transmission, the UE acquires K SSB from the MIB (4 bits plus 1 bit in Frequency Range 1 (FR1) from Physical Broadcast Channel (PBCH)). The K SSB parameter indicates a frequency offset that the UE needs to locate SIB1.

[0038] However, in a cell that provides SIB1 on-demand, the K SSB parameter of the MIB (plus 1 bit in PBCH) has been repurposed and the K SSB frequency offset is instead provided in the UL WUS configuration.

[0039] Some relevant RANI and RAN2 agreements include:

[0040] • RAN2#127bis agreement:If UE has SIB1 request configuration of a cell, UE needs to check if SIB1 is currently being broadcasted or provided on demand for that cell before requesting SIB1 of that cell.

[0041] • RAN l#118bis Agreement:

[0042] For The repetition periodicity of SIB1 within the time window of on-demand SIB1,:

[0043] • Up to NW implementation (no change to existing specification)

[0044] • RAN l#118bis Agreement:

[0045] At least for Case-2: For further work on type 0 PDCCH monitoring occasions for on demand SIB1, on the starting time and duration of the time window of type 0 PDCCH monitoring occasions, RANI to down select from the following two options:

[0046] • Option 1 : starting time and duration are indicated in RAR of the UL-WUS transmission

[0047] • Option 2: starting time and duration are indicated in the UL WUS configuration

[0048] • RANI# 119 Agreement:

[0049] The duration of the time window for on-demand SIB1 is indicated in the UL WUS configuration.

[0050] • Unit of the duration is in slot

[0051] • FFS: Starting time

[0052] • RANI# 119 Agreement:

[0053] The reference time point to determine the window starting time for on-demand SIB1 is based on the RAR window for UL WUS wherein UE successfully received a RAR.

[0054] • FFS: Use starting or ending slot of the RAR window as reference time • RAN2#127 Agreement'.

[0055] Once Rel-19 NES UE camps on the NES cell, the UE expects to receive UL WUS configuration updates from the NES Cell, e.g., via legacy SI modification procedures.

[0056] • RAN2#127bis Agreement'.If UE has SIB1 request configuration of a cell, UE needs to check if SIB1 is currently being broadcasted or provided on demand for that cell before requesting SIB1 of that cell.

[0057] There currently exist certain challenge(s), however. For example, the RAN2#127bis agreement does not describe how a UE is expected to monitor for SIB1 before it can request it. A monitoring behavior needs to be defined to ensure that (1) UEs don’t send UL WUS requesting on-demand SIB1 when it is not needed but can opportunistically exploit already scheduled OD-SIB1 transmissions, (2) unnecessary delays in SIB1 acquisition is avoided, and (3) UEs battery is not drained in monitoring for SIB1 for an extensive duration.

[0058] SUMMARY

[0059] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. According to certain embodiments, for example, as part of an UL WUS configuration for one or more cells, the periodicity and offset of SIB1 is provided as assistance data.

[0060] According to certain embodiments, a method performed by a wireless device for requesting OD-SIB1 includes receiving, from a first network node, an UL-WUS configuration for requesting an OD-SIB1 from a second network node. The UL-WUS configuration comprises assistance data for SIB1 acquisition from the second network node, and the assistance data includes SIB1 periodicity.

[0061] According to certain embodiments, a wireless device for requesting OD-SIB1 is configured to receive, from a first network node, an UL-WUS configuration for requesting an OD-SIB1 from a second network node. The UL-WUS configuration comprises assistance data for SIB1 acquisition from the second network node, and the assistance data includes SIB1 periodicity.

[0062] According to certain embodiments, a method by a first network node for OD-SIB1 includes transmitting, to a wireless device, an UL-WUS configuration for requesting an OD-SIB1 from a second network node. The UL-WUS configuration includes assistance data for SIB1 acquisition from the second network node, and the assistance data comprises SIB1 periodicity.

[0063] According to certain embodiments, a first network node for OD-SIB1 is configured to transmit, to a wireless device, an UL-WUS configuration for requesting an OD-SIB1 from asecond network node. The UL-WUS configuration includes assistance data for SIB1 acquisition from the second network node, and the assistance data comprises SIB1 periodicity.

[0064] Certain embodiments may provide one or more of the following technical advantage(s). For example, certain embodiments may provide a technical advantage of providing the offs et+ periodicity of SIB1 to help the UE to efficiently monitor for SIB1. Accordingly, the UE can skip monitoring and turn off its receiver at occasions where SIB1 is not provided. The UE can monitor for a shorter duration, reducing the access latency. This can be applicable at least for UE monitoring / attempting to acquire SIB1 based on an UL-WUS configuration and before transmitting an UL-WUS.

[0065] As another example, certain embodiments may provide a technical advantage of increasing the probability for a UE to successfully decode SIB1. Additionally or alternatively, the delay for a UE to decode SIB1 can be reduced by coordinating the SIB1 monitoring timeline with the RACH occasions where a UE may send an UL WUS request.

[0066] As still another example, certain embodiments may provide a technical advantage of enabling the UE to save the energy of UL WUS transmission if it detects an ongoing OD-SIB1 transmission.

[0067] As still another example, certain embodiments may provide a technical advantage of enabling the explicit monitoring of the RAR resources to assist the monitoring UE to appropriately adjust / extend the SIB1 monitoring window when RAR is detected and / or promptly terminate monitoring and transmit UL WUS for OD-SIB1, otherwise.

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

[0069] BRIEF DESCRIPTION OF THE DRAWINGS

[0070] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0071] FIGURE 1 illustrates aNES cell transmitting SIB1 once requested by the UE;

[0072] FIGURE 2 illustrates a SIB1 search space, according to certain embodiments;

[0073] FIGURE 3 illustrates an example timetable of SIB1 (periodicity and offset) for the UE receiving assistance information as part of the WUS configuration, according to certain embodiments;

[0074] FIGURE 4 illustrates an example method by a UE with capability to request OD-SIB1from a network node, according to certain embodiments;

[0075] FIGURE 5 illustrates another example method by a UE for OD-SIB1, according to certain embodiments;

[0076] FIGURE 6 illustrates an example method by a network node for providing SIB1 on-demand, according to certain embodiments;

[0077] FIGURE 7 illustrates another example method by a first network node for OD-SIB1, according to certain embodiments;

[0078] FIGURE 8 illustrates an example communication system, according to certain embodiments;

[0079] FIGURE 9 illustrates another example of a communication system, according to some embodiments;

[0080] FIGURE 10 illustrates an example wireless device, according to certain embodiments; FIGURE 11 illustrates an example network node, according to certain embodiments; and

[0081] FIGURE 12 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments.DETAILED DESCRIPTION

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

[0083] As used herein, ‘node’ can be a network node or a UE. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), Operations Support System (OSS), Self-Organizing Network (SON), positioning node (e.g. E-SMLC), etc. The terms network node and radio network node are used interchangeably herein.

[0084] Another example of a node is user equipment (UE), which is a non-limiting term and refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, etc.

[0085] The term radio access technology (RAT), may refer to any RAT such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, NR, 4G, 5G, etc. Any of the equipment denoted by the terms node, network node or radio network node may be capable of supporting a single or multiple RATs.

[0086] The term signal or radio signal used herein can be any physical signal or physical channel. Examples of downlink (DL) physical signals are reference signal (RS) such as Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information-Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS) signals in SS / PBCH block (SSB), discovery reference signal (DRS), Cell Specific Reference Signal(CRS), Positioning Reference Signal (PRS), etc. RS may be periodic. For example, RS occasions carrying one or more RSs may occur with certain periodicity (e.g., 20 ms, 40 ms, etc.). The RS may also be aperiodic.

[0087] Each SSB carries New Radio-Primary Synchronization Signal (NR-PSS), New RadioSecondary Synchronization Signal (NR-SSS) and New Radio-Physical Broadcast Channel (NR-PBCH) in four successive symbols. One or multiple Synchronization Signal Blocks (SSBs) are transmitted in one SSB burst which is repeated with certain periodicity such as, for example, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms. The UE is configured with information about SSB on cells of certain carrier frequency by one or more SS / PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration comprising parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset with regard to reference time (e.g., serving cell’s SFN) etc. Therefore, SMTC occasion may also occur with certain periodicity (e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms). Examples of uplink (UL) physical signals are reference signals such as Sounding Reference Signals (SRS), Demodulation Reference Signals (DMRS), etc. The term physical channel refers to any channel carrying higher layer information e.g. data, control etc. Examples of physical channels are Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Short PUSCH (sPUCCH), Short PDSCH (sPDSCH), Short PUCCH (sPUCCH), Short PUSCH (sPUSCH), MTC PDCCH (MPDCCH), Narrowband PBCH (NPBCH), Narrowband PDCCH (NPDCCH), Narrowband PDSCH (NPDSCH), Narrowband PUSCH (NPUSCH), Enhanced PDCCH (E-PDCCH), etc.

[0088] The term time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are symbol, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, slot, subslot, mini-slot, system frame number (SFN) cycle, hyper-SFN (H-SFN) cycle, etc.

[0089] As discussed above, the RAN2#127bis agreement does not describe how a UE is expected to monitor for SIB 1 before it can request it. A monitoring behavior needs to be defined to ensure that (1) UEs don’t send UL WUS requesting on-demand SIB1 when it is not needed but can opportunistically exploit already scheduled OD-SIB1 transmissions, (2) unnecessary delays in SIB1 acquisition is avoided, and (3) UEs battery is not drained in monitoring for SIB1 for an extensive duration.Certain embodiments described herein may address these and other challenges. For example, according to certain embodiments, the UL WUS configuration is extended such that a UE, which has acquired an UL WUS configuration applicable to a network node (NES cell), can derive candidate PDCCH occasions (or PDCCH monitoring occasions) where SIB1 / OD-SIB1 of NES cell would actually be transmitted, i.e., the “timetable” for actual NES cell SIB1 transmission occasions (if NES cell would be transmitting SIB1) is provided to the UE such that the UE needs only monitor those occasions in search for SIB1 rather than searching in every potential repetition period (SIBl’s 20ms search space).

[0090] According to certain embodiments, for example, as part of an UL WUS configuration for one or more cells, the periodicity and offset of SIB1 is provided as assistance data. In particular embodiments, the expected UE monitoring behavior is detailed with respect to the assistance data. For example, the UE monitors for SIB1 according to the obtained assistance data, in a particular embodiment. As another example, the assistance data includes the timeduration during which the UE keeps monitoring for SIB1, in a particular embodiment. The time duration can be in relation to candidate RACH occasions for UL WUS transmission. As another example, in a particular embodiment, the UE optionally monitoring for RA response to an UL WUS transmitted by another UE.

[0091] FIGURE 2 illustrates a SIB1 search space 100, according to certain embodiments. Specifically, FIGURE 2 illustrates search space 100 according to the specifications, where the filled rectangles 102 are the actual SIB1 transmission occasions when SIB1 is transmitted.

[0092] A UE may use the candidate PDCCH occasions to monitor for SIB1 transmission (of NES cell) at least when the UE attempts to acquire SIB1 of the NES cell prior to transmitting UL WUS.

[0093] The SIB1 PDCCH monitoring occasions for SIB1 reception after transmission of an UL WUS are given by search space zero and a configured time-window (e.g., search space zero and time- window).

[0094] In a particular embodiment, the WUS configuration may include a configuration parameter that indicates that the candidate PDCCH occasions may also be used to monitor for SIB1 transmissions of a NES even for the case where UE attempts to acquire SIB1 for the NES cell after transmitting UL WUS and / or throughout the period the UE is camped on the NES cell.In a particular embodiment, the candidate PDCCH occasions may be a subset of the SIB1 PDCCH monitoring occasions given by the search space zero and the configured timewindow.

[0095] According to certain embodiments, the UE can also compute the time and frequency locations of RACH occasions where UL WUS can be sent.

[0096] The delay before the UE can send UL WUS also depends on the time-positions of RACH occasions where UL WUS can be sent. The time-positions of RACH occasions can be used in different ways. In one example, the UE extends the time it monitors for SIB1 until the next RACH occasion since this will not cause any additional delay for the UE. In another example, the UE may stop monitoring for SIB1 earlier in order to not miss a RACH occasion. This could be meaningful if access delay is important, and RACH occasions are sparse in time. According to certain embodiments, expected UE behavior for monitoring TypeO-PDCCH CSS is proposed.

[0097] When a random access response (RAR) is provided by the gNB in response to an OD-SIB 1 request, the UE can monitor the relevant RAR resources in addition to the SIB 1 resources. When a RAR is detected by the UE, the window of SIB1 monitoring can be appropriately adjusted to ensure that the SIB1 is correctly received by the UE.

[0098] Even if the network node is currently broadcasting SIB1 or providing SIB1 on-demand, the network node doesn’t need to transmit SIB1 in all candidate PDCCH occasions. In one example, the network node only provides SIB1 with 160ms periodicity (in every eighth candidate PDCCH occasion, assuming 20ms SSB periodicity). Thus, the UE is forced to check for SIB1 in up to eight PDCCH occasions before it can conclude whether SIB1 is provided or not. If it is not provided, the UE can proceed with requesting SIB1. According to certain embodiments described herein, however, the network provides the UE with assistance information about the actual SIB1 transmission occasion periodicity and offset in the on-demand SIB1 cell. For example, according to certain embodiments, these parameters are provided in the UL WUS configuration. By doing so, the UE can skip monitoring for SIB1 in the PDCCH occasions that are not consistent with the periodicity and offset.

[0099] FIGURE 3 illustrates an example timetable of SIB1 200 (periodicity and offset) for the UE receiving assistance information as part of the WUS configuration, according to certain embodiments. Specifically, FIGURE 1 shows that, during a SIB1 period 202 of 160m that includes a SIB1 default repetition period of 20ms, the actual SIB1 transmission 204 occurs after an offset of 100ms in the sixth SIB1 transmission occasion.Example Method and Embodiments from UE Perspective

[0100] FIGURE 4 illustrates an example method 300 by a UE with capability to request on-demand SIB1 (OD-SIB1) from a network node that can provide SIB1 on-demand, according to certain embodiments. As illustrated, the method includes a receiving step 302, an optional monitoring step 304, an optional checking / determining step 306, and an optional sending / transmitting step 308.

[0101] For example, according to certain embodiments, the method includes the UE receiving, at step 302, and from a first network node, an UL WUS configuration for requesting OD-SIB1 from a second network node. The UL WUS configuration includes assistance data for SIB1 acquisition from the second network node. In a particular embodiment, the first network node and the second network node are the same nodes. In another particular embodiment, the first network node and the second network node are different nodes.

[0102] Optionally, the UE monitors, at step 304, for RA response to UL WUS transmission in one or more RACH occasions, although the UE itself did not send such UL WUS signal.

[0103] Optionally, at step 306, the UE checks if SIB1 is currently being broadcasted or provided on-demand in the second network node, using the assistance data and optionally using a RA response.

[0104] If the UE does not acquire SIB1 from the second network node it proceeds to send an UL WUS with an on-demand SIB1 request to the second network node, optional step 308. In this case the UE monitors for SIB1 PDCCH, at the occasions according to the assistance data, for a monitoring period defined by a starting time and duration, according to RANI agreements.

[0105] In a further particular embodiment, the UL WUS configuration includes assistance information for the UE monitoring of SIB1 PDCCH in the second network node. The assistance information including one or more of the following:

[0106] • SIB1 periodicity,

[0107] • SIB1 offset.

[0108] In a further particular embodiment, the SIB1 periodicity and / or offset may be expressed in units of milliseconds, frames, subframes, or SIB1 search space occasions. In one example, the periodicity and offset are expressed in relation to the SFN, where

[0109] Period, P, may have the range [2, 4, 6, 8, 16],

[0110] Offset, O, may have the range [0..P-1],such that the UE can derive the SIB1 transmission occasions in the SFNs which satisfy the formula

[0111] SFN mod P = O

[0112] Alternatively, the SIB1 periodicity and / or offset may be expressed in relation to SSB burst periodicity and / or offset. For example, the SIB1 periodicity is twice the SSB periodicity or the SIB1 offset is the same as the SSB offset.

[0113] In a further particular embodiment, the UL WUS configuration includes assistance information for the UE monitoring of SIB1 PDCCH in the second network node. The assistance information including a bitmask / bitmap that is applicable to the prespecified / standardized SIB1 PDCCH occasions (i.e., SIB1 PDCCH search space). For example, within the NR’s SIB1 standardized periodicity of 160ms, there are eight potential occasions (every 20ms). A bitmap / bitmask of eight bits could then be used, such that for example 10101010 would mean that the NW only broadcasts in every other occasion (i.e., every 40 ms), starting (offset) from the first occasion.

[0114] In a further particular embodiment, the NW further includes configuration parameter for whether the assistance information is valid only during the on-demand SIB1 acquisition procedure or also after such as, for example, throughout the time the UE is camped on the cell.

[0115] In a further particular embodiment, the UE has acquired the UL WUS configuration applicable to the second network node and checks if SIB1 is currently being broadcasted or provided on demand in the second network node. The method comprising of the UE checking the MIB / PBCH in an SSB. If the parameter K_SSB>23 and the second network node operates in FR1 or if K_SSB>11 and the second network node operates in FR2, the UE proceeds to monitor for SIB1 PDCCH according to one of the following schemes:

[0116] • The UE determining a first set of candidate SIB1 PDCCH occasions from pdcch-ConfigSIBl and K SSB obtained in the UL WUS configuration. The first set includes all possible SIB1 PDCCH occasions over a first period of time, • The UE determining a second set of candidate SIB1 PDCCH occasions. The second set is the subset of the first set such that the SIB1 PDCCH occasions match the assistance information (i.e., SIB1 periodicity and offset),

[0117] • The UE monitoring the first or the second set of candidate SIB1 PDCCH occasions. If the UE acquires SIB1 PDCCH in one of the occasions, the UE can either stop monitoring or continue monitoring.It is noted that if the parameter K SSB (obtained from PBCH in an SSB) takes other values than those mentioned above, then the UE monitors SIB1 PDCCH according to legacy functionality.

[0118] In a further particular embodiment, the first period of time is one of

[0119] • 160ms,

[0120] • The SIB1 period, according to the assistance information,

[0121] • The time until the next RACH occasion for UL WUS transmission, or • The time until the next RACH occasion for UL WUS transmission after one SIB1 period has passed.

[0122] In a further particular embodiment, the UE has sent an UL WUS with an on-demand SIB1 request to the second network node and determined a monitoring window for SIB1 with a specific start time and duration. The method further includes at least one of:

[0123] • The UE determining a third set of candidate SIB1 PDCCH occasions from pdcch-ConflgSIB 1 and K SSB obtained in the UL WUS configuration. The third set includes all possible SIB1 PDCCH occasions over a second period of time,

[0124] • The UE determining a fourth set of candidate SIB1 PDCCH occasions.

[0125] The fourth set is the subset of the third set such that the SIB1 PDCCH occasions match the assistance information (i.e., SIB1 periodicity and offset).

[0126] • The UE monitoring the third or the fourth set of candidate SIB 1 PDCCH occasions. If the UE acquires SIB1 PDCCH in one of the occasions, the UE can either stop monitoring or continue monitoring.

[0127] In a further particular embodiment, the second period of time is one of

[0128] • The SIB1 monitoring time according to the start time and duration.

[0129] • The time from UL WUS transmission to the end of the monitoring time.

[0130] In a further particular embodiment, the UE monitors the resources where a RAR to an UL WUS, equivalently OD-SIB1 request, is to be expected. In the event that a RAR is received and the associated preamble is the same as the preamble given in the UL WUS configuration, the UE proceeds to OD-SIB1 acquisition of the upcoming OD-SIB1.

[0131] In a further particular embodiment, the UE waits for at least one TypeO-PDCCH CSS and at least one RAR resource and proceeds with a UL WUS if in both attempts no signal was detected.In a further particular embodiment, the UE waits for at most one TypeO-PDCCH CSS or one RAR resource and proceeds with a UL WUS if no signal was detected.

[0132] In a further particular embodiment, the UE monitors the RACH resource for possible transmission of UL WUS for OD-SIB1 request. If signal level significantly above the noise floor is detected, the UE can extend / adjust the window duration where it listens to SIB1 and / or RAR in hope that the detected energy in the RACH resource was a UL WUS transmission from some other UE.

[0133] In a further particular embodiment, the UE detects increased energy levels in RAR but cannot correctly detect the response. In this case, the UE can use the energy levels of RAR to adjust the power of the UL WUS transmission, with the benefit of improving the reliability of the upcoming SIB1 reception.

[0134] In a further particular embodiment, a first network node provides UL WUS configuration for requesting OD-SIB 1 for multiple other network nodes. The first network node can include assistance data for SIB1 acquisition as a part of common or separate UL WUS configuration parameters. For example, if the same assistance data for SIB1 acquisition is applicable for all the network nodes that can provide OD-SIB 1 with the assistance from the first network node, then the assistance data for SIB1 acquisition can be provided as a part of common UL WUS configuration. Otherwise, if the same assistance data for SIB1 acquisition is not applicable for all the network nodes that can provide OD-SIB 1 with the assistance from the first network node, then the assistance data for SIB1 acquisition can be provided as a part of separate UL WUS configuration.

[0135] FIGURE 5 illustrates another example method 400 by a UE for OD-SIB 1, according to certain embodiments. As illustrated the method includes, at step 402, the UE receiving, from a first network node, an UL-WUS configuration for requesting an OD-SIB 1 from a second network node. The UL-WUS configuration includes assistance data for SIB1 acquisition from the second network node, and the assistance data includes SIB1 periodicity.

[0136] In a particular embodiment, based on the assistance data, the UE monitors a SIB1 PDCCH.

[0137] In a particular embodiment, the monitoring of the SIB1 PDCCH is performed during at least one monitoring occasion for a monitoring period.

[0138] In a particular embodiment, the assistance data comprises SIB1 offset.

[0139] In a particular embodiment, the assistance information comprises a bitmask and / or bitmap that is applicable to at least one prespecified and / or standardized SIB1 PDCCHoccasions.

[0140] In a particular embodiment, the UL-WUS configuration includes a configuration parameter indicating whether the assistance data may be used for monitoring for at least one SIB1 transmission even when the UE attempts to acquire SIB1 for the NES cell after transmitting an UL-WUS and / or throughout a period that the UE is camped on the cell.

[0141] In a particular embodiment, the UE monitors for a RAR to an UL WUS transmission in one or more RACH occasions though the wireless device has not transmitted the UL WUS transmission.

[0142] In a particular embodiment, when the RAR is received and an associated preamble of the RAR is the same as a preamble given in the UL WUS configuration, the method proceeds to OD-SIB1 acquisition of an upcoming OD-SIB1.

[0143] In a particular embodiment, the UE waits for at least one TypeO-PDCCH CSS and at least one RAR resource, and the UE proceeds with an UL WUS when no signal was detected in the TypeO-PDCCH CSS or the at least one RAR resource.

[0144] In a particular embodiment, the UE waits for at most one TypeO-PDCCH CSS or one RAR resource and proceeds with an UL WUS when no signal was detected in the at most one TypeO-PDCCH CSS or the one RAR resource.

[0145] In a particular embodiment, the UE detects an increased energy level in RAR and adjusts a power of an UL WUS transmission by the wireless device.

[0146] In a particular embodiment, the UE uses at least one of the UL-WUS configuration comprising the assistance data and a RAR to determine if SIB1 is being broadcasted or provided on-demand by the second network node.

[0147] In a particular embodiment, when determining if SIB1 is being broadcasted or provided on-demand by the second network node, the UE checks a MIB and / or PBCH in a SSB.

[0148] In a particular embodiment, when a parameter K_SSB>23 and the second network node operates in FR1 or when K_SSB>11 and the second network node operates in FR2, the UE monitors for a SIB1 PDCCH according to at least one of:

[0149] • determining a first set of candidate SIB1 PDCCH occasions from a pdcch- ConflgSIBl and K SSB in the UL WUS configuration, wherein the first set of candidates SIB1 PDCCH occasions includes all possible SIB1 PDCCH occasions over a first period of time,

[0150] • determining a second set of candidate SIB1 PDCCH occasions, wherein the second set of candidate SIB1 PDCCH occasions is a subset of the first set ofcandidate SIB1 PDCCH occasions such that the SIB1 PDCCH occasions in the second set of candidate SIB1 PDCCH occasions match the assistance information,

[0151] • monitoring the first or the second set of candidate SIB1 PDCCH occasions, wherein when the wireless device acquires SIB1 PDCCH in one of the occasions, the wireless device either stops monitoring or continues monitoring. In a particular embodiment, the first period of time is one of: 160ms, a SIB1 period according to the assistance information, a time until a next RACH occasion for UL WUS transmission, and / or a time until the next RACH occasion for UL WUS transmission after one SIB1 period has passed.

[0152] In a particular embodiment, based on not receiving SIB 1 from the second network node, the UE transmits an UL WUS with an on-demand SIB1 request to the second network node.

[0153] In a particular embodiment, the UE determines a monitoring window for SIB1 with a start time and a duration, and the method further includes determining a third set of candidate SIB1 PDCCH occasions from pdcch-ConflgSIB 1 and K SSB obtained in the UL WUS configuration. The third set of candidate SIB1 PDCCH occasions includes all possible SIB1 PDCCH occasions over a second period of time. The UE also determines a fourth set of candidate SIB1 PDCCH occasions. The fourth set of candidate SIB1 PDCCH occasions is a subset of the third set of candidate SIB1 PDCCH occasions such that the SIB1 PDCCH occasions in the third set of candidate SIB1 PDCCH occasions match the assistance information. The method further includes the UE monitoring the third set of candidate SIB1 PDCCH occasions or the fourth set of candidate SIB1 PDCCH occasions.

[0154] In a particular embodiment, the second period of time is one of: a SIB 1 monitoring time according to a start time and a duration, or a time from an UL WUS transmission to an end of a SIB1 monitoring time.

[0155] In a particular embodiment, the UL-WUS configuration comprises a parameter indicating whether the assistance information is valid only during an on-demand SIB1 acquisition procedure or during a time when the wireless device is camped on a cell.

[0156] In a particular embodiment, the UE monitors a RACH resource for transmission of an UL WUS for OD-SIB1 request, when a signal level above a noise floor is detected, the UE extends or adjusts a window duration for listening for a SIB1 and / or a RAR.

[0157] Example Method and Embodiments from Network PerspectiveFIGURE 6 illustrates an example method 500 by a network node for providing SIB1 on-demand, according to certain embodiments. As illustrated, the method includes a transmitting step 502 and an optional receiving step 504.

[0158] For example, according to certain embodiments, the method includes the network node sending / transmitting, at step 502, to a UE, an UL WUS configuration for requesting OD-SIB1 from a second network node. The UL WUS configuration includes assistance data for SIB1 acquisition from the second network node. In a particular embodiment, the first network node and the second network node are the same nodes. In another particular embodiment, the first network node and the second network node are different nodes.

[0159] Where the first and second network nodes are the same, if the UE does not acquire SIB1 from the second network node it proceeds to send an UL WUS with an on-demand SIB1 request to the second network node, which is then received by the network node at optional step 502. In this case the UE monitors for SIB1 PDCCH, at the occasions according to the assistance data, for a monitoring period defined by a starting time and duration, according to RANI agreements.

[0160] In a further particular embodiment, the UL WUS configuration includes assistance information for the UE monitoring of SIB1 PDCCH in the second network node. The assistance information including one or more of the following:

[0161] • SIB1 periodicity,

[0162] • SIB1 offset.

[0163] In a further particular embodiment, the SIB1 periodicity and / or offset may be expressed in units of milliseconds, frames, subframes, or SIB1 search space occasions. In one example, the periodicity and offset are expressed in relation to the system frame number (SFN), where Period, P, may have the range [2, 4, 6, 8, 16],

[0164] Offset, O, may have the range [0..P-1],

[0165] such that the UE can derive the SIB1 transmission occasions in the SFNs which satisfy the formula

[0166] SFN mod P = O

[0167] Alternatively, the SIB1 periodicity and / or offset may be expressed in relation to SSB burst periodicity and / or offset. For example, the SIB1 periodicity is twice the SSB periodicity or the SIB1 offset is the same as the SSB offset.

[0168] In a further particular embodiment, the UL WUS configuration includes assistance information for the UE monitoring of SIB1 PDCCH in the second network node. The assistanceinformation includes a bitinask / bitinap that is applicable to the prespecified / standardized SIB1 PDCCH occasions (i.e., SIB1 PDCCH search space). For example, within the NR’s SIB1 standardized periodicity of 160ms, there are eight potential occasions (every 20ms). A bitmap / bitmask of 8 bits could then be used, such that for example 10101010 would mean that the NW only broadcasts in every other occasion (i.e., every 40 ms), starting (offset) from the first occasion.

[0169] In a further particular embodiment, the NW further includes configuration parameter for whether the assistance information is valid only during the on-demand SIB1 acquisition procedure or also after (throughout the time the UE is camped on the cell). It is noted that if the parameter K SSB (obtained from PBCH in an SSB) takes other values than those mentioned above, then the UE monitors SIB1 PDCCH according to legacy functionality, in a particular embodiment.

[0170] In a further particular embodiment, a first network node provides UL WUS configuration for requesting OD-SIB 1 for multiple other network nodes. The first network node includes assistance data for SIB1 acquisition as a part of common or separate UL WUS configuration parameters, in various particular embodiments. For example, if the same assistance data for SIB1 acquisition is applicable for all the network nodes that can provide OD-SIB 1 with the assistance from the first network node, the assistance data for SIB1 acquisition can be provided as a part of common UL WUS configuration. Otherwise, if the same assistance data for SIB1 acquisition is not applicable for all the network nodes that can provide OD-SIB 1 with the assistance from the first network node, the assistance data for SIB1 acquisition can be provided as a part of separate UL WUS configuration.

[0171] FIGURE 7 illustrates a method 600 performed by a first network node for OD-SIB 1, according to certain embodiments. As illustrated, the method 600 begins at step 602 when the network node transmits, to a wireless device, a UL-WUS configuration for requesting an OD-SIB 1 from a second network node. The UL-WUS configuration includes assistance data for SIB1 acquisition from the second network node, and the assistance data includes SIB1 periodicity.

[0172] In a particular embodiment, the assistance data comprises SIB1 offset.

[0173] In a particular embodiment, the assistance information comprises a bitmask and / or bitmap that is applicable to at least one prespecified and / or standardized SIB1 PDCCH occasion.In a particular embodiment, the UL-WUS configuration includes a parameter indicating whether the assistance information is valid only during an on-demand SIB1 acquisition procedure or during a time when the wireless device is camped on a cell.

[0174] In a particular embodiment, the UL-WUS configuration comprises a configuration parameter indicating whether the assistance data may be used for monitoring for at least one SIB1 transmission for aNES cell even when the UE attempts to acquire SIB1 for the NES cell after transmitting an UL-WUS and / or throughout a period that the UE is camped on the NES cell.

[0175] FIGURE 8 shows an example of a communication system 704 in accordance with some embodiments.

[0176] In the example, the communication system 700 includes a telecommunications network 702 that includes an access network 704, such as a radio access network (RAN), and a core network 706, which includes one or more core network nodes 708. The access network 704 includes one or more access network nodes or base stations of various types, access network nodes 710A and 710B are depicted (which may be collectively referred to as network nodes 710), or any other similar 3rdGeneration Partnership Proj ect (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 704 may include more than one access network technology. The network nodes 710 of access network 704 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 712A, 712B, 712C, and 712D (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.

[0177] Moreover, 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 telecommunications network 702 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 702 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 network nodes to implement one or more functionalities of any network node in the telecommunications network 702, including one or more access network nodes 710 and / or core network nodes 708.

[0178] 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 anon-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node 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 0-2 interface defined by the 0-RAN Alliance or comparable technologies.

[0179] The network nodes 710 facilitate direct or indirect connection of one or more UEs 712 to the core network 706 over one or more wireless connections. 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 700 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 700 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0180] The UEs 712 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 710 and other communication devices. Similarly, the network nodes 708, 710 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 702) with the UEs 712 and / or with other network nodes or equipment in the telecommunications network 702 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 702. More specifically, UEs 712 may send messages, data, and / or other signals to network nodes 708, 710 or other elements of thetelecommunications network 702 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 708, 710 may send messages, data, and other signals to UEs 7122, other network nodes 708, 710, and other devices in telecommunications network 702 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 712 by transmitting the message to an access network node 710 that will then transmit the message to the intended UE 712. Similarly, a core network node 108 may receive a particular message from a UE 712 by receiving the message from an access network node 710 that itself received the message from the UE 712.

[0181] In the depicted example, the core network 706 connects elements of the access network 704 (e.g., one or more of the network nodes 710) to one or more host computing systems, such as host 716. 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 706 includes one or more core network nodes (e.g., core network node 708) of various types, one or more of which may be generally referred to as network nodes 708. Network nodes 708 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 708. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management 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).

[0182] The host 716 may be under the ownership or control of a service provider other than an operator or provider of the access network 704 and / or the telecommunications network 702. The host 716 may be operated by the service provider or on behalf of the service provider. The host 716 may host a variety of applications to provide one or more service. 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 withremote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0183] As a whole, the communication system 700 of FIGURE 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 700 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 (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 700 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 700 supporting different standards, protocols, or rule sets.

[0184] As one example, in certain embodiments, access network 704 may contain some access network nodes 710 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 710 support (or the same access network nodes 710 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 702 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 706 that supports multiple different standard generations or may include multiple access networks 704 and / or multiple core networks 106 with individual networks 704, 706 supporting different standard generations.

[0185] Telecommunications network 702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 702. For example, the telecommunications network 702 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)ZMassive loT services to yet further UEs.

[0186] In some examples, one or more of the UEs 712 are configured to transmit and / or receiveinformation without direct human interaction. For instance, a UE may be designed to transmit information to the access network 704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 704. 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).

[0187] In the example, the hub 714 communicates with the access network 704 to facilitate indirect communication between one or more UEs (e.g., UE 712C and / or 712D) and network nodes (e.g., network node 710B). In some examples, the hub 714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 714 may be a broadband router enabling access to the core network 706 for the UEs. As another example, the hub 714 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 710, or by executable code, script, process, or other instructions in the hub 714.

[0188] As another example, the hub 714 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 714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 714 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 714 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0189] The hub 714 may have a constant / persistent or intermittent connection to the network node 710B. The hub 714 may also allow for a different communication scheme and / or schedule between the hub 714 and UEs (e.g., UE 712C and / or 712D), and between the hub 714 and the core network 706. In other examples, the hub 714 is connected to the core network 706 and / or one or more UEs via a wired connection. Moreover, the hub 714 may be configured to connect to an M2M service provider over the access network 704 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 710 while still connected via the hub 714 via a wired or wireless connection. In someembodiments, the hub 714 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 71 OB. In other embodiments, the hub 714 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 71 OB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0190] FIGURE 9 is another example of a communication system 800 according to some embodiments. As used herein, the communication system 800 includes multiple access points (APs) 810 (with four exemplary APs 810A, 810B, 810C, and 810D being depicted) and multiple wireless devices, referred to in the context of communication system 800 as stations (STAs) 812 (referred to individually as STA 812A, STA 812B, STA 812C, STA 812D, and STA 812E). STA 812A is served by AP 810A in a first basic service set (BSS) 820A. STA 810B and STA 810C are served by AP 810B in a second BSS, BSS 820B. STA 812D is served by AP 810C in a third BSS, BSS 820C. STA 812E is served by AP 810D in a fourth BSS, BSS 820D. Stations 812 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 812 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0191] Each of STAs 812 may connect through a radio link to one of APs 810. For example, depending on location or channel conditions experienced by a given STA 812, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0192] Each AP 810 may provide data connectivity to STAs 812 connected to a particular AP 810. As illustrated, APs 810 may be connected to a data network 830. In this way, APs 810 may also provide data connectivity between STAs 812 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 812 and its serving AP 810 may be used for providing various kinds of services to STA 812, e.g., a voice service, a multimedia service, orother data service. Such services may be based on applications that are executed on STA 812 and / or on a device linked to STA 812. By way of example, FIGURE 9 illustrates an application service platform 832 provided in data network 830. The application(s) executed on STA 812 and / or on one or more other devices linked to STA 812 may use the radio link for data communication with one or more other STA 812 and / or the application service platform 832, thereby enabling utilization of the corresponding service(s) at STA 812.

[0193] FIGURE 10 shows a UE 900, which may be an embodiment of the UE 712 of FIGURE 8, 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-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.

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

[0195] The UE 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input / output interface 906, a power source 908, a memory 910, a communication interface 912, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 10. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multipleinstances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0196] The processing circuitry 902 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 910. The processing circuitry 902 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 902 may include multiple central processing units (CPUs).

[0197] In the example, the input / output interface 906 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 900. 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.

[0198] In some embodiments, the power source 908 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 908 may further include power circuitry for delivering power from the power source 908 itself, and / or an external power source, to the various parts of the UE 900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 908. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 908 to make the power suitable for the respective components of theUE 900 to which power is supplied.

[0199] The memory 910 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 910 includes one or more application programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916. The memory 910 may store, for use by the UE 900, any of a variety of various operating systems or combinations of operating systems.

[0200] The memory 910 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 910 may allow the UE 900 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 910, which may be or comprise a device-readable storage medium.

[0201] The processing circuitry 902 may be configured to communicate with an access network or other network using the communication interface 912. The communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922. The communication interface 912 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 918 and / or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 918 and receiver 920 may becoupled to one or more antennas (e.g., antenna 922) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0202] In the illustrated embodiment, communication functions of the communication interface 912 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-based communication 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 / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0203] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 912, 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).

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

[0205] A UE, when in the form of an Internet of Things (loT) 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 loT 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 voicecontrolled 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 for monitoring 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 loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 900 shown in FIGURE 10.

[0206] As yet another specific example, in an loT 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.

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

[0208] FIGURE 11 shows a network node 1000, which may be an embodiment of the network node 710 of FIGURE 8, in accordance with some embodiments.

[0209] 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 telecommunications network. In accordance with respective embodiments,network node 1000 may be configured to operate in communication system 700 of FIGURE 8, like network nodes 708 or 710, or in communication system 800 of FIGURE 9, like an AP 810 or a station 812. 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).

[0210] Network nodes 1000 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. Network node 1000 may be a relay node or a relay donor node controlling a relay. Network nodes 1000 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).

[0211] Other examples of network nodes 1000 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).

[0212] In particular embodiments, network node 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008. In general, in a particular embodiment of network node 1000, processing circuitry 1002, memory 1004, communication interface 1006, and power source 1008 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1000.

[0213] The network node 1000 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 1000 comprises multiple such entities (e.g., BTS and BSC), one or more of the separateentities 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 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1004 or portions of memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), 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 1000.

[0214] The processing circuitry 1002 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 logic operable to provide, either alone or in conjunction with other components, such as the memory 1004, to provide network node 1000 functionality.

[0215] In some embodiments, the processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 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 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.

[0216] The memory 1004 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 computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1002. The memory 1004 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 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 is integrated.

[0217] The communication interface 1006 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 1006 comprises port(s) / terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 900 may be capable of wireless communication and communication interface 1006 may also include radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, an antenna 1010. Particular embodiments of radio front-end circuitry 1018 include filter(s) 1020 and amplifier(s) 1022. The radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002. The radio front-end circuitry 1018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio frontend circuitry 1018 may convert the digital data into a radio signal (s) having the appropriate channel and bandwidth parameters using a combination of filters 1020 and / or amplifiers 1022. The radio signal(s) may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed to the processing circuitry 1002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0218] In certain alternative embodiments, network node 1000 may be capable of wireless communication but does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of adigital unit (not shown).

[0219] The antenna 1010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1010 may be coupled to the radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through one or more interfaces or ports.

[0220] The antenna 1010, communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 1000. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1000. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0221] The power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein. For example, the network node 1000 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 supplies power to power circuitry of the power source 1008. As a further example, the power source 1008 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.

[0222] Embodiments of the network node 1000 may include additional components beyond those shown in FIGURE 11 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 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000.FIGURE 12 is a block diagram illustrating a virtualization environment 1100 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 1100 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a 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 1100 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.

[0223] Applications 1102 (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.

[0224] Hardware 1104 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 1106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 1108A and VM 1108B (which may be collectively referred to as VMs 1108), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1106 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 1108.

[0225] The VMs 1108 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 1106. Different embodiments of the instance of a virtual appliance 1102 may be implemented on one or more of VMs 1108, 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 maybe 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.

[0226] In the context of NFV, each of the VMs 1108 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 1108, and that part of hardware 1104 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 of the VMs 1108 on top of the hardware 1104 and corresponds to an application 1102.

[0227] Hardware 1104 may be implemented in a standalone network node with generic or specific components. Hardware 1104 may implement some functions via virtualization. Alternatively, hardware 1104 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 1110, which, among others, oversees lifecycle management of applications 1102. In some embodiments, hardware 1104 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 1112 which may alternatively be used for communication between hardware nodes and radio units.

[0228] 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 the tasks, 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 boxeslocated 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.

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

[0230] EXAMPLE EMBODIMENTS

[0231] Group A Example Embodiments

[0232] Example Embodiment 1. A method performed by a wireless device for requesting on-demand SIB1 (OD-SIB1), the method comprising: receiving, from a first network node, an uplink wake-up signal (UL-WUS) configuration for requesting OD-SIB1 from a second network node.

[0233] Example Embodiment 2. The method of Example Embodiment 1 , wherein the UL-WUS comprises assistance data for SIB1 acquisition from the second network node.

[0234] Example Embodiment 3. The method of Example Embodiment 2, comprising: based on the assistance data, monitoring of SIB1 PDCCH.

[0235] Example Embodiment 4. The method of Example Embodiment 3, wherein monitoring of SIB1 PDCCH is performed during monitoring occasions for a monitoring period.

[0236] Example Embodiment 5. The method of any one of Example Embodiments 2 to 4, wherein the assistance data comprises at least one of: SIB1 periodicity, and SIB1 offset.Example Embodiment 6. The method of any one of Example Embodiments 2 to 5, wherein the assistance information comprises a bitmask / bitmap that is applicable to the prespecified and / or standardized SIB1 PDCCH occasions.

[0237] Example Embodiment 7. The method of any one of Example Embodiments 2 to 6, wherein the UL-WUS configuration comprises a parameter indicating whether the assistance information is valid only during an on-demand SIB1 acquisition procedure or during a time when the wireless device is camped on a cell.

[0238] Example Embodiment 8. The method of any one of Example Embodiments 1 to 7, wherein the first network node and the second network node are the same node.

[0239] Example Embodiment 9. The method of any one of Example Embodiments 1 to 7, wherein the first network node and the second network node are different nodes.

[0240] Example Embodiment 10. The method of any one of Example Embodiments 1 to 9, comprising monitoring for a RA response (RAR) to a UL WUS transmission in one or more RACH occasions though the wireless device has not transmitted the UL WUS transmission.

[0241] Example Embodiment 11. The method of Example Embodiment 10, wherein when a RAR is received and an associated preamble of the RAR is the same as a preamble given in the UL WUS configuration, the method comprises proceeding to OD-SIB1 acquisition of an upcoming OD-SIB1.

[0242] Example Embodiment 12. The method of Example Embodiment 11, comprising waiting for at least one TypeO-PDCCH CSS and at least one RAR resource and proceeding with an UL WUS if in both attempts no signal was detected.

[0243] Example Embodiment 13. The method of Example Embodiment 11, comprising waiting for at most one TypeO-PDCCH CSS or one RAR resource and proceeding with an UL WUS if no signal was detected.

[0244] Example Embodiment 14. The method of Example Embodiment 10, comprising: detecting an increased energy level in RAR though the RAR is not correctly detected, and adjusting a power of the UL WUS transmission.

[0245] Example Embodiment 15. The method of any one of Example Embodiments 1 to 14, comprising using at least one of the UL-WUS configuration, the assistance data, and the RA response to determine if SIB1 is being broadcasted or provided on-demand by the second network node.

[0246] Example Embodiment 16. The method of Example Embodiment 15, wherein determining if SIB1 is being broadcasted or provided on-demand by the second network nodecomprises checking a MIB / PBCH in an SSB.

[0247] Example Embodiment 17. The method of Example Embodiment 16, wherein when a parameter K_SSB>23 and the second network node operates in FR1 or if K_SSB>11 and the second network node operates in FR2, the method comprises monitoring for SIB1 PDCCH according to at least one of: determining a first set of candidate SIB1 PDCCH occasions from pdcch-ConfigSIBl and K SSB obtained in the UL WUS configuration, wherein the first set of candidates includes all possible SIB1 PDCCH occasions over a first period of time; determining a second set of candidate SIB1 PDCCH occasions, wherein the second set is the subset of the first set such that the SIB1 PDCCH occasions match the assistance information (i.e. SIB1 periodicity and offset); and monitoring the first or the second set of candidate SIB1 PDCCH occasions, wherein when the UE acquires SIB1 PDCCH in one of the occasions, the UE can either stop monitoring or continue monitoring.

[0248] Example Embodiment 18. The method of Example Embodiment 17, where the first period of time is one of: 160ms; a SIB1 period, according to the assistance information; a time until the next RACH occasion for UL WUS transmission; and / or a time until the next RACH occasion for UL WUS transmission after one SIB1 period has passed.

[0249] Example Embodiment 19. The method of any one of Example Embodiments 1 to 18, comprising: based on not receiving SIB1 from the second network node, transmitting an UL WUS with an on-demand SIB1 request to the second network node.

[0250] Example Embodiment 20. The method of Example Embodiment 19, comprising determining a monitoring window for SIB1 with a start time and a duration, and wherein the method further comprises: determining a third set of candidate SIB1 PDCCH occasions from pdcch-ConfigSIBl and K SSB obtained in the UL WUS configuration, wherein the third set includes all possible SIB1 PDCCH occasions over a second period of time; determining a fourth set of candidate SIB1 PDCCH occasions, wherein the fourth set is the subset of the third set such that the SIB1 PDCCH occasions match the assistance information (i.e. SIB1 periodicity and offset); monitoring the third or the fourth set of candidate SIB1 PDCCH occasions.

[0251] Example Embodiment 21. The method of Example Embodiment 20, wherein the second period of time is one of: a SIB1 monitoring time according to the start time and duration, or a time from UL WUS transmission to an end of the monitoring time.

[0252] Example Embodiment 22. The method of any one of Example Embodiments 1 to 21, wherein the UL-WUS configuration comprises a parameter indicating whether the assistanceinformation is valid only during an on-demand SIB1 acquisition procedure or during a time when the wireless device is camped on a cell.

[0253] Example Embodiment 23. The method of any one of Example Embodiments 1 to 22, comprising monitoring a RACH resource for transmission of UL WUS for OD-SIB1 request, and when a signal level above a noise floor is detected, extending or adjusting a window duration for listening for SIB1 and / or RAR.

[0254] Example Embodiment 24. The method of any one of Example Embodiments 1 to 23, comprising detecting an increased energy level in RAR and adjusting a power of the UL WUS transmission.

[0255] Group B Embodiments

[0256] Example Embodiment 25. A method performed by a first network node for on-demand SIB1 (OD-SIB1), the method comprising: transmitting, to a wireless device, an uplink wake-up signal (UL-WUS) configuration for requesting OD-SIB1 from a second network node.

[0257] Example Embodiment 26. The method of Example Embodiment 25, wherein the UL-WUS comprises assistance data for SIB1 acquisition from the second network node.

[0258] Example Embodiment 27. The method of any one of Example Embodiments 25 to 26, wherein the assistance data comprises at least one of: SIB1 periodicity; and SIB1 offset.

[0259] Example Embodiment 28. The method of any one of Example Embodiments 26 to 27, wherein the assistance information comprises a bitmask / bitmap that is applicable to the prespecified and / or standardized SIB1 PDCCH occasions.

[0260] Example Embodiment 29. The method of any one of Example Embodiments 26 to 28, wherein the UL-WUS configuration comprises a parameter indicating whether the assistance information is valid only during an on-demand SIB1 acquisition procedure or during a time when the wireless device is camped on a cell.

[0261] Example Embodiment 30. The method of any one of Example Embodiments 25 to 29, wherein the first network node and the second network node are the same node.

[0262] Example Embodiment 31. The method of any one of Example Embodiments 25 to 29, wherein the first network node and the second network node are different nodes.

[0263] Example Embodiment 32. The method of any one of Example Embodiments 25 to 31, wherein the UL-WUS configuration comprises a parameter indicating whether the assistance information is valid only during an on-demand SIB1 acquisition procedure or during a timewhen the wireless device is camped on a cell.

[0264] Group C Embodiments

[0265] Example Embodiment 33. A wireless device for requesting on-demand SIB1 (OD-SIB1), comprising: processing circuitry configured to perform any of the operations of any of the Group A embodiments; and a power source configured to supply power to the processing circuitry.

[0266] Example Embodiment 34. A network node for on-demand SIB1 (OD-SIB1), the network node comprising: processing circuitry configured to perform any of the operations of any of the Group B embodiments; a power source circuitry configured to supply power to the processing circuitry.

[0267] Example Embodiment 35. A wireless device for requesting on-demand SIB1 (OD-SIB1), the wireless device comprising: one or more antennas; communication interface connected to the one or more antennas and to processing circuitry; the processing circuitry being configured to perform any of the operations of any of the Group A embodiments; 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 interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the UE.

Claims

43CLAIMS1. A method (400) performed by a wireless device (712, 800) for requesting an on-demand System Information Block- 1, OD-SIB1, the method comprising:receiving (402), from a first network node (710, 900), an uplink wake-up signal, UL-WUS, configuration for requesting an OD-SIB1 from a second network node, the UL-WUS configuration comprising assistance data for System Information Block 1, SIB1, acquisition from the second network node, wherein the assistance data comprises SIB1 periodicity.

2. The method of Claim 1, comprising: based on the assistance data, monitoring of a SIB1 Physical Downlink Control Channel, PDCCH.

3. The method of Claim 2, wherein monitoring of the SIB1 PDCCH is performed during at least one monitoring occasion for a monitoring period.

4. The method of any one of Claims 1 to 3, wherein the assistance data comprises SIB1 offset.

5. The method of any one of Claims 1 to 4, wherein the assistance information comprises a bitmask and / or bitmap that is applicable to at least one prespecified and / or standardized SIB1 PDCCH occasions.

6. The method of any one of Claims 1 to 5, wherein the UL-WUS configuration comprises a configuration parameter indicating whether the assistance data may be used for monitoring for at least one SIB1 transmission even when the UE attempts to acquire SIB1 for the NES cell after transmitting an UL-WUS and / or throughout a period that the UE is camped on the cell.

7. The method of any one of Claims 1 to 6, comprising monitoring for a Random Access response, RAR, to an Uplink Wake-Up Signal, UL WUS, transmission in one or more Random Access Channel, RACH, occasions though the wireless device has not transmitted the UL WUS transmission.

448. The method of Claim 7, wherein when the RAR is received and an associated preamble of the RAR is the same as a preamble given in the UL WUS configuration, the method comprises proceeding to OD-SIB1 acquisition of an upcoming OD-SIB1.

9. The method of Claim 8, comprising:waiting for at least one TypeO-PDCCH Common Search Space, CSS, and at least one RAR resource; andproceeding with an UL WUS when no signal was detected in the TypeO-PDCCH CSS or the at least one RAR resource.

10. The method of Claim 8, comprising:waiting for at most one TypeO-PDCCH CSS or one RAR resource; and proceeding with an UL WUS when no signal was detected in the at most one TypeO-PDCCH CSS or the one RAR resource.

11. The method of Claim 7, comprising:detecting an increased energy level in RAR; andadjusting a power of an UL WUS transmission by the wireless device.

12. The method of any one of Claims 1 to 11, comprising using at least one of the UL-WUS configuration comprising the assistance data and a Random Access response, RAR, to determine if SIB1 is being broadcasted or provided on-demand by the second network node.

13. The method of any one of Claims 1 to 12, wherein determining if SIB1 is being broadcasted or provided on-demand by the second network node comprises checking a Master Information Block, MIB, and / or Physical Broadcast Channel, PBCH, in a Synchronization Signal Block, SSB.

14. The method of any one of Claims 1 to 13, wherein when a parameter K_SSB>23 and the second network node operates in Frequency Range 1, FR1, or when K_SSB>11 and the second network node operates in Frequency Range 2, FR2, the method comprises monitoring for a SIB1 Physical Downlink Control Channel, PDCCH, according to at least one of:45determining a first set of candidate SIB1 PDCCH occasions from a pdcch-ConflgSIB 1 and a T SSB in the UL WUS configuration, wherein the first set of candidates SIB1 PDCCH occasions includes all possible SIB1 PDCCH occasions over a first period of time, determining a second set of candidate SIB1 PDCCH occasions, wherein the second set of candidate SIB1 PDCCH occasions is a subset of the first set of candidate SIB1 PDCCH occasions such that the SIB1 PDCCH occasions in the second set of candidate SIB1 PDCCH occasions match the assistance information,monitoring the first or the second set of candidate SIB1 PDCCH occasions, wherein when the wireless device acquires SIB1 PDCCH in one of the occasions, the wireless device either stops monitoring or continues monitoring.

15. The method of Claim 14, wherein the first period of time is one of• 160ms,• a SIB1 period, according to the assistance information,• a time until a next Random Access Channel, RACH, occasion for UL WUS transmission, and / or• a time until the next RACH occasion for UL WUS transmission after one SIB1 period has passed.

16. The method of any one of Claims 1 to 15, comprising: based on not receiving SIB1 from the second network node, transmitting an UL WUS with an on-demand SIB1 request to the second network node.

17. The method of Claim 16, comprising determining a monitoring window for SIB1 with a start time and a duration, and wherein the method further comprises:determining a third set of candidate SIB1 PDCCH occasions from pdcch-ConflgSIB 1 and K SSB obtained in the UL WUS configuration, wherein the third set of candidate SIB1 PDCCH occasions includes all possible SIB1 PDCCH occasions over a second period of time, determining a fourth set of candidate SIB1 PDCCH occasions, wherein the fourth set of candidate SIB1 PDCCH occasions is a subset of the third set of candidate SIB1 PDCCH occasions such that the SIB1 PDCCH occasions in the third set of candidate SIB1 PDCCH occasions match the assistance information,monitoring the third set of candidate SIB1 PDCCH occasions or the fourth set of candidate SIB1 PDCCH occasions.

18. The method of Claim 17, wherein the second period of time is one of:a SIB1 monitoring time according to a start time and a duration, ora time from an UL WUS transmission to an end of a SIB1 monitoring time.

19. The method of any one of Claims 1 to 18, wherein the UL-WUS configuration comprises a parameter indicating whether the assistance information is valid only during an on-demand SIB1 acquisition procedure or during a time when the wireless device is camped on a cell.

20. The method of any one of Claims 1 to 19, comprising:monitoring a Random Access Channel, RACH, resource for transmission of an UL WUS for OD-SIB1 request; andwhen a signal level above a noise floor is detected, extending or adjusting a window duration for listening for a SIB1 and / or a Random Access Response, RAR.

21. A method performed by a first network node for on-demand System Information Block 1, OD-SIB1, the method comprising:transmitting, to a wireless device, an uplink wake-up signal, UL-WUS, configuration for requesting an OD-SIB1 from a second network node, the UL-WUS configuration comprising assistance data for System Information Block 1, SIB1, acquisition from the second network node, wherein the assistance data comprises SIB1 periodicity.

22. The method of Claim 21, wherein the assistance data comprises SIB1 offset.

23. The method of any one of Claims 21 to 22, wherein the assistance information comprises a bitmask and / or bitmap that is applicable to at least one prespecified and / or standardized SIB1 Physical Downlink Control Channel, PDCCH, occasion.

24. The method of any one of Claims 21 to 23, wherein the UL-WUS configuration comprises a parameter indicating whether the assistance information is valid only during an on-demand SIB1 acquisition procedure or during a time when the wireless device is camped on a cell.

25. The method of any one of Claims 21 to 23, wherein the UL-WUS configuration comprises a configuration parameter indicating whether the assistance data may be used for monitoring for at least one SIB1 transmission for a Network Energy Saving, NES, cell even when the UE attempts to acquire SIB1 for the NES cell after transmitting an UL-WUS and / or throughout a period that the UE is camped on the NES cell.

26. A wireless device for requesting on-demand System Information Block 1, OD-SIB1, comprising:processing circuitry configured to receive, from a first network node, an uplink wakeup signal, UL-WUS, configuration for requesting an OD-SIB1 from a second network node, the UL-WUS configuration comprising assistance data for System Information Block 1, SIB1, acquisition from the second network node, wherein the assistance data comprises SIB1 periodicity; anda power source configured to supply power to the processing circuitry.

27. The wireless device of Claim 26, wherein the processing circuitry is configured to perform any of the operations of any of Claims 2 to 20.

28. A network node for on-demand System Information Block 1, OD-SIB1, the network node comprising:processing circuitry configured to transmitting, to a wireless device, an uplink wake-up signal, UL-WUS, configuration for requesting an OD-SIB1 from a second network node, the UL-WUS configuration comprising assistance data for System Information Block 1, SIB1, acquisition from the second network node, wherein the assistance data comprises SIB1 periodicity; anda power source circuitry configured to supply power to the processing circuitry.

29. The network node of Claim 28, wherein the processing circuitry is configured to perform any of the steps of Claims 22 to 25.

Images