Methods, systems, and apparatuses for on-demand UE request for network energy saving operation

Abstract

A UE may send a request to a network node performing a network energy saving operation to request that the network node transmits one or both of a Synchronization Signal Block (SSB) and System Information Block 1 (SIB1). The on-demand request may be sent to the network node via a Layer 1 (L1) message, a Layer 2 (L2) message, or a Layer 3 (L3) message. In response to the on-demand request, the network node may send one or both of the SSB and the SIB1 to the UE.

Description

METHODS. SYSTEMS, AND APPARATUSES FOR ON-DEMAND UE REQUESTFOR NETWORK ENERGY SAVING OPERATIONTECHNICAL FIELD

[0001] This application relates generally to wireless communication systems, including support for on-demand operations when a network is performing an energy saving operation.BACKGROUND

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and Institute of Electrical and Electronics Engineers (IEEE) 802. 11 standard for Wireless Local Area Networks (WLAN) (commonly known to industry groups as Wi-Fi®).

[0003] As contemplated by the 3GPP, different wireless communication systems' standards and protocols can use various radio access networks (RANs) for communicating between a base station of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE). 3GPP RANs can include, for example. Global System for Mobile communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN). Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next-Generation Radio Access Network (NG-RAN).

[0004] Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements Universal Mobile Telecommunication System (UMTS) RAT or other 3 GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE). and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR). In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.

[0005] A base station used by a RAN may correspond to that RAN. One example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E- UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB). One example of an NG-RAN base station is a next generation Node B (also sometimes referred to as a g Node B or gNB).

[0006] A RAN provides its communication services with external entities through its connection to a core network (CN). For example, E-UTRAN may utilize an Evolved Packet Core (EPC) while NG-RAN may utilize a 5G Core Network (5GC).

[0007] Frequency bands for 5G NR may be separated into two or more different frequency ranges. For example, Frequency Range 1 (FR1) may include frequency bands operating in sub-6 gigahertz (GHz) frequencies, some of which are bands that may be used by previous standards, and may potentially be extended to cover new spectrum offerings from 410 megahertz (MHz) to 7125 MHz. Frequency Range 2 (FR2) may include frequency bands from 24.25 GHz to 52.6 GHz. Note that in some systems, FR2 may also include frequency bands from 52.6 GHz to 71 GHz (or beyond). Bands in the millimeter wave (mmWave) range of FR2 may have smaller coverage but potentially higher available bandwidth than bands in FR1. Skilled persons will recognize these frequency ranges, which are provided by way of example, may change from time to time or from region to region.BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0008] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0009] FIG. 1 illustrates a signal flow diagram for an on-demand UE request in accordance with some embodiments.

[0010] FIG. 2 illustrates a method performed by a UE in accordance with some embodiments.

[0011] FIG. 3 illustrates a method performed by a network node in accordance with some embodiments.

[0012] FIG. 4 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.

[0013] FIG. 5 illustrates a system for performing signaling between a wireless device and a network device, according to embodiments disclosed herein.DETAILED DESCRIPTION

[0014] Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.

[0015] Network energy saving operations in New Radio (NR) have been introduced to address the increasing concerns over energy consumption and efficiency as networks evolve. In Rel-18, multiple technical details have been specified to allow network energy saving including the following.

[0016] Synchronization Signal Block (SSB)-less Secondary’ Cell (SCell) operation for inter-band carrier aggregation (CA) for FR1 and co-located cells. Rel-15 NR supports SSB-less SCell option for intra-band CA, Rel-18 extends the SSB-less SCell operation to inter-band CA.

[0017] Solutions for network energy saving in spatial and power domain may include the following. The spatial domain may allow all or subset of antenna elements associated to a logical antenna port to be disabled / enabled. Some embodiments may support configurability’ of Non-Zero Power Channel State Information-Reference Signal (NZP CSI-RS) resource(s) for channel measurement within one resource setting corresponding to more than one spatial adaptation patterns. Some embodiments may support one CSI report configuration that includes multiple CSI report sub-configurations where each sub-configuration corresponds to one spatial adaptation pattern.

[0018] The power domain may allow adaptation of power offset values between Physical Downlink Shared Channel (PDSCH) and CSI-RS. Some embodiments support configuration of one or more resources to be associated with one or more power offset values. Some embodiments support, for CSI report, configuration of more than one power offset values for PDSCH relative to CSI-RS. Some embodiments support one CSI report configuration comprising multiple CSI report sub-configurations where each subconfiguration corresponding to different power offset values for PDSCH relative to CSI-RS. Additionally, cell Discontinuous Transmission (DTX) / Discontinuous Reception (DRX) operation may be used for network energy saving.

[0019] In NR, there are the following channels / signals that a UE expects the network to constantly transmit which can cause high network energy consumption: SSB and System Information Block 1 (SIB1). SSB includes synchronization Primary Synchronization Signal Secondary Synchronization Signal (PSS and SSS) and MIB (Master Information Block). SIB1 carries essential information needed by the device to initiate communication with the network. Accordingly, these are ty pically broadcast by the network frequently. Due to the frequency of transmission, however, these channels / signals may consume a lot of energy.

[0020] Accordingly, to reduce network energy consumption, some embodiments may employ on-demand operations for SSB and SIB1. Such on-demand operations may allow the network to reduce the frequency of broadcasting of these signals or introduce periods where SSB and SIB1 are not broadcast. Some embodiments herein specify procedures and signaling method(s) to support on-demand SSB SCell operation for UEs in connected mode configured with CA, for both intra-Zinter-band CA. Further, some embodiments herein include procedures and signaling method(s) to support on-demand SIB1 for UEs in idle / inactive mode.

[0021] The on-demand operation may allow the UE to make a request for SSB or SIB1. Based on the UE request, the network node may decide whether or not to transmit the SSB or SIB1. Embodiments herein include details regarding using Layer 1 (LI) LI physical (PHY Layer), L2 Medium Access Control (MAC) Layer, and / or L3 RRC Layer for on-demand UE request for network energy saving operation.

[0022] FIG. 1 illustrates a signal flow diagram 118 for an on-demand UE request in accordance with some embodiments. The on-demand UE request (also referred to herein as an on-demand request) refers to a request from a UE 102 for a network node 104 in a power save state to transmit a SSB and / or SIB1. The power save state may refer to any network energy saving operation.

[0023] As shown, the network node 104 may enter a power save state 106. The power save state 106 may allow the network node 104 to conserve power. However, the power save state 106 may prevent the network node 104 from transmitting SSB and SIB1.

[0024] The UE 102 may determine 110 one or more network nodes in power save state that UE desires SSB and / or SIB1. For example, the UE 102 may desire to connect withthe network node 104 which may not be possible without the SSB and / or SIB1. The SIB1 is a message broadcast by the network node 104 that includes essential information for the UE 102 to connect to the network node 104.

[0025] Because of the power save state 106 the network node 104 may not be broadcasting the SSB and / or SIB1. To obtain the SSB and / or SIB 1, the UE may generate 108 an on-demand request. The on-demand request may request that the network node 104 transmit the SSB and / or SIB1. The UE 102 may send 114 the on-demand request via an LI message, an L2 message, or an L3 message.

[0026] The network node 104 may receive the on-demand request and identify 112 it as a request to transmit the SSB and / or SIB1. The network node 104 may decide whether to send the SSB and / or SIB1. The network node 104 may send 116 the SSB and / or SIB1. The UE 102 may receive the SSB and / or SIB 1.

[0027] To support on-demand SSB or SIB1 operation for network energy saving, various mechanisms can be used by the UE to request the SSB or SIB1 transmission (e.g., send 114 the on-demand request). For example, in some embodiments, the SSB or SIB1 request may be sent by the UE as a LI (PHY layer message). For example, the request may be sent via a PRACH transmission (e g., Message 1 transmission). In some embodiments, the UE may send the request in an uplink control information (UCI) by Physical Uplink Control Channel (PUCCH). For example, the SSB / SIB1 request may be sent via a Scheduling Request (SR). In some embodiments, the UE may send the request in a UCI by Physical Uplink Shared Channel (PUSCH). For example, the SSB / SIB1 request may be sent via a configured grant (CG) PUSCH.

[0028] In some embodiments. L2 or L3 may be used by the UE to transmit the SSB or SIB1 request to the network node. For example, in some embodiments, the request may be sent as a L2 (MAC layer) message. For example, the request may be included in a MAC-CE. In some embodiments, the request may be sent as a L3 (RRC layer) message. For example, the request may be included in an RRC (e.g.. UE Assistance Information (UAI)).

[0029] The following sections provides more details regarding the on-demand request based on whether it is sent via an LI message, an L2 message, or an L3 message.

[0030] LI On-Demand Request

[0031] In some embodiments, to support on-demand SSB or SIB1 operation for network energy saving, different mechanisms can be used for UE to request the SSB orSIB1 transmission depending on the RRC State. For example, for UE in RRC CONNECTED state (on-demand SSB request), in some embodiments, the UE may use UCI by PUCCH or UCI by PUSCH for the request. In some embodiments, for UE in RRC CONNECTED state (on-demand SSB request) the UE may use MAC-CE for the request. Further, in some embodiments, when the UE is in RRC IDLE / INACTIVE state (on-demand SIB1 request), the UE may send the request via a PRACH transmission.

[0032] To support on-demand SSB or SIB1 operation for network energy saving, when PRACH is used for UE to send the on-demand request, the following information can be configured by the network node for the corresponding PRACH transmission. In some embodiments, the network node may configure resources or other identifying parameters to be used by a UE when sending the on-demand request for SSB or SIB1. When the network node receives the on-demand request, the network node may identify the request based on the resources used or other identifying parameters.

[0033] For example, the network node may configure resources in the frequency domain for the PRACH transmission corresponding to the on-demand request. In some embodiments, the network node may configure the number of PRACH, msgl, Frequency Division Multiplexed (FDM’d) in the frequency domain for the on-demand request. In some embodiments, the network node may configure the start of PRACH frequency domain resource allocation for the on-demand request.

[0034] In some embodiments, the network node may configure resources in the time domain for the PRACH transmission corresponding to the on-demand request. For example, the network node may configure the periodicity of the PRACH transmission used for the on-demand request. As another example, the network node may configure the selected index of PRACH transmission period for the on-demand PRACH request.

[0035] In some embodiments, the network node may configure the power domain, the power control for the on-demand PRACH request. For example, the network node may configure the targeted PRACH received power, the maximum transmission power, and / or the step size for power ramping.

[0036] In some embodiments, the network node may configure how many SSBs are associated with one PRACH occasion for the on-demand PRACH request. In some embodiments, the network node may configure the index of the PRACH preamble for the on-demand PRACH request. In some embodiments, the network node may configure thePRACH response, Random Access Response (RAR), window for the on-demand PRACH request.

[0037] To support on-demand SSB or SIB1 operation for network energy saving, when PRACH is used for UE to send the on-demand request, for the configuration of PRACH transmission if the request is for on-demand SIB1 for UE in RRC IDLE / INACTIVE state the following options may be used. Typically, PRACH configuration is part of SIB1, however because of the introduction of on-demand SIB1 PRACH request, a new method to provide the UE with PRACH configuration may be introduced. In some embodiments, the PRACH configuration is delivered via a modified Master Information Block (MIB) by utilizing reserved bits in MIB.

[0038] In some embodiments, the PRACH configuration is delivered via a different carrier. For example, the UE may be redirected to a different frequency, other than the camping cell, to reach the configuration. For example, the UE may camp on a cell that is in an energy saving state, and may find another cell where network still transmits system information including the PRACH configuration that the UE may use for the on-demand request.

[0039] To support on-demand SSB or SIB1 operation for network energy saving, when PRACH is used for UE to send the on-demand request, contention free or contention based random access is considered. In some embodiments, a UE and network node may use Contention Free Random Access (CFRA) for the on-demand request. In some embodiments, UE and network node may use Contention Based Random Access (CBRA) for the on-demand request.

[0040] In terms of the number of steps for PRACH the procedure, in some embodiments, there may be a single PRACH preamble transmission. For example, the system may use CFRA for the on-demand request and the UE may send a PRACH preamble transmission. The network node may not need to identify which UE sent the on-demand request, but instead may broadcast the SSB or SIB1 regardless of the identity of the UE. In some embodiments, the UE and network node may perform a four step PRACH or a twostep PRACH.

[0041] To support on-demand SSB or SIB1 operation for NW energy saving, when UCI, e.g., Scheduling Request (SR), on PUCCH is used for UE to send the on-demand request one or more of the following options may be used. In some embodiments, the SchedulingRequestld for on-demand request may be configured for only the Master CellGroup (MCG). In some embodiments, the SchedulingRequestld for on-demand request is configured for both MCG and SCG. In some embodiments, the SchedulingRequestld for on-demand request is configured per serving cell. The network node may configure the SR and when the network node detects a UE uses the PUCCH resource it may determine that SSB or SIB1 is being requested.

[0042] To support on-demand SSB or SIB1 operation for network energy saving, when UCI, e.g., SR, on PUCCH is used for UE to send the on-demand request some embodiments may include a priority for the on-demand request in relation to other scheduling requests. In terms of the SR priority during the UCI multiplexing, if more than 1 SR indicates positive, the following options may be used. In some embodiments, the SR for on-demand request has the same priority as other non-Link Recovery Request (LRR) scheduling requests. In some embodiments, the SR for on-demand request has the same priority as LRR SR. In some embodiments, the SR for on-demand request has lower priority than non-LRR SR. In some embodiments, the SR for on-demand request has lower priority than LRR SR, but higher priority than non-LRR SR. LRR SR is the SR used for Link Recovery Request, i.e., schedulingRequestID-BFR-SCell-rl6, schedulingRequestID-BFR-r!7 or schedulingRequestID-BFR2-r!7. LRR SR has higher priority’ compared to other SR. The priority may be used by the UE to determine which SR to send in the case of multiple SRs, and may be used by the network node to determine which SR to respond to first.

[0043] To support on-demand SSB or SIB1 operation for network energy saving, when UCI. e.g., SR. on PUCCH is used for UE to send the on-demand request, when SR collides with PUSCH transmission with uplink (UL) grant the following options may be used. In some embodiments, SR for on-demand request is dropped or postponed when the SR for on-demand request collides with PUSCH transmission with UL grant. For instance, if a collision occurs the SR for the on-demand request may be postponed until a next slot. In some embodiments, the PUSCH transmission is dropped when the SR for on-demand request collides with PUSCH transmission with UL grant. In some embodiments, the SR for on-demand request is multiplexed on PUSCH when the SR for on-demand request collides with PUSCH transmission with UL grant.

[0044] In some embodiments, the on-demand request may be sent via a UCI on PUSCH (e.g., CG). To support on-demand SSB or SIB1 operation for network energy saving, when UCI on PUSCH, CG PUSCH may be used for UE to send the on-demand request.The CG is periodic. In some embodiments UE reports the UCI in some of the UL CG transmission occasions. In some embodiments, UE reports the UCI in all of the UL CG transmission occasions.

[0045] Further, to support on-demand SSB or SIB1 operation for network energy saving, when UCI on PUSCH (e.g., CG PUSCH is used for UE to send the on-demand request), the following options may be used. In some embodiments, the UE reports the UCI regardless of whether UE has UL data (e.g., transport block or Uplink Shared Channel (UL-SCH)) to transmit on the same UL CG transmission occasion. In some embodiments, the UE reports the UCI only when the UE has UL data (e.g., transport block or UL-SCH) to transmit on the same UL CG transmission occasion.

[0046] In some embodiments, to support on-demand SSB or SIB1 operation for network energy saving, when UCI on PUSCH (e.g., CG PUSCH is used for UE to send the on-demand request) the CG-UCI and unused transmission occasion(s) (UTO)-UCI may be used. The term "UTO-UCI" refers to unused transmission occasion(s) indicated by uplink control information (UCI). The UE may use the UTO-UCI to indicate which transmission occasions it will not use, thereby allowing the network to more effectively manage network resources. Note that CG-UCI was introduced in Rel-16 for NR-U, UTO- UCI was introduced in Rel-18 for XR. In some embodiments, the UE sends the on- demand SSB or SIB request UCI together with CG-UCI / UTO-UCI. In some embodiments, the UE can send the on-demand SSB or SIB request UCI without CG- UCI / UTO-UCI.

[0047] Further to support on-demand SSB or SIB1 operation for network energy saving, when UCI on PUSCH (e.g., CG PUSCH is used for UE to send the on-demand request), in terms of PUSCH resource configuration the following options may be used. For example, beta offset may be configured for the PUSCH resource for the on-demand request. In some embodiments, a separate beta offset can be configured for the on- demand UCI (e.g., Poffset ’)- Accordingly, the beta offset may be configured separately by the network node for the on-demand UCI (i.e., the UCI carrying the on-demand request). In some embodiments, the UE may reuse an existing beta offset (e.g., ^offset1or PoffSetCI). Note that the beta offset is configured by the network node to determine the number of resources for multiplexing different types of UCI in a PUSCH.

[0048] In some embodiments to support on-demand SSB or SIB1 operation for network energy saving, when UCI on PUSCH (e.g., CG PUSCH is used for UE to send the on-demand request), if the on-demand UCI is scheduled to be sent on the same slot as a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) the UE may or may not multiplex the UCI with the HARQ-ACK. In some embodiments, on-demand UCI can be jointly encoded with HARQ-ACK. The network node can configure whether the UE should jointly encode on-demand UCI with HARQ-ACK. When on-demand UCI is jointly encoded with HARQ-ACK. the UE may use beta offset configured for HARQ- ACK (i.e., PoffS<itACK)- In some embodiments, the on-demand UCI cannot be jointly encoded with HARQ-ACK.

[0049] In some embodiments to support on-demand SSB or SIB1 operation for network energy saving, when UCI on PUSCH (e.g., CG PUSCH is used for UE to send the on- demand request), in terms UCI multiplexing when on-demand UCI collides with HARQ- ACK the following options may be used. If the network does not configure the UE, or the UE is not allowed to multiplex on-demand UCI with HARQ-ACK, the collision handling may be based on priority. In some embodiments, if HARQ-ACK has the same priority as PUSCH with the on-demand UCI, the UE drops the PUSCH, and HARQ-ACK is carried by PUCCH or a different PUSCH. In some embodiments, if HARQ-ACK has different priority from PUSCH with the on-demand UCI, the UE drops the one with lower priority

[0050] L2 On-Demand Request

[0051] To support on-demand SSB or SIB1 operation for network energy saving, when MAC-CE is used for UE to send the on-demand request, the following options may be used. In some embodiments, when the UE has an uplink grant, the UE can send the on- demand request in MAC-CE carried by PUSCH based on the uplink grant.

[0052] If UE does not have an uplink grant, the UE can send a scheduling request to request uplink grant for MAC-CE. For example, the UE may send the scheduling request to request uplink grant. The network node may receive the scheduling request and configure the UE with the uplink grant. If the UE is configured with the uplink grant, the UE may send the on-demand request via a MAC-CE using the uplink grant.

[0053] In terms of priority’, the scheduling request for on-demand request may have a priority' according to one of the follow ing options. In some embodiments, the scheduling request for on-demand request has the same priority as other non-LRR scheduling requests. In some embodiments, the scheduling request for on-demand request has the same priority as LRR scheduling requests. In some embodiments, the scheduling requestfor on-demand request has lower priority than non-LRR scheduling requests. In some embodiments, the scheduling request for on-demand request has lower priority than LRR scheduling requests, but higher priority than non-LRR scheduling requests.

[0054] To support on-demand SSB or SIB1 operation for NW energy saving, when MAC-CE is used for UE to send the on-demand request, the MAC-CE can include one or multiple of the following options. In some embodiments, the MAC-CE may include a single indication that indicates the serving cell that needs to transmit SSB / SIB1, and the serving cell is the cell in which UE sends the MAC-CE. In some embodiments, the MAC-CE may include a list of serving cells (e.g., a list of serving cell IDs) indicating that the UE requests those serving cells to transmit SSB / SIB1. In some embodiments, the MAC-CE may include a list of neighbor cells (e.g., a list of Physical Cell Identify (PCIs)) indicating that the UE requests those neighbor cells to transmit SSB / SIB1. In some embodiments, the MAC-CE may include a list of SSB IDs, that UE requests network to transmit SSB with those indicated IDs. In some embodiments, the MAC-CE may include a recommended duration that the UE requests the network to transmit SSB / SIB1. The recommended duration may be in the unit of milliseconds, seconds, etc.

[0055] L3 On-Demand Request

[0056] In some embodiments, to support on-demand SSB or SIB1 operation for network energy saving, the UE can send the on-demand request by RRC via UE assistance Information (UAI).

[0057] In some embodiments, to support on-demand SSB or SIB1 operation for network energy saving, for either LI based, or L2 based, or L3 based UE on-demand request, one or multiple of the following can be considered as conditions to allow the UE to send the on-demand request. In some embodiments, one condition to allow the UE to send the on-demand request is that the UE has Radio Resource Management (RRM) measurement. The RRM measurement needed to fulfill the condition this could include serving cell and / or neighbor cell. In some embodiments, one condition to allow the UE to send the on-demand request is that the UE has time / frequency synchronization for handover or cell reselection. In some embodiments, one condition to allow the UE to send the on-demand request is that the UE has PRACH configuration. In some embodiments, one condition to allow the UE to send the on-demand request is that the UE has time / frequency tracking refinement for the serving cell.

[0058] To support on-demand SSB or SIB1 operation for network energy saving, for either LI based, or L2 based, or L3 based UE on-demand request, a prohibit timer can be introduced to avoid frequent on-demand request. In some embodiments, after the UE sends the on-demand request, the UE cannot send another on-demand request until the prohibit timer expires.

[0059] FIG. 2 illustrates a method 200 performed by a UE in accordance with some embodiments. The illustrated method 200 includes generating 202 an on-demand request for a network node in a power save state to transmit one or both of a SSB and SIB1. The method 200 further comprises sending 204 the on-demand request to the network node via a LI message, a L2 message, or a L3 message. The method 200 further comprises receiving 206 one or both of the SSB and the SIB1 from the network node in response to the on-demand request.

[0060] In some embodiments, the on-demand request is sent via the L I message, and wherein the LI message comprises a PRACH transmission or an UCI on PUCCH.

[0061] In some embodiments, the method 200 further comprises receiving, from the network node, a PRACH configuration for the PRACH transmission comprising frequency domain, time domain, or an index of a PRACH preamble.

[0062] In some embodiments, the PRACH configuration is received via a different carrier than a carrier corresponding to the SSB and the SIB1.

[0063] In some embodiments, the PRACH transmission comprises a single PRACH preamble transmission.

[0064] In some embodiments, when the UCI on the PUCCH is used to send the on- demand request, the UCI is a SR and a SchedulingRequestld for the on-demand request is configured for only a MCG.

[0065] In some embodiments, when the UCI on the PUCCH is used to send the on- demand request, the UCI is a SR, and wherein the SR for the on-demand request has a same priority’ as other non-LRR scheduling requests.

[0066] In some embodiments, when the UCI on the PUCCH is used to send the on- demand request, the UCI is a SR, and wherein when SR collides with a PUSCH transmission with uplink grant the SR for the on-demand request is dropped or postponed.

[0067] In some embodiments, the on-demand request is sent via the L2 message, and wherein the L2 message comprises a MAC-CE. wherein when the UE has an uplink grant, the method 200 further comprises sending the on-demand request in the MAC-CE carried by PUSCH based on the uplink grant, and wherein when the UE does not have the uplink grant, the method 200 further comprises sending a scheduling request to request an uplink grant for the MAC-CE.

[0068] In some embodiments, the on-demand request comprises a list of serving cells or a list of neighbor cells that the UE requests transmit the SSB or the SIB1.

[0069] In some embodiments, the method 200 further comprises determining that one or more conditions are satisfied prior to sending the on-demand request, wherein the conditions include that the UE has an RRM measurement, time and frequency synchronization for handover or cell reselection, a PRACH configuration, time and frequency tracking refinement for serving cell, or a combination thereof.

[0070] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 200. This apparatus may be. for example, an apparatus of a UE (such as a wireless device 502 that is a UE, as described herein).

[0071] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 200. This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory' 06 of a wireless device 502 that is a UE, as described herein).

[0072] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 200. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 502 that is a UE, as described herein).

[0073] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 200. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 502 that is a UE, as described herein).

[0074] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 200.

[0075] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method 200. The processor may be a processor of a UE (such as a processor(s) 504 of a wireless device 502 that is a UE, as described herein). These instructions may be, for example, located in the processor and / or on a memory of the UE (such as a memory 506 of a wireless device 502 that is a UE. as described herein).

[0076] FIG. 3 illustrates a method 300 performed by a UE in accordance with some embodiments. The illustrated method 300 includes entering 302 a power save state. The method 300 further comprises receiving 304, from a UE. an on-demand request for a network node in a power save state to transmit one or both of a SSB and SIB1. The on- demand request is received via a LI message, a L2 message, or a L3 message. The method 300 further comprises sending 306 one or both of the SSB and the SIB1 to the UE in response to the on-demand request.

[0077] In some embodiments, the on-demand request is received via the LI message, and wherein the LI message comprises a PRACH transmission or an UCI on PUCCH.

[0078] In some embodiments, the method 300 further comprises sending, the UE, a PRACH configuration for the PRACH transmission comprising frequency domain, time domain, or an index of a PRACH preamble.

[0079] In some embodiments, the PRACH configuration is sent via a different carrier than a carrier corresponding to the SSB and the SIB1.

[0080] In some embodiments, the PRACH transmission comprises a single PRACH preamble transmission.

[0081] In some embodiments, when the UCI on the PUCCH is used to receive the on- demand request, the UCI is a SR and a SchedulingRequestld for the on-demand request is configured for only a MCG.

[0082] In some embodiments, when the UCI on the PUCCH is used to receive the on- demand request, the UCI is a SR, and wherein the SR for the on-demand request has a same priority as other non-LRR scheduling requests.

[0083] In some embodiments, when the UCI on the PUCCH is used to receive the on- demand request, the UCI is a SR, and wherein when SR collides with a PUSCHtransmission with uplink grant the SR for the on-demand request is dropped or postponed.

[0084] In some embodiments, the on-demand request is received via the L2 message, and wherein the L2 message comprises a MAC -CE, wherein when the UE has an uplink grant, the method 300 further comprises receiving the on-demand request in the MAC- CE carried by PUSCH based on the uplink grant, and wherein when the UE does not have the uplink grant, the method 300 further comprises receiving a scheduling request to request an uplink grant for the MAC-CE.

[0085] In some embodiments, the on-demand request comprises a list of serving cells or a list of neighbor cells that the UE requests transmit the SSB or the SIB1.

[0086] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 300. This apparatus may be, for example, an apparatus of a base station (such as a network device 518 that is a base station, as described herein).

[0087] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 300. This non-transitory computer-readable media may be. for example, a memory of a base station (such as a memory 522 of a network device 518 that is a base station, as described herein).

[0088] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 300. This apparatus may be, for example, an apparatus of a base station (such as a network device 518 that is a base station, as described herein).

[0089] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 300. This apparatus may be. for example, an apparatus of a base station (such as a network device 518 that is a base station, as described herein).

[0090] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 300.

[0091] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of the method 300. The processor may be a processor of a base station (such as a processor(s) 520 of a network device 518 that is a base station, as described herein). These instructions may be, for example, located in the processor and / or on a memory’ of the base station (such as a memory 522 of a network device 518 that is a base station, as described herein).

[0092] FIG. 4 illustrates an example architecture of a wireless communication system 400, according to embodiments disclosed herein. The following description is provided for an example wireless communication system 400 that operates in conjunction with the LTE system standards and / or 5G or NR system standards as provided by 3GPP technical specifications.

[0093] As shown by FIG. 4, the wireless communication system 400 includes UE 402 and UE 404 (although any number of UEs may be used). In this example, the UE 402 and the UE 404 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device configured for wireless communication.

[0094] The UE 402 and UE 404 may be configured to communicatively couple with a RAN 406. In embodiments, the RAN 406 may be NG-RAN, E-UTRAN, etc. The UE 402 and UE 404 utilize connections (or channels) (shown as connection 408 and connection 410, respectively) with the RAN 406, each of which comprises a physical communications interface. The RAN 406 can include one or more base stations (such as base station 412 and base station 414) that enable the connection 408 and connection 410.

[0095] In this example, the connection 408 and connection 410 are air interfaces to enable such communicative coupling, and may be consistent with RAT(s) used by the RAN 406, such as, for example, an LTE and / or NR.

[0096] In some embodiments, the UE 402 and UE 404 may also directly exchange communication data via a sidelink interface 416. The UE 404 is shown to be configured to access an access point (shown as AP 418) via connection 420. By way of example, the connection 420 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 418 may comprise a Wi-Fi® router. Inthis example, the AP 418 may be connected to another network (for example, the Internet) without going through a CN 424.

[0097] In embodiments, the UE 402 and UE 404 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 412 and / or the base station 414 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0098] In some embodiments, all or parts of the base station 412 or base station 414 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 412 or base station 414 may be configured to communicate with one another via interface 422. In embodiments where the wireless communication system 400 is an LTE system (e.g., when the CN 424 is an EPC), the interface 422 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and / or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 400 is an NR system (e.g., when CN 424 is a 5GC), the interface 422 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 412 (e.g., a gNB) connecting to 5GC and an eNB, and / or between two eNBs connecting to 5GC (e.g.. CN 424).

[0099] The RAN 406 is shown to be communicatively coupled to the CN 424. The CN 424 may comprise one or more network elements 426, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UE 402 and UE 404) who are connected to the CN 424 via the RAN 406. The components of the CN 424 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0100] In embodiments, the CN 424 may be an EPC, and the RAN 406 may be connected with the CN 424 via an S I interface 428. In embodiments, the S I interface 428 may be split into two parts, an SI user plane (Sl-U) interface, which carries traffic data between the base station 412 or base station 414 and a serving gateway (S-GW), and the SI -MME interface, which is a signaling interface between the base station 412 or base station 414 and mobility management entities (MMEs).

[0101] In embodiments, the CN 424 may be a 5GC, and the RAN 406 may be connected with the CN 424 via an NG interface 428. In embodiments, the NG interface 428 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 412 or base station 414 and a user plane function (UPF). and the SI control plane (NG-C) interface, which is a signaling interface between the base station 412 or base station 414 and access and mobility management functions (AMFs).

[0102] Generally, an application server 430 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 424 (e.g., packet switched data services). The application server 430 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 402 and UE 404 via the CN 424. The application server 430 may communicate with the CN 424 through an IP communications interface 432.

[0103] FIG. 5 illustrates a system 500 for performing signaling 534 between a wireless device 502 and a network device 518, according to embodiments disclosed herein. The system 500 may be a portion of a wireless communications system as herein described. The wireless device 502 may be, for example, a UE of a wireless communication system. The network device 518 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.

[0104] The wireless device 502 may include one or more processor(s) 504. The processor(s) 504 may execute instructions such that various operations of the wireless device 502 are performed, as described herein. The processor(s) 504 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0105] The wireless device 502 may include a memory 506. The memory 506 may be a non-transitory computer-readable storage medium that stores instructions 508 (which may include, for example, the instructions being executed by the processor(s) 504). The instructions 508 may also be referred to as program code or a computer program. The memory 506 may also store data used by, and results computed by, the processor(s) 504.

[0106] The wireless device 502 may include one or more transceiver(s) 510 that may include radio frequency (RF) transmitter circuitry and / or receiver circuitry that use the antenna(s) 512 of the wireless device 502 to facilitate signaling (e.g., the signaling 534) to and / or from the wireless device 502 with other devices (e.g., the network device 518) according to corresponding RATs.

[0107] The wireless device 502 may include one or more antenna(s) 512 (e.g., one, two, four, or more). For embodiments with multiple antenna(s) 512, the wireless device 502 may leverage the spatial diversity of such multiple antenna(s) 512 to send and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect). MIMO transmissions by the wireless device 502 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 502 that multiplexes the data streams across the antenna(s) 512 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream). Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi user MIMO (MU- MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).

[0108] In certain embodiments having multiple antennas, the wireless device 502 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s) 512 are relatively adjusted such that the (joint) transmission of the antenna(s) 512 can be directed (this is sometimes referred to as beam steering).

[0109] The wireless device 502 may include one or more interface(s) 514. The interface(s) 514 may be used to provide input to or output from the wireless device 502. For example, a wireless device 502 that is a UE may include interface(s) 514 such asmicrophones, speakers, a touchscreen, buttons, and the like in order to allow for input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 510 / antenna(s) 512 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

[0110] The wireless device 502 may include an on-demand request module 516. The on-demand request module 516 may be implemented via hardware, software, or combinations thereof. For example, the on-demand request module 516 may be implemented as a processor, circuit, and / or instructions 508 stored in the memory 506 and executed by the processor(s) 504. In some examples, the on-demand request module 516 may be integrated within the processor(s) 504 and / or the transceiver(s) 510. For example, the on-demand request module 516 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 504 or the transceiver(s) 510.[OHl] The on-demand request module 516 may be used for various aspects of the present disclosure, for example, aspects of FIGS. 1-4. The on-demand request module 516 is configured to generate an on-demand request for a S SB or a SIB1 to be sent by the transceiver(s) 510.

[0112] The network device 518 may include one or more processor(s) 520. The processor(s) 520 may execute instructions such that various operations of the network device 518 are performed, as described herein. The processor(s) 520 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0113] The network device 518 may include a memory 522. The memory 522 may be a non-transitory computer-readable storage medium that stores instructions 524 (which may include, for example, the instructions being executed by the processor(s) 520). The instructions 524 may also be referred to as program code or a computer program. The memory 522 may also store data used by, and results computed by, the processor(s) 520.

[0114] The network device 518 may include one or more transceiver(s) 526 that may include RF transmitter circuitry and / or receiver circuitry' that use the antenna(s) 528 ofthe network device 518 to facilitate signaling (e.g., the signaling 534) to and / or from the network device 518 with other devices (e.g., the wireless device 502) according to corresponding RATs.

[0115] The network device 518 may include one or more antenna(s) 528 (e.g., one, two, four, or more). In embodiments having multiple antenna(s) 528, the network device 518 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.

[0116] The network device 518 may include one or more interface(s) 530. The interface(s) 530 may be used to provide input to or output from the network device 518. For example, a network device 518 that is a base station may include interface(s) 530 made up of transmitters, receivers, and other circuitry' (e.g., other than the transceiver(s) 526 / antenna(s) 528 already described) that enables the base station to communicate with other equipment in a core network, and / or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.

[0117] The network device 518 may include an on-demand response module 532. The on-demand response module 532 may be implemented via hardware, software, or combinations thereof. For example, the on-demand response module 532 may be implemented as a processor, circuit, and / or instructions 524 stored in the memory 522 and executed by the processor(s) 520. In some examples, the on-demand response module 532 may be integrated within the processor(s) 520 and / or the transceiver(s) 526. For example, the on-demand response module 532 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 520 or the transceiver(s) 526.

[0118] The on-demand response module 532 may be used for various aspects of the present disclosure, for example, aspects of FIGS. 1-4. The on-demand response module 532 is configured to receive and identify an on-demand request while the network device 518 is performing a network energy saving operation and cause the network device 518 to send an SSB and / or SIB1 in response.

[0119] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations,techniques, processes, and / or methods as set forth herein. For example, a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.

[0120] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0121] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.

[0122] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.

[0123] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so asto minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[0124] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

CLAIMS1. A method for a User Equipment (UE), the method comprising: generating an on-demand request for a network node in a power save state to transmit one or both of a Synchronization Signal Block (SSB) and System Information Block 1 (SIB1); sending the on-demand request to the network node via a Layer 1 (LI) message, a Layer 2 (L2) message, or a Layer 3 (L3) message; and receiving one or both of the SSB and the SIB1 from the network node in response to the on-demand request.

2. The method of claim 1, wherein the on-demand request is sent via the LI message, and wherein the LI message comprises a Physical Random Access Channel (PRACH) transmission or an uplink control information (UCI) on Physical Uplink Control Channel (PUCCH).

3. The method of claim 2, further comprising receiving, from the network node, a PRACH configuration for the PRACH transmission comprising frequency domain, time domain, or an index of a PRACH preamble.

4. The method of claim 3, wherein the PRACH configuration is received via a different carrier than a carrier corresponding to the SSB and the SIB1.

5. The method of claim 2, wherein the PRACH transmission comprises a single PRACH preamble transmission.

6. The method of claim 2, wherein when the UCI on the PUCCH is used to send the on- demand request, the UCI is a scheduling request (SR) and a SchedulingRequestld for the on-demand request is configured for only a Master Cell Group (MCG).

7. The method of claim 2, wherein when the UCI on the PUCCH is used to send the on- demand request, the UCI is a scheduling request (SR), and wherein the SR for the on- demand request has a same priority as other non-Link Recovery Request (LRR) scheduling requests.

8. The method of claim 2, wherein when the UCI on the PUCCH is used to send the on- demand request, the UCI is a scheduling request (SR), and wherein when SR collideswith a PUSCH transmission with uplink grant, the SR for the on-demand request is dropped or postponed.

9. The method of claim 1, wherein the on-demand request is sent via the L2 message, and wherein the L2 message comprises a Medium Access Control (MAC) control element (CE), wherein when the UE has an uplink grant, the method further comprises sending the on-demand request in the MAC-CE carried by Physical Uplink Shared Channel (PUSCH) based on the uplink grant, and wherein when the UE does not have the uplink grant, the method further comprises sending a scheduling request to request an uplink grant for the MAC-CE.

10. The method of claim 1, wherein the on-demand request comprises a list of serving cells or a list of neighbor cells that the UE requests the network node to transmit the SSB or the SIB1.

11. The method of claim 1, further comprising determining that one or more conditions are satisfied prior to sending the on-demand request, wherein the conditions include that the UE has a Radio Resource Management (RRM) measurement, time and frequency synchronization for handover or cell reselection, a Physical Random Access Channel (PRACH) configuration, time and frequency tracking refinement for serving cell, or a combination thereof.

12. A method for a network node, the method comprising: entering a power save state; receiving, from a User Equipment (UE), an on-demand request for the network node in the power save state to transmit one or both of a Synchronization Signal Block (SSB) and System Information Block 1 (SIB1). wherein the on-demand request is received via a Layer 1 (LI) message, a Layer 2 (L2) message, or a Layer 3 (L3) message; and sending one or both of the SSB and the SIB1 to the UE in response to the on- demand request.

13. The method of claim 12, wherein the on-demand request is received via the LI message, and wherein the LI message comprises a Physical Random Access Channel(PRACH) transmission or an uplink control information (UCI) on Physical Uplink Control Channel (PUCCH).

14. The method of claim 13, further comprising sending, the UE, a PRACH configuration for the PRACH transmission comprising frequency domain, time domain, or an index of a PRACH preamble.

15. The method of claim 14, wherein the PRACH configuration is sent via a different carrier than a carrier corresponding to the SSB and the SIB1.

16. The method of claim 13, wherein the PRACH transmission comprises a single PRACH preamble transmission.

17. The method of claim 13, wherein when the UCI on the PUCCH is used to receive the on-demand request, the UCI is a scheduling request (SR) and a SchedulingRequestld for the on-demand request is configured for only a Master Cell Group (MCG).

18. The method of claim 13, wherein when the UCI on the PUCCH is used to receive the on-demand request, the UCI is a scheduling request (SR), and wherein the SR for the on- demand request has a same priority as other non-Link Recovery Request (LRR) scheduling requests.

19. The method of claim 12, wherein the on-demand request is received via the L2 message, and wherein the L2 message comprises a Medium Access Control (MAC) control element (CE), wherein when the UE has an uplink grant, the method further comprises receiving the on-demand request in the MAC-CE carried by Physical Uplink Shared Channel (PUSCH) based on the uplink grant, and wherein when the UE does not have the uplink grant, the method further comprises receiving a scheduling request to request an uplink grant for the MAC-CE.

20. A user equipment (UE) apparatus comprising: a processor; and a memory storing instructions that, when executed by the processor, configure the UE apparatus to:generate an on-demand request for a network node in a power save state to transmit one or both of a Synchronization Signal Block (SSB) and System Information Block 1 (SIB 1); send the on-demand request to the network node via a Layer 1 (LI) message, a Layer 2 (L2) message, or a Layer 3 (L3) message; and receive one or both of the SSB and the SIB1 from the network node in response to the on-demand request.

21. An apparatus comprising means to perform the method of any one of claim 1 to claim 19.

22. A computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform the method of any one of claim 1 to claim 19.

23. An apparatus comprising logic, modules, or circuitry to perform the method of any one of claim 1 to claim 19.

24. A baseband processor for a user equipment (UE) that is configured to cause the UE to perform one or more elements of any one of claim 1 to claim 11 .

25. A baseband processor for a network node that is configured to cause the network node to perform one or more elements of any one of claim 12 to claim 19.

Images