Supporting ondemand SIB1 signaling

Abstract

According to some embodiments, a method is performed by a wireless device in a wireless network. The method comprises obtaining a master information block (MIB) from a network node. The MIB comprises an indication that a cell allows on-demand transmission of system information comprising random access parameters for the cell. The method further comprises, based on the indication that the cell allows on-demand transmission of system information, transmitting a request for the transmission of the system information comprising random access parameters for the cell.

Description

SUPPORTING ONDEMAND SIB1 SIGNALINGTECHNICAL FIELD

[0001] The present disclosure generally relates to communication networks, and more specifically to support for on-demand system information block one (SIB 1) signaling.BACKGROUND

[0002] The Third Generation Partnership Project (3GPP) Release 19 Work Item entitled “Enhancements of network energy savings for NR,” RP-234065, December 2023, includes the following objective related to on-demand SIB1 transmission. The objective is to study procedures and signaling method(s) to support on-demand SIB1 for user equipment (UE) in idle / inactive mode, including: triggering method by uplink wake-up-signal using an existing signal / channel; wake-up-signal configuration provisioning to UE; and information exchange between gNBs at least for the configuration of wake-up signal, if necessary.

[0003] The master information block (MIB) includes the system information transmitted from the network on the broadcast channel (BCH). Below is the MIB information element (IE) in abstract syntax notation (ASN.l) format:

[0004] There is one spare bit available on the MIB that can be used for future purposes.

[0005] The IE PDCCH-ConfigSIBl (see IE below) within the MIB is used to configureCORESET#0 and search space#0.

[0006] The ssb-SubcarrierOffset described above within the MIB defines the 4 LSBs (LeastSignificant Bits) of the subcarrier offset (Kssb) with value range 0...11 in frequency range two (FR2) and 0...23 in frequency range one (FR1). For FR1, because 5 bits are needed to convey Kssb, a 5thbit is included in the physical broadcast channel (PBCH) payload. Whether a cell contains SIB1 (i.e., remaining minimum system information (RMSI) or TypeO-PDCCH common search space (CSS)) is given by ssb-SubcarrierOffset. Only if ssb-SubcarrierOffset < 24 (for FR1) or ifssb-SubcarrierOffset < 12 (for FR2), the pdcch-ConfigSIBl indicates the physical downlink control channel (PDCCH) configuration for SIB1 reception on the same cell (see 3GPP 38.211, section 7.4.3.1).

[0007] If a SIB1 is not transmitted in a cell, the existing specifications state that a UE shall treat a cell not providing SIB1 as barred. The UE shall: l>if in RRC IDLE or in RRC INACTIVE or in RRC CONNECTED while T311 is running:2> if the UE is unable to acquire theATZS:2>else if the UE is unable to acquire the SIBT.3>consider the cell as barred in accordance with TS 38.304;

[0008] There currently exist certain challenges. For example, there are scenarios in which a UE may enter a cell in which no SIB1 is provided. However, it is unclear how a UE can be made aware of whether the cell may provide SIB1 based on OnDemand (wake-up-signal) signaling and how to distinguish such cell from a legacy scenario in which SIB1 is not transmitted where no OnDemand signaling is supported / allowed.SUMMARY

[0009] As described above, certain challenges currently exist with on-demand system information block one (SIB1) signaling. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, for a cell not providing SIB1, particular embodiments facilitate informing a user equipment (UE) that on-demand SIB1 signaling is supported / allowed. Some embodiments inform the UE from which other carriers / cells the UE may acquire the wake-up signal (OnDemand signaling) configuration.

[0010] Particular embodiments include information in a cell’s synchronization signal block (SSB) master information block (MIB) based on which the UE can deduce whether OnDemand SIB1 request (Wake-up Signaling) is supported by the cell. Particular embodiments include methods in a network node for which cells may omit SIB1 transmission, and UEs may request transmission of SIB1 when required.

[0011] In particular embodiments, the information about the SIB1 OnDemand signaling support is provided as part of the MIB. The OnDemand SIB1 support may be indicated via any one or more of ssb-SubcarrierOffset (including Kssb deduced from ssb-SubcarrierOffset), and / or spare bit of the MIB.

[0012] In particular embodiments, a value for Kssb (deduced from SubcarrierOffset) above 23 in frequency range one (FR1), and above 11 in frequency range two (FR2) is used for indicating support for OnDemand SIB1. In particular embodiments, a Kssb reserved value (30 in FR1, and 14 in FR2) is used for indicating OnDemand SIB1 support.

[0013] In particular embodiments, a spare bit of the MIB indicates support for OnDemand SIB1.

[0014] In particular embodiments, based on the OnDemand support, the UE may use a wake up signal (WUS) (to request OnDemand SIB1) signaling configuration obtained / acquired from same cell / another cell.

[0015] In particular embodiments, the combination of the MIB spare bit, and Kssb / SubcarrierOffset is used for indicating from which cell / carrier the UE may acquire the WUS configuration. The combination of the MIB spare bit, and Kssb / SubcarrierOffset may be used such that if the spare bit indicates support for OnDemand SIB1 signaling, the Kssb / SubcarrierOffset values (values of tables 13-16 for FR1, and 13-17 for FR2 above) are interpreted as where the UE may find other carrier / cells where the configuration for OnDemand SIB1 (WUS) may be found. The WUS configuration may, e.g., be any type of uplink signal / message configuration such as WUS preamble / physical random access channel (PRACH) configuration / indices, etc.

[0016] The combination of the Kssb / SubcarrierOffset and PDCCH-ConfigSIBl may be used such that if the Kssb / SubcarrierOffset reserved value indicates support for OnDemand SIB1 signaling, then the PDCCH-ConfigSIBl values (values of tables 13-3 to 13-10) are interpreted as where the UE may find other carrier / cells where the configuration for OnDemand SIB1 (WUS) may be found.

[0017] In particular embodiments, some combinations of the Kssb / SubcarrierOffset values (values of tables 13-16 for FR1, and 13-17 for FR2 above) are kept in their original form such that it is possible to indicate also to these UEs if the cell is barred already on MIB level.

[0018] In particular embodiments, the cellBarred field in the MIB is used as part of the condition for indicating to UEs supporting a newer release (e.g., Rel-19) that SIB1 can be obtained on demand, and after SIB1 is obtained the UEs of the newer release shall not consider the cell to be barred, while signaling to UEs of a legacy release (e.g., Rel-18 or older) that the cell is barred for them. In addition to the cellBarred bit (set to value “barred”), UEs of a newer release may also check that an additional field or combination of fields in the MIB indicates a reserved or invalid value or value combination, e.g. pdcch-ConfigSIBl or its components (controlResourceSetZero, searchSpaceZero) is indexing a reserved value, etc.

[0019] In particular embodiments, the combination of the Kssb / SubcarrierOffset and at least one of subCarrierSpacingCommon / dmrs-TypeA-Position is used such that if the Kssb / SubcarrierOffset reserved value indicates support for OnDemand SIB1 signaling, the at least one of subCarrierSpacingCommon / dmrs-TypeA-Position values are interpreted as where the UE may find other carrier cells where the configuration for OnDemand SIB1 (WUS) may be found.

[0020] In particular embodiments, a set of WUS configuration may be predefined and programed in the UEs of the newer release. If the Kssb / SubcarrierOffset reserved value indicates support for OnDemand SIB1 signaling, at least one of the subCarrierSpacingCommon / dmrs- TypeA-Position values and the PDCCH-ConfigSIBl values are interpreted as the configuration the UE should use for WUS.

[0021] In particular embodiments, a set of WUS configurations may be predefined and programed in the UEs of the newer release. The combination of the MIB spare bit, and Kssb / SubcarrierOffset is used such that if the spare bit indicates support for OnDemand SIB1 signaling, the Kssb / SubcarrierOffset values are interpreted as the configuration the UE should use for WUS.

[0022] In particular embodiments, if the spare bit is used for indicating support for OnDemand SIB1, the UEs of the newer release shall not consider the cell to be barred, while signaling to UEs of a legacy release (e.g., Rel-18 or older) that the cell is barred for them.

[0023] In particular embodiments, if the UE is not operating on shared spectrum, then the field subCarrierSpacingCommon and least significant bit (LSB) of the ssb-SubcarrierOffset may be used alternatively to indicate the cell is barred or the onDemandSIBl support.

[0024] According to some embodiments, a method is performed by a wireless device (e.g., UE) in a wireless network. The method comprises obtaining a MIB from a network node (e.g., gNB). The MIB comprises an indication that a cell allows on-demand transmission of system information comprising random access parameters for the cell (e.g., SIB1). The method further comprises, based on the indication that the cell allows on-demand transmission of system information, transmitting a request (e.g., WUS) for the transmission of the system information comprising random access parameters for the cell (e.g., SIB1).

[0025] In particular embodiments, the indication is provided via one or more of a SSB subcarrier offset and a spare bit in the MIB.

[0026] In particular embodiments, the indication is provided via an index value derived from the synchronization signal block (SSB) subcarrier offset that is above 23 for FR1 or above 11 for FR2.

[0027] In particular embodiments, the indication is provided via an index value derived from the SSB subcarrier offset that is equal to value 30 for FR1 or equal to value 14 for FR2.

[0028] In particular embodiments, the method further comprises acquiring a resource configuration comprising a configuration of resources to use for transmitting the request for the transmission of the system information.

[0029] In particular embodiments, a combination of a spare bit and a SSB subcarrier offset in the MIB indicates from which cell or carrier the wireless device is to acquire the resource configuration.

[0030] In particular embodiments, the spare bit in the MIB indicates the cell allows on- demand transmission of system information and the SSB subcarrier offset indicates from which cell or carrier the wireless device is to acquire the resource configuration.

[0031] In particular embodiments, the SSB subcarrier offset indicates the cell allows on- demand transmission of system information and a PDCCH configuration in the MIB indicates from which cell or carrier the wireless device is to acquire the resource configuration.

[0032] In particular embodiments, the SSB subcarrier offset indicates the cell allows on- demand transmission of system information and one of a subcarrier spacing field and a DMRS position field indicates from which cell or carrier the wireless device is to acquire the resource configuration.

[0033] In particular embodiments, the indication is provided via a cell barred field in the MIB.

[0034] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above.

[0035] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above.

[0036] According to some embodiments, a method is performed by a network node (e.g., gNB) in a wireless network. The method comprises transmitting a MIB comprising an indication that a cell allows on-demand transmission of system information comprising random access parameters for the cell (e.g., SIB1) and receiving a request (e.g., WUS) from a wireless device (e.g., UE) for transmission of the system information comprising random access parameters for the cell (e.g., SIB1).

[0037] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0038] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above.

[0039] Certain embodiments may provide one or more of the following technical advantages. For example, according to particular embodiments a UE (e.g., wireless device) entering a cell may determine whether the cell supports OnDemand SIB1. Furthermore, legacy UEs are not confused by the signaling and new UEs will know whether they have entered a legacy or new network.BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The present disclosure may be best understood by way of example with reference to the following description and accompanying drawings that are used to illustrate embodiments of the present disclosure. In the drawings:Figure 1 is a flowchart illustrating an example method performed by a user equipment (UE), according to particular embodiments;Figure 2 shows an example of a communication system, according to certain embodiments;Figure 3 shows a UE, according to certain embodiments;Figure 4 shows a network node, according to certain embodiments;Figure 5 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;Figure 6 is a flowchart illustrating an example method in a wireless device, according to certain embodiments; andFigure 7 is a flowchart illustrating an example method in a network node, according to certain embodiments.DETAILED DESCRIPTION

[0041] As described above, certain challenges currently exist with on-demand system information block one (SIB 1) signaling. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, for a cell not providing SIB1, particular embodiments facilitate informing a user equipment (UE) that on-demand SIB1 signaling is supported / allowed. Some embodiments inform the UE from which other carriers / cells the UE may acquire the wake-up signal (OnDemand signaling) configuration.

[0042] Particular embodiments are 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.

[0043] Particular embodiments include information in a cell’s master information block (MIB) (part of a synchronization signal block (SSB)), based on which a UE may deduce whether an OnDemand SIB1 request (i.e., wake-up signaling) is supported by the cell. The information about OnDemand SIB1 support is conveyed via the MIB of the SSB.

[0044] As described above, whether a cell contains SIB1 (i.e., remaining minimum system information (RMSI) or TypeO-PDCCH common search space (CSS)) is given by ssb- SubcarrierOffset. Only if ssb-SubcarrierOffset < 24 (for frequency range one (FR1)) or if ssb- SubcarrierOffset < 12 (for frequency range two (FR2)), the pdcch-ConfigSIBl indicates the physical downlink control channel (PDCCH) configuration for SIB1 reception on the same cell (see 3GPP 38.211, section 7.4.3. 1). This means that for ssb-SubcarrierOffset, values 24...31 in FR1, and values 12...15 in FR2 are available for other purposes as described in 3GPP 38.213, section 13, vl8.1.0 (Tables 13-16, and 13-17 shown below). These tables may be used for specifying a range of global synchronization channel number (GSCN) offsets where a UE may potentially find other SSBs with an associated SIB1. Certain values are not used (e.g., Kssb=30 in FR1 and Kssb=14 in FR2), and Kssb = 31 in FR1 and Kssb = 15 in FR2 are used to indicate that there is no SIB1 for the UE (i.e., there is no pointer to any other SSBs providing SIB1 either).Table 13-16: Mapping between the combination of fcSSBand controlResourceSetZero andTable 13-17: Mapping between the combination of fcSSBand controlResourceSetZero and

[0045] In one aspect, the OnDemand SIB1 support is indicated via the Kssb / ssb- SubcarrierOffset. In some embodiments, the currently reserved values (30 in FR1, and 14 in FR2) of Kssb are used for indicating OnDemand SIB1 support. If the Kssb indicates one of these values, the UE then understands that OnDemand SIB1 signaling is supported.

[0046] In a related aspect, the OnDemand SIB1 support is indicated via a combination of the Kssb / ssb-SubcarrierOffset, and PDCCH-ConfigSIBl. If the Kssb / ssb-SubcarrierOffset is used to indicate the support for OnDemand SIB1 signaling, the PDCCH-ConfigSIBl values of the tables 13-3 to 13-10 in 38.213 are reinterpreted to indicate the SSB location from which the WUS configuration may be obtained. Alternatively, further details on how SIB1 may be requested or other aspects how the cell is configured / behaving, for example, details on the wakeup signal (WUS) configuration, may be associated with the PDCCH-ConfigSIBl values.

[0047] In some embodiments, certain combinations of the Kssb / ssb-SubcarrierOffset, and PDCCH-ConfigSIBl are used for the purpose of the OnDemand SIB1 support, and certain combinations still indicate that SIB1 is not available (directly nor via on-demand) and the UE considers the cell barred. This preserves the option to still bar the cell on this level of system information signaling for the UEs supporting Rel-19 OnDemandSIB 1. In some embodiments, when the UE is not operating on shared spectrum, then the field subCarrierSpacingCommon and the least significant bit (LSB) of the ssb-SubcarrierOffset may be used alternatively to indicate the cell is barred or the onDemandSIB 1 support. Alternatively, the LSB of ssb-SubcarrierOffset indicates the support of OnDemandSIB 1, if the bit is set to 1, it indicates the support and if the bit is set to 0 it indicates OnDemandSIB 1 is not supported. This may be regardless of shared spectrum or not.

[0048] In another aspect, the OnDemand SIB1 support is indicated via a spare bit of the MIB, e.g. by setting the bit to 1 the UE then knows that OnDemand SIB1 signaling is supported.

[0049] In another aspect, the OnDemand SIB1 support is indicated via a combination of the Kssb / ssb-SubcarrierOffset, and a spare bit of the MIB. If the spare bit is used to indicate the supportfor OnDemand SIB1 signaling, the Kssb values of the tables (tables 13-16 for FR1, and 13-17 for FR2 above) are reinterpreted to indicate the SSB location from which the WUS configuration can be obtained. Alternatively, further details on how SIB1 may be requested or other aspects how this cell is configured / behaving, for example, details on the WUS configuration, may be associated with the Kssb / ssb-SubcarrierOffset values. Particular embodiments are described in more detail by considering the following scenarios and steps below.

[0050] One example scenario includes at least two cells, Cell 1 and Cell 2, where Cell 1 provides OnDemand SIB1 and Cell 2 provides WUS configuration for Cell 1.

[0051] In some embodiments, a UE may determine the nearest (in the corresponding frequency direction) global synchronization channel number (GSCN) of a synchronization signal (SS) / physical broadcast channel (PBCH) block having a core resource set (CORESET) for an associated TypeO-PDCCH CSS that provides the SIB1 that consists of WUS information for the OnDemand SIB1 request. In particular embodiments, a UE derives the above mentioned GSCN using any of the following information.• $$\ SubcarrierOffset,' or• $$\ SubcarrierOffset and spare bit in the MIB of NR; or• $$\ SubcarrierOffset and dmrs-TypeA-Position, or• $$\ SubcarrierOffset and any other parameter in MIB

[0052] The following example consists of steps for determining GSCN position for SS / PBCH block having a CORESET for an associated TypeO-PDCCH CSS that provides the SIB1 that consists of WUS information for the OnDemand SIB1 request.

[0053] Figure 1 is a flowchart illustrating an example method performed by a UE, according to particular embodiments. The illustrated example considers ssb-SubcarrierOffset.^nA spare bit in the MIB of New Radio (NR), however any other available parameter in MIB of the current cell, or an indicator potentially configured via another cell, may be used as an indicator. In the example below, Kssb 30 or 14 are example values applicable to FR1 and FR2, respectively.

[0054] Step 0: UE detects a Cell 1 SS / PBCH block and determines that a CORESET for TypeO-PDCCH CSS set is not present.

[0055] Step 1: UE determines the value of kssB of the Cell 1 based on ssb-SubcarrierOffset. If the kssB is 30 or 14, the UE determines the offset to GSCN (Alg^1) with respect to SSB of the Cell 1 (cell that provides OnDemand SIB1).

[0056] Step2: UE obtains ^SCN1using 16 controlResourceSetZero + searchSpaceZero, where controlResourceSetZero is determined from 4 MSB bits of pdcch-configSIB 1 and searchSpaceZero is determined from 4 LSB bits of pdcch-configSIB 1. This step is same as inlegacy. If the pdcch-configSIBl is 00010011, using 16 controlResourceSetZero +searchSpaceZero is 19. If the pdcch-configSIBl is 10010111, Al®^1using 16 controlResourceSetZero + searchSpaceZero is 152.

[0057] Step 3: UE obtains A^CN11using equation Alg^11= N2 * Alg^1, where N2 value is determined based on one or more conditions.

[0058] In one example, N2 value is obtained by considering the spare bit in MIB for deriving the value of N2. If the spare bit in MIB is 0, N2 may be 1 or 2 or 3 or based on one or more conditions. In one example N2 is 3 for FR1 and N2 is 1 for FR2. In other example, depending on the band of operation, N2 is 1 or 2 or 3 based on the band of the Cell 1, which may be specified in a specification.

[0059] If the spare bit in MIB is 1, obtainmay be 1 or 2 or 3 or based on one or more conditions. In one example N2 is 3 for FR1 and N2 is 1 for FR2. In other example, depending on the band of operation, N2 is 1 or 2 or 3 based on the band of the Cell 1, which may be specified in specification.

[0060] In one example, the N2 value is obtained without considering the spare bit in MIB for deriving the value of N2. In one example, N2 may be -0.5 if the Alg^1is below 128 and +0.5 otherwise. In one example, N2 may be -1 if the A^CN1is below 128 and +1 otherwise. In one example, N2 may be -2 if theis below 128 and +2 otherwise. In one example, N2 may be -3 if the Alg^N1is below 128 and +3 otherwise. In one example, N2 may be -XI if the Alg^1is below 128 and +X1 otherwise, where XI may be based one or more conditions mentioned in the specification.

[0061] In one example, the N2 value is obtained by considering other parameters such as subCarrierSpacingCommon for deriving the value of N2. In one example, N2 may be -XI or +X1 based on the value of subCarrierSpacingCommon, where XI is determined based on one or more conditions mentioned in a specification.

[0062] In one example, the N2 value is obtained by considering other parameters such as dmrs-TypeA-Position for deriving the value of N2. In one example, N2 may be -XI or +X1 based on the value of dmrs-TypeA-Position. Where XI is determined based on one or more conditions mentioned in a specification.

[0063] In one example, the N2 value is obtained by considering any other parameters in the MIB and the value may be -XI or +X1 based on the configuration values of such parameter.

[0064] Step 4: the UE may determine the nearest (in the corresponding frequency direction) global synchronization channel number (GSCN) of a Cell 2 SS / PBCH block having a CORESETfor an associated TypeO-PDCCH CSS which provides WUS set as N^cfence+ ^GSCN ’ S N11- = 1 in FR1 and FR2-1,

[0065] In some embodiments, the UE obtains information from another cell. In such cases, the UE may, for example, redefine and / or ignore some of the fields in the MIB. For example, UEs of a legacy release (e.g., Rel 18 or older) may think the cell is barred, but UEs of a newer release (e.g., Rel-19 or newer) ignore the ’’cellBarred” bit. The cellBarred bit set to “barred” may then be used as part of the condition for telling the Rel-19 UE that SIB 1 may be made available on demand. Some embodiments may specify an OnDemandSIBl -indication based on the “barred” bit and have an additional field or combination of fields in the MIB indicating a reserved or invalid value or value combination. There are, e.g., several of reserved value entries in the tables defining the component values of pdcch-ConfigSIBl (i.e., controlResourceSetZero, searchSpaceZero) that may be used for this purpose.

[0066] In some embodiments, the UE obtains WUS information related to OnDemand SIB1 of one cell (e.g., Cell 1) from another cell (e.g., Cell 2). In one example, if a reserved value of Kssb (e.g. 30 for FR1, 14 for FR2) is used to indicate OnDemand SIB1 operation for cell 1, some of the fields in the MIB of cell 1 may be repurposed. For example, the fields such as subCarrierSpacingCommon, dmrs-TypeA-Position may be repurposed to indicate information regarding where (on which other carrier) the UE may find information / other cells where the configuration for OnDemand SIB1 (WUS) may be found.

[0067] Additional combinations of the spare bit of the MIB, Kssb / ssb-SubcarrierOffset, PDCCH-ConfigSIBl, and the “barred” bit may be used to convey the on-demand SIB1 support and the source of WUS configuration information.

[0068] In some embodiments, if the cell / carrier / beam supports on demand SIB1 broadcast, cellBarred parameter in the MIB is set to barred so that legacy UEs are not allowed to camp in the cell / carrier / beam, while for UEs that support on demand SIB1 broadcast whether camping is possible depends the configuration of Kssb / SubcarrierOffset, i.e., if Kssb / SubcarrierOffset indicates support for on demand SIB1 broadcast in a value that is reserved from legacy UEs’ point of view. Otherwise, the cell / carrier / beam will also be barred for UEs that support on demand SIB1 broadcast. If the configuration of Kssb / SubcarrierOffset indicates on demand SIB1 broadcast, the parameter PDCCH-ConfigSIBl provides the configuration for SIB1 broadcast when it is triggered.

[0069] For parameter ssb-SubcarrierOffset, the values of codepoints 24 to 29 in FR1 (because value 30 is reserved and value 31 indicates “no SIB1”), and values of codepoints 12 and 13 in FR2 (because value 14 is reserved and value 15 indicates “no SIB1”) are used to indicate a single or aset of preambles to be transmitted to wake up the gNB to trigger SIB1 broadcast. The new assignment of these codepoints may be indicated using the spare bit in MIB. When the spare bit in the MIB is used to indicate the new assignment of these codepoints, the reserved value for FR1, i.e., 30 or the reserved value for FR2, i.e., 14, may also be included. In some embodiments, each codepoint indicates a single or a set of preambles (that do not overlap with the preamble(s) indicated by other codepoint) that a UE may use to trigger SIB1 broadcast. The preamble(s) associated with each codepoint is specified in the specifications. In some embodiments, only a single or subset of the reserved codepoints are used to indicate the preamble(s) that is / are configured semi-statistically by the network to trigger SIB1 broadcast when requested.

[0070] In some embodiments, only the reserved value for FR1, i.e., 14, or reserved value for FR2, i.e., 30, is used to indicate that a preamble needs to be transmitted to trigger the network for SIB1 broadcast. In that case, a preamble or a set of preambles that can be used are specified in the specifications.

[0071] In another embodiment, instead of indicating a preamble(s), a codepoint indicates that the network supports / enables the transmission of a wake-up signal to trigger SIB1 broadcast. In that case, a wakeup signal may be designed explicitly and specified in the specifications.

[0072] The network may update / enable / disable the configuration for the wake-up signal, e.g., preamble or any other dedicated signal transmission to trigger SIB1 broadcast. To make sure that the UE uses the wake-up signal when enabled or uses the right preamble, UEs that support this feature and camped in the cell / carrier / beam may be required to check MIB before triggering SIB1 broadcast.

[0073] If the UE does not find a cell that provides OnDemand SIB1 (WUS) configuration for the cell (the cell not providing SIB1), according to the indication provided by, or deduced from, one or more parameters of the cell’s SSB MIB, the UE can proceed searching for other cells providing OnDemand SIB1 (WUS) configuration for the cell, e.g., on other frequencies, different from the indicated frequencies. In one example, the UE may not find a WUS- configurationproviding cell according to the indication due to UE capabilities, e.g., because it does not support the indicated frequency band(s). In another example, the UE may not find a WUS- configurationproviding cell according to the indication due to insufficient coverage on the indicated frequency band(s), locally (at the UE’s location) and / or temporarily (at the given time), e.g., as per current network configuration like coverage and capacity optimization (CCO).

[0074] Figure 2 shows an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and acore network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

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

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

[0077] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and 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 ExposureFunction (NEF), and / or a User Plane Function (UPF).

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

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

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

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

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

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

[0084] Figure 3 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, 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.

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

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

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

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

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

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

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

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

[0093] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-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.

[0094] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports thesensed 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).

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

[0096] 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 voice controlled smart speaker, a home security camera, amotion detector, a thermostat, asmoke detector, adoor / 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 itemtracking 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 200 shown in Figure 2.

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

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

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

[0100] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units 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).

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

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

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

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

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

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

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

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

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

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

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

[0112] Figure 5 is a block diagram illustrating a virtualization environment 500 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 morevirtual 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 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0113] Applications 502 (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.

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

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

[0116] In the context of NFV, a VM 508 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 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502.

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

[0118] 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 boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

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

[0120] FIGURE 6 is a flowchart illustrating an example method 600 in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 6 may be performed by UE 200 described with respect to FIGURE 3.

[0121] The method 600 begins at step 612, where the wireless device (e.g., UE 200) obtains a MIB from a network node. The MIB comprises an indication that a cell allows on-demand transmission of system information comprising random access parameters for a cell (e.g., SIB 1 ).

[0122] In particular embodiments, the indication is provided via one or more of a SSB subcarrier offset and a spare bit in the MIB.

[0123] In particular embodiments, the indication is provided via an index value derived from the synchronization signal block (SSB) subcarrier offset that is above 23 for FR1 or above 11 for FR2.

[0124] In particular embodiments, the indication is provided via an index value derived from the SSB subcarrier offset that is equal to value 30 for FR1 or equal to value 14 for FR2.

[0125] In particular embodiments, the indication is provided via a cell barred field in the MIB.

[0126] In particular embodiments, the indication is provided according to any of the embodiments and examples described herein.

[0127] At step 614, the wireless device may acquire a resource configuration comprising a configuration of resources to use for transmitting the request for the transmission of the system information.

[0128] In particular embodiments, a combination of a spare bit and a SSB subcarrier offset in the MIB indicates from which cell or carrier the wireless device is to acquire the resource configuration.

[0129] In particular embodiments, the spare bit in the MIB indicates the cell allows on- demand transmission of system information and the SSB subcarrier offset indicates from which cell or carrier the wireless device is to acquire the resource configuration.

[0130] In particular embodiments, the SSB subcarrier offset indicates the cell allows on- demand transmission of system information and a PDCCH configuration in the MIB indicates from which cell or carrier the wireless device is to acquire the resource configuration.

[0131] In particular embodiments, the SSB subcarrier offset indicates the cell allows on- demand transmission of system information and one of a subcarrier spacing field and a DMRS position field indicates from which cell or carrier the wireless device is to acquire the resource configuration.

[0132] In particular embodiments, the indication from which cell or carrier the wireless device is to acquire the resource configuration comprises an explicit indication of a cell identifier or a carrier identifier. In other embodiments, the indication may be less specific and may indicate that the wireless device may look elsewhere for a cell identifier or a carrier identifier, or the wireless device may use a default or preconfigured cell or carrier.

[0133] In particular embodiments the wireless device may acquire the resource configuration according to any of the embodiments and examples described herein.

[0134] At step 616, the wireless device based on the indication that the cell allows on-demand transmission of system information, transmits a request (e.g., WUS) for the transmission of the system information comprising random access parameters for the cell (e.g., SIB1).

[0135] Modifications, additions, or omissions may be made to method 600 of FIGURE 6. Additionally, one or more steps in the method of FIGURE 6 may be performed in parallel or in any suitable order.

[0136] FIGURE 7 is a flowchart illustrating an example method 700 in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 7 may be performed by network node 300 described with respect to FIGURE 4.

[0137] The method 700 begins at step 712, where the network node (e.g., network node 300) transmits a MIB comprising an indication that a cell allows on-demand transmission of system information comprising random access parameters for a cell (e.g., SIB1). The MIB and the indication are described in more detail with respect to step 612 of FIGURE 6.

[0138] At step 714, the network node receives a request (e.g., WUS) from a wireless device for transmission of the system information comprising random access parameters for the cell (e.g., SIB1). The network node may receive the request according to any of the embodiments and examples described herein.

[0139] Modifications, additions, or omissions may be made to method 700 of FIGURE 7. Additionally, one or more steps in the method of FIGURE 7 may be performed in parallel or in any suitable order.

[0140] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

[0141] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

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

[0143] Some example embodiments are described below.Group A Embodiments1. A method performed by a wireless device in a wireless network, the method comprising:- obtaining a master information block (MIB) from a network node, the MIB comprising an indication that the wireless network supports OnDemand SIB1 signaling; and- based on the indication that the wireless network supports OnDemand SIB1 signaling, transmitting a wake-up signal (WUS) to request SIB1.2. The method of the previous embodiment, wherein the OnDemand SIB1 support is indicated via any one or more of ssb-SubcarrierOffset (incl Kssb deduced from it), and / or spare bit of the MIB.3. The method of any one of the previous embodiments, wherein a value for Kssb (deduced from SubcarrierOffset) is above 23 in FR1, and above 11 in FR2 is used for indicating support for OnDemand SIB1.4. The method of any one of the previous embodiments, wherein a Kssb reserved value (30 in FR1, and 14 in FR2) is used for indicating OnDemand SIB1 support.5. The method of any one of the previous embodiments, wherein a spare bit of the MIB is used for indicating support for OnDemand SIB1.6. The method of any one of the previous embodiments, further comprising acquiring a WUS configuration for transmitting the WUS.7. The method of the previous embodiment, wherein the combination of the MIB spare bit, and Kssb / SubcarrierOffset is used for indicating from which cell / carrier the UE may acquire the WUS configuration.8. The method of embodiment 6, wherein the combination of the MIB spare bit, and Kssb / SubcarrierOffset is used such that if the spare bit indicates support for OnDemand SIB1 signaling, the Kssb / SubcarrierOffset values are interpreted as where the wireless device may find other carrier / cells where the WUS configuration for OnDemand SIB1 may be found.9. The method of embodiment 6, wherein the combination of the Kssb / SubcarrierOffset and PDCCH-ConfigSIBl is used such that if the Kssb / SubcarrierOffset reserved value indicates support for OnDemand SIB1 signaling, and the PDCCH-ConfigSIBl values are interpreted as where the wireless device may find other carrier / cells where the WUS configuration for OnDemand SIB1 may be found.10. The method of any one of the previous embodiments, wherein a cellBarred field in the MIB is used as part of the condition for indicating to wireless devices supporting a newer release (e.g. Rel-19) that SIB1 can be obtained on demand, and after SIB1 is obtained the wireless device of the newer release shall not consider the cell to be barred, while signaling to wireless devices of a legacy release (e.g. Rel-18 or older) that the cell is barred for them.11. The method of embodiment 6, wherein the combination of the Kssb / SubcarrierOffset and at least one of subCarrierSpacingCommon / dmrs-TypeA-Position is used such that if theKssb / SubcarrierOffset reserved value indicates support for OnDemand SIB1 signaling, the at least one of subCarrierSpacingCommon / dmrs-TypeA-Position values are interpreted as where the wireless device may find other carrier cells where the WUS configuration for OnDemand SIB1 may be found. The method of embodiment 6, wherein a set of WUS configuration is predefined and programed in the wireless device and when the Kssb / SubcarrierOffset reserved value indicates support for OnDemand SIB1 signaling, at least one of the subCarrierSpacingCommon / dmrs-TypeA-Position values and the PDCCH-ConfigSIBl values are interpreted as which configuration the wireless device should use for WUS. The method of embodiment 6, wherein a set of WUS configuration is predefined and programed in the wireless device and the combination of the MIB spare bit, and Kssb / SubcarrierOffset is used such that if the spare bit indicates support for OnDemand SIB1 signaling, the Kssb / SubcarrierOffset values are interpreted as which configuration the wireless device should use for WUS. The method of any one of the previous embodiments, wherein when the spare bit is used for indicating support for OnDemand SIB1, wireless devices of the newer release shall not consider the cell to be barred, while signaling to wireless devices of a legacy release (e.g. Rel-18 or older) that the cell is barred for them. The method of any one of the previous embodiments, wherein when the wireless device is not operating on shared spectrum then the field subCarrierSpacingCommon and least significant bit (LSB) of the ssb-SubcarrierOffset is used to indicate the cell is barred or the onDemandSIBl support. A method performed by a wireless device, the method comprising:- any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.Group B Embodiments18. A method performed by a base station in a wireless network in communication with a wireless device, the method comprising:- transmitting a master information block (MIB), the MIB comprising an indication that the wireless network supports OnDemand SIB1 signaling.19. The method of the previous embodiment, wherein the OnDemand SIB1 support is indicated via any one or more of ssb-SubcarrierOffset (incl Kssb deduced from it), and / or spare bit of the MIB.20. The method of any one of the previous two embodiments, wherein a value for Kssb (deduced from SubcarrierOffset) is above 23 in FR1, and above 11 in FR2 is used for indicating support for OnDemand SIB1.21. The method of any one of the previous three embodiments, wherein a Kssb reserved value (30 in FR1, and 14 in FR2) is used for indicating OnDemand SIB1 support.22. The method of any one of the previous four embodiments, wherein a spare bit of the MIB is used for indicating support for OnDemand SIB1.23. The method of any one of the previous five embodiments, wherein the combination of the MIB spare bit, and Kssb / SubcarrierOffset is used for indicating from which cell / carrier the wireless device may acquire the WUS configuration.24. The method of any one of the previous six embodiments, wherein the combination of the MIB spare bit, and Kssb / SubcarrierOffset is used such that if the spare bit indicates support for OnDemand SIB1 signaling, the Kssb / SubcarrierOffset values are interpreted as where the wireless device may find other carrier / cells where the WUS configuration for OnDemand SIB1 may be found.25. The method of any one of the previous seven embodiments, wherein the combination of the Kssb / SubcarrierOffset and PDCCH-ConfigSIBl is used such that if the Kssb / SubcarrierOffset reserved value indicates support for OnDemand SIB1 signaling, and the PDCCH-ConfigSIBl values are interpreted as where the wireless device may findother carrier / cells where the WUS configuration for OnDemand SIB1 may be found.26. The method of any one of the previous eight embodiments, wherein a cellBarred field in the MIB is used as part of the condition for indicating to wireless devices supporting a newer release (e.g. Rel-19) that SIB1 can be obtained on demand, and after SIB1 is obtained the wireless device of the newer release shall not consider the cell to be barred, while signaling to wireless devices of a legacy release (e.g. Rel-18 or older) that the cell is barred for them.27. The method of any one of the previous nine embodiments, wherein the combination of the Kssb / SubcarrierOffset and at least one of subCarrierSpacingCommon / dmrs-TypeA- Position is used such that if the Kssb / SubcarrierOffset reserved value indicates support for OnDemand SIB1 signaling, the at least one of subCarrierSpacingCommon / dmrs-TypeA- Position values are interpreted as where the wireless device may find other carrier cells where the WUS configuration for OnDemand SIB1 may be found.28. The method of any one of the previous ten embodiments, wherein a set of WUS configuration is predefined and programed in the wireless device and when the Kssb / SubcarrierOffset reserved value indicates support for OnDemand SIB1 signaling, at least one of the subCarrierSpacingCommon / dmrs-TypeA-Position values and the PDCCH- ConfigSIBl values are interpreted as which configuration the wireless device should use for WUS.29. The method of any one of the previous ten embodiments, wherein a set of WUS configuration is predefined and programed in the wireless device and the combination of the MIB spare bit, and Kssb / SubcarrierOffset is used such that if the spare bit indicates support for OnDemand SIB1 signaling, the Kssb / SubcarrierOffset values are interpreted as which configuration the wireless device should use for WUS.30. The method of any one of the previous eleven embodiments, wherein when the spare bit is used for indicating support for OnDemand SIB1, wireless devices of the newer release shall not consider the cell to be barred, while signaling to wireless devices of a legacy release (e.g. Rel-18 or older) that the cell is barred for them.31. The method of any one of the previous twelve embodiments, wherein when the wireless device is not operating on shared spectrum then the field subCarrierSpacingCommon and least significant bit (LSB) of the ssb-SubcarrierOffset is used to indicate the cell is barred or the onDemandSIBl support.32. A method performed by a base station, the method comprising:- any of the steps, features, or functions described above with respect to base stations, either alone or in combination with other steps, features, or functions described above.33. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above.Group C Embodiments34. A mobile terminal comprising:- processing circuitry configured to perform any of the steps of any of the Group A embodiments; and- power supply circuitry configured to supply power to the wireless device.35. A base station comprising:- processing circuitry configured to perform any of the steps of any of the Group B embodiments;- power supply circuitry configured to supply power to the wireless device.36. A user equipment (UE) comprising:- an antenna configured to send and receive wireless signals;- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;- the processing circuitry being configured to perform any of the steps 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 outputinformation from the UE that has been processed by the processing circuitry; and- a battery connected to the processing circuitry and configured to supply power to the UE.

Claims

CLAIMS1. A method performed by a wireless device in a wireless network, the method comprising: obtaining (612) a master information block, MIB, from a network node, the MIB comprising an indication that a cell allows on-demand transmission of system information comprising random access parameters for the cell; and based on the indication that the cell allows on-demand transmission of system information, transmitting (616) a request for the transmission of the system information comprising random access parameters for the cell.

2. The method of claim 1, wherein the system information comprising random access parameters for the cell comprises a system information block one, SIB1.

3. The method of any one of claims 1-2, wherein the request for the transmission of the system information comprises a wake-up signal, WUS.

4. The method of any one of claims 1-3, wherein the indication is provided via one or more of a synchronization signal block, SSB, subcarrier offset and a spare bit in the MIB.

5. The method of any one of claims 1-4, wherein the indication is provided via an index value derived from a synchronization signal block, SSB, subcarrier offset that is above 23 for frequency range one, FR1, or above 11 for frequency range two, FR2.

6. The method of any one of claims 1-5, wherein the indication is provided via an index value derived from a synchronization signal block, SSB, subcarrier offset that is equal to value 30 for frequency range one, FR1, or equal to value 14 for frequency range two, FR2.

7. The method of any one of claims 1-6, further comprising acquiring (614) a resource configuration comprising a configuration of resources to use for transmitting the request for the transmission of the system information.

8. The method of claim 7, wherein a combination of a spare bit and a synchronizationsignal block, SSB, subcarrier offset in the MIB indicates from which cell or carrier the wireless device is to acquire the resource configuration.

9. The method of claim 8, wherein the spare bit in the MIB indicates that the cell allows on-demand transmission of system information and the SSB subcarrier offset indicates from which cell or carrier the wireless device is to acquire the resource configuration.

10. The method of claim 7, wherein a synchronization signal block, SSB, subcarrier offset indicates that the cell allows on-demand transmission of system information and a physical downlink control channel, PDCCH, configuration in the MIB indicates from which cell or carrier the wireless device is to acquire the resource configuration.

11. The method of claim 7, wherein a synchronization signal block, SSB, subcarrier offset indicates that the cell allows on-demand transmission of system information and one of a subcarrier spacing field and a demodulation reference signal, DMRS, position field indicates from which cell or carrier the wireless device is to acquire the resource configuration.

12. The method of any one of claims 1-11, wherein the indication is provided via a cell barred field in the MIB.

13. A wireless device (200) capable of operating in a wireless network, thew wireless device comprising processing circuitry (202) operable to: obtain a master information block, MIB, from a network node (300), the MIB comprising an indication that a cell allows on-demand transmission of system information comprising random access parameters for the cell; and based on the indication that the cell allows on-demand transmission of system information, transmit a request for the transmission of the system information comprising random access parameters for the cell.

14. The wireless device of claim 13, wherein the system information comprising random access parameters for the cell comprises a system information block one, SIB1.

15. The wireless device of any one of claims 13-14, wherein the request for the transmission of the system information comprises a wake-up signal, WUS.

16. The wireless device of any one of claims 13-15, wherein the indication is provided via one or more of a synchronization signal block, SSB, subcarrier offset and a spare bit in the MIB.

17. The wireless device of any one of claims 13-16, wherein the indication is provided via an index value derived from a synchronization signal block, SSB, subcarrier offset that is above 23 for frequency range one, FR1, or above 11 for frequency range two, FR2.

18. The wireless device of any one of claims 13-17, wherein the indication is provided via an index value derived from a synchronization signal block, SSB, subcarrier offset that is equal to value 30 for frequency range one, FR1, or equal to value 14 for frequency range two, FR2.

19. The wireless device of any one of claims 13-18, the processing circuitry further operable to acquire a resource configuration comprising a configuration of resources to use for transmitting the request for the transmission of the system information.

20. The wireless device of claim 19, wherein a combination of a spare bit and a synchronization signal block, SSB, subcarrier offset in the MIB indicates from which cell or carrier the wireless device is to acquire the resource configuration.

21. The wireless device of claim 20, wherein the spare bit in the MIB indicates that the cell allows on-demand transmission of system information and the SSB subcarrier offset indicates from which cell or carrier the wireless device is to acquire the resource configuration.

22. The wireless device of claim 19, wherein a synchronization signal block, SSB, subcarrier offset indicates that the cell allows on-demand transmission of system information and a physical downlink control channel, PDCCH, configuration in the MIB indicates from which cell or carrier the wireless device is to acquire the resource configuration.

23. The wireless device of claim 19, wherein a synchronization signal block, SSB, subcarrier offset indicates that the cell allows on-demand transmission of system information and one of a subcarrier spacing field and a demodulation reference signal, DMRS, position field indicates from which cell or carrier the wireless device is to acquire the resource configuration.

24. The wireless device of any one of claims 13-23, wherein the indication is provided via a cell barred field in the MIB.

25. A method performed by a network node in a wireless network, the method comprising: transmitting (712) a master information block, MIB, comprising an indication that a cell allows on-demand transmission of system information comprising random access parameters for the cell; and receiving (714) a request from a wireless device for transmission of the system information comprising random access parameters for the cell.

26. The method of claim 25, wherein the system information comprising random access parameters for the cell comprises a system information block one, SIB1.

27. The method of any one of claims 25-26, wherein the request for the transmission of the system information comprises a wake-up signal, WUS.

28. The method of any one of claims 25-27, wherein the indication is provided via one or more of a synchronization signal block, SSB, subcarrier offset and a spare bit in the MIB.

29. The method of any one of claims 25-28, wherein the indication is provided via an index value derived from a synchronization signal block, SSB, subcarrier offset that is above 23 for frequency range one, FR1, or above 11 for frequency range two, FR2.

30. The method of any one of claims 25-29, wherein the indication is provided via an index value derived from a synchronization signal block, SSB, subcarrier offset that is equal to value 30 for frequency range one, FR1, or equal to value 14 for frequency range two, FR2.

31. The method of any one of claims 25-30, wherein a combination of a spare bit and a synchronization signal block, SSB, subcarrier offset in the MIB indicates from which cell or carrier a wireless device is to acquire a resource configuration comprising a configuration of resources to use for transmitting a request for the transmission of the system information.

32. The method of claim 31, wherein the spare bit in the MIB indicates that the cell allows on-demand transmission of system information and the SSB subcarrier offset indicates from whichcell or carrier the wireless device is to acquire the resource configuration.

33. The method of claim 31, wherein the SSB subcarrier offset indicates that the cell allows on-demand transmission of system information and a physical downlink control channel, PDCCH, configuration in the MIB indicates from which cell or carrier the wireless device is to acquire the resource configuration.

34. The method of claim 31, wherein the SSB subcarrier offset indicates that the cell allows on-demand transmission of system information and one of a subcarrier spacing field and a demodulation reference signal, DMRS, position field indicates from which cell or carrier the wireless device is to acquire the resource configuration.

35. The method of any one of claims 25-34, wherein the indication is provided via a cell barred field in the MIB.

36. A network node (300) capable of operating in a wireless network, the network node comprising processing circuitry (302) operable to: transmit a master information block, MIB, comprising an indication that a cell allows on- demand transmission of system information comprising random access parameters for the cell; and receive a request from a wireless device for transmission of the system information comprising random access parameters for the cell.

37. The network node of claim 36, wherein the system information comprising random access parameters for the cell comprises a system information block one, SIB1.

38. The network node of any one of claims 36-37, wherein the request for the transmission of the system information comprises a wake-up signal, WUS.

39. The network node of any one of claims 36-38, wherein the indication is provided via one or more of a synchronization signal block, SSB, subcarrier offset and a spare bit in the MIB.

40. The network node of any one of claims 36-39, wherein the indication is provided via an index value derived from a synchronization signal block, SSB, subcarrier offset that is above23 for frequency range one, FR1, or above 11 for frequency range two, FR2.

41. The network node of any one of claims 36-40, wherein the indication is provided via an index value derived from a synchronization signal block, SSB, subcarrier offset that is equal to value 30 for frequency range one, FR1, or equal to value 14 for frequency range two, FR2.

42. The network node of any one of claims 36-41, wherein a combination of a spare bit and a synchronization signal block, SSB, subcarrier offset in the MIB indicates from which cell or carrier a wireless device is to acquire a resource configuration comprising a configuration of resources to use for transmitting a request for the transmission of the system information.

43. The network node of claim 42, wherein the spare bit in the MIB indicates the cell allows on-demand transmission of system information and the SSB subcarrier offset indicates from which cell or carrier the wireless device is to acquire the resource configuration.

44. The network node of claim 42, wherein the SSB subcarrier offset indicates the cell allows on-demand transmission of system information and a physical downlink control channel, PDCCH, configuration in the MIB indicates from which cell or carrier the wireless device is to acquire the resource configuration.

45. The network node of claim 42, wherein the SSB subcarrier offset indicates the cell allows on-demand transmission of system information and one of a subcarrier spacing field and a demodulation reference signal, DMRS, position field indicates from which cell or carrier the wireless device is to acquire the resource configuration.

46. The network node of any one of claims 36-45, wherein the indication is provided via a cell barred field in the MIB.

Images