Signaling for on-demand synchronization signal block

Abstract

According to some embodiments, a method performed by a wireless device comprises transmitting to a network node an on-demand synchronization signal block (SSB) request and receiving on-demand SSB transmissions in one or more cells based on the on-demand SSB request. The method may further comprise transmitting capability information to the network node and or receiving, from the network node, an on-demand SSB request configuration. There is also provided a method in a network node, a wireless device and a network node.

Description

[0001] SIGNALING FOR ON-DEMAND SYNCHRONIZATION SIGNAL BLOCK

[0002] TECHNICAL FIELD

[0003] Embodiments of the present disclosure are directed to wireless communications and, more particularly, to signaling for user equipment (UE) request for on-demand synchronization signal block (SSB).

[0004] BACKGROUND

[0005] In a Third Generation Partnership Project (3GPP) Release 15 wireless network, the New Radio (NR) synchronization signal block (SSB) consists of 4 orthogonal frequency division multiplexing (OFDM) symbols where symbols 1 and 3 carry primary synchronization signal (PSS) and secondary synchronization signal (SSS), respectively, and symbols 2-4 carry physical broadcast channel (PBCH) containing the master information block (MIB) payload.

[0006] FIGURE 1 illustrates the SSB structure. The horizontal axis represents symbols in the time domain and the vertical axis represents subcarriers in the frequency domain.

[0007] In legacy NR scenarios, SSBs are typically configured statically, with, e.g. 20 ms period, with constant power and spatial configuration for initial access cells and serve as de- facto coverage indicators. If a UE detects an SSB indicating a cell at a certain location, with a certain signal strength that allows finding and connecting to the network, the UE may usually make a robust assumption that the same cell will be available in a predictable manner in the future, with a sufficient signal strength, or at least the network has activated another cell providing coverage at the same location.

[0008] In ongoing NR evolution, on-demand SSBs may be provided temporarily to UEs whose functionality or performance may be improved if additional signals for loop conversion, synchronization, measurements, or other signal processing steps are available. In some scenarios, a cell may be transmitting baseline SSBs at a lower rate, e.g. 160 ms or 20 ms, or no SSBs may be transmitted as a baseline. The network may then activate additional SSBs or SSB bursts, e.g. with period 20 ms or 5 ms, respectively, in association with certain procedures, or based on a UE requesting them. On-demands SSBs may also be one-shot transmissions or limited-duration SSB bursts, without a recurrent structure. They may be transmitted at the same or at a different power level and spatial configuration than the baseline SSB.

[0009] Some scenarios where on-demand SSBs are expected to be useful include: SCell quality measurements upon SCell configuration; synchronization upon SCell activation; timing / frequency tracking for an active serving cell; Radio Resource Management (RRM) measurements on serving or neighbor cells; reference signal receive power (RSRP)Zradio link management (RLM)Zbeam failure detection (BFD)Zcandidate beam detection (CBD) measurements on serving cell; preparation for paging occasion (PO) monitoring and paging reception; Preparation for uplink access using physical random access channel (PRACH). etc.

[0010] The 3GPP work item description (WID) for New Radio (NR) Rel-19 “Enhancements of network energy savings for NR” has an objective to 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. Another objective is to specify triggering method(s) (select from UE uplink wake-up-signal using an existing signalZchannel, cell onZoff indication via backhaul, SCell activationZdeactivation signaling).

[0011] On-demand SSB transmission may be used by a UE for at least SCell timeZfrequency synchronization, L1ZL3 measurements and SCell activation, and is supported for FR1 and FR2 in non-shared spectrum.

[0012] The work item objective is related to the energy savings technique B-l-1 in 3GPP TR 38.864 V18.1.0, Study on network energy savings for NR. The study objective includes enabling of inter-band SSB-less SCell operation that may include mechanism for UEZgNB to trigger normal SSB transmission andZor reference signals, if needed, on a Scell for fast access, where the on-demand uplink triggering signal can be received either at inter-band SSB-less cell or another carrierZcell. Random access channel (RACH) transmission opportunity may be supported in SSB-less Scell. “

[0013] There currently exist certain challenges. For example, according to the WID objective, triggering of on-demand SSB operation may be based on an uplink wake-up signal using existing channel Zsignal. However, it is a remaining challenge regarding how to configure and signal such on-demand SSB operation.

[0014] SUMMARY

[0015] As described above, certain challenges currently exist with on-demand synchronization signal blocks (SSBs). Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments include configuration, signaling, rules, and triggers for UE to send to the network a request for on- demand synchronization signal (e.g., SSB in 5GNR) transmissions.

[0016] According to embodiments, there is provided a method performed by a wireless device for receiving on-demand synchronization signal transmissions in one or more cells. The method comprises receiving, from a network node, an on-demand synchronization signal request configuration regarding one or more cells. The method further comprises transmitting to the network node an on-demand synchronization signal request. The method further comprises, after transmitting to the network node the on-demand synchronization signal request, receiving on-demand synchronization signal transmissions in one or more cells.

[0017] The method may further comprise transmitting to the network node capability information of the wireless device regarding one or more capabilities related to on-demand synchronization signal operation. The one or more capabilities may comprise a capability to request on-demand synchronization signal transmission.

[0018] The on-demand synchronization signal request configuration may comprise one or more rules for when the wireless device is to or is not to request on-demand synchronization signal transmission.

[0019] For example, the on-demand synchronization signal request configuration may indicate one or more scenarios, channel conditions and / or event criteria when the wireless device is allowed to or is not allowed to request on-demand synchronization signal transmission.

[0020] In addition, or alternatively, the on-demand synchronization signal request configuration may comprise a prohibit timer parameter which indicates a time duration from the transmitting the on-demand synchronization signal request during which the wireless device is not allowed to transmit another on-demand synchronization signal request.

[0021] The on-demand synchronization signal request may be a request for on-demand synchronization signal transmissions in one or more cells.

[0022] For example, the on-demand synchronization signal request may comprise one or more identifiers indicating the one or more cells in which the wireless device requests on-demand synchronization signal transmissions.

[0023] Further, the on-demand synchronization signal request may comprise timing information. For example, the on-demand synchronization signal request may comprise information indicating at least one of: a start and or stop time for requested on-demand synchronization signal transmission; duration of requested on-demand synchronization signal transmission; and frequency of requested on-demand synchronization signal transmissions.

[0024] The on-demand synchronization signal request may be a request for on-demand synchronization signal transmission in connection with a respective connection state and or function and or service.

[0025] The method may further comprising receiving, from the network node, one or more on- demand synchronization signal configurations.

[0026] In this case, the on-demand synchronization signal request may be a request for on- demand synchronization signal transmission according to one or more of the received one or more on-demand synchronization signal configurations.

[0027] In some embodiments, the method may further comprise receiving an on-demand synchronization signal activation indication from the network node, wherein the on-demand synchronization signal activation indication indicates an upcoming on-demand synchronization signal transmission, wherein the received on-demand synchronization signal transmissions comprise the upcoming on-demand synchronization signal transmission.

[0028] The method may further comprise sending a measurement report comprising measurements on the received on-demand synchronization signal transmissions in the one or more cells.

[0029] The on-demand synchronization signal request may be transmitted over a Medium Access Control - Control Element, MAC-CE, Physical Uplink Control Channel, PUCCH, or Radio Resource Control, RRC, signaling.

[0030] The on-demand synchronization signal may comprise an on-demand Synchronization Signal Block, SSB.

[0031] There is further provided a wireless device comprising processing circuitry. The processing circuitry is operable to receive, from a network node, an on-demand synchronization signal request configuration regarding one or more cells. The processing circuitry is further operable to transmit to the network node an on-demand synchronization signal request. The processing circuitry is further operable to, after transmitting to the network node the on-demand synchronization signal request, receive on-demand synchronization signal transmissions in one or more cells.

[0032] There is further provided a method performed by a network node. The method comprises transmitting to a wireless device an on-demand synchronization signal request configuration regarding one or more cells. The method further comprises receiving from the wireless device an on-demand synchronization signal request. The method further comprises, after receiving from the wireless device the on-demand synchronization signal request, causing on-demand synchronization signal transmissions to be transmitted in one or more cells.

[0033] There is further provided a network node comprising processing circuitry. The processing circuitry is operable to transmit to a wireless device an on-demand synchronization signal request configuration regarding one or more cells. The processing circuitry is further operable to receive from the wireless device an on-demand synchronization signal request. The processing circuitry is further operable to, after receiving from the wireless device the on-demand synchronization signal request, cause on-demand synchronization signal transmissions to be transmitted in one or more cells.

[0034] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments facilitate the network to receive input from the UE whether extra reference signal transmissions, e.g., on-demand SSB transmissions are desired. This enables the network to turn off, or configure with a lower periodicity, synchronization signal transmissions, which, in turn, enables network energy savings.

[0035] BRIEF DESCRIPTION OF THE DRAWINGS

[0036] 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:

[0037] FIGURE 1 illustrates the synchronization signal block (SSB) structure;

[0038] FIGURE 2 is a flowchart illustrating an example procedure for sending on-demand SSB based on on-demand SSB request;

[0039] FIGURE 3 illustrates a UE sending “on-demand SSB request” to active PCell / SCell based on which the network may transmit on-demand SSB in one or more configured SCells;

[0040] FIGURE 4 illustrates the network transmitting on-demand SSB in configured SCell after receiving an “on-demand SSB request” in active PCell / Scell;

[0041] FIGURE 5 is a timing diagram illustrating a UE performing on-demand SSB measurements for a time (during a “listening window”) after sending the “on-demand SSB request”;

[0042] FIGURE 6 is a block diagram illustrating an example wireless network;

[0043] FIGURE 7 illustrates an example user equipment, according to certain embodiments;

[0044] FIGURE 8 illustrates an example virtualization environment, according to certain embodiments;

[0045] FIGURE 9 is a flow chart showing a method in a wireless device according to embodiments; and

[0046] Figure 10 is a flow chart showing a method in a network node according to embodiments.

[0047] DETAILED DESCRIPTION

[0048] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

[0049] As described above, certain challenges currently exist with on-demand synchronization signal blocks (SSBs). Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments include configuration, signaling, rules, and triggers for user equipment (UE) to send to the network a request for on-demand synchronization signal (e.g., SSB in fifth generation (5G) New Radio (NR)) transmissions.

[0050] Particular embodiments include on-demand synchronization signal transmission request. For example, a method in a UE for requesting on-demand synchronization signal comprises: reporting to the network a UE capability for “on-demand synchronization signal request” and receiving “on-demand synchronization signal request” configuration from the network related to one or more cells. The method further comprises transmitting to the network an “on-demand synchronization signal request” and receiving from the network on-demand synchronization signal transmissions in one or more cells based on / triggered by transmitted “on-demand synchronization signal request”.

[0051] In particular embodiments, the synchronization signal comprises a 5G NR SSB signal or a 6G synchronization signal.

[0052] In particular embodiments, the “one or more cells” refers to one or more 5GNR SCells or to one or more 6G cells (note that in 6G cells may be defined differently and be more generic, e.g., as a configured collection of signals and channels).

[0053] Particular embodiments include an implicit request of on-demand synchronization signal (e.g. transmission of a scheduling request on certain cells may be interpreted as an on- demand request for additional synchronization signals)

[0054] In particular embodiments, a UE sends measurement report for on-demand synchronization signal transmission. For example, the UE reports to the network measurements on received on-demand synchronization signal transmission in one or more cells.

[0055] In particular embodiments, the on-demand synchronization signal request triggers on- demand synchronization signal transmission. For example, a UE receives “on-demand synchronization signal transmission” after signaling an “on-demand synchronization signal request” (network transmits the synchronization signal after receiving request from UE, i.e., it is not optional).

[0056] In particular embodiments, the UE is ready to measure on-demand synchronization signal after sending request. For example, after sending an “on-demand synchronization signal request”, the UE measures and reports on received on-demand synchronization signal transmissions after a starting criterion and until a stopping criterion. In particular embodiments, the starting criterion is a time after the “on-demand synchronization signal request”. In particular embodiments, the stopping criterion may be a predetermined time (e.g., slots, subframes, frames, seconds, etc.) or a number of synchronization signal transmissions or measurement occasions / measurement gaps. In particular embodiments, the starting and / or stopping criterion may be based on a timer starting and / or stopping. The starting and / or stopping criterion may be preconfigured (e.g., via Radio Resource Control (RRC)) by the network. The starting and / or stopping criterion may be indicated by the UE (part of the “on- demand synchronization signal request”).

[0057] Particular embodiments include on-demand synchronization signal request including timing information. The on-demand request may be accompanied with desire / assistance for start / stop time with a reference time (e.g. system frame number (SFN)), or including timing (e.g., symbol / slots / frames... ) in relation to a certain activity such as discontinuous reception on time (DRX-ON), measurement gap, etc.

[0058] Particular embodiments include on-demand synchronization signal request over medium access control (MAC) control element (CE)). In some embodiments, “on-demand synchronization signal request” is sent from the UE to the network via uplink MAC CE signaling.

[0059] Particular embodiments include on-demand synchronization signal request over physical uplink control channel (PUCCH)) In some embodiments, “on-demand synchronization signal request” is sent from the UE to the network via PUCCH.

[0060] Particular embodiments include on-demand synchronization signal request over RRC. In some embodiments, the "on-demand synchronization signal” request is, e.g., more static (requested over longer period) and sent from the UE to the network via RRC signaling during connected mode or upon connection setup procedure.

[0061] Particular embodiments include on-demand synchronization signal request for various states / functions / services) In some embodiments, the "on-demand synchronization signal” request is requested for various connection states (e.g., Idle and / or Connected), and / or functions (e.g., for paging reception), and / or for specific services (e.g., services with specific quality of service (QoS) requirements, or specific service types such as voice / positioning / etc.).

[0062] In particular embodiments, the on-demand synchronization signal request contains a cell identifier. For example, in some embodiments the “on-demand synchronization signal request” contains one or more identifiers that informs the network about the one or more cells for which the UE requests “on-demand synchronization signal transmission”. In particular embodiments, no cell identifier in the request means the on-demand synchronization signal request is sent in cell where on-demand synchronization signal is requested. In some embodiments, the “on-demand synchronization signal request“ does not include cell identifier(s) and wherein “on-demand synchronization signal transmission” is requested in cell where “on-demand synchronization signal request” was sent.

[0063] In particular embodiments, no cell identifier in the request means on-demand synchronization signal request is sent in configured cells. For example, the “on-demand synchronization signal request“ does not include cell identifier(s) and wherein “on-demand synchronization signal transmission” is requested for all configured cells.

[0064] In particular embodiments, no cell identifier in the request means on-demand synchronization signal request is sent in deactivated cells. For example, the “on-demand synchronization signal request” does not include cell identifier(s) and wherein “on-demand synchronization signal transmission” is requested for all deactivated cells.

[0065] In particular embodiments, the on-demand synchronization signal request includes on- demand synchronization signal configuration identifier. For example, the UE is configured with one or more “on-demand synchronization signal configurations” and wherein the “on- demand synchronization signal request“ includes an “on-demand synchronization signal configuration” identifier.

[0066] Some embodiments include implicit on-demand synchronization signal request. For example, the UE implicitly requests on-demand synchronization signal transmissions by reporting a “reporting quantity” that is below / above a certain threshold. The reporting quantity may be an uplink buffer status report that is above a certain threshold; an RSRP value that is below a certain threshold; a signal to interference plus noise ratio (SINR) value that is below a certain threshold; and / or a channel quality indicator (CQI) value, which is below a certain threshold.

[0067] Some embodiments include network rules for when to ask / not to ask. For example, the “on-demand synchronization signal request” configuration includes one or more scenario indications, channel condition indications, or event criteria when the UE shall request an on- demand synchronization signal, or when the UE shall not request an on-demand synchronization signal.

[0068] Some embodiments include a prohibit timer. For example, the “on-demand synchronization signal request” configuration includes a prohibit timer parameter.

[0069] Particular embodiments are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0070] The term on-demand SSB is used herein for simplicity. However, the ideas are equally applicable to any other type of reference signals such as any newly defined reference signals beyond 5G used for time / frequency synchronization, RRM measurements, etc.

[0071] FIGURE 2 is a flowchart illustrating an example procedure for sending on-demand SSB based on on-demand SSB request.

[0072] In Step 1, a UE indicates support for on-demand SSB via UE capability signaling. In one embodiment, the UE indicating support for on-demand SSB implies support for “on- demand SSB request” (i.e., “on-demand SSB request” is anon-optional feature for on-demand SSB”). In an alternate embodiment, UE reports via additional UE capability support for “on- demand SSB request” (i.e., “on-demand SSB request” is an optional feature for on-demand SSB”). In one embodiment, the network advertises one or more on-demand SSB configurations for on-demand SSB request on broadcast channel and already from Idle mode, upon connection setup, the UE may report on-demand SSB request before the capability exchange.

[0073] In Step 2, the network configures the UE with on-demand SSB and, possibly, if it is an optional feature, “on-demand SSB request”.

[0074] In Step 3, the UE sends “on-demand SSB request” to the network. Additional details / methods related to the “on-demand SSB request” are provided below.

[0075] In (optional) Step 4, the NW sends “on-demand SSB activation” to the UE, which informs the UE about an upcoming on-demand SSB transmission.

[0076] In Step 5, the network sends on-demand SSB.

[0077] In Step 6, the UE performs measurements on on-demand SSB and reports the measurements to the network.

[0078] The following terminology is used herein. The “On-demand SSB request” comprises an indication sent from a UE to the network for requesting / triggering on-demand SSB transmission from the network for various scenarios, such as in one or more SCells. Additional details on “on-demand SSB request” signaling / triggering are provided below. The “On- demand SSB activation” comprises an indication sent from the network to a UE to inform the UE about an upcoming on-demand SSB transmission.

[0079] One example of a UE requesting on-demand SSB transmission is shown in FIGURE 3 and FIGURE 4. Here, the UE is configured with three serving cells with one PCell / SCell being activated and two SCells being configured but not activated (i. e. , deactivated). In this example, the UE detects that channel associated with active PCell / SCell is, e.g., associated with a poor link budget and / or is not expected to meet future traffic demands (e.g., determined based on uplink buffer status). Therefore, as shown in FIGURE 3, the UE sends “on-demand SSB request” to the network, requesting on-demand SSB transmissions in configured / deactivated SCells. After receiving the “on-demand SSB request”, the network performs on-demand SSB transmissions in configured / deactivated SCells, as shown in FIGURE 4, which enables the UE to perform on-demand SSB measurements on the configured / deactivated SCells. Based on the on-demand SSB transmissions, the network may choose to activate on one or more of the configured / deactivated SCells.

[0080] FIGURE 3 illustrates a UE sending “on-demand SSB request” to active PCell / SCell based on which the network may transmit on-demand SSB in one or more configured SCells (that may or may not be activated and that may or may not be collocated with active PCell / SCell). In this example, configured SCells are deactivated and non-collocated with active PCell / SCell.

[0081] FIGURE 4 illustrates the network transmitting on-demand SSB in configured SCell after receiving an “on-demand SSB request” in active PCell / SCell.

[0082] The above example is equally applicable to non-carrier-aggregation scenarios. For example, the UE may be connected to a serving cell but based on excessive channel fluctuations ask the serving cell for on-demand SSBs provision on the serving cell itself and / or one or more neighbor cells. When it comes to neighbor cells, the serving cell may then ask the neighbors via backhaul to provide SSBs. The level of channel fluctuations above which the UE may ask for on-demand SSB may be internally defined in the UE or in one embodiment be configurable by the network. The UE may further ask for specific carriers and / or cells on which on-demand SSB is desired. The UE may have historical information related to historical coverage issues in a certain area (e.g., within a certain cell or within a certain beam of the cell) and potential candidates that may be suitable for handover.

[0083] The UE may have been configured with various criteria and permitted to ask for on- demand SSBs upon criteria fulfillment. Example of such criteria may be based on RRM type of measurement events, e.g. when an inter-frequency cell becomes better than a certain threshold (whereupon the UE may then ask for on-demand SSB on cells of that carrier), or e.g. when the serving cell quality drops below a certain threshold, etc. Other examples maybe positioning-based such that the UE may ask for on-demand SSB if the UE’s speed is above certain threshold, or in case the UE has moved more than a certain distance since its last position. Further examples of scenarios and triggers are defined below. Combinations of the exemplified criteria / scenarios are not precluded.

[0084] In some embodiments, after receiving an “on-demand SSB request”, the network may decide to transmit on-demand SSB or not. In other words, decision to activate / deactivate may be based on a UE request but it may also be based on other considerations from the network side.

[0085] In some embodiments, the “on-demand SSB request” triggers an on-demand SSB transmission (i.e., “on-demand SSB request” determines when on-demand SSB is transmitted).

[0086] In some embodiments, the network, after receiving an “on-demand SSB request” sends an “on-demand SSB activation” to the UE, which informs the UE about an upcoming on- demand SSB transmission on the present cell or other cells, e.g.,, the time-domain properties of the on-demand SSB and in which other cells (e.g., S Cells) the on-demand SSBs will be transmitted. The UE is expected / configured to perform measurements / timing or frequency tracking / synchronization / automatic gain control (AGC) retuning on the upcoming on-demand SSB according to a configurations.

[0087] In some embodiments, the network after receiving an “on-demand SSB request” does not need to send an “on-demand SSB activation” to the UE prior to transmitting on-demand SSB. Instead, the UE is expected to listen for on-demand SSB transmissions on one or multiple cells (e.g., SCells) for a time duration / time window ("listening window”) after the “on-demand SSB request” was sent (as shown in FIGURE 4).

[0088] In one example, the UE is expected to listen for on-demand SSB transmissions on all deactivated SCells for the purpose of SCell activations.

[0089] In another example, the UE is expected to listen for on-demand SSB transmissions on all active SCells for the purpose of data transmission.

[0090] In another example, the UE is expected to listen for on-demand SSB transmissions on a specific active SCell for the purpose of time / frequency tracking.

[0091] In another example, the UE is expected to listen for on-demand SSB transmissions on cells of a specific carrier for the purpose of handover or for carrying out a specific service such as a positioning-related service.

[0092] In another example, the UE is expected to listen for on-demand SSB transmissions on a specific deactivated SCell for the purpose of time / frequency tracking.

[0093] Some benefits of these particular embodiments include, e.g.: reduced downlink control signaling (network does not need to send “on-demand SSB activation” to the UE after receiving an “on-demand SSB request”); reduced delay (UE is ready to listen to on-demand SSB transmission directly / shortly after sending “on-demand SSB request”, no need for additional downlink control signaling prior to transmitting on-demand SSB); and reduced downlink transmissions (network does not need to transmit on-demand SSB after the time window and can go back to sleep if SCell is not to be activated after the on-demand SSB transmission).

[0094] In some embodiments, it may still be up to the network whether or not on-demand SSB is transmitted within “listening window” or not. If no SSB measurements were received by the UE within the “listening window”, the UE may send an “on-demand SSB request” at a later time instance. In some embodiments, the later time instance is defined as a delay with slots, subframes, frame, or in seconds after the end point of the ‘listening window’.

[0095] FIGURE 5 is a timing diagram illustrating a UE performing on-demand SSB measurements for a time (during a “listening window”) after sending the “on-demand SSB request”. The horizontal axis represents the time domain.

[0096] In one embodiment, there is a delay (which may be zero) between the “on-demand SSB request” and the “listening window”. The delay and / or length of time window may be measured in one or more of slots, subframes, frame, or it may be measured in seconds.

[0097] In some embodiments, the “listening window” is one or more upcoming (e.g., next X instances) measurement gaps used for inter-frequency / radio access technology (RAT) measurements. X may be configured by the network or predefined in the specifications.

[0098] In some embodiments, the delay and / or length of the time window is according to a predefined rule. In another embodiment, the delay and / or length of the time window is pre- configured by the network (e.g., based on UE capability signaling and network preparation and scheduling delay). In another embodiment, the delay and / or length of the time window is signaled from the UE and included in the “on-demand SSB request”.

[0099] In some embodiments, the delay and time window is determined by UE starting one or more of a first and second timer after / when sending the “on-demand SSB request”. The UE performs on-demand SSB measurement when the timer is running. If the UE successfully measures on-demand SSB measurement and reports the measurement result before the timer expires, the UE stops the timer and the UE may back to legacy measurement cycle (which may involve not performing SSB measurements) or deprioritize on-demand SSB measurements. If the UE cannot measure on-demand SSB measurement and report the measurement result until the timer expires, the UE switches back legacy measurement cycle or deprioritize the on- demand SSB measurement.

[0100] In some embodiments, the UE may have a desire for specific window timings of the on-demand reference signals. For example, the UE may want to have the SSBs provided such that they coincide or are adjacent with DRX-ON time of the UE, in conjunction with configured measurement gaps, etc. As such, the UE may provide request / preference for start / stop time of the window. The time may be expressed in relation to an absolute reference time such as SFN, or in relation (e.g., offset in symbols / search space occasions / slots / ms, etc.) to an occasion such as DRX measurement gap or alike. In some embodiments, the network may acknowledge the request such that the UE knows whether the network has accepted the request.

[0101] In one embodiment, the “on-demand SSB request” is sent over uplink MAC CE. In some embodiments, an on-demand SSB request may contain start / stop time, duration, frequency of requested SSB transmissions, etc. These attributes may be mapped to bits available / reserved in a new or existing MAC CE dynamically or semi-statically. For the latter bits in the MAC CE may point at a table where each entry is a combination of start / stop time, duration, frequency of requested SSB transmissions, etc.

[0102] In some embodiments, the “on-demand SSB” is sent over PUCCH. In some embodiments, an on-demand SSB request may contain start / stop time, duration, frequency of requested SSB transmissions, etc. These attributes may be mapped to bits available / reserved in a new or existing PUCCH format dynamically or semi-statically. For the latter, bits in a PUCCH message may point at a table where each entry is a combination of start / stop time, duration, frequency of requested SSB transmissions, etc.

[0103] In some embodiments, the “on-demand SSB” request is more static (semi-static) and requested over longer period throughout the existing or all upcoming connections until further changed (not requested longer) by the UE. Alternatively, the request is valid while the UE is involved in a specific measurement operation, such as during a positioning measurement, or during an evaluation of an intra / inter-frequency / RAT measurement event configuration. As such, the request is transmitted to the network via RRC signaling during connected mode or, e.g., via RRC signaling used upon connection setup procedure, or e.g. measurement report in which the UE may ask for on-demand SSB on specific measurement object, or e.g. via UE assistance signaling, etc. In some embodiments, the request may be tied to the radio capabilities of the UE, such as UE equipped with single Rx chain may need more (denser in time) reference signals compared to a UE with more Rx chains. In one embodiment, the “on-demand SSB” request is specified for various states / functions / services. For example, SSBs or extra SSBs are requested for specific RRC states (e.g., Idle and / or connected), and / or functions (e.g., for paging monitoring / reception), and / or for specific services (e.g., services with specific QoS requirements, or specific service types such as voice / positioning / etc.).

[0104] In some embodiments, the UE sends “on-demand SSB request” for a deactivated SCell (i.e., a configured SCell that is not activated) to a network node on another PCell / PSCell / SCell that is already activated.

[0105] In some embodiments, the “on-demand SSB request” contains one or more SCell identifier(s) that informs the network about the SCells for which the UE requests on-demand SSB transmissions.

[0106] In some embodiments, if the “on-demand SSB request” does not contain one or more SCell identifier(s), the “on-demand SSB request” is for the SCell in which the “on-demand SSB request” was transmitted. This may be useful, e.g., if an SCell is already activated and configured with long (non-on-demand) SSB periodicity, and UE requests on-demand SSB burst for, e.g., network and / or UE refining its transmit and / or receive beam(s).

[0107] In some embodiments, if the “on-demand SSB request” does not contain one or more SCell identifier(s), the “on-demand SSB request” is for all configured SCells. In another embodiment, if the “on-demand SSB request” does not contain one or more SCell identifier(s), the “on-demand SSB request” is for all deactivated SCells (i.e., UE does not request on-demand SSB transmissions in activated SCells, where other SSB transmissions may be already present).

[0108] In the following, “on-demand SSB configuration” refers to a set of parameters that are configured for an on-demand SSB transmission. The network may have configured one or more “on-demand SSB configurations” for an SCell.

[0109] In some embodiments, if multiple “on-demand SSB configurations” have been configured for one or more SCells, the UE may request or assist (either implicitly or explicitly) the gNB to activate one or more of the preconfigured “on-demand SSB configurations “by e.g. explicitly or implicitly signaling an “on-demand SSB configuration” identifier to the network.

[0110] In some embodiments, a UE may request on-demand SSB transmission according to one or multiple of the provided preconfigured on-demand SSB configuration(s). This may be done by signaling the indices / identifiers of the requested configuration. Alternatively, the UE may signal a list of indices / identifiers for multiple on-demand SSB configurations. In the latter case, the list may be ordered according to the most preferred configuration to the least preferred configuration. The request from the UE to the gNB may be signaled in a MAC-CE or over RRC or some other message. The request may be time-critical.

[0111] In some embodiments, the UE may signal a request to associate an on-demand SSB configuration with a procedure or an operation or a usage, e.g. in preparation (ahead ol) SCell activation, in preparation for cDRX onDuration, in conjunction with RRM measurements, in conjunction with Idle mode paging reception, etc. The UE may signal such requests, e.g., if it is in a poor coverage area and a larger number of SSBs can facilitate a sync or measurement operation. As a complementary step, the UE may correspondingly signal / request not to receive such OnDemand SSBs any longer, e.g., when the link conditions have improved. Such request may be non-time critical.

[0112] In some embodiments, the IE UEAssistancelnformation is used for UE to communicate preference about the configuration, e.g. SCS. This may be, for example, given in RRCreconflgurationComplete, or Resume.

[0113] In some embodiments, when the network received the UE’s request, such as UE assistant information, the network shall follow the UE request accordingly.

[0114] In some embodiments, when the network received the UE’s request, such as UE assistant information, the network may reject the UE’s request. Optionally, the network may reconfigure a new on-demand SSB configuration based on the network’s preference. In some embodiments, the UE does not explicitly ask for an on-demand SSB pattern but provides assistance / capability such that it implicitly leads to that the network activates a certain on-demand SSB pattern. For example, the UE may indicate that it is a fast-moving UE, or a UE with few (e.g. only 1) Tx / Rx chain leading to that the network provides extra SSBs for this UE compared to other UEs with more capable transceivers or UEs moving at lower speeds. Similarly, if a UE indicates that it is in an RRM relaxed mode (e.g., in good coverage, and / or stationary), the network then may provide fewer SSBs to conserve energy.

[0115] Such adaptation may also be based on service or device type, meaning that there will be a differentiation from the network side with respect to SSB provision depending on whether it is e.g. a reduced capability (RedCap) device or an enhanced mobile broadband (eMBB) device, or whether an ultra-reliable low latency communication (URLLC) type of service is running in the UE.

[0116] In some embodiments, the network advertises the set of options (possible reference signal types and associated patterns, including density, period, instances within a burst, etc.) that the UE may ask for on demand. The network may provide these options either on a broadcast channel or have configured the UE via dedicated signaling. The UE may then point to one or more of these options upon on-demand request.

[0117] In some embodiments, the transmission of an “on-demand synchronization signal request” may be an implicit transmission.

[0118] In some embodiments, the UE is configured with a threshold value, and then every time the UE send a buffer status report containing a number of bits larger than the threshold the network considers this a request for activating / transmitting additional SSB transmissions.

[0119] In some embodiments, the UE is configured with a threshold value, and then every time the UE reports, e.g., an RSRP value, an SINR value or a CQI value smaller than the threshold the network considers this a request for activating / transmitting additional SSB transmissions.

[0120] There are other similar implicit ways to request additional SSB transmissions that the UE may use, e.g. transmitting a scheduling request in one cell triggers on-demand SSB while transmitting the scheduling request in another cell does not, etc.

[0121] In some embodiments, the on-demand SSB request configuration may include rules provided by the network for when the UE is allowed or not allowed to request the on-demand SSB. The configuration may include one or more scenario indications, channel condition indications, or event criteria when the UE shall request, or is allowed to request, an on-demand SSB, or when the UE shall not request an on-demand SSB.

[0122] In one embodiment, the configuration may allow / permit the UE to transmit a request if a certain condition is fulfilled. It may be left up to the UE to decide whether or not to actually send the request. Examples of such conditions may include

[0123] • A serving cell’s (e.g., SCell) SINR or channel quality (e.g., RSRP, RSRQ or alike) is below a threshold

[0124] • SCell is not QCL with the PCell

[0125] • Based on the level of sparsity of the configured SSBs on a cell. For example, if sparser than every N ms, then on-demand SSBs are requested.

[0126] • Based on the level of misalignment of the network provided SSBs compared to DRX operation. For example, if the network provided SSBs are misaligned with the UEs DRX to the level that the UE may need to wake up twice or keep the receiver on for longer time (once for SSB and once for DRX activity) than compared to if the SSBs would have been provided in conj unction / adjacent to the DRX-ON periods.

[0127] • UE buffer status is above a threshold

[0128] • UE’s cDRX period is above a threshold,

[0129] In some embodiments, the configuration may order the UE to transmit a request if a certain condition is fulfilled. The criteria examples may be similar to one or more of those in the previous paragraph, only it is mandatory for the UE to send the request.

[0130] In some embodiments, the configuration may prohibit the UE from transmitting a request if a certain condition is fulfilled. Examples of such conditions may include:

[0131] • SCell SINR or channel quality is above a threshold

[0132] • SCell is QCL with the PCell

[0133] • UE buffer status is below a threshold,

[0134] In some embodiments, the on-demand SSB request configuration may include a prohibit timer parameter. The UE is then not allowed to perform another on-demand SSB request before the time duration has expired from the most recent request.

[0135] FIGURE 6 illustrates an example wireless network, according to certain embodiments. The wireless network may comprise and / or interface with any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and / or ZigBee standards.

[0136] Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0137] Network node 160 and WD 110 comprise various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, 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.

[0138] As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or equipment in the wireless network to enable and / or provide wireless access to the wireless device and / or to perform other functions (e.g., administration) in the wireless network.

[0139] 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)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Y et further examples of network nodes include 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), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and / or MDTs.

[0140] As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and / or operable to enable and / or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

[0141] In FIGURE 6, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 illustrated in the example wireless network of FIGURE 6 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components.

[0142] It is to be understood that a network node comprises any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

[0143] Similarly, network node 160 may be composed of multiple physically separate components (e.g., aNodeB component and aRNC component, or aBTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node.

[0144] In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, 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 160.

[0145] Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 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.

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

[0147] For example, processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC).

[0148] In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 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 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units

[0149] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160 but are enjoyed by network node 160 as a whole, and / or by end users and the wireless network generally.

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

[0151] Interface 190 is used in the wired or wireless communication of signaling and / or data between network node 160, network 106, and / or WDs 110. As illustrated, interface 190 comprises port(s) / terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162.

[0152] Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and / or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0153] In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 may be considered a part of interface 190. In still other embodiments, interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

[0154] Antenna 162 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 192 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit / receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit / receive radio signals in any direction, a sector antenna may be used to transmit / receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit / receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.

[0155] Antenna 162, interface 190, and / or processing circuitry 170 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signals may be received from a wireless device, another network node and / or any other network equipment. Similarly, antenna 162, interface 190, and / or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and / or signals may be transmitted to a wireless device, another network node and / or any other network equipment.

[0156] Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and / or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and / or network node 160.

[0157] For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further example, power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

[0158] Alternative embodiments of network node 160 may include additional components beyond those shown in FIGURE 6 that may be responsible 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, network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

[0159] As used herein, wireless device (WD) refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information through air.

[0160] In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.

[0161] Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.

[0162] As yet another specific example, in an Internet of Things (loT) scenario, a WD 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 WD and / or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3 GPP context be referred to as an MTC device. As one example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).

[0163] In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0164] As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137. WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 110.

[0165] Antenna 111 may include one or more antennas or antenna arrays, configured to send and / or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from WD 110 and be connectable to WD 110 through an interface or port. Antenna 111, interface 114, and / or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and / or signals may be received from a network node and / or another WD. In some embodiments, radio front end circuitry and / or antenna 111 may be considered an interface.

[0166] As illustrated, interface 114 comprises radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116. Radio front end circuitry 112 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 may be coupled to or a part of antenna 111. In some embodiments, WD 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered a part of interface 114.

[0167] Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and / or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0168] Processing circuitry 120 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 WD 110 components, such as device readable medium 130, WD 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

[0169] As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and / or different combinations of components. In certain embodiments processing circuitry 120 of WD 110 may comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips.

[0170] In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 122 may be a part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.

[0171] In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.

[0172] In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of WD 110, but are enjoyed by WD 110, and / or by end users and the wireless network generally.

[0173] Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 110, 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.

[0174] Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and / or other instructions capable of being executed by processing circuitry 120. Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non- transitory device readable and / or computer executable memory devices that store information, data, and / or instructions that may be used by processing circuitry 120. In some embodiments, processing circuitry 120 and device readable medium 130 may be integrated.

[0175] User interface equipment 132 may provide components that allow for a human user to interact with WD 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to WD 110. The type of interaction may vary depending on the type ofuser interface equipment 132 installed in WD 110. For example, if WD 110 is a smart phone, the interaction may be via a touch screen; if WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).

[0176] User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into WD 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from WD 110, and to allow processing circuitry 120 to output information from WD 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, WD 110 may communicate with end users and / or the wireless network and allow them to benefit from the functionality described herein.

[0177] Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and / or scenario.

[0178] Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 110 which need power from power source 136 to carry out any functionality described or indicated herein. Power circuitry 137 may in certain embodiments comprise power management circuitry.

[0179] Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of WD 110 to which power is supplied.

[0180] Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIGURE 6. For simplicity, the wireless network of FIGURE 6 only depicts network 106, network nodes 160 and 160b, and WDs 110, 110b, and 110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 160 and wireless device (WD) 110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and / or use of the services provided by, or via, the wireless network.

[0181] FIGURE 7 illustrates an example user equipment, according to certain embodiments. As used herein, a user equipment or 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). UE 200 may be any UE identified by the 3rdGeneration Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. UE 200, as illustrated in FIGURE 7, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rdGeneration Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and / or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although FIGURE 7 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

[0182] In FIGURE 7, UE 200 includes processing circuitry 201 that is operatively coupled to input / output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 213, and / or any other component, or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may use all the components shown in FIGURE 7, or only a subset of the components. 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.

[0183] In FIGURE 7, processing circuitry 201 may be configured to process computer instructions and data. Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, 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 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0184] In the depicted embodiment, input / output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 200 may be configured to use an output device via input / output interface 205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 200. The output device may be 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.

[0185] UE 200 may be configured to use an input device via input / output interface 205 to allow a user to capture information into UE 200. The input device may 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, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0186] In FIGURE 7, RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 211 may be configured to provide a communication interface to network 243a. Network 243a may encompass wired and / or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243a may comprise a Wi-Fi network. Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM, or the like. Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

[0187] RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I / O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.

[0188] Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.

[0189] Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, 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 microDIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM / RUIM) module, other memory, or any combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or 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 in storage medium 221, which may comprise a device readable medium.

[0190] In FIGURE 7, processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231. Network 243a and network 243b may be the same network or networks or different network or networks. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 233 and / or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[0191] In the illustrated embodiment, the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b may encompass wired and / or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243b may be a cellular network, a Wi-Fi network, and / or a near-field network. Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.

[0192] The features, benefits and / or functions described herein may be implemented in one of the components of UE 200 or partitioned across multiple components of UE 200. Further, the features, benefits, and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Further, processing circuitry 201 may be configured to communicate with any of such components over bus 202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware. FIGURE 8 is a schematic block diagram illustrating a virtualization environment 300 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 a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) 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 (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

[0193] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

[0194] The functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and / or functions disclosed herein.

[0195] Virtualization environment 300, comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and / or instructions executable by processing circuitry 360. Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and / or benefits described in relation with some embodiments described herein.

[0196] Virtual machines 340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.

[0197] During operation, processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.

[0198] As shown in FIGURE 8, hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.

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

[0200] In the context of NFV, virtual machine 340 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 virtual machines 340, and that part of hardware 330 that executes that virtual machine, be it hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).

[0201] Still in the context ofNFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 340 on top of hardware networking infrastructure 330 and corresponds to application 320 in Figure 18.

[0202] In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225. Radio units 3200 may communicate directly with hardware nodes 330 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.

[0203] In some embodiments, some signaling can be effected with the use of control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.

[0204] Figure 9 is a flow chart showing a method in a wireless device according to embodiments. The method may comprise at 900 transmitting to a network node capability information of the wireless device regarding one or more capabilities related to on-demand synchronization signal operation. The one or more capabilities may comprise a capability to request on-demand synchronization signal transmission. Further, the method comprises at 910 receiving, from the network node, an on-demand synchronization signal request configuration regarding one or more cells. The method comprises at 920 transmitting to the network node an on-demand synchronization signal request. The method further comprises at 940, after transmitting the on-demand synchronization signal request at 920, receiving on-demand synchronization signal transmissions in one or more cells.

[0205] The on-demand synchronization signal request configuration may comprise one or more rules for when the wireless device is to or is not to request on-demand synchronization signal transmission.

[0206] For example, the on-demand synchronization signal request configuration may indicate one or more scenarios, channel conditions and / or event criteria when the wireless device is allowed to or is not allowed to request on-demand synchronization signal transmission.

[0207] In addition, or alternatively, the on-demand synchronization signal request configuration may comprise a prohibit timer parameter which indicates a time duration from the transmitting the on-demand synchronization signal request during which the wireless device is not allowed to transmit another on-demand synchronization signal request.

[0208] The on-demand synchronization signal request may be a request for on-demand synchronization signal transmission in the one or more cells. For example, the on-demand synchronization signal request may comprise one or more identifiers indicating the one or more cells.

[0209] Further, the on-demand synchronization signal request may comprise timing information. For example, the on-demand synchronization signal request may comprise information indicating at least one of: a start and or stop time for requested on-demand synchronization signal transmission; duration of requested on-demand synchronization signal transmission; and frequency of requested on-demand synchronization signal transmissions.

[0210] The on-demand synchronization signal request may be a request for on-demand synchronization signal transmission in connection with a respective connection state and or function and or service.

[0211] The method may further comprise at 915 receiving, from the network node, one or more on-demand synchronization signal configurations. In this case, the on-demand synchronization signal request may be a request for on-demand synchronization signal transmission according to one or more of the received one or more on-demand synchronization signal configurations.

[0212] In some embodiments, the method may further comprise at 930, after transmitting the on-demand synchronization signal request at 920, receiving an on-demand synchronization signal activation indication from the network node, wherein the on-demand synchronization signal activation indication indicates an upcoming on-demand synchronization signal transmission, wherein the received synchronization signal transmissions comprise the upcoming on-demand synchronization signal transmission.

[0213] The method may further comprise at 950 sending a measurement report comprising measurements on the received on-demand synchronization signals in the one or more cells.

[0214] The on-demand synchronization signal request may be transmitted over a Medium Access Control - Control Element, MAC-CE, Physical Uplink Control Channel, PUCCH, or Radio Resource Control, RRC, signaling. The on-demand synchronization signal may comprise an on-demand Synchronization Signal Block, SSB.

[0215] Referring back to Figure 6, the wireless device 110 comprises processing circuitry 120 operable to perform any of the methods described above, including any of the methods described with reference to Figure 9.

[0216] Figure 10 is a flow chart showing a method in a network node according to embodiments. The method may comprise at 1000 receiving from a wireless device capability information of the wireless device regarding one or more capabilities related to on-demand SSB operation. The one or more capabilities may comprise a capability to request an on- demand synchronization signal transmission. The method further comprises at 1010 transmitting an on-demand synchronization signal request configuration related to one or more cells to the wireless device. The method further comprises at 1020 receiving from the wireless device an on-demand synchronization signal request. The method further comprises at 1040, after receiving the on-demand synchronization signal request at 1020, causing on-demand synchronization signal transmissions to be transmitted in one or more cells. The network node may cause the on-demand synchronization signal transmissions to be transmitted in the one or more cells based on the on-demand synchronization signal request.

[0217] The on-demand synchronization signal request configuration may comprise one or more rules for when the wireless device is allowed to or is not allowed to request on-demand synchronization signal transmission. The on-demand synchronization signal request configuration may indicate one or more scenarios, channel conditions and / or event criteria when the wireless device is allowed to request or is not allowed to request on-demand synchronization signal transmission.

[0218] In addition, or alternatively, the on-demand synchronization signal request configuration may comprise a prohibit timer parameter which indicates a time duration from the transmitting the on-demand synchronization signal request during which the wireless device is not allowed to transmit another on-demand synchronization signal request.

[0219] The on-demand synchronization signal request may be a request for on-demand synchronization signal transmission in the one or more cells. For example, the on-demand synchronization signal request may comprise one or more identifiers indicating the one or more cells in which the wireless device requests on-demand synchronization signal transmission.

[0220] The on-demand synchronization signal request may comprise timing information. For example, the on-demand synchronization signal request may comprise information indicating at least one of: a start and or stop time for requested on-demand synchronization signal transmission; duration of requested on-demand synchronization signal transmission; and frequency of requested on-demand synchronization signal transmissions.

[0221] The on-demand synchronization signal request may be a request for on-demand synchronization signal transmission in connection with a respective connection state and or function and or service.

[0222] The method may further comprise at 1015 transmitting, to the wireless device, one or more on-demand synchronization signal configurations. In this case, the on-demand synchronization signal request may be a request for on-demand synchronization signal transmission according to one or more of the transmitted one or more on-demand synchronization signal configurations.

[0223] The method may further comprise at 1030 transmitting an on-demand synchronization signal activation indication from the network node, wherein the on-demand synchronization signal activation indication indicates an upcoming on-demand synchronization signal transmission; wherein the on-demand synchronization signal transmissions caused to be transmitted in the one or more cells comprise the upcoming on-demand synchronization signal transmission.

[0224] The method may further comprise at 1050 receiving a measurement report, from the wireless device, comprising measurements on the on-demand synchronization signals caused to be transmitted in the one or more cells.

[0225] The on-demand synchronization signal may comprise an on-demand Synchronization Signal Block, SSB.

[0226] The on-demand synchronization signal request may be transmitted over a Medium Access Control - Control Element, MAC-CE, Physical Uplink Control Channel, PUCCH, or Radio Resource Control, RRC, signaling. Referring again back to Figure 6, the processing circuitry 170 of the network node 160 may be operable to perform any of the methods described above including the methods described with reference to Figure 10.

[0227] The term unit may have conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and / or displaying functions, and so on, as such as those that are described herein.

[0228] Modifications, additions, or omissions may be made to the systems and apparatuses disclosed herein without departing from the scope of the invention. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and / or other logic. As used in this document, “each” refers to each member of a set or each member of a subset of a set.

[0229] Modifications, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the invention. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

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

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

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

[0233] EXAMPLE EMBODIMENTS

[0234] Group A Embodiments

[0235] 1. A method performed by a wireless device, the method comprising: transmitting to a network node an on-demand synchronization signal block (SSB) request; and receiving on-demand SSB transmissions in one or more cells based on the on- demand SSB request.

[0236] 2. The method of the previous embodiment, further comprising transmitting to the network node capability information of the wireless device regarding capabilities related to on-demand SSB operation.

[0237] 3. The method of any one of the previous two embodiments, further comprising receiving on-demand SSB configuration from the network node.

[0238] 4. The method of any one of the previous three embodiments, wherein the on-demand SSB request is implicit.

[0239] 5. A method performed by a wireless device, the method comprising: a. any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. 6. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.

[0240] 7. The method of any of the previous embodiments, further comprising:

[0241] - providing user data; and

[0242] - forwarding the user data to a host computer via the transmission to the base station.

[0243] Group B Embodiments

[0244] 8. A method performed by a base station, the method comprising: receiving from a wireless device an on-demand synchronization signal block (SSB) request; and causing on-demand SSB transmissions to be transmitted in one or more cells based on the on-demand SSB request.

[0245] 9. The method of the previous embodiment, further comprising receiving from the wireless device capability information of the wireless device regarding capabilities related to on-demand SSB operation.

[0246] 10. The method of any one of the previous two embodiments, further comprising transmitting on-demand SSB configuration to the wireless device.

[0247] 11. The method of any one of the previous three embodiments, wherein the on-demand SSB request is implicit.

[0248] 12. A method performed by a base station, the method comprising: a. any of the base station steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.

[0249] 13. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above. The method of any of the previous embodiments, further comprising:

[0250] - obtaining user data; and

[0251] - forwarding the user data to a host computer or a wireless device.

[0252] Group C Embodiments A wireless device, the wireless device comprising:

[0253] - processing circuitry configured to perform any of the steps of any of the Group A embodiments; and

[0254] - power supply circuitry configured to supply power to the wireless device. A base station, the base station comprising:

[0255] - processing circuitry configured to perform any of the steps of any of the Group B embodiments;

[0256] - power supply circuitry configured to supply power to the base station. A user equipment (UE), the UE comprising:

[0257] - an antenna configured to send and receive wireless signals;

[0258] - radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;

[0259] - the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;

[0260] - an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;

[0261] - an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and

[0262] - a battery connected to the processing circuitry and configured to supply power to the UE. A computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group A embodiments. A computer program product comprising a computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group A embodiments. A non-transitory computer-readable storage medium or carrier comprising a computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group A embodiments. A computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group B embodiments. A computer program product comprising a computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group B embodiments. A non-transitory computer-readable storage medium or carrier comprising a computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group B embodiments.

Claims

CLAIMS:

1. A method performed by a wireless device for receiving on-demand synchronization signal transmissions in one or more cells, the method comprising: receiving (910), from a network node, an on-demand synchronization signal request configuration related to one or more cells. transmitting (920) to the network node an on-demand synchronization signal request; and, after transmitting (920) to the network node the on-demand synchronization signal request, receiving (940) on-demand synchronization signal transmissions in one or more cells.

2. The method of claim 1, further comprising transmitting (900) to the network node capability information of the wireless device regarding one or more capabilities related to on-demand synchronization signal operation.

3. The method of claim 2, wherein the one or more capabilities comprise a capability to request on-demand synchronization signal transmission.

4. The method of any preceding claim, wherein the on-demand synchronization signal request configuration comprises one or more rules for when the wireless device is to or is not to request on-demand synchronization signal transmission.

5. The method of any preceding claim, wherein the on-demand synchronization signal request configuration indicates one or more scenarios, channel conditions and / or event criteria when the wireless device is allowed to or is not allowed to request on-demand synchronization signal transmission.

6. The method of any preceding claim, wherein the on-demand synchronization signal request configuration comprises a prohibit timer parameter which indicates a time duration from the transmitting the on-demand synchronization signal request duringwhich the wireless device is not allowed to transmit another on-demand synchronization signal request.

7. The method according to any preceding claim, wherein the on-demand synchronization signal request is a request for on-demand synchronization signal transmission in one or more cells.

8. The method according to claim 7, wherein the on-demand synchronization signal request comprises one or more identifiers indicating the one or more cells in which the wireless device requests on-demand synchronization signal transmission.

9. The method according to any preceding claim, wherein the on-demand synchronization signal request comprises timing information.

10. The method according to any preceding claim, wherein the on-demand synchronization signal request comprises information indicating at least one of: a start and or stop time for requested on-demand synchronization signal transmission; duration of requested on-demand synchronization signal transmission; and frequency of requested on-demand synchronization signal transmissions.

11. The method of any preceding claim, wherein the on-demand synchronization signal request is a request for on-demand synchronization signal transmission in connection with a respective connection state and or function and or service.

12. The method of any preceding claim, further comprising receiving (915), from the network node, one or more on-demand synchronization signal configurations.

13. The method according to claim 12, wherein the on-demand synchronization signal request is a request for on-demand synchronization signal transmission according to one or more of the received one or more on-demand synchronization signal configurations.

14. The method according to any preceding claim, further comprising receiving (940) an on-demand synchronization signal activation indication from the network node, wherein the on-demand synchronization signal activation indication indicates an upcoming on-demand synchronization signal transmission; wherein the received on- demand synchronization signal transmissions comprise the upcoming on-demand synchronization signal transmission.

15. The method according to any preceding claim, further comprising sending (950) a measurement report comprising measurements on the received on-demand synchronization signal transmissions in the one or more cells.

16. The method according to any preceding claim, wherein the on-demand synchronization signal comprises an on-demand Synchronization Signal Block, SSB.

17. The method according to any preceding claim, wherein the on-demand synchronization signal request is transmitted over a Medium Access Control - Control Element, MAC- CE, Physical Uplink Control Channel, PUCCH, or Radio Resource Control, RRC, signaling.

18. A wireless device (110) comprising processing circuitry (120) operable to perform the method of any of claims 1- 17.

19. A method performed by a network node, the method comprising: transmitting (1010) to a wireless device an on-demand synchronization signal request configuration related to one or more cells. receiving (1030) from the wireless device an on-demand synchronization signal request; and, after receiving (1030) from the wireless device the on-demand synchronization signal request, causing (1040) on-demand synchronization signal transmissions to be transmitted in one or more cells.

20. The method according to claim 19, wherein causing (1040) the on-demand synchronization signal transmissions to be transmitted in the one or more cells comprises causing the on-demand synchronization signal transmissions to be transmitted in the one or more cells based on the on-demand synchronization signal request.

21. The method of claim 19 or 20, further comprising receiving (1000) from the wireless device capability information of the wireless device regarding one or more capabilities related to on-demand synchronization signal operation.

22. The method of claim 21, wherein the one or more capabilities comprise a capability to request on-demand synchronization signal transmission.

23. The method of any of claims 19 to 24, wherein the on-demand synchronization signal request configuration comprises one or more rules for when the wireless device is to or is not to request on-demand synchronization signal transmission.

24. The method of claim 19 to 23, wherein the on-demand synchronization signal request configuration indicates one or more scenarios, channel conditions and / or event criteria when the wireless device is allowed to request or is not allowed to request on-demand synchronization signal transmission.

25. The method of any of claims 19 to 24, wherein the on-demand synchronization signal request configuration comprises a prohibit timer parameter which indicates a time duration from the transmitting the on-demand synchronization signal request during which the wireless device is not allowed to transmit another on-demand synchronization signal request.

26. The method according to any of claims 19 to 25, wherein the on-demand synchronization signal request is a request for on-demand synchronization signal transmissions in the one or more cells.

27. The method according to claim 26, wherein the on-demand synchronization signal request comprises one or more identifiers indicating the one or more cells in which the wireless device requests on-demand synchronization signal transmissions.

28. The method according to any of claims 19 to 27, wherein the on-demand synchronization signal request comprises timing information.

29. The method according to any of claims 19 to 28, wherein the on-demand synchronization signal request comprises information indicating at least one of: a start and or stop time for requested on-demand synchronization signal transmission; duration of requested on-demand synchronization signal transmission; and frequency of requested on-demand synchronization signal transmissions.

30. The method of any of claims 19 to 29, wherein the on-demand synchronization signal request is a request for on-demand synchronization signal transmission in connection with a respective connection state and or function and or service.

31. The method of any of claims 19 to 30, further comprising transmitting (1015), to the wireless device, one or more on-demand synchronization signal configurations.

32. The method according to claim 31, wherein the on-demand synchronization signal request is a request for on-demand synchronization signal transmission according to one or more of the transmitted one or more on-demand synchronization signal configurations.

33. The method according to any of claims 19 to 32, further comprising transmitting (1030) an on-demand synchronization signal activation indication to the wireless device, wherein the on-demand synchronization signal activation indication indicates an upcoming on-demand synchronization signal transmission; wherein the on-demandsynchronization signal transmissions caused to be transmitted in the one or more cells comprise the upcoming on-demand synchronization signal transmission.

34. The method according to any of claims 19 to 33, further comprising receiving (1050) a measurement report, from the wireless device, comprising measurements on the on- demand synchronization signal transmissions caused to be transmitted in the one or more cells.

35. The method according to any claims 19 to 34, wherein the on-demand synchronization signal comprises an on-demand Synchronization Signal Block, SSB.

36. The method according to any of claims 19 to 35, wherein the on-demand synchronization signal request is transmitted over a Medium Access Control - Control Element, MAC-CE, Physical Uplink Control Channel, PUCCH, or Radio Resource Control, RRC, signaling.

37. A network node (160) comprising processing circuitry (170) operable to perform the method according to any of claims 19 to 36.

Images