Preconfigured on-demand synchronization signal block

Abstract

NOT VISIBLE DUE TO STATUS OF PATENT

Description

[0001] PRECONFIGURED ON-DEMAND SYNCHRONIZATION SIGNAL BLOCK

[0002] TECHNICAL FIELD

[0003] Embodiments of the present disclosure are directed to wireless communications and, more particularly, to activation of on-demand synchronization signal block (SSB).

[0004] BACKGROUND

[0005] A user equipment (UE) may be configured with multiple serving cells via carrier aggregation (CA) and / or dual connectivity (DC) (e.g., with a master cell group (MCG) and a secondary cell group (SCG)). There can be a primary serving cell (PCell) and one or more secondary serving cells (SCells). Synchronization signal block(s) (SSB(s)) may be transmitted on each of the serving cells, including the PCell and SCell(s).

[0006] The SCells may be activated / deactivated using an SCell activation command that is typically communicated using a medium access control (MAC) control element (CE) such as SCell Activation / Deactivation MAC CE or an enhanced SCell Activation / Deactivation MAC CE. For an activated SCell, the UE monitors downlink control messages (physical downlink control channel (PDCCH), etc.), measures and report channel state information (CSI), transmits uplink sounding reference signal (SRS), etc. For a deactivated SCell, the UE does not need to monitor downlink control messages (PDCCH, etc.), measure and report CSI, or transmit uplink SRS, etc. Thus, a UE can save energy when an SCell is deactivated.

[0007] Upon receiving an SCell activation message (e.g., from the gNB), the UE starts acquiring the automatic gain control (AGC), time / frequency synchronization and should be able to activate the SCell within a certain duration as defined by the requirements for different cases (known cell versus unknown cell, etc.). When using an enhanced SCell Activation / Deactivation MAC CE, the MAC CE may also be used to trigger tracking reference signal(s) (TRS(s)) on the activated SCells to speed up the activation procedure.

[0008] The Third Generation Partnership Project (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- / inter-band CA. Another objective is to specify triggering method(s) (select from UE uplink wake-up-signal using an existing signal / channel, cell on / off indication via backhaul, SCell activation / deactivation signaling).

[0009] On-demand SSB transmission may be used by a UE for at least SCell time / frequency synchronization, L1 / L3 measurements and SCell activation, and is supported for FR1 and FR2 in non-shared spectrum.

[0010] 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 UE / gNB to trigger normal SSB transmission and / or 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 carrier / cell. Random access channel (RACH) transmission opportunity may be supported in SSB-less Scell. “

[0011] One scenario where on-demand Scell SSB operation can be beneficial is for faster Scell activation. In this scenario, a UE in connected mode is initially served by a coverage Pcell and an Scell is to be activated for the UE to increase the capacity. To activate the Scell, the UE needs to measure SSB from the SCell for the sake of synchronization and antenna gain control and more (see SCell Activation Delay, TS 38.133). Consequently, the activation time depends on how often SSBs are transmitted, and if it the activation time becomes too long then it can be too late to use the capacity cell (for instance the data-buffer has already been emptied). If the load on the SCell is low, then a static SSBs configuration with short or normal periodicity (e.g., 20ms) to avoid too lengthy activation time means that many opportunities for entering sleep mode are lost. On-demand SSB SCell operation could enable the SCell to have a static configuration of SSB with a longer periodicity (e.g., 160ms) or no SSB transmissions all, and then add more SSBs dynamically at SCell activation.

[0012] There currently exist certain challenges. For example, the technical solutions to meet the WID objective for on-demand SSB remains to be detailed and specified. The Applicant has appreciated that such challenges include how to select on-demand SSB configuration(s); how does a gNB inform a UE that on-demand SSBs are to be transmitted; and how does a UE request on-demand SSB. SUMMARY

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

[0014] According to an aspect of the present invention there is provided a method performed by a wireless device. The method comprises receiving one or more on-demand SSB configurations from a network node. The method further comprises transmitting a request to the network node for the network node to activate one or more of the one or more on-demand SSB configurations. The method further comprises receiving an activation indication from the network node, the activation indication comprising an indication of activation of at least one of the one or more on-demand SSB configurations. The method further comprises receiving SSBs according to the at least one of the one or more on-demand SSB configurations.

[0015] The one or more on-demand SSB configurations may comprise a plurality of on- demand SSB configurations.

[0016] In this case, the request to the network node may comprise a request to the network node for the network node to activate a particular one of the plurality of on-demand SSB configurations.

[0017] Each of the one or more on-demand SSB configurations may comprise one or more on- demand SSB configuration parameters. For example, the one or more on-demand SSB configuration parameters may comprise SSB transmission periodicity. In addition, or alternatively, the one or more on-demand SSB configuration parameters may comprise one or more of: frequency location information; start or stop time of on-demand SSB transmission; on-demand SSB transmission duration; SSB transmission offset related to a start point of the on-demand SSB configuration; a number of SSB burst set repetitions; SSB burst position within a frame; SSB subcarrier spacing; SSB quasi-colocation, QCL, relation; transmission power of antenna ports; and SSB positions within a SSB burst.

[0018] The request to the network node may be a request to the network node for the network node to activate one or more of the one or more on-demand SSB configurations in one or more cells of the network node.

[0019] Each of the one or more on-demand SSB configurations may apply to one or more cells of the network node. For example, each of the one or more on-demand SSB configurations may apply to a respective cell of the network node.

[0020] Each of the one or more on-demand SSB configurations may be associated with an identifier.

[0021] The request to the network node may include an identifier for each of the one or more of the one or more on-demand SSB configurations.

[0022] The activation indication may comprise an identifier for each of the at least one of the one or more on-demand SSB configurations.

[0023] Further, when the one or more on-demand SSB configurations comprises a plurality of on-demand SSB configurations, the activation indication may indicate activation or deactivation for each of the plurality of on-demand SSB configurations.

[0024] For example, the activation indication may comprise a bitmap, wherein a bit set to one indicates activation and a bit set to zero indicates deactivation of a corresponding one of the plurality of on-demand SSB configurations.

[0025] The method may comprise monitoring for SSBs according to the at least one of the one or more on-demand SSB configurations.

[0026] The one or more on-demand SSB configurations may be received in Radio Resource Control, RRC, signaling.

[0027] The request to the network node may be transmitted, for example, in RRC signaling or a Medium Access Control-Control Element, MAC-CE.

[0028] The activation indication may be received via a MAC-CE.

[0029] According to an aspect of the present invention, there is provided a wireless device comprising processing circuitry. The processing circuitry is operable to receive one or more on-demand SSB configurations from a network node and transmit a request to the network node for the network node to activate one or more of the one or more on-demand SSB configurations. The processing circuitry is further operable to receive an activation indication from the network node, the activation indication comprising an indication of activation of at least one of the one or more of the one or more on-demand SSB configurations, and to receive SSBs according to the at least one of the one or more on-demand SSB configurations.

[0030] There is further provided a method performed by a network node. The method comprises transmitting one or more on-demand synchronization signal block, SSB, configurations to a wireless device. The method further comprises receiving a request from the wireless device for the network node to activate one or more of the one or more on-demand SSB configurations. The method further comprises transmitting an activation indication to the wireless device, the activation indication comprising an indication of activation of at least one of the one or more on-demand SSB configurations.

[0031] The method may further comprise transmitting SSBs according to the at least one of the one or more on-demand SSB configurations.

[0032] There is further provided a network node comprising processing circuitry. The processing circuitry is operable to transmit one or more on-demand synchronization signal block, SSB, configurations to a wireless device, and to receive a request from the wireless device for the network node to activate one or more of the one or more on-demand SSB configurations. The processing circuitry may further be operable to transmit an activation indication to the wireless device, the activation indication comprising an indication of activation of at least one of the one or more on-demand SSB configurations.

[0033] Certain embodiments may provide one or more of the following technical advantages. For example, in particular embodiments the network may preconfigure on-demand SSB configurations that are suitable for different use-cases or states. For example, one on-demand SSB configuration may be suitable for SCell activation, etc. The preconfigured configurations may be signaled to the UE when there is no time-criticality.

[0034] Particular embodiments provide a resource-efficient and fast way for a UE to request on-demand SSB from one or multiple cells of the gNB.

[0035] The network may ensure that the preconfigured on-demand SSB configurations are feasible and can be applied. If instead the UE is allowed to request an arbitrary on-demand SSB configuration, then the result may be that the gNB cannot accommodate the request due to limitations that are not known by the UE.

[0036] Particular embodiments provide a resource-efficient and fast way for a gNB to inform a UE that a preconfigured on-demand SSB configuration is or will be applied and activated on one or more of its cells.

[0037] BRIEF DESCRIPTION OF THE DRAWINGS

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

[0039] FIGURE 1 illustrates examples of time-domain configurations of on-demand synchronization signal blocks (SSBs);

[0040] FIGURE 2 is a block diagram illustrating an example wireless network;

[0041] FIGURE 3 illustrates an example user equipment, according to certain embodiments;

[0042] FIGURE 4 illustrates an example virtualization environment, according to certain embodiments;

[0043] FIGURE 5 is a flowchart illustrating a method in a wireless device, according to embodiments; and

[0044] FIGURE 6 is a flowchart illustrating a method in a network node, according to embodiments.

[0045] DETAILED DESCRIPTION

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

[0047] 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 preconfigured on-demand SSB configurations, a set of feasible SSB configurations that are useful for different scenarios or use-cases. An on-demand SSB configuration may be activated or deactivated. The gNB preconfigures these for its cells and informs connected UEs about them when there is no time-criticality. A user equipment (UE) may then request one of the configurations on-demand in a simple way for example by signaling a configuration identifier. Similarly, the gNB may inform UEs about the activation of one of the configurations in one of its cells by simply signaling the corresponding identifier.

[0048] Particular embodiments apply to on-demand SSB at SCells, but may also be used for on-demand SSB on the PCell.

[0049] According to some embodiments, one or more preconfigured on-demand SSB configurations are sent from a gNB to a UE. A configuration applies to one or multiple cells of the gNB. A configuration may be active, meaning that SSBs are transmitted according to a transmission pattern which is described by the configuration. A configuration may also be inactive, which means that the described transmission pattern is not applied. Each preconfigured on-demand SSB configuration is associated with an identifier.

[0050] The UE may request the gNB to activate one or more of the preconfigured on-demand SSB configurations, either explicitly for example by signaling a configuration identifier to the network or implicitly for example by indicating the need based on capabilities (e.g., transceiver capabilities), running application, or mobility pattern.

[0051] The gNB may inform a UE that one of the preconfigured on-demand SSB configurations is activated or deactivated by sending an activation / deactivation indication including the index of the configuration. The decision to activate / deactivate may be based on a UE request but it may also be based on other considerations.

[0052] Furthermore, some embodiments include conditions that may trigger the UE or gNB to change the SSB configuration, such as: decision by scheduler to activate carrier aggregation requires a temporal additional SSB transmissions to ensure fast SCell activation; additional SSBs are made available (e.g., 5 ms NCD-SSBs on a different bandwidth part (BWP)) when the UE activates a certain service; additional NCD-SSBs (e.g., on different BWP) when number of RedCap UEs exceeds a threshold; additional SSBs transmitted before physical random access channel (PRACH) occasions, i.e., time / frequency resources for UEs to trigger random access, etc.

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

[0054] The term on-demand SSB configuration may be used herein for a description that details where SSBs are sent, in frequency and time and space, so that a UE can listen to it. The concept may also be referred to as something else, e.g. “SSB pattern”, “SSB mapping” or something similar.

[0055] FIGURE 1 illustrates examples of time-domain configurations of on-demand SSB. The illustrated examples include single shot, a specified number of repetitions and time gap, periodic, and switching between transmission patterns.

[0056] In one embodiment, an on-demand SSB configuration includes one or more of the following information / parameters. The parameters may include the cell or cells of the gNB that it applies to; frequency location information such as global synchronization channel number (GSCN) or absolute radio frequency channel number (ARFCN); and / or start time and stop time of the transmission.

[0057] The start and stop time may be expressed either as an absolute time in units of universal time coordinates (UTC) time, global positioning system (GPS) time or local time format or in the format of system frame number. Alternatively, start time and stop time may be expressed as a time offset relative a reference time. The reference time may be the time that a specific signal is sent (the signal should be identified). The time offset may be in unit of hours, minutes, seconds and milliseconds, or a number of frames and subframes and slots.

[0058] Alternatively, start time and stop time can be expressed as a time offset relative an imminent activity. For example, relative to an upcoming channel decoding activity, such as physical downlink control channel (PDCCH), or combined PDCCH / physical downlink shared channel (PDSCH).

[0059] Alternatively, start time and stop time can be expressed as a recurring (multiples instances ol) time offset relative a periodic activity. For example, relative to discontinuous reception (DRX) activity, such as relative to a periodic paging monitoring activity or physical random access channel (PRACH) configuration.

[0060] Alternatively, a set of potential offsets (e.g., slots / subframes / ... ) are defined as part of the configuration and later in the activation signaling, a reference to one of the offsets are indicated. Alternatively, expressed in relation to anchor cell, Pcell, frame number.

[0061] The on-demand SSB configuration parameters may also include: transmission duration, in units of hours or minutes or seconds or milliseconds or frames and subframes and slots; SSB transmission periodicity, in units of milliseconds or frames and subframes and slots; SSB transmission offset related to the start point of the on-demand SSB configuration; the number of SSB burst set repetitions; SSB burst position within a frame (i. e. , if SSB is in first or second half of frame); SSB subcarrier spacing; SSB quasi-colocation (QCL) relation; and / or transmission power of the antenna ports used to transmit the reference signal, e.g. SSB.

[0062] As an example, one configuration may be suitable for one scenario or state while another configuration may be suitable for another scenario or state.

[0063] In one embodiment, the gNB may have multiple predefined on-demand SSB configurations. Each configuration may be active or not active. Active means that the described pattern is applied, SSBs are transmitted according to it. Inactive means that it is not applied, the SSBs are in fact not transmitted.

[0064] In one example, a first on-demand SSB configuration with certain characteristics is active while a second configuration with other characteristics is inactive. UEs may listen to SSBs according to the active configuration. A benefit with the second configuration, which is inactive, is that it shows what other alternative configurations that a UE can request. More details are described below.

[0065] In some embodiments, only one on-demand SSB configuration may be active at each cell, at any given time.

[0066] In some embodiments, multiple on-demand SSB configurations may be active simultaneously for one cell. For this case, the active on-demand SSB configurations may either be (1) non-colliding or (2) partly colliding or (3) completely colliding with respect to the time, frequency, and spatial-resources that they occupy.

[0067] In some embodiments, when two or more non-colliding on-demand SSB configurations are active simultaneously, the total set of transmitted SSB occasions is given by the union of the active configurations.

[0068] In some embodiments, the multiple active on-demand SSBs have different contents or structures, e.g. different subcarrier spacing (SCS), different primary synchronization signal (PSS)Zsecondary synchronization signal (SSS) sequences. For partly or completely colliding on-demand SSB configurations, the gNB applies collision rules. In one example, a UE for which some SSB occasions are down-prioritized may be configured with an explicit pattern of available SSB occasions, comprising, e.g., a sequence of indices of occurrences that are prioritized (transmitted). In another example, the UE may be configured with an SSB occasion period and a list of occasions that are not prioritized (not transmitted).

[0069] In an embodiment, the on-demand SSB configuration is a new field or a set of fields in an existing Radio Resource Control (RRC) information element (IE) used to configure cellspecific parameters for an SCell. The set of fields may be defined as a new IE.

[0070] In an alternate embodiment, single on-demand SSB configuration is signaled to the UE such that at least part of the configuration is shared among S Cells within one cell group. The network indicates which on-demand SSB cells will be applied dynamically.

[0071] In one embodiment, a plurality of SCells may be configured with a same one or more on-demand SSB configuration(s). In this case, the configuration may be given in CellGroupConfig, or in the servingcell config for Pcell with a new IE or by adding fields directly to the existing IES. The configuration shall at least include the on-demand SSB configuration and the serving cell list. As an alternative embodiment, medium access control (MAC) control element (CE) or downlink control information (DCI) may further update the link of on-demand SSB configuration to the on-demand serving cells.

[0072] In one embodiment, a list of on-demand SSB configurations is configured in CellGroupConfig, or in the servingcell config for Pcell. The one or more SCells are configured with one or more indices / identifiers to a specific on demand SSB configuration. As an alternative embodiment, there is MAC CE or DCI to link one / more on-demand SSB configurations to a serving cell.

[0073] In another embodiment, the shared configuration includes only part of the “on-demand configuration” and the rest of the “on-demand configuration” is within the serving cell configurations.

[0074] An advantage with separating the on-demand SSB configuration from the SCell configuration is that a plurality of SCells may share some parameters of the “ on-demand SSB configuration(s)”. For example, the on-demand SSB configuration may include one or more of SSB periodicity, SSB positions within a burst, and SSB position within a frame, etc., while other parameters (e.g., SSB subcarrier spacing) are configured per the SCell by new or existing field. Thus, not having to repeat those parameters or the “on-demand SSB configuration” per SCell results in lower RRC signaling overhead.

[0075] According to some embodiments, a gNB provisions UE(s) with a list of preconfigured on-demand SSB configurations. In some embodiments, a gNB sends a list of preconfigured on- demand SSB configurations. The list may be signaled in a dedicated channel to a UE over RRC or as a MAC CE or it can be broadcast in a SIB or group DCI or some other dedicated or broadcast signal. The list includes an identifier for each configuration.

[0076] If the configurations (and activation indications, see below) are provided via dedicated signaling, the configuration identifiers need not be consistent between multiple UEs. (i.e. configuration with the same parameters need not have the same identifier for UE1 and UE2.)

[0077] If the configurations or part of the configurations or activation indications are to be provided via broadcast or group signaling (e.g., configurations via SIB broadcast, or indications via group DCI), the configuration identifiers are provided consistently to multiple UEs (i.e., configuration with the same parameters has the same identifier for all UEs).

[0078] The provisioning of preconfigured on-demand SSB configurations is not time-critical.

[0079] According to some embodiments, a UE requests a preconfigured on-demand SSB configuration. In one embodiment, 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.

[0080] In an alternative embodiment, the UE may signal a request to associate an on-demand SSB configuration with a procedure or an operation, e.g. in preparation (ahead ol) Scell activation, in preparation for cDRX onDuration, in conjunction with Radio Resource Management (RRM) measurements, etc. The UE may signal such requests, e.g., if it is in a poor coverage area and a larger number of SSBs may facilitate a synchronization 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. In one embodiment, the IE UEAssistancelnformation is used for UE to communicate preference about the configuration, e.g. SCS. This may be for example given in RRCreconfigurationComplete, or Resume.

[0081] In one embodiment, when the network receives a UE request, such as UE assistance information, the network shall follow the UE request accordingly.

[0082] In another embodiment, when the network receives a UE request, such as UE assistance information, the network may reject the UE request. Optionally, the network may reconfigure a new on-demand SSB configuration based on the network’s preference.

[0083] In another embodiment, the UE does not explicitly ask for a specific on-demand SSB configuration but instead provides assistance / capability such that it implicitly leads to that the network activates a certain on-demand SSB configuration. 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.

[0084] 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 a ultra-reliable low-latency communications (URLLC) type of service is running in the UE.

[0085] According to some embodiments, a gNB indicates activation or deactivation of on- demand SSB configuration. In one embodiment, a gNB may indicate the activation or deactivation of one or multiple on-demand SSB configuration(s) to a UE.

[0086] In one embodiment, a gNB may indicate the activation or deactivation of on-demand SSB configurations to some of serving cells in one CG at the same time, including both deactivated and active serving cells. For example, gNB may activate an on-demand SSB configuration and together with a candidate cell list to UE by PCell. UE will apply the on- demand SSB configurations to the serving cells in the candidate list.

[0087] In one embodiment, one on-demand SSB configuration in a list of on-demand SSB configurations is determined to be a default on-demand SSB configuration, which is expected by a UE to be transmitted in an SCell unless explicitly deactivated by a gNB.

[0088] In one embodiment, one on-demand SSB configuration in a list of on-demand SSB configurations is determined to be a default on-demand SSB configuration, which is expected by a UE to be transmitted in a deactivated SCell until or immediately before receiving the SCell activation command by a gNB.

[0089] In an alternate embodiment, all on-demand SSB configuration in a list of on-demand SSB configurations is not expected by a UE to be transmitted in an SCell unless UE has received an activation indication from a gNB.

[0090] In one embodiment, “other” (i.e., not configured by on-demand SSB configuration) SSBs in an SCell are assumed by the UE to be transmitted by gNB in an SCell irrespectively of whether UE has received an activation or deactivation of one or multiple on-demand SSB configuration(s) or not. In an alternate embodiment, if UE has received one or multiple on- demand SSB configuration(s) for an SCell , UE does not expect gNB to transmit “other” SSBs in said SCell.

[0091] In one embodiment, UE does not expect gNB to transmit “other” SSBs for the duration of which an on-demand SSB configuration is activated.

[0092] In some embodiments, the indication includes a list of identifiers of activated configurations and a list of identifiers of deactivated configurations. In an alternative embodiment, the indication is provided with a bitmap where zero corresponds to deactivated and one to activated.

[0093] In some embodiments, when only one on-demand SSB configuration can be active for a certain cell, only the identity of the activated configuration is indicated to the UE and it is assumed that any previously active configuration becomes deactivated.

[0094] In one embodiment, when the start time or the end time of the on-demand SSB configuration is expressed as an offset relative a reference time, the activation indication from the gNB includes the specific reference time that should be used. If the reference time is the transmission time of a signal, then the specific signal to be used shall be indicated. Alternatively, the indication points to one of the preconfigured offsets whereby it becomes clear to the UE that the new SSB pattern will be available starting offset from the indication. If the UE has previously requested on-demand SSB transmission associated with specific procedures or operations, the gNB may provide an one-time indication that the requested on- demand SSBs will be provided when the procedure or operation occurs. Alternatively, the gNB may indicate activation of on-demand SSB at each future occasion.

[0095] The gNB indication may be sent to specific UEs via dedicated signaling (e.g. MAC CE or DCI via PDCCH scrambled with cell radio network temporary identifier (C-RNTI)). If the configuration identifiers have been provided consistently to multiple UEs (i. e. , a configuration with the same parameters has the same identifier for all UEs), the indication may be sent via group signaling, e.g. using DCI via PDCCH scrambled with a group RNTI,

[0096] In one embodiment, when gNB decides to indicate the on-demand SSB configurations to specific UEs via dedicated signaling (e.g., MAC CE or DCI via PDCCH scrambled with C- RNTI), the indication shall include the valid cell information to explain the on-demand SSB configuration will be applied in which serving cell(s) for which UEs.

[0097] In one embodiment, on-demand SSB configurations are provided via broadcast signaling for preconfiguration and they are activated / deactivated using DCI signaling in PDCCH transmitted at paging occasions, i.e., similar to how system information update notification, Earthquake and Tsunami Warning System (ETWS) or Commercial Mobile Alert System (CMAS) notification is transmitted.

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

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

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

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

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

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

[0104] In FIGURE 2, 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 2 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components.

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

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

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

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

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

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

[0111] 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

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

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

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

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

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

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

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

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

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

[0121] Alternative embodiments of network node 160 may include additional components beyond those shown in FIGURE 2 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0140] 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 formating, 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.

[0141] Although the subject mater 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 2. For simplicity, the wireless network of FIGURE 2 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.

[0142] FIGURE 3 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 3, 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 3 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa. In FIGURE 3, 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 3, 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.

[0143] In FIGURE 3, 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.

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

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

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

[0147] In FIGURE 3, 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.

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

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

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

[0151] In FIGURE 3, 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.

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

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

[0154] FIGURE 4 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).

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

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

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

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

[0159] As shown in FIGURE 4, 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.

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

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

[0162] Still in the context of NFV, 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.

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

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

[0165] Figure 5 is a flow chart showing a method performed by a wireless device for receiving on-demand synchronization signal blocks, SSBs according to embodiments. The method comprises at 600 receiving one or more on-demand SSB configurations from a network node. The method further comprises at 610 transmitting a request to the network node for the network node to activate one or more of the one or more on-demand SSB configurations. The request may be an explicit request or an implicit request as described above. The method further comprises at 620 receiving an activation indication from the network node, the activation indication comprising an indication of activation of at least one of the one or more on-demand SSB configurations. The at least one of the one or more on-demand SSB configurations may comprise the requested one or more of the one or more on-demand SSB configurations. The method further comprises at 630 receiving SSBs according to the at least one of the one or more on-demand SSB configurations.

[0166] The one or more on-demand SSB configurations may comprise a plurality of on- demand SSB configurations.

[0167] In particular, in this case, transmitting 610 the request to the network node may comprise transmitting a request to the network node for the network node to activate a particular one of the plurality of on-demand SSB configurations.

[0168] Thus, the request to the network node may comprise a request to the network node for the network node to activate a subset of the plurality of on-demand SSB configurations.

[0169] Each of the one or more on-demand SSB configurations may comprise one or more on- demand SSB configuration parameters. The one or more on-demand SSB configuration parameters may comprise SSB transmission periodicity. In addition or alternatively, the one or more on-demand SSB configuration parameters may comprise one or more of: frequency location information; start or stop time of on-demand SSB transmission information; on- demand SSB transmission duration; SSB transmission offset related to a start point of the on- demand SSB configuration; a number of SSB burst set repetitions; SSB burst position within a frame; SSB subcarrier spacing; SSB quasi-colocation, QCL, relation; transmission power of antenna ports; and SSB positions within a SSB burst.

[0170] Further, the request to the network node may be a request to the network node for the network node to activate the one or more of the one or more on-demand SSB configurations in one or more cells of the network node. The one or more cells of the network node may comprise a Primary cell, Pcell, and / or one or more Secondary cells, Scells.

[0171] Each of the one or more on-demand SSB configurations may apply to one or more cells of the network node. The one or more cells of the network node may comprise a Primary cell, Pcell, and / or one or more Secondary cells, Scells.

[0172] For example, each of the one or more on-demand SSB configurations may apply to a respective cell of the network node. Alternatively, for example, each of the one or more on- demand SSB configurations may apply to a same one or more cells of the network node.

[0173] Further, each of the one or more on-demand SSB configurations may be associated with an identifier.

[0174] The request to the network node may include an identifier for each of the one or more of the one or more on-demand SSB configurations.

[0175] Further, the activation indication may comprise an identifier for each of the at least one of the one or more on-demand SSB configurations.

[0176] In some embodiments, where the one or more on-demand SSB configurations comprise a plurality of on-demand SSB configurations, the activation indication may indicate activation or deactivation for each of the plurality of on-demand SSB configurations.

[0177] For example, in one embodiment, the activation indication may comprise a bitmap, wherein a bit set to one indicates activation and a bit set to zero indicates deactivation of a corresponding one of the plurality of on-demand SSB configurations.

[0178] The method may comprise monitoring for SSBs according to the at least one of the one or more on-demand SSB configurations.

[0179] The one or more on-demand SSB configurations may be received in Radio Resource Control, RRC, signaling. The request to the network node may be transmitted in RRC signaling or a Medium Access Control-Control Element, MAC-CE, for example. The activation indication may be received via a MAC-CE. Referring back to Figure 2, the processing circuitry 120 of the wireless device 110 described above with respect to Figure 2 may be operable to perform any of the methods described above, including the methods described with reference to Figure 5.

[0180] Figure 6 is a further flow chart showing a method performed by a network node. The method comprises transmitting at 700 one or more on-demand synchronization signal block, SSB, configurations to a wireless device. The method further comprises receiving at 710 a request from the wireless device for the network node to activate one or more of the one or more on-demand SSB configurations. The method further comprises transmitting at 720 an activation indication to the wireless device, the activation indication comprising an indication of activation of at least one of the one or more on-demand SSB configurations.

[0181] The method may further comprise transmitting at 730 SSBs according to the at least one of the one or more on-demand SSB configurations.

[0182] The one or more on-demand SSB configurations may comprise a plurality of on- demand SSB configurations.

[0183] The request to the network node may comprise a request to the network node for the network node to activate a particular one of the plurality of on-demand SSB configurations.

[0184] In this case, the request to the network node may comprise a request to the network node for the network node to activate a subset of the plurality of on-demand SSB configurations.

[0185] Each of the one or more on-demand SSB configurations may comprise one or more on- demand SSB configuration parameters.

[0186] The one or more on-demand SSB configuration parameters may comprise SSB transmission periodicity.

[0187] In addition or alternatively, the one or more on-demand SSB configuration parameters may comprise one or more of: frequency location information; start or stop time of on-demand SSB transmission information; on-demand SSB transmission duration; SSB transmission offset related to a start point of the on-demand SSB configuration; a number of SSB burst set repetitions; SSB burst position within a frame; SSB subcarrier spacing; SSB quasi-colocation, QCL, relation; transmission power of antenna ports; and SSB positions within a SSB burst.

[0188] The request to the network node may be a request to the network node for the network node to activate the one or more of the one or more on-demand SSB configurations in one or more cells of the network node. The one or more cells of the network node may comprise a Primary cell, Pcell, and / or one or more Secondary cells, Scells.

[0189] Each of the one or more on-demand SSB configurations may apply to one or more cells of the network node. The one or more cells of the network node may comprise a Primary cell, Pcell, and / or one or more Secondary cells, Scells.

[0190] For example, each of the one or more on-demand SSB configurations may apply to a respective serving cell of the network node. Alternatively, for example, each of the one or more on-demand SSB configurations may apply to a same one or more cells of the network node.

[0191] Each of the one or more on-demand SSB configurations may be associated with an identifier.

[0192] The request to the network node may include an identifier for each of the one or more of the one or more on-demand SSB configurations.

[0193] The activation indication may comprise an identifier for each of the at least one of the one or more on-demand SSB configurations.

[0194] Further, when the one or more on-demand SSB configurations comprise a plurality of on-demand SSB configurations, the activation indication may further indicate activation or deactivation for each of the plurality of on-demand SSB configurations.

[0195] For example, in one embodiment, the activation indication may comprise a bitmap, wherein a bit set to one indicates activation and a bit set to zero indicates deactivation of a corresponding one of the plurality of on-demand SSB configurations.

[0196] The one or more on-demand SSB configurations may be transmitted in Radio Resource Control, RRC, signaling. The request to the network node may be received in RRC signaling or a Medium Access Control-Control Element, MAC-CE, for example. The activation indication may be transmitted via a MAC-CE.

[0197] Referring back again to Figure 2, 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 6.

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

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

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

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

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

[0203] EXAMPLE EMBODIMENTS

[0204] Group A Embodiments

[0205] 1. A method performed by a wireless device, the method comprising: receiving one or more on-demand synchronization signal block (SSB) configurations from a network node; activating one of the one or more on-demand SS configurations; and monitoring for SSB signals according to the activated on-demand SSB configuration.

[0206] 2. The method of embodiment 1, wherein activating one of the one or more on-demand SS configurations is in response to an activation indication received from the network node.

[0207] 3. The method of embodiment 1, wherein activating one of the one or more on-demand SS configurations is in response to the wireless device determining a particular on- demand SSB configuration is applicable for a procedure to be performed by the wireless device.

[0208] 4. The method of any one of embodiments 1-3, wherein each of the one or more on- demand SSB configurations is associated with a priority for use when multiple on- demand SSB configurations are active simultaneously.

[0209] 5. The method of any one of embodiments 1-4, wherein the wireless device transmits a request to the network node for the network node to activate a particular on-demand SSB configuration.

[0210] 6. 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.

[0211] 7. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.

[0212] 8. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.

[0213] Group B Embodiments

[0214] 9. A method performed by a base station, the method comprising: transmitting one or more on-demand synchronization signal block (SSB) configurations to a wireless device; and transmitting an activation indication to the wireless device, the activation indication comprising an indication to activate one of the one or more on-demand SS configurations.

[0215] 10. The method of embodiment 1, comprising receiving an activation request for one of the one or more on-demand SS configurations from the wireless device.

[0216] 11. The method of any one of embodiments 9-10, wherein each of the one or more on- demand SSB configurations is associated with a priority for use when multiple on- demand SSB configurations are active simultaneously.

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

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

[0219] 14. The method of any of the previous embodiments, further comprising:

[0220] - obtaining user data; and

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

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

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

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

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

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

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

[0228] - 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;

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

[0230] - 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;

[0231] - 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

[0232] - 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 Blocks, SSBs, the method comprising: receiving (600) one or more on-demand SSB configurations from a network node; transmitting (610) a request to the network node for the network node to activate one or more of the one or more on-demand SSB configurations; receiving (620) an activation indication from the network node, the activation indication comprising an indication of activation of at least one of the one or more on- demand SSB configurations; and receiving (630) SSBs according to the at least one of the one or more on-demand SSB configurations.

2. The method of claim 1 or 2, wherein the one or more on-demand SSB configurations comprise a plurality of on-demand SSB configurations.

3. The method of claim 3, wherein the request to the network node comprises a request to the network node for the network node to activate a particular one of the plurality of on-demand SSB configurations.

4. The method according to any preceding claim, wherein each of the one or more on-demand SSB configurations comprises one or more on-demand SSB configuration parameters.

5. The method according to claim 4, wherein the one or more on-demand SSB configuration parameters comprise SSB transmission periodicity.

6. The method according to claim 4 or 5, wherein the one or more on-demand SSB configuration parameters comprise one or more of: frequency location information;start or stop time of on-demand SSB transmission; on-demand SSB transmission duration;SSB transmission offset related to a start point of the on-demand SSB configuration; a number of SSB burst set repetitions;SSB burst position within a frame;SSB subcarrier spacing;SSB quasi-colocation, QCL, relation; transmission power of antenna ports; andSSB positions within a SSB burst.

7. The method of any preceding claim, wherein the request to the network node is a request to the network node for the network node to activate the one or more of the one or more on-demand SSB configurations in one or more cells of the network node.

8. The method of any preceding claim, wherein each of the one or more on- demand SSB configurations applies to one or more cells of the network node.

9. The method of claim 8, wherein each of the one or more on-demand SSB configurations applies to a respective cell of the network node.

10. The method of any preceding claim, wherein each of the one or more on- demand SSB configurations is associated with an identifier.

11. The method of any preceding claim, wherein the request to the network node includes an identifier for each of the one or more of the one or more on-demand SSB configurations.

12. The method of any preceding claim, wherein the activation indication comprises an identifier for each of the at least one of the one or more on-demand SSB configurations.

13. The method according to any of claims 2 to 12, when dependent on claim 2, wherein the activation indication further indicates activation or deactivation for each of the plurality of on-demand SSB configurations.

14. The method according to claim 13, wherein the activation indication comprises a bitmap, wherein a bit set to one indicates activation and a bit set to zero indicates deactivation of a corresponding one of the plurality of on-demand SSB configurations.

15. The method according to any preceding claim, further comprising monitoring for SSBs according to the at least one of the one or more on-demand SSB configurations.

16. The method of any preceding claim, wherein the one or more on-demand SSB configurations are received in Radio Resource Control, RRC, signaling.

17. The method of any preceding claim, wherein the request to the network node is transmitted in RRC signaling or a Medium Access Control-Control Element, MAC-CE.

18. The method of any preceding claim, wherein the activation indication is received via a MAC-CE.

19. A wireless device (110) comprising processing circuitry (120) operable to: receive one or more on-demand SSB configurations from a network node; transmit a request to the network node for the network node to activate one or more of the one or more on-demand SSB configurations; receive an activation indication from the network node, the activation indication comprising an indication of activation of at least one of the one or more on-demand SSB configurations; and receive SSBs according to the at least one of the one or more on-demand SSB configurations.

20. A wireless device (110) according to claim 19, wherein the processing circuitry (120) is operable to perform the method of any of claims 2 to 18.

21. A method performed by a network node, the method comprising: transmitting (700) one or more on-demand synchronization signal block, SSB, configurations to a wireless device; receiving a request from the wireless device for the network node to activate one or more of the one or more on-demand SSB configurations. and transmitting (720) an activation indication to the wireless device, the activation indication comprising an indication of activation of at least one of the one or more on-demand SSB configurations.

22. The method according to claim 22, further comprising transmitting (730) SSBs according to the at least one of the one or more on-demand SSB configurations.

23. The method of claim 21 or 22, wherein the one or more on-demand SSB configurations comprise a plurality of on-demand SSB configurations.

24. The method of claim 23, wherein the request to the network node comprises a request to the network node for the network node to activate a particular one of the plurality of on-demand SSB configurations.

25. The method according to any of claims 21 to 24, wherein each of the one or more on-demand SSB configurations comprises one or more on-demand SSB configuration parameters.

26. The method according to claim 25, wherein the one or more on-demand SSB configuration parameters comprise SSB transmission periodicity.

27. The method according to claim 25 or 26, wherein the one or more on-demand SSB configuration parameters comprise one or more of: frequency location information; start or stop time of on-demand SSB transmission; on-demand SSB transmission duration;SSB transmission offset related to a start point of the on-demand SSB configuration; a number of SSB burst set repetitions;SSB burst position within a frame;SSB subcarrier spacing;SSB quasi-colocation, QCL, relation; transmission power of antenna ports; andSSB positions within a SSB burst.

28. The method of any of claims 21 to 27, wherein the request to the network node is a request to the network node for the network node to activate the one or more of the one or more on-demand SSB configurations in one or more serving cells of the network node.

29. The method of any of claims 21 to 28, wherein each of the one or more on- demand SSB configurations applies to one or more serving cells of the network node.

30. The method of claim 29, wherein each of the one or more on-demand SSB configurations applies to a respective serving cell of the network node.

31. The method of any of claims 21 to 30, wherein each of the one or more on- demand SSB configurations is associated with an identifier.

32. The method of any of claims 21 to 31, wherein the request to the network node includes an identifier for each of the one or more of the one or more on-demand SSB configurations.

33. The method of any of claims 21 to 32, wherein the activation indication comprises an identifier for each of the at least one of the one or more on-demand SSB configurations.

34. The method according to any of claims 23 to 33, when dependent on claim 23, wherein the activation indication further indicates activation or deactivation for each of the plurality of on-demand SSB configurations.

35. The method according to claim 34, wherein the activation indication comprises a bitmap, wherein a bit set to one indicates activation and a bit set to zero indicates deactivation of a corresponding one of the plurality of on-demand SSB configurations.

36. The method of any of claims 21 to 35, wherein the one or more on-demand SSB configurations are transmitted in Radio Resource Control, RRC, signaling.

37. The method of any of claims 21 to 36, wherein the request to the network node is received in RRC signaling or a Medium Access Control-Control Element, MAC-CE.

38. The method of any of claims 21 to 37, wherein the activation indication is transmitted via a MAC-CE.

39. A network node (160) comprising processing circuitry (170) operable to: transmit one or more on-demand synchronization signal block, SSB, configurations to a wireless device; receive a request from the wireless device for the network node to activate one or more of the one or more on-demand SSB configurations; and transmit an activation indication to the wireless device, the activation indication comprising an indication of activation of at least one of the one or more on-demand SSB configurations.

40. The network node (160) according to claim 39, wherein the processing circuitry (170) is further operable to perform the method of any of claims 21 to 38.