Signaling in connection of on-demand SIB1

On-demand SIB1 signaling optimizes power usage and resource allocation in mobile communication systems by allowing UEs to manage SIB1 requests and select alternative nodes, addressing inefficiencies in network energy saving cells.

WO2026033165A1PCT designated stage Publication Date: 2026-02-12NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/FI2025/050319
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-08-09
Filing Date
2025-06-13
Publication Date
2026-02-12

AI Technical Summary

Technical Problem

Existing mobile communication systems face inefficiencies in power consumption and resource wastage due to the periodic broadcasting of System Information Block 1 (SIB1) signals, particularly in network energy saving (NES) cells, which can be addressed by implementing on-demand SIB1 (OD-SIB1) signaling.

Method used

The implementation of on-demand SIB1 (OD-SIB1) signaling, where a user equipment (UE) sends a request for SIB1 transmission, and the network node provides a response indicating whether the transmission will be delayed or not, allowing the UE to terminate unnecessary requests and select alternative nodes if barred, thereby optimizing power usage and resource allocation.

Benefits of technology

This approach reduces power consumption and resource wastage by allowing UEs to efficiently manage SIB1 requests and select appropriate network nodes, enhancing overall system efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure FI2025050319_12022026_PF_FP_ABST
    Figure FI2025050319_12022026_PF_FP_ABST
Patent Text Reader

Abstract

A method, apparatus and computer program is described comprising: receiving, at a UE, uplink wake up signal (UL WUS) configuration information, determining whether the UE is barred from a first node of a mobile communication system (wherein said determination is made before receiving or monitoring for OD-SIB1 from the first node), and selecting an alternative node of the mobile communication system for communications in the event that the UE is barred from the first node.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] SIGNALING IN CONNECTION OF ON-DEMAND SIB1

[0002] Field

[0003] Example embodiments may relate to systems, methods and / or computer programs for use in mobile communication.

[0004] Background

[0005] The principles described herein relate on-demand SIB1 (OD-SIB1) operation in mobile communication systems. For example, OD-SIB1 signals can be used to enable a user equipment (UE) to access a network node, such as a network energy saving (NES) cell.

[0006] Summary

[0007] The scope of protection sought for various embodiments of the invention is set out by the independent claims. The embodiments and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the invention.

[0008] In a first aspect, this specification describes an apparatus (e.g. a UE) comprising: means for sending an on-demand SIB1, OD-SIB1, transmission request from a UE to a first node of a mobile communication system; and means for receiving a response to the OD-SIB1 transmission request from the first node indicating that the requested OD-SIB1 response will not be transmitted.

[0009] Some example embodiments further comprise means for selecting an alternative node of the mobile communication system for communications in response to the indication that the requested OD-SIB1 response will not be transmitted.

[0010] Some example embodiments further comprise means for receiving (e.g. from another node, such as a Cell A, or from said first node) UL WUS configuration information. The UL WUS configuration information may include uplink synchronization details, for example. The OD-SIB1 transmission request may, for example, be sent after receiving the UL WUS configuration information.

[0011] The OD-SIB1 transmission request may be provided as an uplink wake up signal (UL WUS).

[0012] The OD-SIB1 transmission request may be implemented by a Msgl or MsgA sent from the UE to the first node. The response indicating that the requested OD-SIB1 transmission will not be transmitted may be provided as part of an RAR response.

[0013] The response indicating that the requested OD-SIB1 transmission will not be transmitted may be an acknowledgement of receipt, at the first node, of the OD-SIB1 transmission request. The acknowledgement of receipt may provide feedback from the network / cell to acknowledge reception of the ID-SIP1 request (e.g. receipt of an UL WUS signal).

[0014] Some example embodiments further comprise means for terminating sending of further OD-SIB1 transmission requests in response to the receipt of the response to the OD-SIB1 transmission request from the first node indicating that the requested OD-SIB1 response will not be transmitted.

[0015] The response indicating that the requested OD-SIB1 transmission will not be transmitted may further comprise an indication that the OD-SIB1 response will not be transmitted within a preconfigured time window or at a preconfigured time instance. The response indicating that the requested OD-SIB1 transmission will not be transmitted may, for example, further comprise an indication of a later time at which the OD-SIB1 will be transmitted.

[0016] In a second aspect, this specification describes an apparatus (e.g. a network node, such as an NES cell) comprising: means for receiving an on-demand SIB1, OD-SIB1, transmission request from a UE of a mobile communication system at a first node of the mobile communication system; and means for providing a response to the OD-SIB1 transmission request to the UE indicating that the requested OD-SIB1 response will not be transmitted.

[0017] The OD-SIB1 transmission request may be provided as an uplink wake up signal (UL WUS).

[0018] The response indicating that the requested OD-SIB1 transmission will not be transmitted may be provided as part of an RAR response.

[0019] The response indicating that the requested OD-SIB1 transmission will not be transmitted may be an acknowledgement of receipt, at the first node, of the OD-SIB1 transmission request. The acknowledgement of receipt may provide feedback from the network / cell to acknowledge reception of the OD-SIB1 request (e.g. to acknowledge receipt of an UL WUS signal).

[0020] The response indicating that the requested OD-SIB1 transmission will not be transmitted may further comprise an indication that the OD-SIB1 response will not be transmitted within a preconfigured time window or at a preconfigured time instance. Furthermore, the response indicating that the requested OD-SIB1 transmission will not be transmitted may further comprise an indication of a later time at which the OD-SIB1 will be transmitted.

[0021] In a third aspect, this specification describes an apparatus (e.g. a UE) comprising: means for receiving (e.g. from another node, such as a Cell A), at a UE, uplink wake up signal (UL WUS) configuration information; means for determining whether the UE is barred from a first node of a mobile communication system; and means for selecting an alternative node of the mobile communication system for communications in the event that the UE is barred from the first node. The means for determining whether the UE is barred from the first node may be configured to make said determination before receiving or monitoring for on-demand SIB1, OD-SIB1, from the first node.

[0022] Some example embodiments further comprise means for determining whether the UE is barred from the first node is configured to determine whether the UE is barred from the first node based, at least in part, on the received uplink wake signal configuration information. Thus, the barring information can be received without needing to wait for (or even request) the OD-SIB1. The uplink wakeup signal configuration information may identify one or more UEs that are barred by the first node. Alternatively, or in addition, the uplink wakeup signal configuration information may identify one or more types of UEs that are barred by the first node. The types of UEs may, for example, include nonterrestrial network (NTN) UEs and / or reduced capacity (RedCap) UEs.

[0023] The means for determining whether the UE is barred from the first node may be configured to determine whether the UE is barred from the first node based, at least in part, on information received from the first node. In some example embodiments, the means for determining whether the UE is barred from the first network node comprises: means for sending an OD-SIB1 transmission request from the UE to the first node; and means for receiving a response to the OD-SIB1 transmission from the first node indicating that the UE is barred. The OD-SIB1 transmission request may be provided as an uplink wake up signal (UL WUS). The OD-SIB1 transmission request may be implemented by a Msgl or MsgA sent from the UE to the first node. The response indicating that the requesting device is barred may be provided as part of an RAR response. In some example embodiments, determining whether the UE is barred from the first node comprises determining whether the UE is barred from a node providing said uplink wakeup signal configuration information. Some example embodiments further comprise: means for receiving SIB1 information for the node providing said uplink wakeup signal configuration information; and means for determining that barring information including in the SIB1 information for the node providing said uplink wakeup signal configuration information applies to said first node.

[0024] In a fourth aspect, this specification describes an apparatus (e.g. a network node, such as a network node providing UL WUS configuration information) comprising: means for providing, to a UE of a mobile communication system, uplink wake up signal configuration information, wherein the uplink wakeup signal configuration information provides information enabling the UE to determine whether the UE is barred from a first node. The uplink wakeup signal configuration information may identify one or more UEs that are barred by the first node. Alternatively, or in addition, the uplink wakeup signal configuration information may identify one or more types of UEs that are barred by the first node. The types of UEs may, for example, include non-terrestrial network (NTN) UEs and / or reduced capacity (RedCap) UEs.

[0025] In a fifth aspect, this specification describes an apparatus (e.g. a network node, such as an NES cell) comprising: means for receiving an on-demand SIB1, OD-SIB1, transmission request from a UE of a mobile communication system at a first node of the mobile communication system; and means for providing a response to the OD-SIB1 transmission request to the UE providing barring information. The OD-SIB1 transmission request may be provided as an uplink wake up signal (UL WUS). The OD-SIB1 transmission request may be implemented by a Msgl or MsgA sent from the UE to the first node. The response providing barring information may be provided as part of an RAR response.

[0026] In a sixth aspect, this specification describes a method comprising: sending an on-demand SIB1, OD-SIB1, transmission request from a UE to a first node of a mobile communication system; and receiving a response to the OD-SIB1 transmission request from the first node indicating that the requested OD-SIB1 response will not be transmitted. The method may be implemented at a UE of the mobile communication system.

[0027] Some example embodiments further comprise selecting an alternative node of the mobile communication system for communications in response to the indication that the requested 0D-SIB1 response will not be transmitted.

[0028] Some example embodiments further comprise receiving (e.g. from another node, such as a Cell A, or from said first node) UL WUS configuration information. The UL WUS configuration information may include uplink synchronization details, for example. The OD-SIB1 transmission request may, for example, be sent after receiving the UL WUS configuration information.

[0029] The OD-SIB1 transmission request may be provided as an uplink wake up signal (UL WUS).

[0030] The OD-SIB1 transmission request may be implemented by a Msgl or MsgA sent from the UE to the first node.

[0031] The response indicating that the requested OD-SIB1 transmission will not be transmitted may be provided as part of an RAR response.

[0032] The response indicating that the requested OD-SIB1 transmission will not be transmitted may be an acknowledgement of receipt, at the first node, of the OD-SIB1 transmission request. The acknowledgement of receipt may provide feedback from the network / cell to acknowledge reception of the ID-SIP1 request (e.g. receipt of an UL WUS signal).

[0033] Some example embodiments further comprise terminating sending of further OD-SIB1 transmission requests in response to the receipt of the response to the OD-SIB1 transmission request from the first node indicating that the requested OD-SIB1 response will not be transmitted.

[0034] The response indicating that the requested OD-SIB1 transmission will not be transmitted may further comprise an indication that the OD-SIB1 response will not be transmitted within a preconfigured time window or at a preconfigured time instance. The response indicating that the requested OD-SIB1 transmission will not be transmitted may, for example, further comprise an indication of a later time at which the OD-SIB1 will be transmitted.

[0035] In a seventh aspect, this specification describes a method comprising: receiving an on- demand SIB1, OD-SIB1, transmission request from a UE of a mobile communication system at a first node of the mobile communication system; and providing a response to the OD-SIB1 transmission request to the UE indicating that the requested OD-SIB1 response will not be transmitted. The method may be implemented at a network node, such as an NES cell. The OD-SIB1 transmission request may be provided as an uplink wake up signal (UL WUS). The response indicating that the requested OD-SIB1 transmission will not be transmitted may be provided as part of an RAR response. The response indicating that the requested OD-SIB1 transmission will not be transmitted may be an acknowledgement of receipt, at the first node, of the OD-SIB1 transmission request. The acknowledgement of receipt may provide feedback from the network / cell to acknowledge reception of the OD-SIB1 request (e.g. to acknowledge receipt of an UL WUS signal). The response indicating that the requested OD-SIB1 transmission will not be transmitted may further comprise an indication that the OD-SIB1 response will not be transmitted within a preconfigured time window or at a preconfigured time instance. Furthermore, the response indicating that the requested OD-SIB1 transmission will not be transmitted may further comprise an indication of a later time at which the OD-SIB1 will be transmitted.

[0036] In an eighth aspect, this specification describes a method comprising: receiving, at a UE, uplink wake up signal (UL WUS) configuration information; determining whether the UE is barred from a first node of a mobile communication system; and selecting an alternative node of the mobile communication system for communications in the event that the UE is barred from the first node. The method may be implemented at a UE of the mobile communication system. Whether the UE is barred from the first node may be determined before receiving or monitoring for on-demand SIB1, OD-SIB1, from the first node.

[0037] Determining whether the UE is barred from the first node may be based, at least in part, on the received uplink wake signal configuration information. Thus, the barring information can be received without needing to wait for (or even request) the OD-SIB1. The uplink wakeup signal configuration information may identify one or more UEs that are barred by the first node. Alternatively, or in addition, the uplink wakeup signal configuration information may identify one or more types of UEs that are barred by the first node. The types of UEs may, for example, include non-terrestrial network (NTN) UEs and / or reduced capacity (RedCap) UEs.

[0038] Determining whether the UE is barred from the first node may be based, at least in part, on information received from the first node. In some example embodiments determining whether the UE is barred from the first network node comprises: sending an OD-SIB1 transmission request from the UE to the first node; and receiving a response to the OD- SIB1 transmission from the first node indicating that the UE is barred. The OD-SIB1 transmission request may be provided as an uplink wake up signal (UL WUS). The OD- SIB1 transmission request may be implemented by a Msgl or MsgA sent from the UE to the first node. The response indicating that the requesting device is barred may be provided as part of an RAR response.

[0039] In some example embodiments, determining whether the UE is barred from the first node comprises determining whether the UE is barred from a node providing said uplink wakeup signal configuration information. Some example embodiments further comprise: receiving SIB1 information for the node providing said uplink wakeup signal configuration information; and determining that barring information including in the SIB1 information for the node providing said uplink wakeup signal configuration information applies to said first node.

[0040] In a ninth aspect, this specification describes a method comprising: providing, to a UE of a mobile communication system, uplink wake up signal configuration information, wherein the uplink wakeup signal configuration information provides information enabling the UE to determine whether the UE is barred from a first node. The method may be implemented at a network node, such as a network node providing UL WUS configuration information. The uplink wakeup signal configuration information may identify one or more UEs that are barred by the first node. Alternatively, or in addition, the uplink wakeup signal configuration information may identify one or more types of UEs that are barred by the first node. The types of UEs may, for example, include non-terrestrial network (NTN) UEs and / or reduced capacity (RedCap) UEs.

[0041] In a tenth aspect, this specification describes a method comprising: receiving an on- demand SIB1, OD-SIB1, transmission request from a UE of a mobile communication system at a first node of the mobile communication system; and providing a response to the OD-SIB1 transmission request to the UE providing barring information. The method may be implemented at a network node, such as an NES cell. The OD-SIB1 transmission request may be provided as an uplink wake up signal (UL WUS). The OD-SIB1 transmission request may be implemented by a Msgl or MsgA sent from the UE to the first node. The response providing barring information may be provided as part of an RAR response.

[0042] In an eleventh aspect, this specification describes computer-readable instructions which, when executed by a computing apparatus, cause the computing apparatus to perform (at least) any method as described herein (including the methods of the sixth to tenth aspects described above). In a twelfth aspect, this specification describes a computer-readable medium (such as a non-transitory computer-readable medium) comprising program instructions stored thereon for performing (at least) any method as described herein (including the methods of the sixth to tenth aspects described above).

[0043] In a thirteenth aspect, this specification describes an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, causes the apparatus to perform (at least) any method as described herein (including the methods of the sixth to tenth aspects described above).

[0044] In a fourteenth aspect, this system comprising a UE as set above (including as set out above with respect to the first or third aspects) and a network node (including as set out above with respect to the second or fifth aspects).

[0045] In a fifteenth aspect, this specification describes a computer program comprising instructions which, when executed by an apparatus (such as a UE), cause the apparatus to: send an on-demand SIB1, OD-SIB1, transmission request from a UE to a first node of a mobile communication system; and receive a response to the OD-SIB1 transmission request from the first node indicating that the requested OD-SIB1 response will not be transmitted.

[0046] In a sixteenth aspect, this specification describes a computer program comprising instructions which, when executed by an apparatus (such as a network node), cause the apparatus to: receive an on-demand SIB1, OD-SIB1, transmission request from a UE of a mobile communication system at a first node of the mobile communication system; and provide a response to the OD-SIB1 transmission request to the UE indicating that the requested OD-SIB1 response will not be transmitted.

[0047] In a seventeenth aspect, this specification describes a computer program comprising instructions which, when executed by an apparatus (such as a UE), cause the apparatus to: receive, at a UE, uplink wake up signal configuration information; determine whether the UE is barred from a first node of a mobile communication system (wherein said determination may be made before receiving or monitoring for on-demand SIB1, OD-SIB1, from the first node); and select an alternative node of the mobile communication system for communications in the event that the UE is barred from the first node. In an eighteenth aspect, this specification describes a computer program comprising instructions which, when executed by an apparatus (such as a network node), cause the apparatus to: provide, to a UE of a mobile communication system, uplink wake up signal configuration information, wherein the uplink wakeup signal configuration information provides information enabling the UE to determine whether the UE is barred from a first node.

[0048] In a nineteenth aspect, this specification describes a computer program comprising instructions which, when executed by an apparatus, cause the apparatus (such as a network node) to: receive an on-demand SIB1, OD-SIB1, transmission request from a UE of a mobile communication system at a first node of the mobile communication system; and provide a response to the OD-SIB1 transmission request to the UE providing barring information.

[0049] In a twentieth aspect, this specification describes an apparatus comprising: an output (or some other means) for sending an on-demand SIB1, OD-SIB1, transmission request from a UE to a first node of a mobile communication system; and an input (or some other means) for receiving a response to the OD-SIB1 transmission request from the first node indicating that the requested OD-SIB1 response will not be transmitted.

[0050] In a twenty-first aspect, this specification describes an apparatus comprising: an output (or some other means) for sending an on-demand SIB1, OD-SIB1, transmission request from a UE to a first node of a mobile communication system; and an input (or some other means) for receive a response to the OD-SIB1 transmission request from the first node indicating that the requested OD-SIB1 response will not be transmitted.

[0051] In a twenty-second aspect, this specification describes an apparatus comprising: an input of a UE (or some other means) for receiving uplink wake up signal configuration information; a processor (or some other means) for determining whether the UE is barred from a first node of a mobile communication system (wherein said determination may be made before receiving or monitoring for on-demand SIB1, OD-SIB1, from the first node); and a control module (or some other means) for selecting an alternative node of the mobile communication system for communications in the event that the UE is barred from the first node.

[0052] In a twenty-third aspect, this specification describes an apparatus comprising: an output (or some other means) for providing to a UE of a mobile communication system, uplink wake up signal configuration information, wherein the uplink wakeup signal configuration information provides information enabling the UE to determine whether the UE is barred from a first node.

[0053] In a twenty-fourth aspect, this specification describes an apparatus comprising: an input (or some other means) for receiving an on-demand SIB1, OD-SIB1, transmission request from a UE of a mobile communication system at a first node of the mobile communication system; and an output (or some other means) for providing a response to the OD-SIB1 transmission request to the UE providing barring information.

[0054] Brief Description of the Drawings

[0055] Example embodiments will now be described by way of non-limiting example, with reference to the accompanying drawings, in which:

[0056] FIG. 1 is a block diagram of a system in accordance with an example embodiment;

[0057] FIGS. 2 to 5 show systems in which example embodiments may be used;

[0058] FIG. 6 is a message flow sequence in accordance with an example embodiment;

[0059] FIGS. 7 to 10 are flow diagrams in accordance with example embodiments;

[0060] FIGS. 11 to 13 are message flow sequences in accordance with example embodiments;

[0061] FIGS. 14 and 15 are flow diagrams in accordance with example embodiments;

[0062] FIG. 16 is a schematic diagram of components of one or more of the example embodiments described previously; and

[0063] FIG. 17 shows tangible media for storing computer-readable code which when run by a computer may perform methods according to example embodiments described herein.

[0064] Detailed Description

[0065] In the description and drawings, like reference numerals refer to like elements throughout.

[0066] FIG. 1 is a block diagram of a system, indicated generally by the reference numeral 10, in accordance with an example embodiment. The system 10 shows a user equipment (UE) 12 of a mobile communication system in two-way communication with a network node 14 of the mobile communication system. As shown in FIG. 1, the network node 14 is operating in a network energy saving (NES) mode of operation.

[0067] Access to cells, such as the NES cell 14, can be configured by a System Information Block referred to as SIB1. Each SIB1 communication provides a range of configuration information that enables a UE (such as the UE12) to communicate with and / or access a network node / cell. Without the SIB1 information, it is generally not possible for a UE to access the cell.

[0068] SIB1 information is typically broadcast (e.g. periodically) by a node so that a UE that wants to access a node can detect, decode, and use the configuration information included in the SIB1. The NES cell 14 (which is operating in a Network Energy Saving mode) may not periodically broadcast SIB1 information (in order to save power). Instead, the cell 14 may provide SIB1 information on-demand (so called on-demand SIB1, or OD-SIB1). For example, the SIB1 information may be provided to a UE (such as the UE12) in response to a request to provide that information.

[0069] A cell operating in OD-SIB1 mode will provide a SIB1 response only on-demand (thereby saving power, for example). Specifically, transmission of the SIB1 signal may be triggered by the receipt of a Wake-up signal (WUS) sent by the UE to the relevant cell.

[0070] In the system 10, the SIB1 relating to the cell 14 may be provided on-demand based on the UE 12 in RRC idle or RRC inactive requesting its transmission. As discussed further below, the UE 12 may trigger the transmission of the OD-SIB1 by sending a wake-up signal (WUS), which could, for example, be a Physical Random-Access CHannel (PRACH) i.e. a preamble. This requires that the UE is configured with resources and information to transmit the WUS.

[0071] FIGS. 2 to 5 show systems in which OD-SIB1 information may be provided.

[0072] FIG. 2 is a system, indicated generally by the reference numeral 20, in which example embodiments described herein may be used. The system 20 is a non-standalone system comprising a first cell (Cell A), a second cell (NES Cell), and a UE 22. The UE 22 and the NES Cell may be the UE 12 and the NES Cell 14 described above.

[0073] In the system 20, the first cell (Cell A) provides UL wake-up signal (WUS) configuration information to the UE 22. The UE 22 uses the WUS configuration information to send an UL WUS to the NES Cell. The UL WUS signal is interpreted by the NES Cell as a request for OD-SIB1 information. The NES Cell provides the OD-SIB1 information to the UE 22.

[0074] FIG. 3 is a system, indicated generally by the reference numeral 30, in which example embodiments described herein may be used. The system 30 is a non-standalone system comprising the first cell (Cell A), the second cell (NES Cell), and the UE 22 described above.

[0075] In the system 30, the first cell (Cell A) provides UL wake-up signal (WUS) configuration information to the UE 22. The UE 22 uses the WUS configuration information to send an UL WUS to the Cell A. Cell A provides the OD-SIB1 information to the UE 22.

[0076] FIG. 4 is a system, indicated generally by the reference numeral 40, in which example embodiments described herein may be used. The system 40 is a non-standalone system comprising the first cell (Cell A), the second cell (NES Cell), and the UE 22 described above.

[0077] In the system 40, the first cell (Cell A) provides UL wake-up signal (WUS) configuration information to the UE 22. The UE 22 uses the WUS configuration information to send an UL WUS to the NES Cell. The UL WUS signal is interpreted by the NES Cell as a request for OD-SIB1 information. The NES Cell provides the OD-SIB1 information to the UE 22.

[0078] The system 40 differs from the system 20 in that the UL WUS configuration provided by Cell A is provided as part of an RRC release (rather than in a SIB as in the system 20).

[0079] FIG. 5 is a system, indicated generally by the reference numeral 50, in which example embodiments described herein may be used. The system 50 is a standalone system comprising the NES Cell and the UE 22 described above.

[0080] In the system 50, the UL wake-up signal (WUS) configuration information is provided by the NES Cell to the UE 22. The UE 22 uses the WUS configuration information to send an UL WUS to the NES Cell. The UL WUS signal is interpreted by the NES Cell as a request for OD-SIB1 information. The NES Cell provides the OD-SIB1 information to the UE 22.

[0081] In the systems 20 to 50:

[0082] • The UE 22 obtains WUS configuration information from Cell A in the stand-alone configurations.

[0083] • The UE 22 sends UL WUS (e.g. RACH / Msgl) to the NES cell or to Cell A.

[0084] • The UE 22 monitors / receives a Random Access Response (RAR response) from the node that receives the WUS.

[0085] • The UE 22 monitors / receives OD-SIB1 from NES cell or cell A.

[0086] The OD-SIB1 procedure can be used to enable a UE operating in an IDLE or Inactive mode to access a network node.

[0087] For example, the following steps may be applied in accordance with random access in New Radio (NR) principles (from Msgl transmission by a UE to Msg2 reception):

[0088] • UE transmits Msgl RACH preamble.

[0089] • UE monitors PDCCH (DCI l_0) from gNB scrambled with RA-RNTI. The monitoring window is configured by rar-WindowLength in a SIB1 message. • UE decodes PDCCH to get the PRB resources information to receive PDSCH carrying Msg2 Random Access Response (RAR) payload.

[0090] • UE decodes PDSCH carrying data Msg2 and checks the Random Access Preamble Identifier (RAPID) in RAR is matching with the RAPID assigned to it. If RAPID in RAR response matches with the RAPID assigned to it, UE assumes successfully received Msg2.

[0091] Generally, the RAR responses carries, in addition to the RAPID, the timing advance to be applied at UE and the UL grant for Msg3. However, in OD-SIB1 operation, the UE generally uses the RAR only as gNB feedback to acknowledge UL WUS reception by gNB. Thus, at least timing advance and UL grant are not required.

[0092] FIG. 6 is a message flow sequence, indicated generally by the reference numeral 60, in accordance with an example embodiment. The sequence 60 shows messages transferred between a UE 62 and an NES Cell 64 (or some other node of a mobile communication system). The UE 62 is similar to the UEs 12 and 22 described above. The NES Cell 64 is similar to the NES Cell 14 described above.

[0093] The sequence 60 starts with an on-demand SIB1 (OD-SIB1) transmission request being sent (message 66) from the UE 62 to the NES Cell 64. A response 68 is received in response to the request. In a normal mode of operation, the response may be an acknowledgement message (ACK)and the requested SIB1 may follow after the response.

[0094] On receipt of the request 66 from the UE 62, the NES Cell 64 will generally provide a response acknowledging (ACK) the request that includes the request ID-SIB1. However, some networks may nevertheless decide not to transmit OD-SIB1. This may, for example, be because the cell is operating in a hard energy saving mode.

[0095] If the UE does not receive a response to the OD-SIB1 request, the request will generally be re-sent (thereby wasting resources). If an acknowledgement is sent, but the OD-SIB1 is not provided, the UE 62 may wait and monitor for the SIB1; again, this would waste resources (e.g. power) for SIB1 monitoring.

[0096] In an example implementation of the message sequence 60, the response 68 sent from the NES Cell 64 to the UE 62 indicates that the requested OD-SIB1 response will not be transmitted. The response 68 thereby acknowledges that the request 66 has been successfully received (and does not need to be re-sent). Moreover, the response 68 informs the UE 62 that the OD-SIB1 will not be provided (or, as discussed further below, indicate a starting time when the NES cell will be able to transmit OD-SIB1) and so resources do not need to be wasted in monitoring for the SIB1. Thus, the UE 62 may terminate sending of further OD-SIB1 transmission requests 66 in response to the receipt of the response 68 and omit OD-SIB1 monitoring.

[0097] As discussed further below, the OD-SIB1 transmission request 66 may be provided as an uplink wake up signal (UL WUS) and may, for example, be implemented by a Msgl or MsgA sent from the UE to the first node. Similarly, the response 68 may be provided as part of an RAR response.

[0098] In an embodiment, at least one bit of the bits reserved for timing advance information in RAR (e.g. Msg2 or MsgB) is used to indicate that the OD-SIB1 will not be sent or that it will be sent after a certain time duration (different duration than what is expected in legacy systems). The time duration may be indicated in one or more of the bits of the RAR (e.g. one or more of the bits previously reserved for timing advance information or in some other bits of the RAR). The UE can thus re-interpret that field of the RAR to obtain information on whether (or when) the UE can expect to receive SIB1.

[0099] In an embodiment, at least one bit of the bits reserved for UL grant information in RAR (e.g. Msg2 or MsgB) is used to indicate that the OD-SIB1 will not be sent or that it will be sent after a certain time duration (different duration than what is expected in legacy systems). The time duration may be indicated in one or more of the bits of the RAR (e.g. one or more of the bits previously reserved for UL grant information or in some other bits of the RAR). The UE can thus re-interpret that field of the RAR to obtain information on whether (or when) the UE can expect to receive SIB1.

[0100] FIG. 7 is a flow diagram, indicated generally by the reference numeral 70, in accordance with an example embodiment. The flow diagram 70 may be implemented by the UE 62.

[0101] The flow diagram 70 starts at operation 72, where uplink wake-up signal (UL WUS) configuration information is received. The UL WUS configuration may be received (at the UE 62) from another node (e.g. Cell A as shown in FIGS. 2 to 4); alternatively, the UL WUS configuration could be provided by the same node that the OD-SIB1 request will be sent (e.g. an NES Cell), as in the standalone scenario shown in FIG. 5.

[0102] At operation 74, an OD-SIB1 transmission request is sent, thereby implementing the message 66 described above. In the specific example shown in the flow diagram 70, the operation 74 is implemented by sending an uplink wake-up signal (UL WUS) from the UE 62 (for example to the NES Cell 64). The UL WUS may be in accordance with the UL WUS configuration information received in the operation 62. Moreover, the request may be implemented by a Msgl or MsgA sent from the UE 62 to the relevant node (e.g. the NES Cell 64).

[0103] A response to the message sent in the operation 74 is received in operation 76. The response may indicate that the requested OD-SIB1 response will not be transmitted. The response may be provided as part of an RAR response. The response may be provided as an acknowledgement of receipt of the OD-SIB1 request.

[0104] The receipt of the response (indicating that the requested OD-SIB1 response will not be transmitted) may result in the terminating of sending further OD-SIB1 transmission requests to the respective node (e.g. the NES Cell 64).

[0105] In operation 78, following receipt of the response (indicating that the requested OD-SIB1 response will not be transmitted), an alternative node of the mobile communication system may be selected for communications between the UE and the network.

[0106] The flow diagram 70 may be implemented by a network node using available information elements (IE) (e.g. UL grant IES) in the existing RAR to inform the UE 62 that:

[0107] • The network node has correctly received the UL WUS;

[0108] • The network node NW is not transmitting OD-SIB1, for example to save power. (Note that the network node does not necessarily need to provide reason, just indicating no- SIB1 is transmitted.) Alternatively, as discussed further below, the network node may indicate that it will transmit the OD-SIB1 after a certain time window.

[0109] FIG. 8 is a flow diagram, indicated generally by the reference numeral 80, in accordance with an example embodiment. The flow diagram 80 is implemented at a network node or cell (such as the NES Cell 64).

[0110] The flow diagram 80 starts at operation 82 where an OD-SIB1 transmission request is received from a UE (e.g. the US 62) of a mobile communication system. As indicated in FIG. 8, the OD-SIB1 transmission request may be provided as an uplink wake up signal (UL WUS).

[0111] At operation 84, a response to the OD-SIB1 transmission request is provided, indicating that the requested OD-SIB1 will not be transmitted. The response may be transmitted as an acknowledgement of receipt of the OD-SIB1 transmission request, thereby providing feedback from the network / cell (e.g. the NES Cell 66) to acknowledge receipt of the OD- SIB1 request.

[0112] FIG. 9 is a flow diagram, indicated generally by the reference numeral 90, in accordance with an example embodiment. The flow diagram 90 in an alternative implementation of the operation 76 described above.

[0113] The flow diagram 90 starts at operation 92, where the response indicating that the requested OD-SIB1 transmission will not be transmitted takes the form (or includes) an indication that the OD-SIB1 response will not be transmitted within a preconfigured time window or at a preconfigured time instance (e.g. an indication of a later time at which the OD-SIB1 will be transmitted may be provided). This is sent from the network node (e.g. the NES Cell 66) to the US 62.

[0114] At operation 94, a decision may be taken at the UE 62 to either wait for the OD-SIB1, or to connect to another cell.

[0115] In some example embodiments, some UEs may be barred from using a particular cell. For example, non-terrestrial network (NTN) devices or Reduced Capacity (RedCap) devices may not be able to operate with a particular cell. In the OD-SIB1 procedure outlined above, a UE sends an OD-SIB1 request to a cell, receives ACK (e.g. RAR response) and may then receive an OD-SIB1 payload that may indicate that the UE is barred. The sending of the request, the receiving of the SIB1 and related processing consumes resources and is therefore inefficient.

[0116] FIG. 10 is a flow diagram, indicated generally by the reference numeral 100, in accordance with an example embodiment.

[0117] The flow diagram 100 starts at operation 102, where uplink wake ups signal (UL WUS) configuration information is received at a UE (for example from a network node, such as Cell A as discussed above).

[0118] At operation 104 a determination is made regarding whether the UE is barred from a first node of a mobile communication system (e.g. a node that the UE wants to connect to).

[0119] At operation 106, an alternative node of the mobile communication system may be selected in the event that the UE is barred from the first node.

[0120] FIG. 11 is a message flow sequence, indicated generally by the reference numeral 110, in accordance with an example embodiment. The sequence 110 shows messages transferred between the UE 62, the NES Cell 64 (or some other node of a mobile communication) and a Cell A 112 (or some other node of the mobile communication system). The sequence 110 shows an example implementation of the flow diagram 100.

[0121] The message sequence 110 starts with UL WUS configuration information being received at the UE 62 from the Cell A 112 (message 114).

[0122] In operation 116, the UE 62 determines whether the UE is barred from the NES Cell 64 based, at least in part, on the received uplink wake signal configuration information. Thus, the barring information can be received before an OD-SIB1 request is sent; thus, if the an indication is received that the UE is barred, then the UE does not need to request OD-SIB1 and can simply treat the cell as barred.

[0123] By way of example, the UL WUS configuration information may identify one or more UEs that are barred by the NES Cell 64 or may identify one or more types of UEs that are barred by the NES Cell 64. For example, NTN and / or RedCap devices may be barred by some network nodes.

[0124] FIG. 12 is a message flow sequence, indicated generally by the reference numeral 120, in accordance with an example embodiment. The sequence 120 shows messages transferred between the UE 62, the NES Cell 64 (or some other node of a mobile communication) and the Cell A 112 (or some other node of the mobile communication system). The sequence 120 shows another example implementation of the flow diagram 100.

[0125] The message sequence 120 starts with UL WUS configuration information being received at the UE 62 from the Cell A 112 (message 122).

[0126] An OD-SIB1 transmission request (message 124) is sent from the UE to the NES Cell 64 and a response (message 126) to that request is received. As discussed above, OD-SIB1 transmission request 124 may be an uplink wake up signal (UL WUS) and may be implemented by a Msgl or MsgA.

[0127] The UE 62 determines whether the UE is barred from the NES Cell 64 based, at least in part, on information received in the response 126. A response indicating that the UE 62 is barred may be provided as part of an RAR response. In an embodiment, at least one bit of the bits reserved for timing advance or uplink grant in the RAR may be used for this purpose. The UE can thus re-interpret that field of the RAR to obtain information on whether the UE is barred from the cell. Thus, a network node can decide to include the barring information in RAR response. Thus, when UE receives an RAR response, it can understand if it is barred by the cell or not. In case of other UEs monitoring for the RAR response before requesting OD-SIB1, this information can be useful by allowing UEs monitoring RAR response to know if they are barred by this cell or not before requesting OD-SIB1.

[0128] FIG. 13 is a message flow sequence, indicated generally by the reference numeral 130, in accordance with an example embodiment. The sequence 130 shows messages transferred between the UE 62, the NES Cell 64 (or some other node of a mobile communication) and the Cell A 112 (or some other node of the mobile communication system). The sequence 130 shows another example implementation of the flow diagram 100.

[0129] The message sequence 130 starts with UL WUS configuration information being received at the UE 62 from the Cell A 112 (message 132). SIB1 information is also provided by Cell A (message 134). Note that the messages 132 and 134 may be combined or provided in a different order.

[0130] At operation 136, the UE 62 determines whether it is barred from the NES Cell 64 by determining whether the UE is barred from Cell A (and assuming that the same barring applies to NES Cell 64). The assumption that Cell A barring is applicable to the NES cell may, for example, be based on a predefined specification or may be indicated by the WUS configuration (as received in the message 132); other configurations are also possible.

[0131] FIG. 14 is a flow diagram, indicated generally by the reference numeral 140, in accordance with an example embodiment. The flow diagram 140 may be implemented at a UE.

[0132] At operation 142, a determination is made regarding whether a UE is barred from a particular network node or cell. If so, the UE may select a different node or cell to communicate with.

[0133] At operation 144, if an indication is received that a particular node or cell will not provide OD-SIB1 (or will provide a delayed OD-SIB1), the UE may select a different node or cell to communicate with, or wait for the delayed SIB1.

[0134] Finally, at operation 146, communication can occur based on received OD-SIB1 information (i.e. with a node or cell for which the UE is not barred and for which OD-SIB1 information is provided). Thus, the flow diagram 140 may combine aspects of embodiments described with reference to FIGS. 6 to 9 and aspects of embodiments described with reference to FIGS. 10 to 13.

[0135] FIG. 15 is a flow diagram, indicated generally by the reference numeral 150, in accordance with an example embodiment.

[0136] The flow diagram 150 starts at operation 152, where an UL WUS signal is sent (for example from one of the UEs described above to a network node or cell that the UE wants to communicate with). The UL WUS may be in accordance with a previously received UL WUS configuration.

[0137] At operation 153, a response (e.g. an RAR response) to the UL WUS is received.

[0138] At operation 154, a determination is made regarding whether the UE is barred from the relevant node. If so, another cell may be selected (and the flow diagram 150 terminated).

[0139] At operation 155, if an indication is received that no OD-SIB1 will be provided, then another cell may be selected (and the flow diagram 150 terminates).

[0140] Finally, at operation 156, communication can occur based on received OD-SIB1 information (i.e. with a node or cell for which the UE is not barred and for which OD-SIB1 information is provided).

[0141] For completeness, FIG. 16 is a schematic diagram of components of one or more of the example embodiments described previously, which hereafter are referred to generically as a processing system 300. The processing system 300 may, for example, be the apparatus referred to in the claims below.

[0142] The processing system 300 may have a processor 302, a memory 304 closely coupled to the processor and comprised of a RAM 314 and a ROM 312, and, optionally, a user input 310 and a display 318. The processing system 300 may comprise one or more network / apparatus interfaces 308 for connection to a network / apparatus, e.g. a modem which may be wired or wireless. The network / apparatus interface 308 may also operate as a connection to other apparatus such as device / apparatus which is not network side apparatus. Thus, direct connection between devices / apparatus without network participation is possible.

[0143] The processor 302 is connected to each of the other components in order to control operation thereof. The memory 304 may comprise a non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (SSD). The ROM 312 of the memory 304 stores, amongst other things, an operating system 315 and may store software applications 316. The RAM 314 of the memory 304 is used by the processor 302 for the temporary storage of data. The operating system 315 may contain code which, when executed by the processor implements aspects of the flow diagrams, algorithms and message sequences 60, 70, 80, 90, 100, 110, 120, 130, 140 and 150 described above. Note that in the case of small device / apparatus the memory can be most suitable for small size usage i.e. not always a hard disk drive (HDD) or a solid state drive (SSD) is used.

[0144] The processor 302 may take any suitable form. For instance, it may be a microcontroller, a plurality of microcontrollers, a processor, or a plurality of processors.

[0145] The processing system 300 may be a standalone computer, a server, a console, or a network thereof. The processing system 300 and needed structural parts may be all inside device / apparatus such as loT device / apparatus i.e. embedded to very small size.

[0146] In some example embodiments, the processing system 300 may also be associated with external software applications. These may be applications stored on a remote server device / apparatus and may run partly or exclusively on the remote server device / apparatus. These applications may be termed cloud-hosted applications. The processing system 300 may be in communication with the remote server device / apparatus in order to utilize the software application stored there.

[0147] FIG. 17 shows a tangible media, in the form of a removable memory unit 365, storing computer-readable code which when run by a computer may perform methods according to example embodiments described above. The removable memory unit 365 may be a memory stick, e.g. a USB memory stick, having internal memory 366 storing the computer-readable code. The internal memory 366 may be accessed by a computer system via a connector 367. Of course, other forms of tangible storage media may be used, as will be readily apparent to those of ordinary skilled in the art. Tangible media can be any device / apparatus capable of storing data / information which data / information can be exchanged between devices / apparatus / network.

[0148] Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and / or hardware may reside on memory, or any computer media. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "memory" or "computer-readable medium" may be any non-transitory media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

[0149] Reference to, where relevant, "computer-readable medium", "computer program product", "tangibly embodied computer program" etc., or a "processor" or "processing circuitry" etc. should be understood to encompass not only computers having differing architectures such as single / multi-processor architectures and sequencers / parallel architectures, but also specialised circuits such as field programmable gate arrays FPGA, application specify circuits ASIC, signal processing devices / apparatus and other devices / apparatus. References to computer program, instructions, code etc. should be understood to express software for a programmable processor firmware such as the programmable content of a hardware device / apparatus as instructions for a processor or configured or configuration settings for a fixed function device / apparatus, gate array, programmable logic device / apparatus, etc.

[0150] The term "means" as used in the description and in the claims may refer to one or more individual elements configured to perform the corresponding recited functionality or functionalities, or it may refer to several elements that perform such functionality or functionalities. Furthermore, several functionalities recited in the claims may be performed by the same individual means or the same combination of means. For example performing such functionality or functionalities may be caused in an apparatus by a processor that executes instructions stored in a memory of the apparatus.

[0151] If desired, the different functions discussed herein may be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the abovedescribed functions may be optional or may be combined. Similarly, it will also be appreciated that the flow diagrams, message sequences and block diagrams of Figures 6 to 15 are examples only and that various operations depicted therein may be omitted, reordered and / or combined.

[0152] It will be appreciated that the above-described example embodiments are purely illustrative and are not limiting on the scope of the invention. Other variations and modifications will be apparent to persons skilled in the art upon reading the present specification.

[0153] Moreover, the disclosure of the present application should be understood to include any novel features or any novel combination of features either explicitly or implicitly disclosed herein or any generalization thereof and during the prosecution of the present application or of any application derived therefrom, new claims may be formulated to cover any such features and / or combination of such features. Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described example embodiments and / or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims. It is also noted herein that while the above describes various examples, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.

Claims

Claims:

1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive, at a UE, uplink wake up signal configuration information; determine whether the UE is barred from a first node of a mobile communication system, wherein determining whether the UE is barred from the first node comprises making said determination before receiving or monitoring for on-demand SIB1, OD-SIB1, from the first node; and select an alternative node of the mobile communication system for communications in the event that the UE is barred from the first node.

2. An apparatus as claimed in claim 1, wherein determining whether the UE is barred from the first node comprises determining whether the UE is barred from the first node based, at least in part, on the received uplink wake signal configuration information.

3. An apparatus as claimed in claim 2, wherein the uplink wakeup signal configuration information identifies one or more UEs that are barred by the first node.

4. An apparatus as claimed in claim 2 or claim 3, wherein the uplink wakeup signal configuration information identifies one or more types of UEs that are barred by the first node.

5. An apparatus as claimed in any one of the preceding claims, wherein determining whether the UE is barred from the first node comprises determining whether the UE is barred from the first node based, at least in part, on information received from the first node.

6. An apparatus as claimed in claim 5, wherein determining whether the UE is barred from the first network node comprises: sending an OD-SIB1 transmission request from the UE to the first node; and receiving a response to the OD-SIB1 transmission from the first node indicating that the UE is barred.

7. An apparatus as claimed in claim 6, wherein the OD-SIB1 transmission request is provided as an uplink wake up signal.

8. An apparatus as claimed in claim 6 or claim 7, wherein the OD-SIB1 transmission request is implemented by a Msgl or MsgA sent from the UE to the first node.

9. An apparatus as claimed in any one of clams 6 to 8, wherein the response indicating that the requesting device is barred is provided as part of an RAR response.

10. An apparatus as claimed in any one of the preceding claims, wherein determining whether the UE is barred from the first node comprises determining whether the UE is barred from a node providing said uplink wakeup signal configuration information.

11. An apparatus as claimed in claim 10, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least: receive SIB1 information for the node providing said uplink wakeup signal configuration information; and determine that barring information including in the SIB1 information for the node providing said uplink wakeup signal configuration information applies to said first node.

12. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: provide, to a UE of a mobile communication system, uplink wake up signal configuration information, wherein the uplink wakeup signal configuration information provides information enabling the UE to determine whether the UE is barred from a first node.

13. An apparatus as claimed in claim 12, wherein the uplink wakeup signal configuration information identifies one or more UEs that are barred by the first node.

14. An apparatus as claimed in claim 12 or claim 13, wherein the uplink wakeup signal configuration information identifies one or more types of UEs that are barred by the first node.

15. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least oneprocessor, cause the apparatus to at least: receive an on-demand SIB1, OD-SIB1, transmission request from a UE of a mobile communication system at a first node of the mobile communication system; and provide a response to the OD-SIB1 transmission request to the UE, the response providing barring information.

16. An apparatus as claimed in claim 15, wherein the OD-SIB1 transmission request is provided as an uplink wake up signal.

17. An apparatus as claimed in claim 15 or claim 16, wherein the OD-SIB1 transmission request is implemented by a Msgl or MsgA sent from the UE to the first node.

18. An apparatus as claimed in any one of clams 15 to 17, wherein the response providing barring information is provided as part of an RAR response.

19. A method comprising: receiving, at a UE, uplink wake up signal configuration information; determining whether the UE is barred from a first node of a mobile communication system, wherein said determination is made before receiving or monitoring for on-demand SIB1, OD-SIB1, from the first node; and selecting an alternative node of the mobile communication system for communications in the event that the UE is barred from the first node.

20. A method comprising: providing, to a UE of a mobile communication system, uplink wake up signal configuration information, wherein the uplink wakeup signal configuration information provides information enabling the UE to determine whether the UE is barred from a first node.

21. A method comprising: receiving an on-demand SIB1, OD-SIB1, transmission request from a UE of a mobile communication system at a first node of the mobile communication system; and providing a response to the OD-SIB1 transmission request to the UE, the response providing barring information.

22. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to:receive, at a UE, uplink wake up signal configuration information; determine whether the UE is barred from a first node of a mobile communication system, wherein said determination is made before receiving or monitoring for on-demand SIB1, OD-SIB1, from the first node; and select an alternative node of the mobile communication system for communications in the event that the UE is barred from the first node.

23. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to: provide, to a UE of a mobile communication system, uplink wake up signal configuration information, wherein the uplink wakeup signal configuration information provides information enabling the UE to determine whether the UE is barred from a first node.

24. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to: receive an on-demand SIB1, OD-SIB1, transmission request from a UE of a mobile communication system at a first node of the mobile communication system; and provide a response to the OD-SIB1 transmission request to the UE, the response providing barring information.