Management of synchronization signal block (SSB) adaptations

Abstract

A method implemented in a second network node that is configured to communicate with a user equipment (UE) and a first network node includes: obtaining information relating to a change in a synchronization signal block (SSB) transmission of the first network node; and signaling to the UE based on the obtained information.

Description

[0001] MANAGEMENT OF SYNCHRONIZATION SIGNAL BLOCK (SSB) ADAPTATIONS

[0002] FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to managing synchronization signal block, SSB, adaptations.

[0004] BACKGROUND

[0005] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0006] Synchronization Signal Block (SSB) transmission in 3GPP Release 18

[0007] For a cell in NR, typically, an SSB is transmitted periodically, and it may be used to aid UE’s initial cell search, acquire frame / slot timing, initial time / frequency synchronization, measurements, and as quasi-colocation (QCL) reference for channels / signals, etc. With beamforming, SSBs may need to be transmitted in multiple beams. This can lead to further increased network energy consumption when the SSBs are transmitted in a burst that can span one or multiple slots.

[0008] An NR network node can be configured with up to 64 SSBs. The configured SSBs in a cell for UEs in RRC IDLE / INACTIVE may have all the same periodicity and output power. The network node can provide information to the UEs about how many / which SSBs are active (e.g., present) within the serving cell and neighboring cells. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS) and the physical broadcast channel (PBCH).

[0009] The master information block (MIB) is transmitted in the PBCH. The MIB together with system information block 1 (SIB 1) includes the minimum System Information (SI), which may be required for initial access and for acquiring remaining SI (e.g., SIB2 / SIB4). The network node can provide further information about the rate / periodicity at which these SSBs are provided on cell level. For the serving cell, the parameter ssb-PositionsInBurst indicates which of the SSBs are active, and the parameter ssb-PeriodicityServingCell specifies their rate / periodicity.

[0010] For neighbor cells, a network node can specify the neighboring active (e.g., present) SSBs via the parameter ssb-ToMeasure. The associated rate / periodicity via the SS / PBCH Measurement Timing Configuration (SMTC) defines the time window during which the UE measures the SSBs belonging to these neighboring cells. The UE makes certain assumptions for a standalone NR cell upon the cell selection procedure. Even though the periodicity of the SSB may be configurable, the UE upon initial cell selection expects that the SSB is provided every 20ms in that cell.

[0011] UEs are configured with the above SSB / SIB1 / SI presence and timing / rate information either in RRC IDLE / INACTIVE via broadcast system information or in RRC CONNECTED via dedicated RRC messages. In RRC IDLE / INACTIVE, the ssb- PositionsInBurst and ssb-PeriodicityServing for a serving cell is configured via SIB1, and the SMTC configurations for neighboring cells are provided in SIB2 / SIB4 contained in SI messages.

[0012] SMTC configuration in 3GPP Release 18

[0013] The UE may set up the first SMTC in accordance with the received periodicityAndOffset parameter (providing Periodicity and Offset value for the following condition) in the smtcl configuration. The first subframe of each SMTC occasion occurs at a system frame number (SFN) and subframe of the NR SpCell meeting the following condition:

[0014] SFN mod T = (FLOOR (Offset / X ff if the Periodicity is larger than sf5 subframe = Offset mod 10; else: subframe = Offset or (Offset +5); with T= CEIL(Periodicity / 10).

[0015] See some SMTC ASN.l examples below (reproduced from 3GPP Technical Specification (TS) 38.331 V18.1.0):

[0016] SSB-MTC SEQUENCE { periodicityAndOffset CHOICE { sf5 INTEGER (0..4), sflO INTEGER (0 .9), sf20 INTEGER (0 .19), sf40 INTEGER (0 .39), sf80 INTEGER (0 .79), sfl 60 INTEGER (0..159) duration ENUMERATED { sfl, sf2, sf3, sf4, sf5 }

[0017] SSB-MTC2 ::= SEQUENCE { pci-List SEQUENCE (SIZE (L.maxNrofPCIsPerSMTC)) OF

[0018] PhysCellld OPTIONAL, - Need M periodicity ENUMERATED {sf5, sflO, sf20, sf40, sf80, spare3, spare2, spare 1}

[0019] SSB-MTC2-LP-rl6 ::= SEQUENCE { pci-List SEQUENCE (SIZE (1. maxNrofPCIsPerSMTC)) OF

[0020] PhysCellld OPTIONAL, - Need R periodicity ENUMERATED {sflO, sf20, sf40, sf80, sfl 60, spare3, spare2, spare 1}

[0021] If smtc2 is present, for cells indicated in the pci-List parameter in smtc2 in the same MeasObjeciNR. the UE may set up an additional SMTC in accordance with the received periodicity parameter in the smtc2 configuration and use the Offset (derived from parameter periodicityAndOffset) and duration parameter from the smtcl configuration. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell meeting the above condition. If smtc2-LP is present, for cells indicated in the pci-List parameter in smtc2-LP in the same frequency (for intra frequency cell reselection) or different frequency (for inter frequency cell reselection), the UE may setup an additional SMTC in accordance with the received periodicity parameter in the smtc2-LP configuration and use the Offset (derived from parameter periodicityAndOffsef) and duration parameter from the smtc configuration for that frequency. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell or serving cell (for cell reselection) meeting the above condition.

[0022] Release 19: On-demand SSB provision and adaptation of SSB in time domain

[0023] In ongoing 3GPP Release 19 Work Item “Enhancements of network energy savings for NR,” time-domain dynamics are introduced. For example, the transmission period (i.e., rate) and location (e.g., SSB offset and SSB positions in a burst) of SSBs may be adapted based on UE needs for a serving cell. Alternately, on-demand SSBs may be provided upon indication to UEs whose functionality or performance may be improved if additional signals for loop conversion, synchronization, measurements, or other signal processing steps are available.

[0024] In some scenarios, a cell may be transmitting baseline SSBs at a lower rate, e.g. 160 ms or 20 ms, or no SSBs may be transmitted as a baseline. The network (NW) (e.g., via a network node) may then adapt the rate of the provided SSBs or activate additional SSBs or SSB bursts, e.g., with period 20 ms or 5 ms, respectively. This may be in association with certain procedures, such as activation of secondary cells for carrier aggregation, during handover of UEs between neighbour cells, based on UE speed, etc. On-demand SSBs or adaptive SSBs of limited duration can even one-shot transmissions, with or without a recurrent structure. The on-demand SSBs and or adapted rate may be transmitted during a specified / configured time window or transmitted until further notice (until explicitly notified to the UE and turned off). They may be transmitted on the same or on different frequency resources, power levels, and spatial configuration than the baseline SSB.

[0025] If a UE measures on a frequency and time resource where no SSB is transmitted, UE battery life is wasted.

[0026] If a UE is provided with a static neighbor cell SMTC configuration suited for potential OD-SSB transmissions that may or may not occur, then the UE may end up measuring on a frequency and time resource where no SSB is transmitted, and therefore, UE battery life is wasted and / or the cell quality estimate after filtering may be incorrect. A network node may operate a cell with sparse persistent SSB transmission and only temporarily provide high-rate SSBs on demand. If UEs in other cells / network nodes are not made aware of the OD-SSBs, the only source of measurement for mobility / positioning / etc. may be the low rate SSB. While the network transmits additional SSB signals that the UE is not aware of, the UE mobility measurements are sub-optimal, e.g. mobility decisions can be delayed or not executed as needed.

[0027] If individual cells activate OD-SSBs independently, the resulting aggregate SSB pattern may be spread out in time and not favorable for the UE to perform radio resource management (RRM) measurements.

[0028] SUMMARY

[0029] Some embodiments advantageously provide methods, systems, and apparatuses for managing SSB adaptations.

[0030] While some methods may inform the UE about dynamic SMTCs such that measurements can be carried out on on-demand SSBs from neighbor cells and on SCell candidates, these methods only covered the air interface protocol between the UE and the NW. The network architecture for coordination of SMTC configurations was not covered.

[0031] Thus, there is a need for a solution to manage OD-SSB transmissions in a geographical area that enables a cell to obtain dynamic information about available SSB transmission in their neighbor cells, to be conveyed to the UEs served by the cell. The management solution should also preferably allow efficient coordination of OD-SSB activation decisions and the used SSB resources.

[0032] Such approaches for managing transmissions of OD-SSBs and information related to transmissions of OD-SSB in multiple cells in a cellular network are described herein. Embodiments disclosed herein relate to solutions for making OD-SSB activation decisions and for providing current / dynamic info about OD-SSB status in neighbor cells to a serving / camping cell that may signal such info to one or more UEs in its coverage area.

[0033] Advantages of embodiments described herein include the ability for on-demand SSB transmissions that can enable significant network energy savings as well as reduce unnecessary interference from non-data related downlink transmissions. Some embodiments enable the use of OD-SSB transmissions in an efficient way, which may ensure that both network nodes and UEs are informed about relevant OD-SSB changes. As a result, at least RRM measurement quality and efficiency is improved, increasing UE link robustness and energy efficiency. According to one aspect of the present disclosure, a method in a second network node is provided. The method includes obtaining information relating to a change in an SSB transmission of the first network node. The method includes signaling to the UE based on the obtained information.

[0034] According to one or more embodiments of this aspect, the information is obtained from: the first network node; or from a third network node, the first network node having informed the third network node of the change in the SSB transmission.

[0035] According to one or more embodiments of this aspect, the information is obtained from the third network node, and each of the first network node and the network node (e.g., second network node) manages one of a target cell of the UE and a source cell of the UE.

[0036] According to one or more embodiments of this aspect, the method includes determining to change the SSB transmission; and one of: configuring the first network node with the change in the SSB; or causing a third network node to configure the first network node with the change in the SSB.

[0037] According to one or more embodiments of this aspect, the signaling comprises one or both of: one or more of: update, change, add, or delete an SSB measurement timing configuration window for the UE, the UE being in a coverage area of the second network node; and signal an explicit SSB configuration for a first cell.

[0038] According to another aspect of the present disclosure, a network node is provided. Network node (e.g., a second network node) is configured to obtain information relating to a change in an SSB transmission of the first network node. Network node is configured to signal to the UE based on the obtained information.

[0039] According to one or more embodiments of this aspect, the information is obtained from: the first network node; or from a third network node, the first network node having informed the third network node of the change in the SSB transmission.

[0040] According to one or more embodiments of this aspect, the information is obtained from the third network node, and each of the first network node and the network node (e.g., second network node) manages one of a target cell of the UE and a source cell of the UE.

[0041] According to one or more embodiments of this aspect, the network node (e.g., second network node) is further configured to: determine to change the SSB transmission; and one of: configure the first network node with the change in the SSB; or cause a third network node to configure the first network node with the change in the SSB. According to one or more embodiments of this aspect, the signaling comprises one or both of: one or more of: update, change, add, or delete an SSB measurement timing configuration window for the UE, the UE being in a coverage area of the second network node; and signal an explicit SSB configuration for a first cell.

[0042] According to another aspect of the present disclosure, a method implemented in a first network node is provided. The method includes obtaining information relating to an on-demand synchronization signal block, OD-SSB, transmission pattern suitable for a transmission. The method includes causing or requesting a second network node to transmit an OD-SSB based on the OD-SSB transmission pattern.

[0043] According to one or more embodiments of this aspect, the method includes obtaining, prior to causing or requesting the second network node to transmit the OD-SSB, information relating to OD-SSB capabilities of the second network node.

[0044] According to one or more embodiments of this aspect, the method includes receiving, in response to causing or requesting the second network node to transmit the OD-SSB, an indication that the second network rejected the request, the indication comprising at least one alternative OD-SSB pattern.

[0045] According to one or more embodiments of this aspect, the method includes determining to change the OD-SSB transmission pattern.

[0046] According to one or more embodiments of this aspect, changes to OD-SSBs of the OD-SSB transmission pattern are persistent for a time period longer than a threshold.

[0047] According to another aspect of the present disclosure, a first network node is provided. First network node is configured to obtain information relating to an on-demand synchronization signal block, OD-SSB, transmission pattern suitable for a transmission. First network node is configured to cause or request a second network node to transmit an OD-SSB based on the OD-SSB transmission pattern.

[0048] According to one or more embodiments of this aspect, the first network node is further configured to obtain, prior to causing or requesting the second network node to transmit the OD-SSB, information relating to OD-SSB capabilities of the second network node.

[0049] According to one or more embodiments of this aspect, the first network node is further configured to receive, in response to causing or requesting the second network node to transmit the OD-SSB, an indication that the second network rejected the request, the indication comprising at least one alternative OD-SSB pattern. According to one or more embodiments of this aspect, the first network node is further configured to determine to change the OD-SSB transmission pattern.

[0050] According to one or more embodiments of this aspect, changes to OD-SSBs of the OD-SSB transmission pattern are persistent for a time period longer than a threshold.

[0051] BRIEF DESCRIPTION OF THE DRAWINGS

[0052] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0053] FIG. 1 is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein;

[0054] FIG. 2 is a block diagram of a network node in communication with a user equipment over a wireless connection according to some embodiments of the present disclosure;

[0055] FIG. 3 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0056] FIG. 4 is a flowchart of another example process in a network node according to some embodiments of the present disclosure;

[0057] FIG. 5 is a flowchart of another example process in a network node according to some embodiments of the present disclosure;

[0058] FIG. 6 is a flowchart of another example process in a network node according to some embodiments of the present disclosure;

[0059] FIG. 7 is a schematic diagram of a persistent SSB and a OD-SSB according to some embodiments of the present disclosure;

[0060] FIG. 8 is a schematic diagram of different ways in which OD-SSB management might be implemented according to some embodiments of the present disclosure; and

[0061] FIG. 9 is a schematic diagram of communication between network nodes according to some embodiments of the present disclosure.

[0062] DETAILED DESCRIPTION

[0063] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to managing SSB adaptations. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0064] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0065] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0066] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0067] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0068] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of user equipment capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc.

[0069] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0070] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0071] According to one or more embodiments of this aspect, the general description elements in the form of “one of A and B” corresponds to A or B. According to one or more embodiments of this aspect, at least one of A and B corresponds to A, B or AB, or to one or more of A and B, or one or both of A and B . According to one or more embodiments of this aspect, at least one of A, B and C corresponds to one or more of A, B and C, and / or A, B, C or a combination thereof.

[0072] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0073] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0074] Some embodiments are directed to managing SSB adaptations.

[0075] Referring to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP-type cellular network that may support standards such as LTE and / or NR (5G) and / or (6G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0076] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0077] A network node 16 (eNB or gNB) is configured to include a configuration 24 which is configured to perform one or more network node 16 functions described herein, including functions related to managing SSB adaptations. A user equipment 22 is configured to include an implementation unit 26 which is configured to perform one or more UE 22 functions described herein, including functions related to managing SSB adaptations.

[0078] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 2.

[0079] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves.

[0080] In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0081] Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include configuration unit 24 which is configured to perform one or more network node 16 functions described herein, including functions related to managing SSB adaptations.

[0082] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may include a radio interface 46 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves.

[0083] The hardware 44 of the UE 22 further includes processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read from) memory 54, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0084] Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22.

[0085] The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for performing UE 22 functions described herein. The UE 22 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 50 of the user equipment 22 may include implementation unit 26 which is configured to perform one or more UE 22 functions described herein, including functions related to managing SSB adaptations.

[0086] In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 1.

[0087] The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0088] Although FIGS. 1 and 2 show various “units” such as configuration unit 24 and implementation unit 26 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0089] FIG. 3 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the configuration unit 24), processor 38, and / or radio interface 30. Network node 16 (e.g., a second network node) configured to obtain information relating to a change in a synchronization signal block, SSB, transmission of a first network node (Block SI 00). Network node 16 is configured to signal to the UE 22 based on the obtained information (Block SI 02).

[0090] In some embodiments, each of the first network node and the second network node manage at least one cell.

[0091] In some embodiments, the information is obtained from at least one of: the first network node; and from a third network node, the first network node having informed the third network node of the change in the SSB transmission.

[0092] In some embodiments, network node 16 is further configured to determine to change the SSB transmission, and one of configuring the first network node with the change in the SSB or requesting the first network node be configured with the change in the SSB.

[0093] In some embodiments, the signaling comprises one of: one or more of: updating, changing, adding, or deleting an SSB measurement timing configuration window for the UE, the UE being idle in a coverage area of the second network node; and signaling an explicit SSB configuration for a first cell.

[0094] FIG. 4 is a flowchart of another example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the configuration unit 24), processor 38, and / or radio interface 30. Network node 16 (e.g., a first network node) configured to obtain information relating to an on-demand synchronization signal block, OD-SSB, transmission pattern suitable for a transmission (Block S104). Network node 16 is configured to transmit a request to a second network node configured to cause the second network node to transmit an OD-SSB based on the OD-SSB transmission pattern (Block SI 06). In some embodiments, the network node 16 is further configured to obtain, prior to transmitting the request, information relating to OD-SSB capabilities of the second network node.

[0095] In some embodiments, the network node 16 is further configured to receive, in response to transmitting the request, an indication that the second network rejected the request, the indication comprising at least one alternative OD-SSB pattern.

[0096] FIG. 5 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the configuration unit 24), processor 38, and / or radio interface 30. Network node 16 (e.g., a second network node) is configured to obtain (Block S108) information relating to a change in an SSB transmission of a first network node. Network node 16 is configured to signal (Block SI 10) to the UE 22 based on the obtained information.

[0097] In some embodiments, the information is obtained from: the first network node; or from a third network node, the first network node having informed the third network node of the change in the SSB transmission.

[0098] In some embodiments, the information is obtained from the third network node, and each of the first network node and the network node 16 (e.g., second network node) manages one of a target cell of the UE 22 and a source cell of the UE 22.

[0099] In some embodiments, the network node 16 (e.g., second network node) is further configured to: determine to change the SSB transmission; and one of: configure the first network node with the change in the SSB; or cause a third network node to configure the first network node with the change in the SSB.

[0100] In some embodiments, the signaling comprises one or both of: one or more of: update, change, add, or delete an SSB measurement timing configuration window for the UE 22, the UE 22 being in a coverage area of the second network node; and signal an explicit SSB configuration for a first cell.

[0101] A network node (e.g. the first network node or the third network node) may be configured to transmit information relating to a change in an SSB transmission of the first network node to the network node 16 (e.g. second network node).

[0102] FIG. 6 is a flowchart of another example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the configuration unit 24), processor 38, and / or radio interface 30. Network node 16 (e.g., a first network node) is configured to obtain (Block SI 12) information relating to an OD-SSB transmission pattern suitable for a transmission. Network node 16 (e.g., a first network node) is configured to cause or request (Block SI 14) a second network node to transmit an OD-SSB based on the OD-SSB transmission pattern.

[0103] In some embodiments, the network node 16 (e.g., first network node) is further configured to obtain, prior to causing or requesting the second network node to transmit the OD-SSB, information relating to OD-SSB capabilities of the second network node.

[0104] In some embodiments, the network node 16 (e.g., first network node) is further configured to receive, in response to causing or requesting the second network node to transmit the OD-SSB, an indication that the second network node rejected the request. The indication may comprise at least one alternative OD-SSB pattern.

[0105] In some embodiments, the network node 16 (e.g., first network node) is further configured to determine to change the OD-SSB transmission pattern.

[0106] In some embodiments, changes to OD-SSBs of the OD-SSB transmission pattern are persistent for a time period longer than a threshold.

[0107] In some embodiments, the network node 16 (e.g. first network node) may further be configured to transmit information a further network node, e.g. a neighbor network node of the second network node, the information indicating a change in an SSB transmission of the second network node.

[0108] The second network node may be configured to receive a request from the network node 16 (e.g. a first network node) requesting the second network node to transmit an OD- SSB based on an OD-SSB transmission pattern. In response to the request, the second network node may transmit an OD-SSB based on the OD-SSB transmission pattern. Alternatively, the second network node may send an indication to the network node 16 (e.g. first network node) that the second network node rejects the request. The indication may comprise at least one alternative OD-SSB transmission pattern.

[0109] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for managing SSB adaptations. One or more UE 22 functions described below may be performed by one or more of processing circuitry 50, processor 52, implementation unit 26, etc. One or more network node 16 functions described below may be performed by one or more of processing circuitry 36, processor 38, configuration unit

[0110] 24, etc.

[0111] The term OD-SSB may be used interchangeably or to include both cases when one or more SSBs (e.g., SSB instances) are turned on / off, and / or when the transmission period of the SSB varies in time. In both cases, the adaptation or turning on / off may occur when there is a demand for doing so. The demand itself can come from the UE 22, from an external node, or from the network node 16 itself.

[0112] FIG. 7 depicts a network node 16 with one persistent SSB (solid line) and one OD- SSB (dashed line). The persistent SSB may e.g. be a cell-defining SSB (CD-SSB) or a non- cell-defining SSB (NCD-SSB). Note that even a persistent SSB can be turned off. Turning off a persistent SSB would be equivalent to turning off the power supply to the base station 16 or to the radio frequency (RF) power amplifier of the base station 16. A persistent SSB may be unable to have any pre-determined “stop time.” It may be transmitted all the time, until it no longer is transmitted. Furthermore, the removal of a persistent SSB may be accomplished without any information being sent to any UE 22. There may be other differences between persistent SSBs and OD-SSBs, e.g. as specified in a future cellular standard. For example, the OD-SSB may differ from a persistent SSB in one of more of the following aspects: it may use a different frequency location, have different PSS sequences, have different SSS sequences, have a different physical broadcast channel (PBCH) resource, have different PBCH content, have different demodulation reference signal (DMRS) sequence for decoding the PBCH, have different periodicity, etc. In some embodiments, there is no difference between a persistent SSB and an OD-SSB other than that the UEs 22 are explicitly informed by the network about which SSBs that are OD-SSBs and which that are not, and / or when the OD-SSBs are activated / inactivated.

[0113] In FIG. 7, the OD-SSB is depicted with a dashed line in the left sub-figure to indicate that it may not always be transmitted. An OD-SSB may be time-multiplexed with other persistent SSBs, or it may be frequency multiplexed (as in FIG. 7). An OD SSB may be transmitted in the same set of beams as a persistent SSB or in a different set of beams.

[0114] A benefit of the use of OD-SSBs is that they can help reduce network energy consumption. Instead of constantly transmitting persistent SSBs with a short periodicity, on every carrier, and from every beam in a way that can support all possible use cases, it is possible to design persistent SSB transmissions that may only support limited network functions, such as enabling idle mode UEs 22 to connect to the network (e.g., via network node 16). When situations emerge where additional SSB transmissions would be beneficial, the network (e.g., via network node 16) can activate OD-SSB transmissions to support such transmissions. One example of such use-cases is temporarily enabling or disabling OD- SSBs for connected mode mobility measurements on a cell (e.g., via network node 16).

[0115] Network nodes 16 may not need to inform each other about every OD-SSB transmission. If the transmissions only last for a relatively short duration (e.g., a few milliseconds), the information exchange can become too excessive over the network interfaces. Instead, for OD-SSB transmissions that last for relatively longer durations (e.g. more than 1 second), neighbours (cells / nodes) should be informed when activating, deactivating, or modifying the OD-SSB. Described herein are solutions for management of the transmission of OD-SSBs in a network (e.g., via network node 16), both in terms of controlling which OD-SSBs are transmitted and in terms of ensuring that the network nodes 16 have relevant information about which OD-SSBs are currently transmitted in the network.

[0116] As used herein “OD-SSB change” may refer to activation, deactivation, or modification of an OD-SSB transmission.

[0117] Further, some embodiments differentiate between the function of controlling which OD-SSB signals are used in the network and the function of providing information about OD-SSB signals in the network to the relevant network nodes. FIG. 8 depicts four considerations / functions according to various embodiments, namely:

[0118] • Centralized (upper row of FIG. 8) or distributed (lower row of FIG. 8) management of OD-SSB control

[0119] • Centralized (left column of FIG. 8) or distributed (right column of FIG. 8) management of OD-SSB information

[0120] In some embodiments, both functions (i.e., control and information) are centralized (upper left of FIG. 8) or both are distributed (lower right of FIG. 8). However, in some cases, only the control of OD-SSB transmissions may be able to be centralized (upper right of FIG. 8). In that case, the OD-SSB controller may inform a network node 16 that it is to change (i.e., start transmitting / stop transmitting / modify transmission) an OD-SSB and then inform all its neighbours about this change. The motivation for the OD-SSB change as decided by the centralized controller may be, e.g., coordinated NES feature control in multiple network nodes (e.g., network nodes 16), or coordinated support for RRM measurements in a geographical area in the network (e.g., via network node 16), e.g., as a result of detecting a fast moving UE 22 within the area. Alternatively, in some embodiments (e.g., according to the lower left of FIG. 8) the control of OD-SSB transmissions can be delegated to the individual network nodes. For example, this may occur when each network node 16 makes local NES feature decisions. However, whenever an OD-SSB transmission is changed, the network node 16 may inform a central node (which may be a network node 16) (e.g., as represented by “OD-SSB Information” in FIG. 8).

[0121] When the OD-SSB control is distributed (lower row of FIG. 8) there may be a need for a base station to be able to request OD-SSB transmissions from a cell that can become a potential target for a served UE 22 (e.g., as denoted by “OD-SSB request” in FIG. 8). A decision to activate / deactivate OD-SSB can be implemented in a central RAN Area Function (RANAF) node, or it can be implemented in each base station in a distributed manner.

[0122] When the OD-SSB information exchange is distributed, the network node 16 may inform neighboring cells about OD-SSB changes (e.g., as denoted “OD-SSB Information” in FIG. 8).

[0123] With further reference to FIG. 8, the arrows to and from central network nodes are not marked with labels because the type of information exchanged (e.g., OD-SSB control or OD-SSB information) may be determined by the type of central node (e.g., network node 16) that terminates the communication.

[0124] In at least one embodiment, for control of the OD-SSB transmission, the controlling node (e.g., network node 16) requests according to its needs and the serving node (node that provides OD-SSB, e.g., network node 16) responds whether it can fully or partially satisfy the request. In at least one embodiment, the controlling node (e.g., network node 16) already knows the capabilities of the serving nodes (e.g., network nodes 16) and accordingly requests transmission of a supported OD-SSB pattern that best suits the demands of the controlling node. In some embodiments, such capability knowledge may have been provided via operations and management (0AM) to the controlling node. In some embodiments, the serving nodes (e.g., network nodes 16) provide their OD-SSB and / or SMTC capability information (and associated updates) to the controlling node(s) (e.g., network nodes 16).

[0125] Some embodiments may relate to a distinction between a physical node in the network and a logical function in the network. A centralized function is often implemented by a single network node (e.g., network node 16), while a distributed function is often implemented in many different network nodes (e.g., network nodes 16). In some embodiments, both logical functions (OD-SSB control and OD-SSB information) are implemented in the same physical node, and in other embodiments they are implemented in different physical nodes.

[0126] FIG. 9 depicts additional aspects of various embodiments described herein. FIG. 9 is intended to provide further context and should not be interpreted as exhausting possible alternatives or in any way limiting the present disclosure. Step 1 (OD-SSB control) and Step 2 (OD-SSB information) are discussed above. The “Third NW node” is the “OD-SSB Control” node (e.g., a network node 16), and the “Fourth NW node” is the OD-SSB Information” node (e.g., a network node 16).

[0127] Once a network node 16 obtains updated information about OD-SSB transmissions in the networks, it may enable some served UEs 22 to measure on this new OD-SSB, e.g. for the purpose of enabling connected mode mobility to the new potential target cell that transmits the OD-SSB. Alternatively, the information about OD-SSB transmissions in neighbor cells may be provided to idle / inactive UEs 22 via system information (SI), e.g. by modifying the SMTC configuration that the UEs 22 use for RRM measurements for cell reselection. This is depicted in step “3. Inform” in FIG. 9. With this information about the OD-SSB change, the UE 22 can either start or stop a measurement (indicated by step “4. Measure” in FIG. 9). If certain criteria on the measurements are fulfilled, the UE 22 may end a report back to the network (indicated by step “5. Report” in FIG. 9).

[0128] The following are some example options relating to steps 3, 4, and 5 of FIG. 9 according to some embodiments. Example options include:

[0129] • which UEs 22 are to receive this updated information. In some embodiments, it may be assumed that this information is provided to at least one UE 22 served by the second cell (e.g., network node 16).

[0130] • which information is provided to the UE 22 (e.g., via network node 16). The network may filter some of the information related to OD-SSB changes. In some embodiments, it may be assumed that the UE 22 is receiving information about at least one OD-SSB change.

[0131] • how information about OD-SSB changes is to be transmitted to the UE 22, e.g., on which physical channel. One way is to provide this information to the UE 22 using a medium access control (MAC) control element transmitted on the physical downlink shared channel (PDSCH) (e.g., via network node 16).

[0132] • how the foregoing information is to be formatted. Typically, a UE 22 may measure SSB transmissions after the UE 22 is provided with an SMTC (SSB-based RRM Measurement Timing Configuration) window. • what the UE 22 is to do with the information. For example, this may include details as to how the UE 22 may measure (as depicted by step 4 in FIG. 9) and when and what the UE 22 may report (as depicted by step 5 in FIG. 9) to the network (e.g., via network node 16) based on the measurements.

[0133] In at least one embodiment, the OD-SSB status update may pertain to a carrier (e.g., on frequency 2) other than the one the UE 22 is currently served on (e.g., on frequency 1). In some embodiments, the OD-SSB may be provided as additional SSBs in the same carrier.

[0134] From the perspective of the network node 16 that receives and disseminates othercell OD-SSB change info to UEs 22 in its coverage area.

[0135] Example embodiments may be according to the following:

[0136] Example 1. A method in a second (e.g., serving cell-managing) network node (e.g., network node 16) for adapting to dynamic OD-SSB patterns in the network, the method comprising obtaining info about a change in an S SB transmission in a first network node (e.g., network node 16), and signaling to at least one served or camping UE 22 the SSB change.

[0137] Example 2. The method of Example 1, wherein the first and second network nodes are radio base stations each managing at least one cell.

[0138] Example 3. The method of any one of Examples 1-2, wherein the second network node obtains information about the SSB change from the first network node.

[0139] Example 4. The method of any one of Examples 1-3, wherein the second network node obtains information about the SSB change from a third network node (e.g., an area SSB information manager, which may be a network node 16), where the first network node informs the third network node about the SSB change.

[0140] Example 5. The method of any one of Examples 1-4, wherein the decision to change the SSB transmission is performed in the first network node (local at the base station, e.g., to provide or remove additional SSBs according to a network energy saving (NES) strategy).

[0141] Example 6. The method of any one of Examples 1-5, wherein the decision to change the SSB transmission is performed in the second node, where the second node requests or configures the SSB change in the first node (e.g., to enable better mobility measurements to the UE 22).

[0142] Example 7. The method of any one of Examples 1-6, wherein the decision to change the SSB transmission is performed in the third network node (i.e. the area SSB information manager also controls the SSB transmissions within the area), where the third node requests or configures the SSB change in the first node.

[0143] Example 8. The method of any one of Examples 1-7, wherein the decision to change the SSB transmission is performed in a fourth network node (e.g., a new node responsible for managing SSB transmissions within an area, which may be a network node 16), where the fourth node requests or configures the SSB change in the first node.

[0144] Example 9. The method of any one of Examples 1-8, wherein the signaling comprises updating / changing / adding / deleting an SSB measurement timing configuration (SMTC) window (e.g., for idle UEs 22 in the second node coverage area).

[0145] Example 10. The method of any one of Examples 1-9, wherein the signaling comprises signaling explicit SSB configuration info pertaining to the first cell to the at least one served UE 22 (e.g., for connected UEs 22 served by the second node).

[0146] Example 11. The method of any one of Examples 1-10, wherein the decision to change the SSB transmission may comprise (in case of activation) an activation decision and one or more of: SSB time resource, SSB frequency resource, SSB format (e.g. SSB resource selection so that the SMTC window would be as short as possible).

[0147] Example 12. The method of any one of Examples 1-11, wherein only information related do SSB changes in the first node that are persistent for a time period larger than a threshold (e.g., 1-10 seconds) are communicated to other network nodes and / or to UEs 22 served by the other network nodes.

[0148] Example 13. The method of any one of Examples 1-12, wherein changing an SSB (e.g., CD-SSB, NCD-SSB, or OD-SSB) transmissions can imply e.g. adding or removing an SSB; modifying an existing SSB; activating or deactivating a preconfigured SSB; modifying an SSB configuration (with or without simultaneously activating the SSB).

[0149] Example 14. The method of any one of Examples 1-13, wherein changing the SMTC window comprises adding or removing time durations corresponding to SSBs transmitted in the first cell, or forming / updating the SMTC window as a union of current SSB transmission occasions in two or more first cells in the area.

[0150] Example 15. The method of any one of Examples 1-14, wherein the SSB change decision (order / request) and SSB change information signaling between the first, second, third, and / or fourth nodes may comprise signaling preconfigured SSB transmission patterns and indications / indices to such patterns. Example 16. The method of any one of Examples 1-5, wherein the SSB change information signaling between the second node and a UE 22 served by the second node may comprise signaling preconfigured SMTC windows or SSB transmission patterns and indications / indices to such patterns.

[0151] Corresponding example embodiments are from the perspective of the first, third, and fourth network nodes.

[0152] From the perspective of the network node (e.g., network node 16) that controls the OD-SSB transmission in another network node (e.g., a network node 16).

[0153] Example embodiments include:

[0154] Example 1A. A method in a first network node (e.g., network node 16) for controlling (e.g., turning on, off, or changing periodicity ol) dynamic OD-SSB pattern in a second network node, the method comprising obtaining info about the OD-SSB transmission pattern that is suitable for the current or upcoming service / scenario, and requesting from the second network node (e.g., network node 16) a transmission of OD- SSB according to the desired OD-SSB transmission pattern.

[0155] Example 2A. The method of Example 1 A, wherein, prior to the request, the first network node obtains information about second network node’s OD-SSB capabilities (e.g., possible OD-SSB patterns). a. The obtaining can be from an 0AM defined OD-SSB capabilities for a second network node. b. The obtaining can be based on OD-SSB capabilities reported by the second network node to the first network node. The capability reporting can be triggered by the second node itself (e.g., upon interface setup towards the first network node or alike), or triggered upon capability request from the first network node.

[0156] Example 3A. The method of Example 1A, wherein, upon the OD-SSB pattern request by the first network node, the second network node accepts or rejects the request from the first network node.

[0157] Example 4A. The method of Example 3 A, wherein, upon rejection, the second network node may inform the first network node about alternative OD-SSB patterns that the second network node can instead conform to.

[0158] Example Embodiments:

[0159] Example Al . A method implemented in a second network node 16 that is configured to communicate with a UE 22 and a first network node 16, the method comprising: obtaining information relating to a change in a synchronization signal block, SSB, transmission of the first network node 16; and signaling to the UE 22 based on the obtained information.

[0160] Example A2. The method of Example Al, wherein each of the first network node 16 and the second network node 16 manage at least one cell.

[0161] Example A3. The method of Example Al, wherein the information is obtained from at least one of: the first network node 16; and from a third network node, the first network node 16 having informed the third network node of the change in the SSB transmission.

[0162] Example A4. The method of Example Al , further comprising determining to change the SSB transmission, and one of configuring the first network node 16 with the change in the SSB or requesting the first network node 16 be configured with the change in the SSB.

[0163] Example A5. The method of Example Al, wherein the signaling comprises one of: one or more of: updating, changing, adding, or deleting an SSB measurement timing configuration window for the UE 22, the UE 22 being idle in a coverage area of the second network node 16; and signaling an explicit SSB configuration for a first cell.

[0164] Example Bl. A second network node 16 that is configured to communicate with a UE 22 and a first network node 16, the second network node 16 comprising processing circuitry configured to: obtain information relating to a change in a synchronization signal block, SSB, transmission of the first network node 16; and signal to the UE 22 based on the obtained information.

[0165] Example B2. The second network node 16 of Example Bl, wherein each of the first network node 16 and the second network node 16 manage at least one cell.

[0166] Example B3. The second network node 16 of Example Bl, wherein the information is obtained from at least one of: the first network node 16; and from a third network node, the first network node 16 having informed the third network node of the change in the SSB transmission.

[0167] Example B4. The second network node 16 of Example Bl, wherein the processing circuitry is further configured to determine to change the SSB transmission, and one of configuring the first network node 16 with the change in the SSB or requesting the first network node 16 be configured with the change in the SSB.

[0168] Example B5. The second network node 16 of Example Bl, wherein the signaling comprises one of: one or more of: updating, changing, adding, or deleting an SSB measurement timing configuration window for the UE 22, the UE 22 being idle in a coverage area of the second network node 16; and signaling an explicit SSB configuration for a first cell.

[0169] Example Cl. A method implemented in a first network node 16 that is configured to communicate with a UE 22 and a second network node 16, the method comprising: obtaining information relating to an on-demand synchronization signal block, OD-SSB, transmission pattern suitable for a transmission; and transmitting a request to the second network node 16 configured to cause the second network node 16 to transmit an OD-SSB based on the OD-SSB transmission pattern.

[0170] Example C2. The method of Example Cl, further comprising obtaining, prior to transmitting the request, information relating to OD-SSB capabilities of the second network node 16.

[0171] Example C3. The method of Example Cl, further comprising receiving, in response to transmitting the request, an indication that the second network rejected the request, the indication comprising at least one alternative OD-SSB pattern.

[0172] Example DI. A first network node 16 that is configured to communicate with a UE 22 and a second network node 16, the first network node 16 comprising processing configured to: obtain information relating to an on-demand synchronization signal block, OD-SSB, transmission pattern suitable for a transmission; and transmit a request to the second network node 16 configured to cause the second network node 16 to transmit an OD-SSB based on the OD-SSB transmission pattern.

[0173] Example D2. The first network node 16 of Example DI, wherein the processing circuitry is further configured to obtain, prior to transmitting the request, information relating to OD-SSB capabilities of the second network node 16.

[0174] Example D3. The first network node 16 of Example DI, wherein the processing circuitry is further configured to receive, in response to transmitting the request, an indication that the second network rejected the request, the indication comprising at least one alternative OD-SSB pattern.

[0175] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0176] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0177] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0178] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0179] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0180] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0181] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0182] Abbreviations that may be used in the preceding description include:

[0183] Abbreviation Explanation

[0184] CD-SSB Cell-defining SSB

[0185] NCD-SSB Non cell-defining SSB

[0186] OD-SSB On-demand SSB

[0187] SMTC SSB Measurement Timing Configuration

[0188] SSB Synchronization Signal Block

[0189] UE User equipment

[0190] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings and following claims.

Claims

What is claimed is:

1. A method implemented in a second network node (16) that is configured to communicate with a user equipment, UE, (22) and a first network node, the method comprising: obtaining (SI 08) information relating to a change in a synchronization signal block, SSB, transmission of the first network node; and signaling (SI 10) to the UE (22) based on the obtained information.

2. The method of Claim 1, wherein the information is obtained from: the first network node; or from a third network node, the first network node having informed the third network node of the change in the SSB transmission.

3. The method of Claim 2, wherein the information is obtained from the third network node, and each of the first network node and the second network node (16) manages one of a target cell of the UE (22) and a source cell of the UE (22).

4. The method of any of Claims 1-3, further comprising: determining to change the SSB transmission; and one of: configuring the first network node with the change in the SSB transmission; or causing a third network node to configure the first network node with the change in the SSB transmission.

5. The method of any of Claims 1-4, wherein the signaling comprises one or both of: one or more of: updating, changing, adding, or deleting an SSB measurement timing configuration window for the UE (22), the UE (22) being in a coverage area of the second network node; and signaling an explicit SSB configuration for a first cell.

6. A second network node (16) that is configured to communicate with a user equipment, UE, (22) and a first network node, the second network node (16) comprising processing circuitry configured to: obtain information relating to a change in a synchronization signal block, SSB, transmission of the first network node; and signal to the UE (22) based on the obtained information.

7. The second network node (16) of Claim 6, wherein the information is obtained from: the first network node; or from a third network node, the first network node having informed the third network node of the change in the SSB transmission.

8. The second network node (16) of Claim 7, wherein the information is obtained from the third network node, and each of the first network node and the second network node (16) manages one of a target cell of the UE (22) and a source cell of the UE (22).

9. The second network node (16) of any of Claims 6-8, wherein the processing circuitry is further configured to: determine to change the SSB transmission; and one of: configure the first network node with the change in the SSB; or cause a third network node to configure the first network node with the change in the SSB.

10. The second network node (16) of any of Claims 6-9, wherein the signaling comprises one or both of: one or more of: update, change, add, or delete an SSB measurement timing configuration window for the UE (22), the UE (22) being in a coverage area of the second network node; and signal an explicit SSB configuration for a first cell.

11. A method implemented in a first network node (16) that is configured to communicate with a user equipment and a second network node, the method comprising: obtaining (SI 12) information relating to an on-demand synchronization signal block, OD-SSB, transmission pattern suitable for a transmission; and causing or requesting (SI 14) the second network node to transmit an OD-SSB based on the OD-SSB transmission pattern.

12. The method of Claim 11, further comprising obtaining, prior to causing or requesting the second network node to transmit the OD-SSB, information relating to OD- SSB capabilities of the second network node.

13. The method of any of Claims 11-12, further comprising receiving, in response to causing or requesting the second network node to transmit the OD-SSB, an indication that the second network rejected the request, the indication comprising at least one alternative OD-SSB transmission pattern.

14. The method of any of Claims 11-13, further comprising determining to change the OD-SSB transmission pattern.

15. The method of any of Claims 11-14, wherein changes to OD-SSBs of the OD-SSB transmission pattern are persistent for a time period longer than a threshold.

16. A first network node (16) that is configured to communicate with a user equipment and a second network node, the first network node (16) comprising processing circuitry configured to: obtain information relating to an on-demand synchronization signal block, OD- SSB, transmission pattern suitable for a transmission; and cause or request the second network node to transmit an OD-SSB based on the OD-SSB transmission pattern.

17. The first network node (16) of Claim 16, wherein the processing circuitry is further configured to obtain, prior to causing or requesting the second network node to transmit the OD-SSB, information relating to OD-SSB capabilities of the second network node.

18. The first network node (16) of any of Claims 16-17, wherein the processing circuitry is further configured to receive, in response to causing or requesting the second network node to transmit the OD-SSB, an indication that the second network rejected the request, the indication comprising at least one alternative OD-SSB pattern.

19. The first network node (16) of any of Claims 16-18, wherein the processing circuitry is further configured to determine to change the OD-SSB transmission pattern.

20. The first network node (16) of any of Claims 16-19, wherein changes toOD-SSBs of the OD-SSB transmission pattern are persistent for a time period longer than a threshold.

Images