Systems and methods for indication of additional system information transmissions

The described method optimizes network energy savings and SI delivery reliability by using UL WUS configurations to guide UEs in monitoring a subset of SSB beams, addressing the challenge of rapid UE movement and beam misalignment in on-demand SI systems.

WO2026234184A1PCT designated stage Publication Date: 2026-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/063287
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in balancing network energy savings and reliable on-demand System Information (SI) delivery, particularly in scenarios where UEs move rapidly, leading to potential misalignment between the initially selected SSB beam and the optimal beam for SI reception.

Method used

A method where a UE receives an UL WUS configuration from a first network node, which includes assistance information for monitoring PDCCH occasions associated with a subset of SSBs, allowing the UE to determine the most appropriate additional SSB beams for potential SI transmissions beyond the initial request beam, thereby optimizing energy consumption and reliability.

Benefits of technology

This approach achieves a balance between minimizing energy consumption and ensuring robust and reliable SI delivery by controlling the number of SSB beams used for transmission and reducing unnecessary UE PDCCH monitoring efforts.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026063287_12112026_PF_FP_ABST
    Figure EP2026063287_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method (300) is performed by a user equipment, UE, (812) for On-Demand System Information, OD-SI, monitoring. The method includes receiving (302), from a first network node (810), an uplink Wake-up Signal, UL WUS, configuration for a request of OD-SI associated with a second network node (810). The UL WUS configuration includes assistance 5 information for OD-SI monitoring. The UE sends (304), to the second network node, an UL WUS to request OD-SI from the second network node. The UL WUS is sent in a Random Access Channel, RACH, occasion associated with a first Synchronization Signal Block, SSB. The UE receives (306), from the second network node, a Random Access Response, RAR, for the UL WUS. Based on the RAR and the UL WUS configuration including the assistance 0 information, the UE monitors (308), for the OD-SI, at least one Physical Downlink Control Channel, PDCCH, occasion associated with a subset of SSBs of the second network node.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] SYSTEMS AND METHODS FOR INDICATION OF ADDITIONAL SYSTEM INFORMATION TRANSMISSIONS

[0002] TECHNICAL FIELD

[0003] The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for indication of additional System Information (SI) transmissions.

[0004] BACKGROUND

[0005] System Information (SI) consists of a Master Information Block (MIB) and a number of System Information Blocks (SIBs). Other System Information (OSI) encompasses all SIBs other than MIB and SIB1. Already as part of 3GPP Release 15 (Rel-15) New Radio (NR), the OSI SIBs can either be periodically broadcast on Downlink- Shared Channel (DL-SCH) or broadcast on-demand on DL-SCH such as, for example, upon request from User Equipments (UEs) in RRC IDLE, RRC INACTIVE, or RRC CONNECTED. See, 3GPP 38.300, section 7.3.1; See also, 3GPP 38.331, section 5.2.2.1.

[0006] Additionally, the 3GPP Release 19 (Rel-19) Work Item entitled “Enhancements of network energy savings for NR” includes the following objective related to on-demand SIB1 transmission:

[0007] Study procedures and signaling method(s) to support on-demand SIB1 for UEs in idle / inactive mode, including: [RAN1 / 2 / 3]

[0008] • Triggering method by uplink wake-up-signal using an existing signal / channel.

[0009] • Wake-up-signal configuration provisioning to UE

[0010] ■ Note: No modification of Synchronization Signal Block (SSB) will be discussed under this objective

[0011] • Information exchange between gNodeBs (gNBs) at least for the configuration of wake-up signal, if necessary.

[0012] • Checkpoint for normative work in RAN# 105

[0013] See, RP-223540, New WID: Network energy savings for NR, Dec. 19, 2022.

[0014] Network Energy ConsumptionFor a cell in NR, typically, an SSB is transmitted periodically, and it may be used to aid UE’s initial cell search, acquire frame / slot timing, initial time / frequency synchronization, measurements, and as Quasi Co Location (QCL) reference for channels / signals, etc. When the gNB is equipped with an antenna array, SSBs are grouped in a burst and each SSB is transmitted to a different directi on / beam. Part of the SSB, i.e., transmitted in the Physical Broadcast Channel (PBCH), is the Master Information Block (MIB), which contains essential information for the reception of SIB1. MIB and SIB1 constitute the Minimum System Information (Minimum SI) and must be read by a UE that intends to camp or establish a connection with the cell. In legacy operation, SIB1 must also be transmitted periodically towards all the available SSB directions. The SIB1 periodicity is 160ms and has a variable repetition periodicity within 160ms.

[0015] In order to increase the opportunities for a gNB to transition towards deeper sleep modes, which comes with lower energy consumption, procedures are studied with the Rel-19 Work Item (WI) to support on-demand SIB1 transmission for UEs in idle / inactive mode. In the basic scenario under discussion, the Network Energy Savings (NES) Cell relies on some other cell, Cell A, to transmit an Uplink (UL) Wake-Up-Signal (WUS) Configuration, i.e., system information that is necessary so that a UE can request SIB1 to the NES Cell. The information includes the time / frequency resources that can be used for the transmission of the request (UL WUS transmission), the type of random access that can be used, and the resources for the random access response (RAR) and other useful parameters.

[0016] According to previous techniques relating to request of SI, the gNB provides the requested SIB in at least one Physical Downlink Control Channel (PDCCH) resource that corresponds to each of the SSB beams that are transmitted in the SSB burst. It has been agreed that the network can use either this legacy approach, or the network can transmit the On-Demand-SIBl (OD-SIB1) only on the resources corresponding to the SSB beam where the requesting UE sent the UL WUS. To be more precise, the OD-SIB1 request (UL WUS transmission is the same thing in this context) is sent by Physical Random Access Channel (PRACH) in a Random Access Channel (RACH) occasion, and each RACH occasion is associated with one or more SSBs. Consequently, an OD-SIB1 request sent by a UE is associated with one or more SSBs. The gNB replies to a request by transmitting first a random access response (RAR) and then proceeds with the transmission of OD-SIB1 on appropriate downlink (DL) time-frequency resources, which are related with the SSB beams on the SSB burst transmitted by the gNB. Thus, the phrase ‘the gNB transmits OD-SIB1 on some SSB beam’ implies that the gNB transmits Random Access Response (RAR) and OD-SIB1 ontime-frequency DL resources that are associated with the particular SSB beam as discussed above.

[0017] The legacy approach improves the reliability for the reception of the requested SIB1, but network energy is likely to be wasted. In the latter approach, NES is maximized but there is the risk that the OD-SIB1 is not delivered such as, for example, when the UE is moving rapidly and its current best SSB beam is not the one when the OD-SIB1 request was transmitted.

[0018] RAN 1# 120-bis Agreement

[0019] The following agreement is updated as follows:

[0020] The UE assumes that, in the OD-SIB1 window, PDCCH for an OD- SIB1 message is transmitted in PDCCH monitoring occasions corresponding only to at least the SSB associated with the transmitted PRACH for UL-WUS if this is indicated via UL WUS configuration by a 1 -bit indication

[0021] If the 1 -bit indication is included in UL WUS config and indicates as TRUE, the UE assumes that, in the OD-SIB1 window, PDCCH for an OD-SIB1 message is transmitted in PDCCH monitoring occasions corresponding only to the SSB associated with the PRACH for UL- WUS.

[0022] If the 1 -bit indication is not included in UL WUS config or the 1 -bit indication is FALSE, the UE assumes the same as legacy, i.e., in the OD-SIB1 window, PDCCH for an OD-SIB1 message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB.

[0023] Further study possible down selection from the following options to indicate additional information related to SSBs associated with PDCCH monitoring occasions.

[0024] • Altl: The information is provided in UL-WUS config • Alt2: The information is provided in RAR in response to UL- WUS transmission

[0025] • Alt3: No additional information is provided

[0026] One of the issues for further study considers the inclusion of indication informationin the UL WUS configuration, which is transmitted by Cell A. This indication can signal to the UE that OD-SIB1 is likely to be transmitted on additional SSB beams beyond the one that was used for the transmission of the OD-SIB1 request by the UE. The transmission of OD-SIB1 on a limited number of SSB beams strikes a balance between the reliability of OD-SIB1 delivery and the achieved network energy savings.

[0027] UE Energy Saving

[0028] The UE can also benefit from knowing, in greater detail, in which PDCCH occasions (associated with which SSBs) the SIB1 is provided since then the UE can avoid monitoring in candidate PDCCH occasions which are not used. That way, the UE can save energy too.

[0029] SI in 6G

[0030] The design of SI in 6thGeneration (6G) is about to start and on-demand provisioning of both SIB1 and OSI will be considered. There are several limitations on the way on-demand of OSI (other than MIB and SIB1) works in 5thGeneration (5G) such as, for example, regarding in which beams it is provided.

[0031] There currently exist certain challenges. For example, the description of all the possible sets of additional beams can grow very large even for a few SSB beams per SSB burst and when the additional beams are restricted to 2 or 3. Yet, the size of the UL WUS configuration (OD-SIB / OD-SI request configuration) must be kept as small as possible.

[0032] SUMMARY

[0033] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, methods and systems are provided for indication of additional SI transmissions.

[0034] According to certain embodiments, a method by a UE for OD-SI monitoring includes receiving, from a first network node, an UL WUS configuration for a request of OD-SI associated with a second network node. The UL WUS configuration includes assistance information for OD-SI monitoring. The UE sends, to the second network node, an UL WUS to request OD-SI from the second network node. The UL WUS is sent in a RACH occasion associated with a first SSB. The UE receives, from the second network node, a RAR for the UL WUS. Based on the RAR and the UL WUS configuration including the assistanceinformation, the UE monitors, for the OD-SI, at least one PDCCH occasion associated with a subset of SSBs of the second network node.

[0035] According to certain embodiments, UE for OD-SI monitoring includes processing circuitry configured to receive, from a first network node, an UL WUS configuration for a request of OD-SI associated with a second network node. The UL WUS configuration includes assistance information for OD-SI monitoring. The processing circuitry is configured to send to the second network node, an UL WUS to request OD-SI from the second network node. The UL WUS is sent in a RACH occasion associated with a first SSB. The processing circuitry is configured to receive, from the second network node, a RAR for the UL WUS. Based on the RAR and the UL WUS configuration including the assistance information, the processing circuitry is configured to monitor, for the OD-SI, at least one PDCCH occasion associated with a subset of SSBs of the second network node.

[0036] According to certain embodiments, a method by a first network node for assisting OD-SI monitoring by a UE includes transmitting, to the UE for OD-SI monitoring, an UL WUS configuration for a request of OD-SI associated with a second network node. The UL WUS configuration includes assistance information for monitoring, for the OD-SI, of at least one PDCCH occasion associated with a subset of SSBs of the second network node.

[0037] According to certain embodiments, a first network node for assisting OD-SI monitoring by a UE includes processing circuitry configured to transmit, to the UE for OD-SI monitoring, an UL WUS configuration for a request of OD-SI associated with a second network node. The UL WUS configuration includes assistance information for monitoring, for the OD-SI, of at least one PDCCH occasion associated with a subset of SSBs of the second network node.

[0038] Certain embodiments may provide one or more of the following technical advantage(s). For example, certain embodiments may provide a technical advantage of achieving a balance between minimizing the energy consumption during the on-demand SIB / SI transmission and the robustness and reliability of the on-demand SIB / SI delivery. Network and UE energy consumption are minimized by controlling the number of SSB beams where OD-SIB / SI is transmitted and at the same time the UE PDCCH monitoring efforts. Robustness and reliability are improved against the event that the initially selected SSB direction for OD-SIB / SI request has rapidly deteriorated and some other SSB direction is more appropriate for OD-SIB / SI reception.

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

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

[0041] FIGURES 1A, IB, and 1C illustrate example SSB_ODSI_REQ-to-SSB_ODSI_RESP mappings, according to certain embodiments;

[0042] FIGURES 2A and 2B illustrate example methods by a UE for OD-SI monitoring, according to certain embodiments;

[0043] FIGURE 3 illustrates another example method by a UE for limiting OD-SI monitoring, according to certain embodiments;

[0044] FIGURE 4 illustrates an example method by a first network node associated with a first cell, according to certain embodiments;

[0045] FIGURE 5 illustrates another example method by a first network node for limiting OD-SI monitoring by a UE, according to certain embodiments;

[0046] FIGURE 6 illustrates an example method by a second network node associated with a second cell, according to certain embodiments

[0047] FIGURE 7 illustrates another method by a second network node for limiting OD-SI monitoring by a UE, according to certain embodiments;

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

[0049] FIGURE 9 illustrates another example communication system, according to certain embodiments;

[0050] FIGURE 10 illustrates an example wireless device, according to certain embodiments; FIGURE 11 illustrates an example network node, according to certain embodiments; FIGURE 12 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments;

[0051] FIGURE 13 illustrates an example grid of SSB-beams and an associated subset of SSB indices for each SSB index, according to certain embodiments; and

[0052] FIGURE 14 illustrates example assistance data.

[0053] DETAILED DESCRIPTION

[0054] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.As used herein, ‘node’ can be a network node or a UE. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), Operations Support System (OSS), Self Organizing Network (SON), positioning node (e.g. E-SMLC), etc. The terms network node and radio network node are used interchangeably herein.

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

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

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

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

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

[0060] According to previous methods and systems, the set of beams in which the UE can expect OD-SI provision is added to the random access response message (i.e., the response to the UL-WUS or OD-SIB request). According to certain embodiments described herein, however, information is added as part of the UL-WUS configuration. Note that the term UL-WUS configuration used may equally be interchanged to any OD-SIB / OD-SI configuration.

[0061] Several ways to concisely describe a small number of sets of additional SSB beams are provided. Each set is associated with the SSB beam where the initial request of OD-SIB / OD-SI (e.g. OD-SIB 1) was sent. This beam does not need to be a member of the associated set since it is already guaranteed that the OD-SIB / SI will be transmitted on that direction. The set characterization includes the explicit enumeration of the relevant SSB beams but can also be based on a qualitative description of some common property of the included beams.In addition, according to certain embodiments, methods and systems are provided for use by a UE that has requested the SIB / SI on demand. With these systems and methods, the UE can independently determine the most appropriate additional SSB beams to monitor for potential OD-SIB / SI transmissions beyond the transmission that corresponds to the SSB beam of the OD-SIB / SI request.

[0062] Certain methods at the UE and the gNB, as described herein, have mainly been outlined based on the 3GPP Rel-19 WI on Network Energy Savings. However, several of them can be trivially extended to other System Information transmissions, i.e., System Information Blocks (SIBx), x=2,3..., that are not essential for connection and camping on a cell but carry other useful information to the UE.

[0063] As used herein, the following definitions / naming conventions are adopted:

[0064] • The SSB associated with the PRACH resource and RACH occasion used by the UE for the OD-SI request is referred to as SSB ODSI REQ.

[0065] • Upon OD-SI request, the NES cell sends OD-SI PDCCH in PDCCH occasions associated with a set of SSBs. This set of SSBs is denoted SSB ODSI RESP.

[0066] • SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping: For each possible SSB ODSI REQ, a mapping to the corresponding SSB ODSI RESP.

[0067] • In a list or vector or other enumeration of elements, the first order neighbors of the element at position k are the elements at position k-1 and k+1, given that these element positions exist. The second and order neighbors are the elements at positions k-2 and k+2, etc. Furthermore the first order left neighbor is the element at position k-1, the first order right neighbor is k+1, etc.

[0068] • In a two-dimensional (2D) structure, e.g., a matrix or a list of lists (or vectors), the first order neighbors of the element at position (j, k) are the elements at positions (j-1, k-1), (j-1, k), (j-1, k+1), (j, k-1), (j, k+1), (j+1, k-1), (j+1, k), and (j+1, k+1) given that these element positions exist. In mathematics, this corresponds to 1 in Chebyshev distance, also known as maximum metric or chessboard distance. Other metrics in 2D are not precluded, like the taxicab distance (also known as rectilinear distance or LI distance), but the examples are based in Chebyshev distance for simplicity.Currently, in a case when the legacy approach for request of SI is not used, there is no mechanism in place to enable the UE to infer or assume that the OD-SIB1 will be sent in SSB beams other than the SSB beam corresponding to the initial request. Additionally, as described above, the description of all the possible sets of additional beams can grow very large even for a few SSB beams per SSB burst and when the additional beams are restricted to 2 or 3. Yet, the size of the UL WUS configuration (OD-SIB / OD-SI request configuration) must be kept as small as possible. Thus, systems and methods are needed for defining the most useful sets of additional beams without increasing the size of the configuration too much.

[0069] According to certain embodiments, a method in a UE for limiting OD-SI monitoring to PDCCH occasions associated with a subset of SSBs includes at least one of:

[0070] • Receiving, from a first network node (Cell A), an UL WUS configuration for the request of on-demand SI (OD-SI) in a second network node (NES Cell). The UL WUS configuration includes assistance information regarding the OD-SI monitoring behavior following an OD-SI request.

[0071] • Sending UL WUS to request OD-SI from a second network node (NES Cell).

[0072] The UL WUS is sent in a RACH occasion associated with a specific SSB referred to as SSB ODSI REQ.

[0073] • Receiving, from the second network node, a random access response (RAR) for the UL WUS, where the RAR may or may not include additional assistance information regarding the OD-SI monitoring behavior.

[0074] • Monitoring SI PDCCH occasions associated with a subset of all SSBs in the second network node (NES Cell) in accordance with the assistance information in the UL WUS configuration and / or RAR. The subset of SSBs is referred to as SSB ODSI RESP.

[0075] In a particular embodiment, the SI is SIB1 or some other system information block, which may be referred to as SIBX, or a system information message including one or more different SIBs.

[0076] In a particular embodiment, the first and second network node can be the same cell or different cells.

[0077] In a particular embodiment, the assistance information in the UL WUS configuration can be explicit or descriptive. If explicit, the assistance information indicates a mapping from each possible SSB ODSI REQ to the corresponding SSB ODSI RESP. This is referred to asthe SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping. FIGURE 1A illustrates an example SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping 100, according to certain embodiments.

[0078] In a particular embodiment, for a given SSB ODSI REQ, SSB ODSI RESP always includes SSB ODSI REQ. That is, SI will always be provided in the PDCCH occasions associated with the SSB which is associated to the RACH occasion where the OD-SI request was sent.

[0079] In a particular embodiment, SSB ODSI REQ is not explicitly included in the SSB ODSI RESP included in the assistance information. Given that the SI will always be provided in the PDCCH occasions associated with the SSB which is associated to the RACH occasion where the OD-SI request was sent, this information need not be explicitly included and can be deduced. FIGURE IB illustrates another example SSB ODSI REQ to SSB ODSI RESP mapping 120 but without explicitly including SSB ODSI REQ in SSB ODSI RESP, according to certain embodiments. In the illustrated embodiment, the element in position SSB ODSI REQ in the bitmap SSB ODSI RESP is assumed to be ‘1’ and is not included.

[0080] In a further particular embodiment, some SSB ODSI REQ may not be explicitly included in the assistance information. For example, the SSB_ODSI_REQ-to-SSB ODSI RESP mapping is not present for some SSB ODSI REQ. If a particular SSB ODSI REQ is not present, it may be understood as the SSB ODSI RESP being equal to the SSB ODSI REQ. For example, if the OD-SI request was sent in that SSB ODSI REQ, the SI is only provided in that same SSB ODSI REQ.

[0081] In a particular embodiment, the SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping is expressed as one of the following:

[0082] • For each possible SSB ODSI REQ, the corresponding SSB ODSI RESP is provided as a bitmap where each SSB in the set is indicated with “1” at the corresponding SSB index position, and the remaining SSBs are indicated with “0”. In this case, SSB ODSI REQ need not to be included in the bitmap since it is anyway assumed that SSB ODSI REQ is always included in the corresponding SSB ODSI RESP set.

[0083] • For each possible SSB ODSI REQ, the corresponding SSB ODSI RESP is provided as a list of SSB indices. In this case, SSB ODSI REQ need not to be included in the list since it is anyway assumed that SSB ODSI REQ is always included in the corresponding SSB ODSI RESP set.• A single structure or enumeration applicable for all SSB ODSI REQ.

[0084] In a particular embodiment, the SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping allows the following:

[0085] • Different SSB ODSI REQ can be mapped to the same or different SSB ODSI RESP. If two or more different SSB ODSI REQ are mapped to the same SSB ODSI RESP, the SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping is from one set of SSBs to another set of SSBs. FIGURE 1C illustrates an example SSB ODSI REQ to SSB ODSI RESP mapping 130 where two SSB-ODSI REQ are mapped to the same SSB ODSI RESP, according to certain embodiments. Specifically, SSB ODSI REQ = 1 and 2 are mapped to the same SSB ODSI RESP. That is, if SSB ODSI REQ = 1, then SSB ODSI RESP = {1,2}, etc.

[0086] • The same SSB can be in the SSB ODSI RESP set for different SSB ODSI REQ.

[0087] • Some SSBs need not belong to SSB ODSI RESP for any possible SSB ODSI REQ.

[0088] • SSB ODSI RESP can be the empty set.

[0089] In a particular embodiment, the SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping is provided for each possible SSB ODSI REQ in a single structure rather than multiple mapping lists. The single structure includes all possible SSB ODSI REQ in a one-dimensional (ID) structure. For example, the single structure may include an ordered list or vector or other enumeration. Alternatively, the single structure may include all possible SSB ODSI REQ in a two-dimensional (2D) structure such as, for example, a matrix, a list of lists or vectors, or similar. For a given SSB ODSI REQ at a specific position in the structure, the corresponding SSB ODSI RESP is obtained from the adjacent elements within the structure.

[0090] In a particular embodiment, the single structure is an enumeration of all SSBs. For the ID structure, for SSB ODSI REQ being the SSB at position k in the enumeration, SSB ODSI RESP is given by the SSBs at positions {k-1, k, k+1} in the enumeration, i.e., the first order neighbors of SSB ODSI REQ (and SSB ODSI REQ itself). Similarly, in the case of the 2D structure, for SSB ODSI REQ being the SSB at position (j, k) in the matrix, SSB ODSI RESP is given by the SSBs at positions (j-1, k-1), (j-1, k), (j-1, k+1), (j, k-1), (j, k), (j, k+1), (j+1, k-1), (j+1, k), and (j+1, k+1).In an example, assume that there are 8 SSBs used by the second network node (the NES cell), which may be denoted as bO... b 7. In the UL WUS configuration, the first network node (Cell A) configures an SSB ODSI REQ-to-SSB ODSI RESP mapping structure such as:

[0091] {bl, b3, b2, bO, b5, b6, b4, b7}.

[0092] In this example, if the UE would transmit OD-SIB1 request in b3 (i.e., transmit PRACH which is associated with b3), then the UE would expect the second network node to, in response, transmit OD-SIB1 in at least bl, b3 and b2 which are first-order neighbors according to the configuration structure.

[0093] In another example, assume that there are 16 SSBs used in the second network node (the NES cell), which may be denoted as b0...bl5. In a particular embodiment, the SSBs are located in the following 2D mapping structure:

[0094] {{ bO, bl, b2, b3},

[0095] { b4, b5, b6, b7},

[0096] { b8, b9, blO, bll},

[0097] { b!2, b!3, b!4, b!5}}

[0098] In this example, if the UE would transmit OD-SIB1 request in b7, then the UE would expect the second network node to, in response, transmit OD-SIB1 in at least b2, b3, b6, b7, blO and bll.

[0099] In a particular embodiment, the explicit assistance information by a single structure in the UL WUS configuration is further extended by a parameter, which may be denoted, for example, as num adjacent resp beams. This parameter configures the order of neighbors within the configuration structure, which make up the set SSB ODSI RESP. For a given SSB_ODSI_REQ in the single structure, if num adjacent resp beams = 2, then the corresponding SSB ODSI RESP is given by the neighbors of order up to 2 in the structure, etc. For example, with num adjacent resp beams = 2, the single structure {bl, b3, b2, bO, b5, b6, b4, b7} and SSB ODSI REQ = b3, the corresponding SSB_ODSI_RESP = {bl, b3, b2, bO}. Note that on the left side of b3 in the structure there is only a first-order neighbor, hence only bl on that side.

[0100] In a particular embodiment, the UL WUS configuration allows a configuration of different num adjacent resp beams for left and right side of the initiated beam in the configuration, in the case of a ID structure. For a 2D structure, the WUS configuration may allow a configuration of different num adjacent resp beams for left, right, up, down, or any subset / grouping of them (e.g., vertical vs horizontal direction).In a particular embodiment, the UE receives an indication of the value of num adjacent resp beams from the second network node (NES cell) in the RAR for UL WUS.

[0101] In a particular embodiment, the SSB ODSI REQ- o-SSB ODSI RESP mapping provided in the UL WUS configuration is descriptive. That is, SSB beams are split into different sets depending on some property such as, for example, a property name indicating sets of SSB beams. In a further particular embodiment, the property is, for example, based on the geometry of the array such as, for example, the SSB beams are associated with antenna ports that are adjacent to each other. In another particular embodiment, the property is associated with propagation properties of the SSB beams such as, for example, the set of beams that overlap by a certain part of the coverage area. In another particular embodiment, the property is determined by other channel characteristics such as, for example, some beams could be more likely to experience a specific degree of Doppler shift or delay spread. Data collected during offline network measurement campaigns, analysis of historical data related to UEs’ channel characteristics obtained during network operation, analysis of the propagation environment based on software tools (digital twins, ray tracing) can be used to uncover potential relations between SSB beams.

[0102] In another example, the UL WUS configuration has a first entry:

[0103] (property name = Doppler Shift bO, SSB ODSI REQ = bO, SSB ODSI RESP = {bO, b3, b4, b7}).

[0104] The same SSB ODSI REQ could also be associated with a different set of response beams via a different property such as for example:

[0105] (property name = area overlap bO, SSB ODSI REQ = bO, SSB ODSI RESP = {bO, bl, b5}).

[0106] In a particular embodiment, the UE receives multiple descriptive associations for the same SSB ODSI REQ in the UL WUS configuration, and the UE receives, from the second network node, in the RAR for UL WUS, an indication of:

[0107] • which of the multiple descriptive associations that apply, i.e., SSB ODSI RESP is determined by the property indicated in RAR, or

[0108] • an explicit indication of the additional SSB beams. In this case, the updated information overwrites the information provided in the UL WUS configuration. In the UE side, based on the correct entry in the UL WUS configuration, the UE independently selects the beams where it can monitor PDCCH for potential OD-SItransmissions as given by the corresponding SSB ODSI RESP set. In a particular embodiment, when the beam where the OD-SI was requested is not associated with any set of additional SSB beams, it is up to UE implementation to decide if it is monitoring additional PDCCH occasions. When the SSB ODSI REQ is associated with an SSB ODSI RESP, the UE uses this indication to monitor additional monitoring occasions, in various particular embodiments. When the SSB ODSI REQ is associated with several SSB ODSI RESP, the UE selects one of the association sets or combines the beams from the indicated association cells, in a particular embodiment. One type of combining could be the union of all the sets of SSB ODSI RESP or the intersection of the sets of SSB ODSI RESP or the entries in SSB ODSI RESP that appear in at least A of the associated response SSB sets. The selection of the type of combining could depend on several parameters, states and conditions. For example, assume that the UE is operating in a battery saving mode. Then the intersection could be most appropriate choice for combining. An example where the union of all sets of SSB ODSI RESP is appropriate follows. In an example where the two properties are transitive, it makes sense from the UE side to consider the union of the SSB ODSI RESP sets. In some other example, if the UE has a record of SSB measurements that show a consistently low received power for certain beams belonging to SSB ODSI RESP it can decide to avoid monitoring the corresponding SI resources associated with these beams. In contrast, if the UE has a record of consistently high power SSB beams, the UE can prioritize the monitoring of the SI resources corresponding to these beams.

[0109] In the above, several embodiments applying to the UE side have been described in detail. A similar set of embodiments that mirror the functionality described above can also apply to a first network node (Cell A) to limit on-demand system information (OD-SI) transmissions to PDCCH occasions associated with a subset of SSBs. Certain of these embodiments are described in more detail below.

[0110] FIGURES 2A and 2B illustrate example methods by a UE for OD-SI monitoring, according to certain embodiments. Specifically, FIGURE 2A illustrates an example method 200 by a UE for OD-SI monitoring that includes at least one of: a receiving step 202, a sending step 204, a receiving step 206, and a monitoring step 208.

[0111] For example, at step 202, the UE may receive, from a first network node (Cell A), an UL WUS configuration for a request of OD-SI in a second network node (NES Cell). The UL WUS configuration comprising assistance information regarding the OD-SI monitoring behavior following an OD-SI request.For example, at step 204, the UE may send UL WUS to request OD-SI from a second network node (NES Cell), the UL WUS being sent in a RACH occasion associated with a specific SSB referred to as SSB ODSI REQ.

[0112] For example, at step 206, the UE may receive, from the second network node, a RAR for the UL WUS, wherein the RAR may or may not include additional assistance information regarding the OD-SI monitoring behavior.

[0113] For example, at step 208, the UE may monitor SI Physical Downlink Control Channel PDCCH occasions associated with a subset of all SSBs in the second network node (NES Cell) in accordance with the assistance information in the UL WUS configuration and / or RAR, wherein the subset of SSBs is referred to as SSB ODSI RESP .

[0114] In various particular embodiments, the UE may perform any of the operations and steps or include any of the features described with respect to the Group A and / or B Example Embodiments below or any other embodiments described herein.

[0115] As another example, FIGURE 2B illustrates another example method 250 by a UE for OD-SI monitoring that includes at least one of: a receiving step 252, a sending step 254, a receiving step 256, and a monitoring step 258.

[0116] For example, at step 252, the UE may receive, from a first network node associated with a first cell, an UL WUS configuration for a request of OD-SI in a second cell associated with a second network node. The UL WUS configuration comprises assistance information for OD-SI monitoring.

[0117] For example, at step 254, the UE may send, to the second network node, an UL WUS to request OD-SI from the second network node. The UL WUS is sent in a RACH occasion associated with a first SSB.

[0118] For example, at step 256, the UE may receive, from the second network node, a RAR for the ULWUS.

[0119] For example, at step 258, the UE may, based on the RAR, monitor at least one PDCCH occasion associated with a subset of all SSBs in the second cell for the OD-SI.

[0120] In various particular embodiments, the UE may perform any of the operations and steps or include any of the features described with respect to the Group A and / or B Example Embodiments below or any other embodiments described herein.

[0121] FIGURE 3 illustrates another example method 300 by a UE for OD-SI monitoring, according to certain embodiments. In the illustrated embodiment, for example, the method 300 begins at step 302 when the UE receives, from a first network node, an UL WUS configuration for a request of OD-SI associated with a second network node. The UL WUS configurationincludes assistance information for OD-SI monitoring. At step 304, the UE sends, to the second network node, an UL WUS to request OD-SI from the second network node. The UL WUS is sent in a RACH occasion associated with a first SSB. At step 306, the UE receives, from the second network node, a RAR for the UL WUS. Based on the RAR and the UL WUS configuration comprising the assistance information, the UE monitors, for the OD-SI, at least one PDCCH occasion associated with a subset of SSBs of the second network node, at step 308.

[0122] In a particular embodiment, the OD-SI comprises at least one of: a SIB1; SIBX; and a system information message comprising one or more different system information blocks.

[0123] In a particular embodiment, the first network node and the second network node are a same network node, or the first network node and the second network node are different network nodes.

[0124] In a particular embodiment, the RAR comprises additional assistance information for performing the monitoring for the OD-SI, and wherein the monitoring of the at least one PDCCH occasion associated with the subset of SSBs is based on the additional assistance information.

[0125] In a particular embodiment, the assistance information indicates a mapping of each of a plurality of SSBs to a corresponding one of a plurality of subsets of SSBs of the second network node for monitoring.

[0126] In a further particular embodiment, the first SSB is denoted as a SSB ODSI REQ,- the subset of SSBs is denoted as a SSB ODSI RESP, ' and the mapping comprises a SSB ODSI REQ-to-SSB ODSI RESP mapping.

[0127] In a further particular embodiment, the SSB ODSI RESP always includes the SSB ODSI REQ.

[0128] In a further particular embodiment, the SSB ODSI REQ is not explicitly indicated in the assistance information, and the UE determines that the SSB ODSI RESP is equal to the SSB ODSI REQ.

[0129] In a further particular embodiment, the mapping is expressed as at least one of: for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a bitmap where each SSB in the set is indicated with “1” at the corresponding SSB index position, and the remaining SSBs are indicated with “0”; for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a list of SSB indices; and a single structure or enumeration applicable for all SSB ODSI REQ.In a further particular embodiment, the mapping is provided for each possible SSB ODSI REQ in a single structure. The single structure comprises an ordered list, vector, or enumeration of SSBs; or the single structure includes all possible SSB ODSI REQ in a two-dimensional structure, and the two-dimensional structure comprises at least one of: a matrix, a list, a list of lists, and a list of vectors.

[0130] In a particular embodiment, the UL WUS configuration or the RAR for UL WUS comprises a value of a parameter configuring an order of neighbors within a configuration structure.

[0131] In a particular embodiment, the assistance information includes a mapping that splits SSB beams into different sets depending on at least one property, and wherein the property is based on at least one of: a geometry of an array, at least one propagation property of the SSB beams, at least one channel characteristic, data collected during offline network measurement campaigns, analysis of historical data related to UEs’ channel characteristics obtained during network operation, and analysis of the propagation environment based on software tools.

[0132] In a particular embodiment, the UE receives a plurality of descriptive associations for a particular SSB in the UL WUS configuration, and the UE receives from the second network node in the RAR for UL WUS an indication of at least one of: which of the multiple descriptive associations that apply, and an explicit indication of an additional SSB beams.

[0133] In a particular embodiment, when the first SSB is associated with a single subset of SSBs, using an indication of an association to monitor at least one additional monitoring occasion. Alternatively, when the first SSB is associated with at least two subsets of SSBs, selecting one of a plurality of association sets or combining beams from an indication of associated cells.

[0134] FIGURE 4 illustrates an example method 400 by a first network node associated with a first cell, according to certain embodiments. In the illustrated embodiment, the method 400 includes a transmitting step 402. For example, at step 402, the first network node transmits, to a UE for the performance of OD-SI monitoring, an UL WUS configuration for a request of OD-SI in a second cell associated with a second network node. The UL WUS configuration comprises assistance information for OD-SI monitoring of at least one PDCCH occasion associated with a subset of all SSBs in the second cell for the OD-SI.

[0135] In various particular embodiments, the first network node may perform any of the operations and steps or include any of the features described with respect to the Group C and / or D Example Embodiments below or any other embodiments described herein.FIGURE 5 illustrates another example method 500 by a first network node for OD-SI monitoring by a UE, according to certain embodiments. In the illustrated example, the method includes, at step 502, the first network node transmitting, to the UE for OD-SI monitoring, an UL WUS configuration for a request of OD-SI associated with a second network node. The UL WUS configuration includes assistance information for monitoring, for the OD-SI, of at least one PDCCH occasion associated with a subset of SSBs of the second network node.

[0136] In a particular embodiment, the OD-SI comprises at least one of: a SIB1; SIBX; and a system information message comprising one or more different system information blocks.

[0137] In a particular embodiment, the first network node and the second network node are a same network node, and the first network node receives, from the UE, an UL WUS to request OD-SI from the second network node. The UL WUS is sent in a RACH occasion associated with a first SSB. The first network node transmits, to the UE, a RAR for the UL WUS, and the monitoring is based on at least the RAR. The first network node transmits, to the UE, a PDCCH for the OD-SI in the at least one PDCCH occasion associated with the subset of SSBs of the second network node.

[0138] In a further particular embodiment, the RAR comprises additional assistance information for performing the monitoring for the OD-SI.

[0139] In a particular embodiment, the assistance information indicates a mapping of each of a plurality of SSBs to a corresponding one of a plurality of subsets of SSBs of the second network node for monitoring.

[0140] In a further particular embodiment, the first SSB is denoted as a SSB ODSI REQ,- the subset of SSBs is denoted as a SSB ODSI RESP, ' and the mapping comprises a SSB ODSI REQ-to-SSB ODSI RESP mapping.

[0141] In a further particular embodiment, the SSB ODSI RESP always includes the SSB ODSI REQ.

[0142] In a further particular embodiment, the SSB ODSI REQ is not explicitly indicated in the assistance information, and the method comprises determining that the SSB ODSI RESP is equal to the SSB ODSI REQ.

[0143] In a further particular embodiment, the mapping is expressed as at least one of: for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a bitmap where each SSB in the set is indicated with “1” at the corresponding SSB index position, and the remaining SSBs are indicated with “0”; for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a list of SSB indices; and a single structure or enumeration applicable for all SSB ODSI REQ.In a further particular embodiment, the mapping is provided for each possible SSB ODSI REQ in a single structure. The single structure comprises an ordered list, vector, or enumeration of SSBs; or the single structure includes all possible SSB ODSI REQ in a two-dimensional structure, and the two-dimensional structure comprises at least one of: a matrix, a list, a list of lists, and a list of vectors.

[0144] In a particular embodiment, the UL WUS configuration or the RAR for the UL WUS comprises a value of a parameter configuring an order of neighbors within a configuration structure.

[0145] In a particular embodiment, the assistance information comprises a mapping that splits SSB beams into different sets depending on at least one property, and wherein the property is based on at least one of: a geometry of an array, at least one propagation property of the SSB beams, at least one channel characteristic, data collected during offline network measurement campaigns, analysis of historical data related to UEs’ channel characteristics obtained during network operation, and analysis of the propagation environment based on software tools.

[0146] FIGURE 6 illustrates an example method 600 by a second network node associated with a second cell, according to certain embodiments. In the illustrated embodiment, the method 600 includes a receiving step 602 and a transmitting step 604. For example, at step 602, the second network node receives, from a UE, an UL WUS to request OD-SI from the second network node. The UL WUS is sent in a RACH occasion associated with a first SSB. At step 604, for example, the second network node transmits, to the UE, a RAR for the UL WUS for monitoring by the UE of at least one PDCCH occasions associated with a subset of all SSBs in the second cell for the OD-SI.

[0147] In various particular embodiments, the second network node may perform any of the operations and steps or include any of the features described with respect to the Group C and / or D Example Embodiments below or any other embodiments described herein.

[0148] FIGURE 7 illustrates another method 700 by a second network node for OD-SI monitoring by a UE, according to certain embodiments. As illustrated, the method begins at step 702 when the second network node receives, from the UE, an UL WUS requesting OD-SI from the second network node. The UL WUS is sent in a RACH occasion associated with a first SSB. At step 704, the second network node transmits, to the UE, a RAR for the UL WUS, and the RAR includes assistance information for monitoring, for the OD-SI, by the UE of at least one PDCCH, occasion associated with a subset of SSBs of the second network node.

[0149] In a particular embodiment, the OD-SI comprises at least one of: SIB1, SIBX, and a system information message comprising one or more different system information blocks.In a particular embodiment, the second network node transmits, to the UE, an UL WUS configuration for the request of OD-SI, and the UL WUS configuration comprises additional assistance information for OD-SI monitoring.

[0150] In a particular embodiment, the OD-SI is always provided in PDCCH occasions associated with the first SSB.

[0151] In a particular embodiment, the assistance information comprises a mapping of each of a plurality of SSBs to a corresponding one of a plurality of subsets of SSBs of the second network node for monitoring.

[0152] In a particular embodiment, the first SSB is denoted as a SSB ODSI REQ,' the subset of SSBs is denoted as a SSB ODSI RES,' and the mapping comprises a SSB ODSI REQ-to-SSB ODSI RESP mapping.

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

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

[0155] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 802 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 802, including one or more access network nodes 810 and / or core network nodes 808.Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or anon-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies.

[0156] The network nodes 810 facilitate direct or indirect connection of one or more UEs 812 to the core network 806 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 800 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 800 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

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

[0158] In the depicted example, the core network 806 connects elements of the access network 804 (e.g., one or more of the network nodes 810) to one or more host computing systems, such as host 816. 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 806 includes one or more core network nodes (e.g., core network node 808) of various types, one or more of which may be generally referred to as network nodes 808. Network nodes 808 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 808. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

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

[0160] As a whole, the communication system 800 of FIGURE 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 800 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 800 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 800 supporting different standards, protocols, or rule sets.

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

[0162] Telecommunications network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 802. For example, the telecommunications network 802 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

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

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

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

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

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

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

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

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

[0171] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP 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).

[0172] The UE 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input / output interface 1006, apower source 1008, amemory 1010, a communication interface 1012, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 10. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0173] The processing circuitry 1002 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructionsstored as machine-readable computer programs in the memory 1010. The processing circuitry 1002 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 1002 may include multiple central processing units (CPUs).

[0174] In the example, the input / output interface 1006 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 1000. 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.

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

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

[0177] The memory 1010 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1010 may allow the UE 1000 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 1010, which may be or comprise a device-readable storage medium.

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

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

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

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

[0182] 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, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring aplant 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 1000 shown in FIGURE 10.

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

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

[0185] FIGURE 11 shows a network node 1100, which may be an embodiment of the network node 810 of FIGURE 8, in accordance with some embodiments.

[0186] As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 1100 may be configured to operate in communication system 800 of FIGURE 8, like network nodes 808 or 810, or in communication system 900 of FIGURE 9, like an AP 910 or a station 912. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0187] Network nodes 1100 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 ofcoverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 1100 may be a relay node or a relay donor node controlling a relay. Network nodes 1100 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

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

[0189] In particular embodiments, network node 1100 includes a processing circuitry 1102, a memory 1104, a communication interface 1106, and a power source 1108. In general, in a particular embodiment of network node 1100, processing circuitry 1102, memory 1104, communication interface 1106, and power source 1108 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1100.

[0190] The network node 1100 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 1100 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities 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 1100 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1104 or portions of memory 1104 for different RATs) and some components may be reused (e.g., a same antenna 1110 may be shared by different RATs). The network node 1100 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1100, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1100.

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

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

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

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

[0195] In certain alternative embodiments, network node 1100 may be capable of wireless communication but does not include separate radio front-end circuitry 1118, instead, the processing circuitry 1102 includes radio front-end circuitry and is connected to the antenna 1110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1112 is part of the communication interface 1106. In still other embodiments, the communication interface 1106 includes one or more ports or terminals 1116, the radio front-end circuitry 1118, and the RF transceiver circuitry 1112, as part of a radio unit (not shown), and the communication interface 1106 communicates with the baseband processing circuitry 1114, which is part of a digital unit (not shown).

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

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

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

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

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

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

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

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

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

[0205] Hardware 1204 may be implemented in a standalone network node with generic or specific components. Hardware 1204 may implement some functions via virtualization. Alternatively, hardware 1204 may be part of a larger cluster of hardware (e.g. such as in a data31 of 66

[0206] center or CPE) where many hardware nodes work together and are managed via management and orchestration 1210, which, among others, oversees lifecycle management of applications 1202. In some embodiments, hardware 1204 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 1212 which may alternatively be used for communication between hardware nodes and radio units.

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

[0208] 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 thoseparticular 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.

[0209] ADDITIONAL INFORMATION

[0210] On-demand SIB1 for UEs in IDLE / INACTIVE mode for NES

[0211] Introduction

[0212] After revision at RAN#105, the WID for NR Rel-19 “Enhancements of network energy savings for NR states the following objective:

[0213] Specify support for on-demand SIB1 for UEs in idle / inactive mode [RAN1 / 2 / 3] • Specify procedures and signaling method(s) for Case 2 [RAN1 / 2] Case 2: UE obtains UL WUS configuration from Cell A, UE transmits UL WUS on NES Cell, UE receives on-demand SIB1 from NES Cell

[0214] Triggering method by UL WUS using PRACH

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

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

[0217] • Note 2:

[0218] UL WUS: Uplink wake-up signal

[0219] Cell A: A cell that is periodically transmitting at least its own SIB1 NES Cell: A cell that may transmit SIB1 transmission in response to ULWUS from aUE

[0220] • Note 3:

[0221] RANI strives to minimize impact to legacy UE

[0222] RANI specification impact to support this feature should be minimized

[0223] See, RP-242354, ‘Enhancements of network energy savings for NR”, 3GPP TSG RAN Meeting #105, Melbourne, Australia, September, 2024.

[0224] Herein, analysis and proposals are presented with respect to this objective.Discussion

[0225] Spatial-domain aspects of OD-SIB1 delivery

[0226] Background:

[0227] RANl#120-bis Agreement

[0228] The following agreement is updated as follows:

[0229] • The UE assumes that, in the OD-SIB1 window, PDCCH for an OD-SIB1 message is transmitted in PDCCH monitoring occasions corresponding only to at least the SSB associated with the transmitted PRACH for UL-WUS if this is indicated via UL WUS configuration by a 1-bit indication

[0230] ■ If the 1-bit indication is included in UL WUS config and

[0231] indicate as TRUE, the UE assumes that, in the OD-SIB1 window, PDCCH for an OD-SIB1 message is transmitted in PDCCH monitoring occasions corresponding only to the SSB associated with the PRACH for UL-WUS.

[0232] ■ If the 1-bit indication is not included in UL WUS config or the

[0233] 1-bit indication is FALSE, the UE assumes the same as legacy, i.e., in the OD-SIB1 window, PDCCH for an OD-SIB1

[0234] message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB.

[0235] • Further study possible down selection from the following options

[0236] to indicate additional information related to SSBs associated with PDCCH monitoring occasions

[0237] • Altl : The information is provided in UL-WUS config

[0238] • Alt2: The information is provided in RAR in response to UL- WUS transmission

[0239] • Alt3: No additional information is provided

[0240] The above agreement enables the NW to save energy by limiting OD-SIB1 transmissions to PDCCH monitoring occasions corresponding to the SSB associated with the PRACH for UL-WUS, if this is indicated via UL WUS configuration.

[0241] The third bullet in the above agreement is a For Future Study (FFS) about “additional information related to SSBs associated with PDCCH monitoring occasions.” Based on previous discussions and proposals, an understanding is that the key idea is to indicate a subset of SSBs,or rather PDCCH occasions associated with SSBs, where SIB1 is provided. It is reasonable that the subset of PDCCH occasions depends on which PRACH resource that the UE uses for UL-WUS. For example, if the UE send UL-WUS in an RO which is mapped to SSB index 1, then SIB1 is provided in the PDCCH occasions of SSB#1 and additional SSBs that are spatially adjacent to SSB#1. (This can for example improve the coverage for UEs that are moving fast.) The information can be encoded as a list of SSB indices or a bitfield indicating the subset of SSBs, for example.

[0242] When the information is provided in UL-WUS config (Altl), it is semi-static. Hence it must account for all RACH occasions where the UE can send UL WUS. The information could for example consist of a list of SSB indices and SSB subsets, where each SSB index is mapped to a subset of SSBs. If the UE sends UL WUS in an RO mapped to SSB A, then the UE should expect SIB1 in the PDCCH occasions of the corresponding subset of SSBs. FIGURE 13 illustrates an example 1300 a grid of SSB-beams 1302 on the right. For each SSB index 1304 there is an associated subset of SSB indices 1306. If the UE send UL WUS in a RO associated with SSB index 1, it should expect SIB1 to be provided in the PDCCH occasions associated with SSB indices 1,2 and 5, etc. With Altl, the entire Table must be provided in UL WUS config, while with Alt2 it is enough to provide the applicable row of the table in RAR.

[0243] Observation 1 : If additional information related to SSBs associated with PDCCH monitoring occasions is provided in UL-WUS (Altl), it is semi-static and must account for all RACH occasions where the UE can send UL WUS.

[0244] With Alt2, the information can be dynamic and adjusted depending on the PRACH resource that the UE use for UL-WUS and other things. This means that the information can be significantly condensed: only the applicable subset of SSBs is indicated in RAR, see Figure 1. Additional methods for compression of the signaling information can be devised.

[0245] Observation 2: If additional information related to SSBs associated with PDCCH monitoring occasions is provided in RAR (Alt2), it is dynamic and can be tailored to the PRACH resource used for UL WUS.

[0246] Alt2 is preferred over Altl because it is dynamic and much more efficient (the UL WUS configuration must be kept as small as possible). However, this kind of additional information should be considered as an optimization for a comer case. If the UE fails to receive OD-SIB1 due to moving from one SSB direction to another between the UL-WUS transmission time and the OD-SIB1 monitoring window, then it can simply request OD-SIB1 again in a RACH occasion associated with the new SSB direction.Proposal 1: Support additional information related to SSBs associated with PDCCH monitoring occasions provided in RAR in response to UL-WUS transmission (Alt2) or no additional information is provided (Alt3).

[0247] Proposal 2: IfAlt2 is adopted, the additional information in RAR consists of a subset of SSBs indicated with a bitmap or a list of SSB indices.

[0248] SIB1 periodicity and offset as assistance information

[0249] In earlier discussions about UE with UL WUS configuration checking for SIB1 before sending OD-SIB1 request, it has been suggested to provide SIB1 periodicity and offset as assistance information to simplify monitoring. However, this assistance information can also simplify for the UE after sending the request and receiving RAR, or if the NES Cell switches to periodic SIB1 transmission (legacy behavior):

[0250] The fundamental SIB1 period is 160ms and within such period it is up to NW implementation to provide SIB1 in one or more candidate TypeO-PDCCH CSS occasions. In Figure 2, SIB1 is provided in candidate occasions {2, 4, 6, 8}, effectively obtaining the periodicity 40ms. If the UE knows this pattern, then it can avoid blind decoding during candidate occasions which are not used, saving UE power.

[0251] Observation 3: If the UE knows the SIB1 transmission pattern within a 160 ms period, then it can avoid blind detection in TypeO PDCCH CSS occasions which are not used.

[0252] FIGURE 14 illustrates example assistance data 1400 to indicate the SIB1 transmission pattern within a 160 ms period.

[0253] The transmission pattern in FIGURE 14 can be indicated with a periodicity (40ms) and offset. The offset can be expressed in number of TypeO-PDCCH CSS occasions which is 1 in the example above. Alternatively, the transmission pattern can be expressed as a search space mask indicating which of the occasions are used by the NES cell.

[0254] Proposal 3: Include assistance parameters in the UL WUS configuration that informs the UE of the SIB1 transmission / repetition occasions. For example:

[0255] a) SIB1 periodicity and offset, or

[0256] b) SIB1 search space mask indicating which of the occasions are used by the NES cellThe assisting parameters above can also be useful for the UE beyond the on-demand SIB1 acquisition procedure. UE could be informed of whether the transmission scheme is also applicable for later SIB1 acquisition.

[0257] Proposal 4: The assistance parameters in the WUS configuration that informs of the SIB1 transmission / repetition occasions are also valid after the on-demand SIB1 acquisition procedure.

[0258] RRC parameter list for OD-SIB1

[0259] Agreement

[0260] RANI to discuss the value range for od-sibl -duration. For example, Option 1 : Use the value-range for si-windowLength (from 5 slots to 5120 slot) as starting point.

[0261] Option 2: The duration of the time window can be a multiple of 160ms (i.e. legacy SIB1 periodicity).

[0262] Option 3: The duration of the time window can be a multiple of the on- demand SIB1 repetition periodicity (if supported) Other options are not precluded.

[0263] The specification of the purpose and allowed values of the parameter od-sibl -duration is important for the effective operation of the OD-SIB1 feature. Firstly, the purpose of the parameter needs some clarification. It is reasonable to assume that od-sibl -duration signals the time interval that the NES Cell is guaranteed that OD-SIB1 is transmitted. While it makes sense that the transmission of OD-SIB1 ceases after the expiration of that interval, it should be up to the NES Cell to decide whether to prolong it or not and whether to broadcast this choice to the cell area or not.

[0264] Proposal 5: It is clarified that od-sibl -duration corresponds to the time duration where the NES Cell is guaranteed to transmit OD-SIB1 after an OD-SIB1 request.

[0265] Option 1 determines the use of the value-range for si-windowLength as the starting point. However, both the range, i.e., up to 5120 slots and the unit, i.e., in number of slots, appear to be much longer and more flexible than what is really required. It would be better if the od-sibl -duration parameter can take a limited number of values from a list rather than have a range as extensive as the one proposed in Option 1. Further, it is sufficient to specify the number of subframes instead of the unnecessary precision of slots. Hence, Option 1 should be avoided.Observation 4: The granularity of od-sib 1 -duration in terms of slots is unnecessarily fine and the range, i.e., up to 5120 slots, is unnecessarily long.

[0266] Option 2 provides a reasonable compromise between flexibility and simplicity.

[0267] Another option could be 80ms which is the minimum duration that MIB must remain unmodified. Other options along these lines could be discussed.

[0268] Observation 5: The duration of the time window being a multiple of 160ms (Option 2) is a reasonable compromise between flexibility and simplicity.

[0269] Option 3 relates the duration of the time window with the OD-SIB1 repetition periodicity, which could be optionally specified. It is preferable that if the parameter od-sibl- duration is determined with relation to some second parameter, the latter is mandatorily specified. Hence, Option 3 should be deprioritized.

[0270] Observation 6: Relating the duration of the time window with the optional property of repetition periodicity can be error prone and it is best to be avoided.

[0271] Proposal 6: Support the duration of the time window is a multiple of 160ms (Option 2). Additionally, support the duration 80ms.

[0272] Conclusion

[0273] In the previous sections, the following observations were made:

[0274] Observation 1 If additional information related to SSBs associated with PDCCH monitoring occasions is provided in UL-WUS (Altl), it is semi-static and must account for all RACH occasions where the UE can send UL WUS. Observation 2 If additional information related to SSBs associated with PDCCH monitoring occasions is provided in RAR (Alt2), it is dynamic and can be tailored to the PRACH resource used for UL WUS.

[0275] Observation 3 If the UE knows the SIB1 transmission pattern within a 160 ms period, then it can avoid blind detection in TypeO PDCCH CSS occasions which are not used.

[0276] Observation 4 The granularity of od-sibl -duration in terms of slots is unnecessarily fine and the range, i.e., up to 5120 slots, is unnecessarily long. Observation 5 The duration of the time window being a multiple of 160ms (Option 2) is a reasonable compromise between flexibility and simplicity. Observation 6 Relating the duration of the time window with the optional property of repetition periodicity can be error prone and it is best to be avoided.

[0277] Based on the discussion in the previous sections, the following is proposed:Proposal 1 Support additional information related to SSBs associated with PDCCH monitoring occasions provided in RAR in response to UL-WUS transmission (Alt2) or no additional information is provided (Alt3).

[0278] Proposal 2 If Alt2 is adopted, the additional information in RAR consist of a subset of SSBs indicated with a bitmap or a list of SSB indices.

[0279] Proposal 3 Include assistance parameters in the UL WUS configuration that informs the UE of the SIB1 transmission / repetition occasions. For example: a) SIB1 periodicity and offset, or b) SIB1 search space mask indicating which of the occasions are used by the NES cell

[0280] Proposal 4 The assistance parameters in the WUS configuration that informs the of the SIB1 transmission / repetition occasions are also valid after the on-demand SIB1 acquisition procedure.

[0281] Proposal 5 It is clarified that od-sibl -duration corresponds to the time duration where the NES Cell is guaranteed to transmit OD-SIB1 after an OD-SIB1 request. Proposal 6 Support the duration of the time window is a multiple of 160ms (Option 2).

[0282] Additionally, support the duration 80ms.

[0283] EXAMPLE EMBODIMENTS

[0284] Group A Example Embodiments

[0285] 1. A method performed by a user equipment (UE) for On-Demand System Information (OD-SI) monitoring, the method comprising at least one of: receiving, from a first network node (Cell A), an uplink (UL) Wake-up Signal (WUS) configuration for a request of OD-SI in a second network node (NES Cell), the UL WUS configuration comprising assistance information regarding the OD-SI monitoring behavior following an OD-SI request; sending UL WUS to request OD-SI from a second network node (NES Cell), the UL WUS being sent in a RACH occasion associated with a specific Synchronization Signal Block (SSB) referred to as SSB ODSI REQ,- receiving, from the second network node, a Random Access Response (RAR) for the UL WUS, wherein the RAR may or may not include additional assistance information regarding the OD-SI monitoring behavior; and monitoring System Information (SI) Physical Downlink Control Channel (PDCCH) occasions associated with a subset of all SSBs in the second network node (NES Cell) in accordance with the assistance information in the UL WUS configuration and / or RAR, wherein the subset of SSBs is referred to as SSB ODSI RESP.

[0286] la. The method of Example Embodiment 1, wherein the SI is system information block 1 (SIB1) or some other system information block (SIBX) or a system information message including one or more different system information blocks.lb. The method of any one of Example Embodiments 1 to la, wherein the first and second network node can be the same or different cells.

[0287] 2. The method of any one of Example Embodiments 1 to lb, wherein the assistance information in the UL WUS configuration is explicit or descriptive.

[0288] 2a. The method of Example Embodiment 2, wherein the assistance information in the UL WUS configuration is explicit and the assistance information indicates a mapping from each possible SSB ODSI REQ to the corresponding SSB ODSI RESP. This is referred to as the SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping. For a given SSB ODSI REQ, SSB ODSI RESP always includes SSB ODSI REQ. That is, SI will always be provided in the PDCCH occasions associated with the SSB which is associated to the RACH occasion where the OD-SI request was sent.

[0289] 2b. The method of Example Embodiment 2 and / or 2a, wherein SSB ODSI REQ is not explicitly included in the SSB ODSI RESP included in the assistance information. Given that the SI will always be provided in the PDCCH occasions associated with the SSB which is associated to the RACH occasion where the OD-SI request was sent, this information need not be explicitly included and can be deduced.

[0290] 2c. The method of Example Emboidment 2 and / or 2a and / or 2b, wherein some SSB ODSI REQ may not be explicitly included in the assistance information, i.e., the SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping is not present for some SSB ODSI REQ. If a particular SSB ODSI REQ is not present, it may be understood as the SSB ODSI RESP being equal to the SSB ODSI REQ, i.e., if the OD-SI request was sent in that SSB ODSI REQ, the SI is only provided in that same SSB ODSI REQ.

[0291] 3. The method of any one of Example Embodiments 1 to 2c, wherein the SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping is expressed as one of the following:

[0292] • For each possible SSB ODSI REQ, the corresponding SSB ODSI RESP is provided as a bitmap where each SSB in the set is indicated with “1” at the corresponding SSB index position, and the remaining SSBs are indicated with “0”. In this case, SSB ODSI REQ need not to be included in the bitmap since it is assumed that SSB ODSI REQ is always included in the corresponding SSB ODSI RESP set.

[0293] • For each possible SSB ODSI REQ, the corresponding SSB ODSI RESP is provided as a list of SSB indices. In this case, SSB ODSI REQ need not to beincluded in the list since it is anyway assumed that SSB ODSI REQ is always included in the corresponding SSB ODSI RESP set.

[0294] • A single structure or enumeration applicable for all SSB ODSI REQ.

[0295] 4. The method of any one of Example Embodiments 1 to 3, wherein the SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping allows the following:

[0296] o Different SSB ODSI REQ can be mapped to the same or different SSB ODSI RESP. If two or more different SSB ODSI REQ are mapped to the same SSB ODSI RESP, the SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping is from one set of SSBs to another set of SSBs.

[0297] o The same SSB can be in the SSB ODSI RESP set for different SSB ODSI REQ.

[0298] o Some SSBs need not belong to SSB ODSI RESP for any possible SSB ODSI REQ.

[0299] o SSB ODSI RESP can be the empty set.

[0300] 5. The method of any one of Example Embodiments 1 to 4, wherein the SSB_ODSI_REQ-to-SSB_ODSI_RESP mapping is provided for each possible SSB ODSI REQ in a single structure rather than multiple mapping lists. The single structure includes all possible SSB ODSI REQ in a ID structure, e.g., an ordered list or vector or other enumeration; alternatively, the single structure includes all possible SSB ODSI REQ in a 2D structure, e.g., a matrix, a list of lists or vectors, or similar. For a given SSB ODSI REQ at a specific position in the structure, the corresponding SSB ODSI RESP is obtained from the adjacent elements within the structure.

[0301] 6. The method of any one of Example Embodiments 1 to 5, wherein the single structure is an enumeration of all SSBs. For the ID structure, for SSB ODSI REQ being the SSB at position k in the enumeration, SSB ODSI RESP is given by the SSBs at positions {k-1, k, k+1} in the enumeration, i.e., the first order neighbors of SSB ODSI REQ (and SSB ODSI REQ itself). Similarly, in the case of the 2D structure, for SSB ODSI REQ being the SSB at position (j, k) in the matrix, SSB ODSI RESP is given by the SSBs at positions (j-1, k-1), (j-1, k), (j-1, k+1), (j, k-1), (j, k), (j, k+1), (j+1, k-1), (j+1, k), and (j+1, k+1).

[0302] 7. The method of any one of Example Embodiments 1 to 6, wherein the explicit assistance information by a single structure in the UL WUS configuration is further extended by a parameter, e.g., num adjacent resp beams. This parameter configures the order of neighbors within the configuration structure, which makes up the set SSB ODSI RESP. For a given SSB_ODSI_REQ in the single structure, if num adjacent resp beams = 2, then thecorresponding SSB ODSI RESP is given by the neighbors of order up to 2 in the structure, etc.

[0303] 8. The method of any one of Example Embodiments 1 to 7, wherein the WUS configuration allows to configure different num adjacent resp beams for left vs. right side of the initiated beam in the configuration, in the case of a ID structure. For a 2D structure, the WUS configuration may allow to configure different num adjacent resp beams for left, right, up, down, or any subset / grouping of them (e.g., vertical vs horizontal direction).

[0304] 9. The method of any one of Example Embodiments 1 to 8, wherein the UE is indicated the value of num adjacent resp beams by the second network node (NES cell) in the RAR for UL WUS.

[0305] 10. The method of any one of Example Embodiments 1 to 9, wherein the SSB ODS1 REQ-Xo-SSB ODS1 RESP mapping provided in the UL WUS configuration is descriptive. That is, SSB beams are split into different sets depending on some property, e.g., (property name, sets of SSB beams). The property could be for example based on the geometry of the array, e.g., the SSB beams are associated with antenna ports that are adjacent to each other. It can also be associated with propagation properties of the SSB beams, e.g., the set of beams that overlap by a certain part of the coverage area. The property can be also determined by other channel characteristics, e.g., some beams could be more likely to experience a specific degree of Doppler shift or delay spread. Data collected during offline network measurement campaigns, analysis of historical data related to UEs’ channel characteristics obtained during network operation, analysis of the propagation environment based on software tools (digital twins, ray tracing) can be used to uncover potential relations between SSB beams.

[0306] 11. The method of any one of Example Embodiments 1 to 10, wherein the UE has received multiple descriptive associations for the same SSB ODSI REQ in the UL WUS configuration, the UE receives from the second network node in the RAR for UL WUS an indication of: which of the multiple descriptive associations that applies, i.e., SSB ODSI RESP is determined by the property indicated in RAR, or an explicit indication of the additional SSB beams. In this case, the updated information overwrites the information provided in the UL WUS configuration.

[0307] 12. The method of any one of Example Embodiments 1 to 11, comprising: based on an entry in the UL WUS configuration, independently selecting at least one beam for monitoring PDCCH for potential OD-SI transmissions as given by the corresponding SSB ODSI RESP set.13. The method of any one of Example Embodiments 1 to 12, comprising when the SSB ODSI REQ is associated with an SSB ODSI RESP, using this indication to monitor additional monitoring occasions.

[0308] 14. The method of any one of Example Embodiments 1 to 12, comprising when the SSB ODSI REQ is associated with several SSB ODSI RESP, selecting one of the association sets or combining the beams from the indicated association cells.

[0309] 15. The method of Example Embodiment 14, wherein combining the beams from the indicated association cells comprises combining a union of all the sets of SSB ODSI RESP or the intersection of the sets of SSB ODSI RESP or the entries in SSB ODSI RESP that appear in at least N of the associated response SSB sets.

[0310] 16. The method of any one of Example Embodiments 14 to 15, wherein the selection of a type of combining depends on at least one parameter, state, and / or condition.

[0311] Group B Example Embodiments

[0312] 17. A method performed by a user equipment (UE) for On-Demand System Information (OD-SI) monitoring, the method comprising at least one of: receiving, from a first network node associated with a first cell, an uplink (UL) Wake-up Signal (WUS) configuration for a request of OD-SI in a second cell associated with a second network node, wherein the UL WUS configuration comprises assistance information for OD-SI monitoring; sending, to the second network node, an UL WUS to request OD-SI from the second network node, wherein the UL WUS is sent in a Random Access Channel (RACH) occasion associated with a first Synchronization Signal Block (SSB); receiving, from the second network node, a Random Access Response (RAR) for the UL WUS; and based on the RAR, monitoring at least one Physical Downlink Control Channel (PDCCH) occasion associated with a subset of all SSBs in the second cell for the OD-SI.

[0313] 18. The method of Example Embodiment 17, wherein the second cell is aNES cell.

[0314] 19. The method of any one of Example Embodiments 17 to 18, wherein the OD-SI comprises at least one of: a system information block 1 (SIB1), other system information block (SIBX), and a system information message comprising one or more different system information blocks.

[0315] 20. The method of any one of Example Embodiments 17 to 19, wherein at least one of: the first network node and the second network node are a same network node, and the first cell and the second cell are a same cell.21. The method of any one of Example Embodiments 17 to 20, wherein at least one of: the first network node and the second network node are different network nodes, and the first cell and the second cell are different cells.

[0316] 22. The method of any one of Example Embodiments 17 to 21, wherein the RAR comprises additional assistance information for performing the monitoring for the OD-SI.

[0317] 23. The method of any one of Example Embodiments 17 to 22, wherein the assistance information in the UL WUS configuration is explicit or descriptive.

[0318] 24. The method of any one of Example Embodiments 17 to 23, wherein a least one of: the UL WUS to request the OD-SI from the second network node sent in the RACH occasion associated with the first SSB is a SSB ODSI REQ,- and the subset of SSBs is a SSB ODSI RES.

[0319] 25. The method of any one of Example Embodiments 23 to 24, wherein: the assistance information in the UL WUS configuration is explicit, and the assistance information indicates a mapping from each possible SSB ODSI REQ to the corresponding SSB ODSI RESP.

[0320] 26. The method of Example Embodiment 25, wherein the mapping comprises a SSB ODSI REQ-to-SSB ODSI RESP mapping.

[0321] 27. The method of any one of Example Embodiments 24 to 26, wherein, for a given SSB ODSI REQ, SSB ODSI RESP always includes SSB ODSI REQ.

[0322] 28. The method of Example Embodiment 27, wherein SI is always provided in PDCCH occasions associated with the SSB that is associated to a RACH occasion where the OD-SI request was sent.

[0323] 29. The method of any one of Example Embodiments 23 to 28, wherein SSB ODSI REQ is not explicitly included in the SSB ODSI RESP included in the assistance information.

[0324] 30. The method of any one of Example Embodiment 23 to 28, wherein some SSB ODSI REQ is not explicitly included in the assistance information (for example, the SSB ODSI REQ-to-SSB ODSI RESP mapping is not present for some SSB ODSI REQ).

[0325] 31. The method of Example Embodiment 30, comprising: when a particular SSB ODSI REQ is not present, determining that the SSB ODSI RESP is equal to the SSB ODSI REQ.

[0326] 32. The method of any one of Example Embodiments 25 to 31, wherein the mapping is expressed as at least one of: for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a bitmap where each SSB in the set is indicated with “1” atthe corresponding SSB index position, and the remaining SSBs are indicated with “0”; for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a list of SSB indices; and a single structure or enumeration applicable for all SSB ODSI REQ.

[0327] 33. The method of any one of Example Embodiments 25 to 32, wherein at least one of: the mapping allows different SSB ODSI REQ to be mapped to a same or different SSB ODSI RESP. the mapping allows a same SSB to be in the SSB ODSI RESP set for different SSB ODSI REQ,' the mapping allows some SSBs to not belong to SSB ODSI RESP for any possible SSB ODSI REQ,' and SSB ODSI RESP is an empty set.

[0328] 34. The method of any one of Example Embodiments 25 to 33, wherein the mapping is provided for each possible SSB ODSI REQ in a single structure.

[0329] 35. The method of Example Embodiment 34, wherein the single structure comprises an ordered list or vector or other enumeration

[0330] 36. The method of Example Embodiment 34, wherein the single structure includes all possible SSB ODSI REQ in a two-dimensional structure.

[0331] 37. The method of Example Embodiment 36, wherein the two-dimensional structure comprises at least one of a matrix, a list, a list of lists, and a list of vectors.

[0332] 38. The method of any one of Example Embodiments 36 to 37, wherein, for a given SSB ODSI REQ at a specific position in the structure, a corresponding SSB ODSI RESP is obtained from adjacent elements within the two-dimensional structure.

[0333] 39. The method of any one of Example Embodiments 35 to 38, wherein the single structure comprises an enumeration of all SSBs.

[0334] 40. The method of at least Example Embodiment 35, wherein, for a onedimensional structure, for a. SSB ODSI REQ being the SSB at position k in the enumeration, SSB ODSI RESP is given by the SSBs at positions {k-1, k, k+1} in the enumeration.

[0335] 41. The method of at least Example Embodiment 35, wherein, for a two-dimensional structure, for SSB ODSI REQ being the SSB at position (j, k) in the matrix, SSB ODSI RESP is given by the SSBs at positions (j-1, k-1), (j-1, k), (j-1, k+1), (j, k-1), (j, k), (j, k+1), (j+1, k-1), (j+1, k), and (j+1, k+1).

[0336] 42. The method of any one of Example Embodiments 17 to 41, wherein the assistance information in the UL WUS configuration is extended by a parameter configures an order of neighbors within the configuration structure.

[0337] 43. The method of Example Embodiment 42, wherein at least one of: the parameter comprises num adjacent resp beams, the order of neighbors within the configuration structure make up the set SSB ODSI RESP, and for a given SSB ODSI REQ in a singlestructure, if num adjacent resp beams = 2, then a corresponding SSB ODSI RESP is given by neighbors of order up to 2 in the structure.

[0338] 44. The method of any one of Example Embodiments 17 to 43, wherein the WUS configuration configures different num adjacent resp beams for a left vs. a right side of an initiated beam in the configuration in a case of a one-dimensional structure.

[0339] 45. The method of any one of Example Embodiments 17 to 43, wherein the WUS configuration configures configure different num adjacent resp beams for at least one of a left, a right, an up, a down, or any subset / grouping of beams in a two-dimensional structure.

[0340] 46. The method of any one of Example Embodiments 17 to 45, comprising receiving, by the UE, a value of num adjacent resp beams by the second network node in the RAR for UL WUS.

[0341] 47. The method of any one of Example Embodiments 17 to 46, wherein the mapping provided in the UL WUS configuration is descriptive such that SSB beams are split into different sets depending on at least one property.

[0342] 48. The method of Example Embodiment 47, wherein the property is based on at least one of: a geometry of an array, at least one propagation property of the SSB beams, at least one channel characteristic, data collected during offline network measurement campaigns, analysis of historical data related to UEs’ channel characteristics obtained during network operation, and analysis of the propagation environment based on software tools.

[0343] 49. The method of any one of Example Embodiments 17 to 48, wherein the UE receives multiple descriptive associations for a same SSB ODSI REQ in the UL WUS configuration, and wherein the UE receives from the second network node in the RAR for UL WUS an indication of at least one of: which of the multiple descriptive associations that applies, i.e., SSB ODSI RESP is determined by the property indicated in RAR, and an explicit indication of the additional SSB beams.

[0344] 50. The method of any one of Example Embodiments 17 to 49, comprising: based on an entry in the UL WUS configuration, independently selecting at least one beam for monitoring PDCCH for potential OD-SI transmissions as given by a corresponding SSB ODSI RESP set.

[0345] 51. The method of any one of Example Embodiments 17 to 50, comprising when a SSB ODSI REQ is associated with an SSB ODSI RESP, using an indication of an association to monitor additional monitoring occasions.52. The method of any one of Example Embodiments 17 to 51, comprising when a SSB ODSI REQ is associated with at least two SSB ODSI RESP, selecting one of a plurality of association sets or combining beams from an indication of associated cells.

[0346] 53. The method of Example Embodiment 52, wherein combining the beams from the indicated associated cells comprises combining a union of all the sets of SSB ODSI RESP or the intersection of the sets of SSB ODSI RESP or the entries in SSB ODSI RESP that appear in at least N of the associated response SSB sets.

[0347] 54. The method of any one of Example Embodiments 52 to 53, wherein the selection of a type of combining depends on at least one parameter, state, and / or condition.

[0348] Group C Example Embodiments

[0349] 55. A method performed by a first network node associated with a first cell, the method comprising at least one of: transmitting, to a User Equipment (UE) for the performance of On-Demand System Information (OD-SI) monitoring, an uplink (UL) Wake-up Signal (WUS) configuration for a request of OD-SI in a second cell associated with a second network node, and wherein the UL WUS configuration comprises assistance information for OD-SI monitoring of at least one Physical Downlink Control Channel (PDCCH) occasion associated with a subset of all SSBs in the second cell for the OD-SI.

[0350] 56. The method of Example Embodiment 55, wherein the second cell is aNES cell.

[0351] 57. The method of any one of Example Embodiments 55 to 56, wherein the OD-SI comprises at least one of: a system information block 1 (SIB 1 ), other system information block (SIBX), and a system information message comprising one or more different system information blocks.

[0352] 58. The method of any one of Example Embodiments 55 to 57, wherein at least one of: the first network node and the second network node are a same network node, and the first cell and the second cell are a same cell.

[0353] 59. The method of Example Embodiment 58, comprising: receiving, from the UE, an UL WUS to request OD-SI from the second network node, wherein the UL WUS is sent in a Random Access Channel (RACH) occasion associated with a first Synchronization Signal Block (SSB); transmitting, to the UE, a Random Access Response (RAR) for the UL WUS, wherein the monitoring is based on at least the RAR.

[0354] 60. The method of any one of Example Embodiments 55 to 57, wherein at least one of: the first network node and the second network node are different network nodes, and the first cell and the second cell are different cells.61. The method of Example Embodiment 59, wherein the RAR comprises additional assistance information for performing the monitoring for the OD-SI.

[0355] 62. The method of any one of Example Embodiments 55 to 61, wherein the assistance information in the UL WUS configuration is explicit or descriptive.

[0356] 63. The method of any one of Example Embodiments 55 to 62, wherein a least one of: the UL WUS to request the OD-SI from the second network node sent in the RACH occasion associated with the first SSB is a SSB ODSI REQ,' and the subset of SSBs is a SSB ODSI RES.

[0357] 64. The method of any one of Example Embodiments 62 to 63, wherein: the assistance information in the UL WUS configuration is explicit, and the assistance information indicates a mapping from each possible SSB ODSI REQ to the corresponding SSB ODSI RESP.

[0358] 65. The method of Example Embodiment 64, wherein the mapping comprises a SSB ODSI REQ-to-SSB ODSI RESP mapping.

[0359] 66. The method of any one of Example Embodiments 63 to 65, wherein, for a given SSB ODSI REQ, SSB ODSI RESP always includes SSB ODSI REQ.

[0360] 67. The method of Example Embodiment 66, wherein SI is always provided in PDCCH occasions associated with the SSB that is associated to a RACH occasion where the OD-SI request was sent.

[0361] 68. The method of any one of Example Embodiments 62 to 67, wherein SSB ODSI REQ is not explicitly included in the SSB ODSI RESP included in the assistance information.

[0362] 69. The method of any one of Example Embodiments 62 to 67, wherein some SSB ODSI REQ is not explicitly included in the assistance information (for example, the SSB ODSI REQ-to-SSB ODSI RESP mapping is not present for some SSB ODSI REQ).

[0363] 70. The method of any one of Example Embodiments 64 to 69, wherein the mapping is expressed as at least one of: for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a bitmap where each SSB in the set is indicated with “1” at the corresponding SSB index position, and the remaining SSBs are indicated with “0”; for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a list of SSB indices; and a single structure or enumeration applicable for all SSB ODSI REQ.

[0364] 71. The method of any one of Example Embodiments 64 to 70, wherein at least one of: the mapping allows different SSB ODSI REQ to be mapped to a same or different SSB ODSI RESP,' the mapping allows a same SSB to be in the SSB ODSI RESP set fordifferent SSB ODSI REQ, ' the mapping allows some SSBs to not belong to SSB ODSI RESP for any possible SSB ODSI REQ and SSB ODSI RESP is an empty set.

[0365] 72. The method of any one of Example Embodiments 64 to 71, wherein the mapping is provided for each possible SSB ODSI REQ in a single structure.

[0366] 73. The method of Example Embodiment 72, wherein the single structure comprises an ordered list or vector or other enumeration.

[0367] 74. The method of Example Embodiment 72, wherein the single structure includes all possible SSB ODSI REQ in a two-dimensional structure.

[0368] 75. The method of Example Embodiment 74, wherein the two-dimensional structure comprises at least one of a matrix, a list, a list of lists, and a list of vectors.

[0369] 76. The method of any one of Example Embodiments 74 to 75, wherein, for a given SSB ODSI REQ at a specific position in the structure, a corresponding SSB ODSI RESP is obtained from adjacent elements within the two-dimensional structure.

[0370] 77. The method of any one of Example Embodiments 73 to 76, wherein the single structure comprises an enumeration of all SSBs.

[0371] 78. The method of at least Example Embodiment 73, wherein, for a onedimensional structure, for a. SSB ODSI REQ being the SSB at position k in the enumeration, SSB ODSI RESP is given by the SSBs at positions {k-1, k, k+1} in the enumeration.

[0372] 79. The method of at least Example Embodiment 73, wherein, for a two-dimensional structure, for SSB ODSI REQ being the SSB at position (j, k) in the matrix, SSB ODSI RESP is given by the SSBs at positions (j-1, k-1), (j-1, k), (j-1, k+1), (j, k-1), (j, k), (j, k+1), (j+1, k-1), (j+1, k), and (j+1, k+1).

[0373] 80. The method of any one of Example Embodiments 55 to 79, wherein the assistance information in the UL WUS configuration is extended by a parameter configures an order of neighbors within the configuration structure.

[0374] 81. The method of Example Embodiment 80, wherein at least one of: the parameter comprises num adjacent resp beams, the order of neighbors within the configuration structure make up the set SSB ODSI RESP, and for a given SSB ODSI REQ in a single structure, if num adjacent resp beams = 2, then a corresponding SSB ODSI RESP is given by neighbors of order up to 2 in the structure.

[0375] 82. The method of any one of Example Embodiments 55 to 81, wherein the WUS configuration configures different num adjacent resp beams for a left vs. a right side of an initiated beam in the configuration in a case of a one-dimensional structure.83. The method of any one of Example Embodiments 55 to 81, wherein the WUS configuration configures configure different num adjacent resp beams for at least one of a left, a right, an up, a down, or any subset / grouping of beams in a two-dimensional structure.

[0376] 84. The method of any one of Example Embodiments 55 to 83, comprising receiving, by the UE, a value of num adjacent resp beams by the second network node in the RAR for UL WUS.

[0377] 85. The method of any one of Example Embodiments 55 to 84, wherein the mapping provided in the UL WUS configuration is descriptive such that SSB beams are split into different sets depending on at least one property.

[0378] 86. The method of Example Embodiment 85, wherein the property is based on at least one of: a geometry of an array, at least one propagation property of the SSB beams, at least one channel characteristic, data collected during offline network measurement campaigns, analysis of historical data related to UEs’ channel characteristics obtained during network operation, and analysis of the propagation environment based on software tools.

[0379] 87. The method of any one of Example Embodiments 55 to 86, wherein the UE receives multiple descriptive associations for a same SSB ODSI REQ in the UL WUS configuration, and wherein the UE receives from the second network node in the RAR for UL WUS an indication of at least one of: which of the multiple descriptive associations that applies, i.e., SSB ODSI RESP is determined by the property indicated in RAR, and an explicit indication of the additional SSB beams.

[0380] Group D Example Embodiments

[0381] 88. A method performed by a second network node associated with a second cell, the method comprising at least one of: receiving, from a user equipment (UE), an uplink (UL) wake-up signal (WUS) to request On Demand-System Information (OD-SI) from the second network node, wherein the UL WUS is sent in a Random Access Channel (RACH) occasion associated with a first Synchronization Signal Block (SSB); transmitting, to the UE, a Random Access Response (RAR) for the UL WUS for monitoring by the UE of at least one Physical Downlink Control Channel (PDCCH) occasions associated with a subset of all SSBs in the second cell for the OD-SI.

[0382] 89. The method of Example Embodiment 88, wherein the second cell is aNES cell.

[0383] 90. The method of any one of Example Embodiments 88 to 89, wherein the OD-SI comprises at least one of: a system information block 1 (SIB1), other system information block(SIBX), and a system information message comprising one or more different system information blocks.

[0384] 91. The method of any one of Example Embodiments 88 to 90, wherein at least one of: the first network node and the second network node are a same network node, and the first cell and the second cell are a same cell.

[0385] 92. The method of Example Embodiment 91, further comprising: transmitting, to the UE, an UL WUS configuration for the request of OD-SI in the second cell associated with the second network node, wherein the UL WUS configuration comprises assistance information for OD-SI monitoring.

[0386] 93. The method of Example Embodiment 92, wherein the UL WUS configuration is transmitted to the UE prior to receiving the WUS request from the UE.

[0387] 94. The method of any one of Example Embodiments 88 to 90, wherein at least one of: the first network node and the second network node are different network nodes, and the first cell and the second cell are different cells.

[0388] 95. The method of any one of Example Embodiments 88 to 94, wherein the RAR comprises additional assistance information for performing the monitoring for the OD-SI.

[0389] 96. The method of any one of Example Embodiments 88 to 95, wherein the assistance information in the UL WUS configuration is explicit or descriptive.

[0390] 97. The method of any one of Example Embodiments 88 to 96, wherein a least one of: the UL WUS to request the OD-SI from the second network node is sent by the UE in the RACH occasion associated with the first SSB is a SSB ODSI REQ,' and the subset of SSBs is a. SSB ODSI RES.

[0391] 98. The method of any one of Example Embodiments 96 to 97, wherein: the assistance information in the UL WUS configuration is explicit, and the assistance information indicates a mapping from each possible SSB ODSI REQ to the corresponding SSB ODSI RESP.

[0392] 99. The method of Example Embodiment 98, wherein the mapping comprises a SSB ODSI REQ-to-SSB ODSI RESP mapping.

[0393] 100. The method of any one of Example Embodiments 97 to 99, wherein, for a given SSB ODSI REQ, SSB ODSI RESP always includes SSB ODSI REQ.

[0394] 101. The method of Example Embodiment 100, wherein SI is always provided in PDCCH occasions associated with the SSB that is associated to a RACH occasion where the OD-SI request was sent.102. The method of any one of Example Embodiments 96 to 101, wherein SSB ODSI REQ is not explicitly included in the SSB ODSI RESP included in the assistance information.

[0395] 103. The method of any one of Example Embodiment 96 to 101, wherein some SSB ODSI REQ is not explicitly included in the assistance information (for example, the SSB ODSI REQ-to-SSB ODSI RESP mapping is not present for some SSB ODSI REQ).

[0396] 104. The method of Example Embodiment 103, comprising: when a particular SSB ODSI REQ is not present, determining that the SSB ODSI RESP is equal to the SSB ODSI REQ.

[0397] 105. The method of any one of Example Embodiments 98 to 104, wherein the mapping is expressed as at least one of: for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a bitmap where each SSB in the set is indicated with “1” at the corresponding SSB index position, and the remaining SSBs are indicated with “0”; for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a list of SSB indices; and a single structure or enumeration applicable for all SSB ODSI REQ.

[0398] 106. The method of any one of Example Embodiments 98 to 105, wherein at least one of: the mapping allows different SSB ODSI REQ to be mapped to a same or different SSB ODSI RESP,' the mapping allows a same SSB to be in the SSB ODSI RESP set for different SSB ODSI REQ,' the mapping allows some SSBs to not belong to SSB ODSI RESP for any possible SSB ODSI REQ,' and SSB ODSI RESP is an empty set.

[0399] 107. The method of any one of Example Embodiments 98 to 105, wherein the mapping is provided for each possible SSB ODSI REQ in a single structure.

[0400] 108. The method of Example Embodiment 107, wherein the single structure comprises an ordered list or vector or other enumeration.

[0401] 109. The method of Example Embodiment 107, wherein the single structure includes all possible SSB ODSI REQ in a two-dimensional structure.

[0402] 110. The method of Example Embodiment 109, wherein the two-dimensional structure comprises at least one of a matrix, a list, a list of lists, and a list of vectors.

[0403] 111. The method of any one of Example Embodiments 109 to 110, wherein, for a given SSB ODSI REQ at a specific position in the structure, a corresponding SSB ODSI RESP is obtained from adjacent elements within the two-dimensional structure.

[0404] 112. The method of any one of Example Embodiments 108 to 111, wherein the single structure comprises an enumeration of all SSBs.113. The method of at least Example Embodiment 108, wherein, for a onedimensional structure, for a SSB ODSI REQ being the SSB at position k in the enumeration, SSB ODSI RESP is given by the SSBs at positions {k-1, k, k+1} in the enumeration.

[0405] 114. The method of at least Example Embodiment 108, wherein, for a two-dimensional structure, for SSB ODSI REQ being the SSB at position (j, k) in the matrix, SSB ODSI RESP is given by the SSBs at positions (j-1, k-1), (j-1, k), (j-1, k+1), (j, k-1), (j, k), (j, k+1), (j+1, k-1), (j+1, k), and (j+1, k+1).

[0406] 115. The method of any one of Example Embodiments 88 to 114, wherein the assistance information in the UL WUS configuration is extended by a parameter configures an order of neighbors within the configuration structure.

[0407] 116. The method of Example Embodiment 115, wherein at least one of: the parameter comprises num adjacent resp beams, the order of neighbors within the configuration structure make up the set SSB ODSI RESP, and for a given SSB ODSI REQ in a single structure, if num adjacent resp beams = 2, then a corresponding SSB ODSI RESP is given by neighbors of order up to 2 in the structure.

[0408] 117. The method of any one of Example Embodiments 88 to 116, wherein the WUS configuration configures different num adjacent resp beams for a left vs. a right side of an initiated beam in the configuration in a case of a one-dimensional structure.

[0409] 118. The method of any one of Example Embodiments 88 to 116, wherein the WUS configuration configures different num adjacent resp beams for at least one of a left, a right, an up, a down, or any subset / grouping of beams in a two-dimensional structure.

[0410] 119. The method of any one of Example Embodiments 88 to 118, comprising transmitting, to the UE, a value of num adjacent resp beams by the second network node in the RAR for UL WUS.

[0411] 120. The method of any one of Example Embodiments 88 to 119, wherein the mapping provided in the UL WUS configuration is descriptive such that SSB beams are split into different sets depending on at least one property.

[0412] 121. The method of Example Embodiment 120, wherein the property is based on at least one of: a geometry of an array, at least one propagation property of the SSB beams, at least one channel characteristic, data collected during offline network measurement campaigns, analysis of historical data related to UEs’ channel characteristics obtained during network operation, and analysis of the propagation environment based on software tools.

[0413] 122. The method of any one of Example Embodiments 88 to 121, wherein the UE receives multiple descriptive associations for a same SSB ODSI REQ in the UL WUSconfiguration, and wherein the method comprises transmitting, to the UE, in the RAR for UL WUS, an indication of at least one of: which of the multiple descriptive associations that applies, i.e., SSB ODSI RESP is determined by the property indicated in RAR, and an explicit indication of the additional SSB beams.

[0414] E Example Embodiments

[0415] 123. A user equipment comprising processing circuitry configured to perform any of the steps of any of the Group A and Group B Example Embodiments.

[0416] 124. A user equipment configured to perform any of the steps of any of the Group A and Group B Example Embodiments.

[0417] 125. A wireless device comprising processing circuitry configured to perform any of the steps of any of the Group A and Group B Example Embodiments.

[0418] 126. A network node comprising processing circuitry configured to perform any of the steps of any of the Group C and Group D Example Embodiments.

[0419] 127. A network node configured to perform any of the steps of any of the Group C and Group D Example Embodiments.

[0420] 128. A computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group A, Group B, Group C, and Group D Example Embodiments.

[0421] 129. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group A, Group B, Group C, and Group D Example Embodiments.

[0422] 130. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the steps of any of the Group A, Group B, Group C, and Group D Example Embodiments.

Claims

CLAIMS1. A method (300) performed by a user equipment, UE, (812) for On-Demand System Information, OD-SI, monitoring, the method comprising:receiving (302), from a first network node (810), an uplink Wake-up Signal, UL WUS, configuration for a request of OD-SI associated with a second network node, wherein the UL WUS configuration comprises assistance information for OD-SI monitoring;sending (304), to the second network node (810), an UL WUS to request OD-SI from the second network node, wherein the UL WUS is sent in a Random Access Channel, RACH, occasion associated with a first Synchronization Signal Block, SSB;receiving (306), from the second network node, a Random Access Response, RAR, for the UL WUS; andbased on the RAR and the UL WUS configuration comprising the assistance information, monitoring (308), for the OD-SI, at least one Physical Downlink Control Channel, PDCCH, occasion associated with a subset of SSBs of the second network node.

2. The method of Claim 1, wherein the OD-SI comprises at least one of:a system information block 1, SIB1,other system information block, SIBX, anda system information message comprising one or more different system information blocks.

3. The method of any one of Claims 1 to 2, wherein:the first network node and the second network node are a same network node, or the first network node and the second network node are different network nodes.

4. The method of any one of Claims 1 to 3, wherein the RAR comprises additional assistance information for performing the monitoring for the OD-SI, and wherein the monitoring of the at least one PDCCH occasion associated with the subset of SSBs is based on the additional assistance information.

5. The method of any one of Claims 1 to 4, wherein the assistance information indicates a mapping of each of a plurality of SSBs to a corresponding one of a plurality of subsets of SSBs of the second network node for monitoring.

6. The method of Claim 5, wherein:the first SSB is denoted as a SSB ODSI REQthe subset of SSBs is denoted as a SSB ODSI RESP,' andthe mapping comprises a SSB ODSI REQ-to-SSB ODSI RESP mapping.

7. The method of Claim 6, wherein the SSB ODSI RESP always includes the SSB ODSI REQ.

8. The method of any one of Claims 6 to 7, wherein the SSB ODSI REQ is not explicitly indicated in the assistance information, and the method comprises determining that the SSB ODSI RESP is equal to the SSB ODSI REQ.

9. The method of any one of Claims 6 to 8, wherein the mapping is expressed as at least one of:for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a bitmap where each SSB in the set is indicated with “1” at the corresponding SSB index position, and the remaining SSBs are indicated with “0”;for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a list of SSB indices; anda single structure or enumeration applicable for all SSB ODSI REQ.

10. The method of any one of Claims 6 to 9, wherein the mapping is provided for each possible SSB ODSI REQ in a single structure, and wherein:the single structure comprises an ordered list, vector, or enumeration of SSBs; or the single structure includes all possible SSB ODSI REQ in a two-dimensional structure, and wherein the two-dimensional structure comprises at least one of: a matrix, a list, a list of lists, and a list of vectors.

11. The method of any one of Claims 1 to 10, wherein:the UL WUS configuration or the RAR for UL WUS comprises a value of a parameter configuring an order of neighbors within a configuration structure.

12. The method of any one of Claims 1 to 11, wherein the assistance information comprises a mapping that splits SSB beams into different sets depending on at least one property, and wherein the property is based on at least one of:a geometry of an array,at least one propagation property of the SSB beams,at least one channel characteristic,data collected during offline network measurement campaigns,analysis of historical data related to UEs’ channel characteristics obtained during network operation, andanalysis of the propagation environment based on software tools.

13. The method of any one of Claims 1 to 12, comprising receiving a plurality of descriptive associations for a particular SSB in the UL WUS configuration, and wherein the UE receives from the second network node in the RAR for UL WUS an indication of at least one of: which of the multiple descriptive associations that apply, andan explicit indication of an additional SSB beams.

14. The method of any one of Claims 1 to 13, comprising;when the first SSB is associated with a single subset of SSBs , using an indication of an association to monitor at least one additional monitoring occasion, orwhen the first SSB is associated with at least two subsets of SSBs, selecting one of a plurality of association sets or combining beams from an indication of associated cells.

15. A method (500) performed by a first network node (810) for assisting On-Demand System Information, OD-SI, monitoring by a User Equipment, UE (812), the method comprising:transmitting (502), to the UE (812) for OD-SI monitoring, an uplink Wake-up Signal, UL WUS, configuration for a request of OD-SI associated with a second network node (810), andwherein the UL WUS configuration comprises assistance information for monitoring, for the OD-SI, of at least one Physical Downlink Control Channel, PDCCH, occasion associated with a subset of SSBs of the second network node.

16. The method of Claim 15, wherein the OD-SI comprises at least one of:a system information block 1, SIB1,other system information block, SIBX, anda system information message comprising one or more different system information blocks.

17. The method of any one of Claims 15 to 16, wherein the first network node and the second network node are a same network node, and the method further comprises:receiving, from the UE, an UL WUS to request OD-SI from the second network node, wherein the UL WUS is sent in a Random Access Channel, RACH, occasion associated with a first Synchronization Signal Block, SSB;transmitting, to the UE, a Random Access Response, RAR, for the UL WUS, wherein the monitoring is based on at least the RAR; andtransmitting, to the UE, a PDCCH for the OD-SI in the at least one PDCCH occasion associated with the subset of SSBs of the second network node.

18. The method of Claim 17, wherein the RAR comprises additional assistance information for performing the monitoring for the OD-SI.

19. The method of any one of Claims 15 to 18, wherein the assistance information indicates a mapping of each of a plurality of SSBs to a corresponding one of a plurality of subsets of SSBs of the second network node for monitoring.

20. The method of Claim 19, wherein:the first SSB is denoted as a SSB ODSI REQthe subset of SSBs is denoted as a SSB ODSI RESP, ' andthe mapping comprises a SSB ODSI REQ-to-SSB ODSI RESP mapping.

21. The method of Claim 20, wherein the SSB ODSI RESP always includes the SSB ODSI REQ.

22. The method of any one of Claims 20 to 21, wherein the SSB ODSI REQ is not explicitly indicated in the assistance information, and the method comprises determining that the SSB ODSI RESP is equal to the SSB ODSI REQ.

23. The method of any one of Claims 20 to 22, wherein the mapping is expressed as at least one of:for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a bitmap where each SSB in the set is indicated with “1” at the corresponding SSB index position, and the remaining SSBs are indicated with “0”;for each possible SSB ODSI REQ, a corresponding SSB ODSI RESP is provided as a list of SSB indices; anda single structure or enumeration applicable for all SSB ODSI REQ.

24. The method of any one of Claims 20 to 23, wherein the mapping is provided for each possible SSB ODSI REQ in a single structure, and wherein:the single structure comprises an ordered list, vector, or enumeration of SSBs; or the single structure includes all possible SSB ODSI REQ in a two-dimensional structure, and the two-dimensional structure comprises at least one of: a matrix, a list, a list of lists, and a list of vectors.

25. The method of any one of Claims 15 to 24, wherein the UL WUS configuration or the RAR for the UL WUS comprises a value of a parameter configuring an order of neighbors within a configuration structure.

26. The method of any one of Claims 15 to 25, wherein the assistance information comprises a mapping that splits SSB beams into different sets depending on at least one property, and wherein the property is based on at least one of:a geometry of an array,at least one propagation property of the SSB beams,at least one channel characteristic,data collected during offline network measurement campaigns,analysis of historical data related to UEs’ channel characteristics obtained during network operation, andanalysis of the propagation environment based on software tools.

27. A user equipment, UE, (812) for On-Demand System Information, OD-SI, monitoring, the UE comprising processing circuitry (1002) configured to:receive, from a first network node (810), an uplink Wake-up Signal, UL WUS, configuration for a request of OD-SI associated with a second network node (810), wherein the UL WUS configuration comprises assistance information for OD-SI monitoring;send, to the second network node, an UL WUS to request the OD-SI from the second network node, wherein the UL WUS is sent in a Random Access Channel, RACH, occasion associated with a first Synchronization Signal Block, SSB;receive, from the second network node, a Random Access Response, RAR, for the UL WUS; andbased on the RAR and the UL WUS configuration comprising the assistance information, monitor, for the OD-SI, at least one Physical Downlink Control Channel, PDCCH, occasion associated with a subset of SSBs of the second network node.

28. The UE of Claim 27, wherein the processing circuitry is configured to perform any of the steps of any of Claims 2 to 14.

29. A first network node (810) for On-Demand System Information, OD-SI, monitoring by a User Equipment, UE (812), the first network node comprising processing circuitry (1102) configured to:transmit, to the UE for OD-SI monitoring, an uplink Wake-up Signal, UL WUS, configuration for a request of OD-SI associated with a second network node (810), and wherein the UL WUS configuration comprises assistance information for monitoring, for the OD-SI, of at least one Physical Downlink Control Channel, PDCCH, occasion associated with a subset of SSBs of the second network node.

30. The first network node of Claim 29, wherein the processing circuitry is configured to perform any of the steps of any of Claims 16 to 26.