User equipment, network node and methods in a wireless communication network

Abstract

A method performed by a network node (110) for handling SSB signaling in wireless communication network (100) is provided. The network node (110) sends an RRC message to a UE (121). The RRC message comprises one or more configurations for OD-SSB in one or more serving cells. The network node (110) sends a message to the UE (121). The message comprises a MAC CE controls an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

Description

[0001] USER EQUIPMENT, NETWORK NODE AND METHODS IN A WIRELESS

[0002] COMMUNICATION NETWORK

[0003] TECHNICAL FIELD

[0004] Embodiments herein relate to a User Equipment, a network node and methods performed therein regarding wireless communication. Furthermore, a computer program and a carrier are also provided herein. Especially, embodiments herein relate to handling or enabling Synchronization Signal Block signaling in a wireless communication network.

[0005] BACKGROUND

[0006] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0007] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E- UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5GC is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5G Core (5GC). Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0008] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0009] Network energy consumption

[0010] For a cell in NR, typically, a Synchronization Signal Block (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 QCL reference for channels / signals, etc. With beamforming, SSBs must be transmitted in multiple beams, and this can lead to further increased network energy consumption, when the SSBs are transmitted in a burst that can span one or multiple slots.

[0011] An NR gNB can be configured with up to 64 SSBs. The configured SSBs in a cell for UEs in Radio Resource Control (RRC) IDLE / INACTIVE have all the same periodicity and output power. The gNB can provide information to the UEs about how many / which SSBs that are active (present) within the serving cell and neighboring cells. The SSB consists of a primary synchronization signal (PSS), a secondary synchronization signal (SSS) and the physical broadcast channel (PBCH). The gNB can further provide 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 that are active, and the parameter ssb-PeriodicityServingCell specifies the rate / periodicity of them. Furthermore, the UEs are informed about the SSBs output power via the common parameter ss-PBCH-BlockPower. When it comes to neighbor cells, a gNB can specify the neighboring active (present) SSBs via the parameter ssb-ToMeasure and the associated rate / periodicity via the SSB Measurement Timing Configuration (SMTC) which 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 is configurable, the UE upon initial cell selection expects that the SSB is provided every 20ms in that cell. The master information block (MIB) is part of the SSB. Together with SIB1 they are called Minimum System Information (Minimum SI).

[0012] UEs are configured with the above SSB / SIB1 / SI presence and timing / rate information either in RRCJDLE / IN ACTIVE via broadcast system information or in RRC_Connected via dedicated RRC messages. In IDLE / INACTIVE, the ssb- PositionsInBurst and ssb-PeriodicityServing for serving cell is configured via SIB1 and the SMTC configurations for neighboring cells are provided in SIB2 / SIB4 contained in SI messages. Figure 1 shows an example of SSB transmission / structure.

[0013] Master Information Block (MIB)

[0014] The MIB is transmitted in the message part of the PBCH, which is a part of the SSB, and it contains the following information: In addition to the Ml B content, the SSB also provides the UE with a physical cell identity (ID), derived from the sequence indexes of the PSS and SSS, and an SSB-lndex, derived from the sequence index of the DM-RS transmitted in the PBCH.

[0015] In certain scenarios, a gNB may omit SSB transmissions on a cell and the UE may use SSB of another cell, e.g., another serving deployed on frequency resources adjacent to current serving cell’s frequency resources in same frequency band, or with certain restrictions, in another serving cell in in another frequency band.

[0016] A UE may be configured with multiple serving cells via carrier aggregation and / or dual connectivity, e.g., with a Master Cell Group (MCG) and a Secondary Cell Group (SCG). There may be a primary serving cell (PCell) and one or more secondary serving cells (SCell). SSB(s) may be transmitted on each of the serving cells, including the primary serving cell and secondary serving cell. The SCells can 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, e.g., Physical Downlink Control Channel (PDCCH), etc., measures and report Channel State Information (CSI), transmits uplink Sounding Reference Signals (SRS) etc. For a deactivated SCell, the UE does not need to monitor downlink control messages, measure and report CSI, or transmit uplink SRS, etc. Thus, a UE can save energy when an SCell is deactivated. Upon receiving an SCell activation message, e.g., from the gNB, the UE starts acquiring the Automatic Gain Control (AGC), time / frequency sync and should be able to activate the SCell within a certain duration as defined by the requirements for different cases, such as known cell vs unknown cell, etc. If the SCell is known, delay required for SCell activation is shorter and if the SCell is unknown, the delay required to activate SCell is longer.

[0017] SCell activation / de-activation MAC CEs

[0018] Examples of Legacy SCell activation / deactivation MAC CEs are given below. Some of these MAC CEs were described in prior Release (Rel 15 / 16 / 17 / 18) NR specifications.

[0019] In one example, the legacy SCell Activation / Deactivation MAC CE of one octet is identified by a MAC subheader with LCID as specified in Table 6.2.1-1 of 3GPP TS 38.321. It has a fixed size and consists of a single octet containing seven C-fields and one R-field (Reserve field). The SCell Activation / Deactivation MAC CE with one octet is defined as follows in Figure 6.1.3.10-1 in 3GPP TS 38.321 and is shown in Figure 2.. - Ci: If there is an SCell configured for the MAC entity with SCelllndex i as specified in TS 38.331, this field indicates the activation / deactivation status of the SCell with SCelllndex i, else the MAC entity shall ignore the Ci field. The Ci field is set to 1 to indicate that the SCell with SCelllndex i shall be activated. The Ci field is set to 0 to indicate that the SCell with SCelllndex i shall be deactivated;

[0020] - R: Reserved bit, set to 0.

[0021] There is another legacy SCell activation / deactivation MAC CE of four octets that can support up-to 31 SCells. In this MAC CE signaling, network has to indicate the wanted activation status for each configured SCell.

[0022] There is yet another legacy SCell activation / deactivation MAC CE called Enhanced SCell activation / deactivation MAC CE shown in Figure 3, wherein along with the SCell activation message, the gNB can also indicate to the UE whether TRS for SCell activation is also triggered:

[0023] - Ci: If there is an SCell configured for the MAC entity with SCelllndex i as specified in TS 38.331 [5], this field indicates the activation / deactivation status of the SCell with SCelllndex i, else the MAC entity shall ignore the Ci field. The Ci field is set to 1 to indicate that the SCell with SCelllndex i shall be activated and that a TRS I Dj field is included for the SCell. The Ci field is set to 0 to indicate that the SCell with SCelllndex i shall be deactivated and that no TRS ID field is included for this SCell;

[0024] - TRS IDj: If TRS IDj is set to a non-zero value, it indicates the corresponding TRS address by scellActivationRS-ld as specified in TS 38.331 [5] is activated. If TRS IDj is set to zero, it indicates that no TRS is used for the corresponding SCell;

[0025] - R: Reserved bit, set to 0.

[0026] On-demand SSB (OD-SSB) provision

[0027] In ongoing NR evolution, on-demand SSBs may be provided “temporarily” to UEs whose functionality or performance may be improved if additional signals for loop conversion, synchronization, measurements, or other signal processing steps are available. In some scenarios, a cell may be transmitting baseline SSBs at a lower rate, e.g. 160 ms or 20 ms, or no SSBs may be transmitted as a baseline. The NW may then activate additional SSBs or SSB bursts, e.g. with period 20 ms or 5 ms, respectively, in association with certain procedures, such as SCell activation. On-demand SSBs may be one-shot transmissions or limited-duration SSB bursts, with or without a recurrent structure. The on-demand SSBs may be transmitted during a specified / configured time window or transmitted until further notice, e.g., until explicitly notified to the UE and turned off. They may be transmitted at the same or at a different power level and spatial configuration than the baseline SSB. Some scenarios where on-demand SSBs are expected to be useful include:

[0028] • SCell quality measurements upon SCell configuration.

[0029] • Synchronization upon SCell activation.

[0030] • Timing / Frequency tracking for an active serving cell.

[0031] • RRM measurements on serving or neighbour cells. Etc.

[0032] Current Status in 3GPP

[0033] RAN1 has sent a RAN2 LS on the MAC CE aspects with the following content:

[0034] RAN1 has discussed signaling mechanisms to indicate on-demand SSB transmission and has reached agreements to support indication by both RRC and MAC CE signalling.

[0035] Agreement (RAN1#118)

[0036] For a cell supporting on-demand SSB SCell operation,

[0037] • Support RRC based signaling to indicate on-demand SSB transmission on the cell at least for the case where this RRC also configures the SCell, activates the SCell, and provides on-demand SSB configuration. o FFS: Whether to support RRC based signaling for other cases.

[0038] • Support MAC CE based signaling to indicate on-demand SSB transmission on the cell for Scenarios #2 and #2A.

[0039] Note: Deactivation and adaptation of on-demand SSB transmission can be separately discussed.

[0040] Agreement (RAN1#118)

[0041] For a cell supporting on-demand SSB SCell operation, at least for the following parameter(s), multiple candidate values can be configured by RRC and the applicable value can be indicated by MAC CE for on-demand SSB transmission indication for the cell.

[0042] Periodicity of the on-demand SSB FFS: Any other relevant parameters

[0043] Agreement (RAN1#116bis) For a cell supporting on-demand SSB SCell operation, further study the following options.

[0044] • Option 1 : Separate signaling between legacy / existing signaling (e.g., RRC, MAC CE) providing SCell activation / deactivation and signaling providing On- demand SSB transmission indication.

[0045] • Option 2: A single signaling in which both SCell activation / deactivation and On-demand SSB transmission indication are provided. o FFS: Details of the signaling

[0046] • Other options are not precluded.

[0047] • FFS: Details on On-demand SSB transmission indication

[0048] To provide more context for RAN2, the following are relevant RAN1 agreements on Cases and Scenarios for on-demand SSB SCell operation.

[0049] Agreement (RAN1#116)

[0050] Regarding the UE assumption on SSB transmission on a cell supporting on-demand SSB SCell operation, the following cases are identified for further study:

[0051] • Case #1 : No always-on SSB on the cell

[0052] • Case #2: Always-on SSB is periodically transmitted on the cell

[0053] • FFS: Whether always-on SSB and on-demand SSB are not cell-defining SSB if transmitted.

[0054] FFS: Which scenario the above applies for

[0055] Agreement (RAN1#116)

[0056] For the following identified scenarios for on-demand SSB SCell operation, focus future RAN1 discussion to down-select (both may be selected) between the two scenarios.

[0057] • Scenario #2: SCell is configured to a UE but before the UE receives SCell activation command (e.g., as defined in TS 38.321)

[0058] • Scenario #3: After UE receives SCell activation command (e.g., as defined in TS 38.321) o This does not preclude SCell for which activation is completed o FFS: The case where SCell activation is completed

[0059] FFS: Application timing between NW triggering message and on demand SSB transmission Agreement (RAN1#116bis)

[0060] For the identified scenarios and cases (as per RAN1#116 agreement), on-demand

[0061] SSB can be triggered by gNB at least for the following scenarios / cases:

[0062] • Scenario #2 and Case #1

[0063] • Scenario #2 and Case #2

[0064] • Scenario #2A and Case #1

[0065] • Scenario #2A and Case #2

[0066] • FFS: Scenario #3A and Case #1

[0067] • FFS: Scenario #3A and Case #2

[0068] • FFS: Scenario #3B and Case #1

[0069] • FFS: Scenario #3B and Case #2

[0070] • For Case #1 , once on-demand SSB is triggered, its transmission is in a periodic manner. o Note: This does not imply periodic on-demand SSB is transmitted indefinitely after triggered.

[0071] • Notes: o Scenario #2A refers to

[0072] ■ “When UE receives SCell activation command (e.g., as defined in TS 38.321)” o Scenario #3A refers to

[0073] ■ “After UE receives SCell activation command (e.g., as defined in TS 38.321) until SCell activation is completed” o Scenario #3B refers to

[0074] ■ “When SCell activation is completed and SCell is activated” or

[0075] ■ “After SCell activation is completed and SCell is activated” o For discussion purpose under Al 9.5.1, always-on SSB is SSB supported in Rel-18 specifications. o Timing for on-demand SSB transmission (e.g. when the triggered SSB starts and ends) will be separately discussed.

[0076] RAN1 respectfully requests RAN2 to design MAC CE based signaling to indicate on-demand SSB transmission for Scenarios #2 and #2A. RAN1 is working on the further details needed for RRC and MAC CE based signaling to indicate on-demand SSB transmission and will inform RAN2 as further agreements are made.

[0077] In the context of the MAC CE, RAN2 made the following agreements:

[0078] • Scenarios on OD-SSB:

[0079] • RAN2 start the discussion from Scenario 2 / 2A and wait for RAN1 conclusion on Scenario 3A / 3B.

[0080] • OD-SSB transmission indication:

[0081] • RRC based OD-SSB transmission indication is used to indicate at least the initial activation / deactivation state of OD-SSB configuration. FFS on reconfiguration.

[0082] • New MAC-CE for OD-SSB transmission indication is introduced. We will not change legacy SCell activation / deactivation MAC CE. FFS if we need further optimization for scenario 2A.

[0083] SUMMARY

[0084] An object of embodiments herein is to handle SSB signalling in a wireless communication network in an efficient manner and improve the performance of the wireless communication network.

[0085] According to an aspect of embodiments herein, the object is achieved by a method performed by a network node for handling SSB signalling in a wireless communication network. The network node sends an RRC message to a UE. The RRC message comprises one or more configurations for OD-SSB in one or more serving cells. The network node sends a message to the UE. The message comprises a MAC CE controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

[0086] According to another aspect of embodiments herein, the object is achieved by a method performed by a UE for handling SSB signaling in a wireless communication network. The UE receives an RRC message from a network node. The RRC message comprises one or more configurations for OD-SSB in one or more serving cells. The UE receives a message from the network node. The message comprises a MAC CE controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

[0087] It is furthermore provided herein a computer program, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the UE and the network node, respectively. It is additionally provided herein a carrier, having stored thereon a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the UE and the network node, respectively.

[0088] According to another aspect of embodiments herein, the object is achieved by providing a network node and a UE configured to perform the methods herein, respectively.

[0089] Thus, according to another aspect of embodiments herein, the object is achieved by a network node configured to handle SSB signaling in a wireless communication network. The network node is configured to send an RRC message to a UE. The RRC message is adapted to comprise one or more configurations for OD-SSB in one or more serving cells. The network node is configured to send a message to the UE. The message is adapted to comprise a MAC CE controlling an OD-SSB transmission based on the one or more OD- SSB configurations for the one or more serving cells.

[0090] According to another aspect of embodiments herein, the object is achieved by a UE configured to handle SSB signaling in a wireless communication network. The UE is configured to receive an RRC message from a network node. The RRC message is adapted to comprise one or more configurations for OD-SSB in one or more serving cells. The UE is configured to receive a message from the network node. The message is adapted to comprise a MAC CE controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

[0091] Further embodiments are provided in the dependant claims.

[0092] BRIEF DESCRIPTION OF THE DRAWINGS

[0093] Examples of embodiments herein are described in more detail with reference to the accompanying drawings, according to the following description.

[0094] Figure 1 is a schematic diagram illustrating an example of SSB transmission, according to prior art.

[0095] Figure 2 is a schematic diagram illustrating an example of a MAC Ce for SCell Activation / Deactivation, according to prior art. Figure 3 is a schematic diagram illustrating another example of a MAC CE for SCell activation / deactivation, according to prior art.

[0096] Figure 4 is a schematic diagram illustrating a non-limiting example of a wireless communication network, according to embodiments herein.

[0097] Figure 5 is a flowchart depicting embodiments of a method in a network node, according to embodiments herein.

[0098] Figure 6 is a flowchart depicting embodiments of a method in a user equipment, according to embodiments herein.

[0099] Figures 8a-c are schematic diagrams illustrating non-limiting examples of a MAC CE for

[0100] OD-SSB activation / deactivation, according to embodiments herein.

[0101] Figures 9a-b are schematic diagrams illustrating non-limiting examples of a MAC CE for

[0102] OD-SSB activation / deactivation, according to embodiments herein.

[0103] Figure 10 is a schematic block diagram illustrating a non-limiting example of a network node, according to embodiments herein.

[0104] Figure 11 is a schematic block diagram illustrating a non-limiting example of a user equipment, according to embodiments herein.

[0105] Figure 12 shows an example of a communication system, according to embodiments herein.

[0106] Figure 13 shows a block diagram illustrating a non-limiting example of a user equipment, according to embodiments herein.

[0107] Figure 14 shows a block diagram illustrating a non-limiting example of a network node, according to embodiments herein.

[0108] Figure 15 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0109] DETAILED DESCRIPTION

[0110] As a part of developing embodiments herein the inventors identified a problem which first will be discussed.

[0111] RAN1 has asked RAN2 to design the MAC CE based signaling to indicate on- demand SSB transmission for #2 and #2A. The RAN1 agreements with relevant content as input for the design are:

[0112] Agreement (RAN1#118) For a cell supporting on-demand SSB SCell operation, at least for the following parameter(s), multiple candidate values can be configured by RRC and the applicable value can be indicated by MAC CE for on-demand SSB transmission indication for the cell.

[0113] • Periodicity of the on-demand SSB

[0114] • FFS: Any other relevant parameters

[0115] The problem is that as there can be a long list of different configuration parameters, it is not feasible to do as this agreement guides. The agreement would imply that the MAC CE would have for each on-demand SSB configuration that is activated (at least one per SCell) as many fields as there are parameters to basically RRC configure the on-demand SSB details via the MAC CE. This makes it also not feasible to include more than one activated on-demand SSB in one MAC CE. In worse case this means that network has to send more than one MAC CE per SCell to activate the on-demand SSBs.

[0116] According to embodiments herein, a new MAC CE design is provided. In examples of the embodiments herein, a list of potential parameters to be configured for OD-SSB is provided. Further, according to examples of embodiments herein, it is provided which of the parameters t may be preconfigured via an RRC (re-)configuration, and which may be controlled dynamically via MAC-CE. This separation is summarized in the Table 1 and Table 2 below. It should be noted that the name of the parameters is just exemplary, and one or more of the RRC parameters may be optionally configured:

[0117] Table 1 : Example of parameters configured by RRC.

[0118]

[0119] Table 2: Example of parameters that can be controlled via MAC-CE.

[0120] Embodiments herein may e.g., bring the advantage of providing an efficient mechanism for dynamic mechanism for OD-SSB provision through a design of a simple yet flexible framework including RRC signaling and MAC-CE, resulting in an improved performance of the wireless communication network.

[0121] Figure 4 is a schematic overview depicting a wireless communication network 100, wherein embodiments herein may be implemented. The wireless communication network 100 comprises one or more RANs and one or more CNs. The wireless communication network 100 may use 5G NR but may further use a number of other different technologies, such as, 6G, Wi-Fi, (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0122] Network nodes, such as a network node 110, operates in the wireless communication network 100. Each of the network nodes e.g., provides a number of cells and may use these cells for communicating with other network nodes. Each of the network nodes may be a transmission and reception point e.g., a radio access network node such as a base station, a radio base station, a NodeB, an evolved Node B (eNB, eNodeB, eNode B), an NR / g Node B (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wireless Local Area Network (WLAN) access point, an Access Point Station (AP STA), an access controller, a UE acting as an access point or a peer in a Device to Device (D2D) communication, or any other network unit capable of communicating with a UE within a service area 11 , such as a cell 11 , served by the network node 110, depending e.g., on a radio access technology and terminology used. The service area 11 may also be referred to as a cell, a beam or a beam group of a first radio access technology (RAT), such as 6G, 5G, LTE, Wi-Fi, or similar.

[0123] UEs, such as a UE 121 , operate in the wireless communication network 100. The UE 121 may e.g. be a radio device, a wireless device, an NR device, a mobile station, a wireless terminal, an internet of things (loT) device, an enhanced Machine Type Communication (eMTC) device, an NR RedCap device, a CAT-M device, a Vehicle-to- everything (V2X) device, Vehicle-to-Vehicle (V2V) device, a Vehicle-to-Pedestrian (V2P) device, a Vehicle-to-lnfrastructure (V2I) device, a Vehicle-to-Network (V2N) device, a WiFi device, an LTE device, a non-access point (non-AP) STA, a STA, that communicates via a base station, and one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN). It should be understood by the skilled in the art that the term UE relates to a non-limiting term which means any UE, terminal, wireless communication terminal, user equipment, (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.

[0124] Methods herein may in one aspect be performed by the UE 121 and in another aspect by the network node 110. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud 190 as shown in Figure 4, may be used for performing or partly performing the methods of embodiments herein.

[0125] The cloud 190 may comprise a cloud network infrastructure. A cloud network infrastructure may e.g. be a collection of hardware and software elements such as computing power, networking, storage, and virtualization resources needed to enable cloud computing in a wireless communication network such as e.g. a communication network.

[0126] A number of embodiments will now be described, some of which may be seen as alternatives, while some may be used in combination. The methods described below in reference to Figures 5-6 may be combined in any suitable way. That is, any part of a described method may be combined with any part of one or more of the other methods. A method according to embodiments will now be described from the view of the network node 110 together with Figure 5. Figure 5 depicts example embodiments of a method performed by the network node 110, e.g., for handling SSB signaling in the wireless communication network 100. A serving cell as used below, may e.g., comprise an SCell. The method comprises any one or more of the following actions, which actions may be taken in any suitable order. Optional actions are referred to as dashed boxes in Figure 5.

[0127] Action 501

[0128] The network node 110 sends an RRC message to the UE 121. The RRC message comprises one or more configurations for OD-SSB in one or more serving cells. In other words, the network node 110 configures the UE 121 with one or more OD-SSB configurations for the one or more serving cells. The respective configurations may e.g., comprise any one or more out of time domain transmission characteristics, frequency domain transmission characteristics, spatial domain transmission characteristics, and / or power domain transmission characteristics for OD-SSB transmission.

[0129] In some embodiments, the one or more OD-SSB configurations comprises any one or more out of:

[0130] - one or more OD-SSB configurations per serving cell,

[0131] - one or more common OD-SSB configurations for all of the one or more serving cells, and

[0132] - one or more common OD-SSB configurations for a subset of the one or more serving cells.

[0133] One or more OD-SSB configurations per serving cell may e.g., mean that for each serving cell, the UE 121 is configured with one or more OD-SSB configurations.

[0134] One or more common OD-SSB configurations for all of the one or more serving cells may e.g., mean that all of the one or more serving cells share the same one or more configurations, i.e., all of the serving cells may use any of the one or more common OD- SSB configurations.

[0135] One or more common OD-SSB configurations for a subset of the one or more serving cells may e.g., mean that a subset of serving cells share the same one or more common configurations. Further, different subsets of serving cells, where the subsets are overlapping, partly overlapping or non-overlapping, may have different one or more OD- SSB configurations. The network node 110 may send the UE 121 a combination of the above described examples, meaning that some, or all, serving cells have a separate OD-SSB configuration, all the serving cells share one or more common OD-SSB configurations, and at least one subset of serving cells may share one or more common OD-SSB configuration.

[0136] Action 502

[0137] The network node 110 sends a message to the UE 121. The message comprises a MAC CE controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells. In other words, the network node 110 controls the OD-SSB transmission to the UE 121 by sending the MAC CE to the UE 121.

[0138] In some embodiments, the MAC CE comprises a first number of bits. Each of the one or more serving cells is associated with a specific bit of the first number of bits. The respective bits indicate whether an OD-SSB for a serving cell should be activated or deactivated. Thus, the UE 121 knows which serving cells have an OD-SSB activated and / or deactivated.

[0139] In some embodiments, the MAC CE further comprises a second bit. The second bit is indicative of whether the first number of bits further indicates an activation / deactivation status of the one or more serving cells. This may mean that, in addition to only activating OD-SSB, the first number of bits further indicates whether the serving cell should be activated and / or deactivated.

[0140] In some embodiments, the MAC CE comprises a respective first field for one or more activated OD-SSBs. The respective first fields control the transmission of the activated OD-SSBs. This may e.g., mean that one or more the first field indicates, such as activates, the one or more OD-SSBs in their respective serving cell. The respective first fields may e.g., be N bits long. When combined with the first number of bits, and in some examples with the second bit, the respective first fields may e.g., be ordered in the same order as the serving cells are ordered in the first number of bits.

[0141] In some embodiments, the respective first fields comprise an index or identity. The index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations. In other words, the index or identity indicates the configuration used for an OD-SSB. The configuration may comprise one of the one or more OD-SSB configurations sent in the RRC message.

[0142] In some embodiments, the respective first fields comprise two or more subfields. A first subfield may comprise an OD-SSB subfield. The OD-SSB subfield may e.g., indicate an index or identity indicating an OD-SSB configuration of the one or more received OD- SSB configurations. A one or more second subfields may e.g., comprise a respective parameter subfield. A parameter subfield may e.g., indicate a parameter value of a parameter in the indicated OD-SSB configuration. Thus, a first field may comprise a number of subfields, where one subfield, the OD-SSB subfield, indicates the OD-SSB configuration, while the one or more second subfields indicate parameter values to use for specific parameters in the OD-SSB configuration. This may e.g., comprise a change of an already used parameter or an initial selection of a parameter value. The parameter values may e.g., be selected from a list of possible parameter values.

[0143] In some embodiments, sending the message comprising the MAC CE comprises sending separate MAC CE for each activated / deactivated OD-SSB, or for each OD-SSB which configuration is changed. The respective separate MAC CE comprises a cell identity field and an OD-SSB field. The cell identity field comprises an identity or index indicating a serving cell. The OD-SSB field comprises an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations. A changed configuration may e.g., comprise indicating another OD-SSB configuration of the one or more OD-SSB configuration sent in the RRC message. Alternatively, or additionally, a changed configuration may e.g., comprise changed or updated parameter value for a parameter in an OD-SSB configuration.

[0144] In some embodiments, the respective separate MAC CE further comprises a parameter field indicating a parameter value of a parameter in the indicated OD-SSB configuration. This may e.g., comprise a change of an already used parameter or an initial selection of a parameter value. The parameter values may e.g., be selected from a list of possible parameter values.

[0145] In some embodiments, sending the message comprising the MAC CE comprises sending separate MAC CEs for OD-SSB activation / deactivation and OD-SSB configuration. This may e.g., mean that one MAC CE activates and / or deactivates OD- SSBs and / or serving cells and another MAC CE configures the OB-SSBs, e.g., as described above.

[0146] In some embodiments, sending the message comprising the MAC CE further comprises indicating a Transmission Configuration Indicator, TCI, state for activated OD- SSBs in the one or more serving cells.

[0147] In some embodiments, sending the message comprising the MAC CE further comprises indicating a set of candidate OS-SSBs. A method according to embodiments will now be described from the view of the UE 121 together with Figure 6. Figure 6 depicts example embodiments of a method performed by the UE 121 , e.g., for handling SSB signaling in the wireless communication network 100. A serving cell as used below, may e.g., comprise an SCell. The method comprises any one or more of the following actions, which actions may be taken in any suitable order. Optional actions are referred to as dashed boxes in Figure 6.

[0148] Action 601

[0149] The UE 121 receives an RRC message from the network node 110. The RRC message comprises one or more configurations for OD-SSB in one or more serving cells. In other words, the UE 121 is configured, by the network node 110, with one or more OD- SSB configurations for the one or more serving cells. The respective configurations may e.g., comprise any one or more out of time domain transmission characteristics, frequency domain transmission characteristics, spatial domain transmission characteristics, and / or power domain transmission characteristics for OD-SSB transmission.

[0150] In some embodiments, the one or more OD-SSB configurations comprises any one or more out of:

[0151] - one or more OD-SSB configurations per serving cell,

[0152] - one or more common OD-SSB configurations for all of the one or more serving cells, and

[0153] - one or more common OD-SSB configurations for a subset of the one or more serving cells.

[0154] One or more OD-SSB configurations per serving cell may e.g., mean that for each serving cell, the UE 121 is configured with one or more OD-SSB configurations.

[0155] One or more common OD-SSB configurations for all of the one or more serving cells may e.g., mean that all of the one or more serving cells share the same one or more configurations, i.e., all of the serving cells may use any of the one or more common OD- SSB configurations.

[0156] One or more common OD-SSB configurations for a subset of the one or more serving cells may e.g., mean that a subset of serving cells share the same one or more common configurations. Further, different subsets of serving cells, where the subsets are overlapping, partly overlapping or non-overlapping, may have different one or more OD- SSB configurations.

[0157] The network node 110 may send the UE 121 a combination of the above described examples, meaning that some, or all, serving cells have a separate OD-SSB configuration, all the serving cells share one or more common OD-SSB configurations, and at least one subset of serving cells may share one or more common OD-SSB configuration.

[0158] Action 602

[0159] The UE 121 receives a message from the network node 110. The message comprises a MAC CE controlling an OD-SSB transmission based on the one or more OD- SSB configurations for the one or more serving cells. In other words, the network node 110 controls the OD-SSB transmission to the UE 121 by sending the MAC CE to the UE 121.

[0160] In some embodiments, the MAC CE comprises a first number of bits. Each of the one or more serving cells is associated with a specific bit of the first number of bits. The respective bits indicate whether an OD-SSB for a serving cell should be activated or deactivated. Thus, the UE 121 knows which serving cells has an OD-SSB activated and / or deactivated.

[0161] In some embodiments, the MAC CE further comprises a second bit. The second bit is indicative of whether the first number of bits further indicates an activation / deactivation status of the one or more serving cells. This may mean that, in addition to only activating OD-SSB, the first number bits further indicates whether the serving cell should be activated and / or deactivated.

[0162] In some embodiments, the MAC CE comprises a respective first field for one or more activated OD-SSBs. The respective first fields control the transmission of the activated OD-SSBs. This may e.g., mean that one or more the first field indicates, such as activates, the one or more OD-SSBs in their respective serving cell. The respective first fields may e.g., be N bits long. When combined with the first number of bits, and in some examples with the second bit, the respective first fields may e.g., be ordered in the same order as the serving cells are ordered in the first number of bits.

[0163] In some embodiments, the respective first fields comprise an index or identity. The index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations. In other words, the index or identity indicates the configuration used for an OD-SSB. The configuration may comprise one of the one or more OD-SSB configurations sent in the RRC message.

[0164] In some embodiments, the respective first fields comprise two or more subfields. A first subfield may comprise an OD-SSB subfield. The OD-SSB subfield may e.g., indicate an index or identity indicating an OD-SSB configuration of the one or more received OD- SSB configurations. A one or more second subfields may e.g., comprise a respective parameter subfield. A parameter subfield may e.g., indicate a parameter value of a parameter in the indicated OD-SSB configuration. Thus, a first field may comprise a number of subfields, where one subfield, the OD-SSB subfield, indicates the OD-SSB configuration, while the one or more second subfields indicate parameter values to use for specific parameters in the OD-SSB configuration. This may e.g., comprise a change of an already used parameter or an initial selection of a parameter value. The parameter values may e.g., be selected from a list of possible parameter values.

[0165] In some embodiments, receiving the message comprising the MAC CE comprises receiving separate MAC CE for each activated / deactivated OD-SSB, or for each OD-SSB which configuration is changed. The respective separate MAC CE comprises a cell identity field and an OD-SSB field. The cell identity field comprises an identity or index indicating a serving cell. The OD-SSB field comprises an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations. A changed configuration may e.g., comprise indicating another OD-SSB configuration of the one or more OD-SSB configuration sent in the RRC message. Alternatively, or additionally, a changed configuration may e.g., comprise changed or updated parameter value for a parameter in an OD-SSB configuration.

[0166] In some embodiments, the respective separate MAC CE further comprises a parameter field indicating a parameter value of a parameter in the indicated OD-SSB configuration. This may e.g., comprise a change of an already used parameter or an initial selection of a parameter value. The parameter values may e.g., be selected from a list of possible parameter values.

[0167] In some embodiments, receiving the message comprising the MAC CE comprises receiving separate MAC CEs for OD-SSB activation / deactivation and OD-SSB configuration. This may e.g., mean that one MAC CE activates and / or deactivates OD- SSBs and / or serving cells and another MAC CE configures the OB-SSBs, e.g., as described above.

[0168] In some embodiments, receiving the message comprising the MAC CE further comprises receiving an indication indicating a Transmission Configuration Indicator, TCI, state for activated OD-SSBs in the one or more serving cells.

[0169] In some embodiments, receiving the message comprising the MAC CE further comprises receiving an indication indicating a set of candidate OS-SSBs. Embodiments herein such as the embodiments mentioned above will now be further described and exemplified. The text below is applicable to embodiments herein and may be combined with any suitable embodiment described above.

[0170] Any of the methods, solutions, embodiments and examples described below may be combined with each other and with the methods and embodiments described above, as a whole or in parts.

[0171] Examples of embodiments herein may e.g., enable the network, such as the network node 110 to configure one or more of time- / frequency- / spatial- / power domain transmission characteristics for OD-SSB transmission for one or more serving cells. Through this method, the network may for example deploy SCells which initially have no always-on SSB transmissions on them, or alternately only provide always-on SSBs at a low rate, e.g., once every 160ms instead of the typical 20ms period. When seen as needed by the network, it may activate SSBs on-demand at a higher rate during a period on one or more beams of the SCells. A set of parameters related to transmission characteristics of OD-SSBs are first configured via RRC, see e.g., Table 1 above. As seen in Table 1 above, there could be multiple options configured per parameter. Furthermore, the configuration could be different for the different serving cells. Once configured, the network may, through one of the proposed MAC-CE options herein, inform the UE, such as the UE 121 , about availability and transmission scheme of OD-SSBs on one or more serving cells. This may e.g., be done by the MAC-CE pointing out the relevant serving cell(s) and the applicable OD-SSB transmission pattern / characteristics transmitted to the UE 121 earlier via the RRC configuration. In general, the type of parameters that may be dynamically configured through said MAC-CE are exemplified in Table 2 above.

[0172] According to some examples of embodiments herein, there is only one OD-SSB configuration provided per SCell, such as serving cell, via RRC. Alternatively, or additionally, one or more common OD-SSB configurations are provided for all of the SCells. Alternatively, or additionally, one or more common OD_SSB configurations are provided for a subset of the SCells, where different subsets may have different one or more common OD-SSB configurations. This may e.g., mean that there is no list of parameters, with different options, e.g., no list of periodicities to choose among, instead a single entry per parameter exemplified in Table 1 above. Then a MAC-CE design is used which has a bit for each configured SCell and it uses 1 — X octets for that, where X is an integer. In the example shown in Figure 7, there are 4 octets used for indicating for one or more of the individual SCells which the OD-SSB is activated or deactivated. In one variant, each “C” bit informs the status of the OD-SSB by value 0:deactivated and value 1 :active. This would be irrespective to SCell activation status which can be given to the UE with a legacy SCell activation / deactivation MAC CE, thus OD-SSB can be activated or deactivated for an SCell which is either active or deactivated.

[0173] According to some examples of embodiments herein, the “R” field is used to indicate if the “C” field, in addition to activating and deactivating the OD-SSB, also gives the SCell activated / deactivated status.

[0174] According to some examples of embodiments herein, the MAC-CE includes a field, such as the first field, for each activated OD-SSB instead of using the “C” bits. This new field for OD-SSB may be N bits long. In one example, the field per OD-SSB is 4 bits long, as shown in Figure 8a, which means each octet is used to control two OD-SSB transmission. In another example, the field is 8 bits, as shown in Figure 8b, which means the MAC-CE may control one OD-SSBs per octet. Further examples of how these fields may be used or further divided into subfields are described in subsequent examples.

[0175] According to some examples of embodiments herein, each OD-SSB field, e.g., 4 or 8 bits, points to an index or an identity of RRC configured OD-SSB. For example, the corresponding RRC configuration of an OD-SSB may entail a set configuration options for the same OD-SSB. For example, same Absolute Radio Frequency Channel Number (ARFCN), i.e., frequency resource, may be used but with different periodicities / offsets or different SSB position in burst, or alike. With the 4-bit example, potentially 16 different configuration variations can then be pointed out. In some examples, one or more values may be reserved for a special purpose. For example, the bits 0000 in this example may then mean that the OD-SSB is deactivated for an SCell, while the other bit combinations point out the RRC OD-SSB configurations to be activated.

[0176] According to some examples of embodiments herein, the field, such as the first field, is divided into subfields as shown in Figure 8c. A first subfield, such as the OD-SSB subfield, is similar to the one described above, and then there are one or more other subfields, such as the one or more parameter subfields, that control one particular parameter for the same configurations pointed in the first subfield. For example, the first subfield may give the base configuration, and the second subfield may change e.g. the periodicity, or the SSB position in the burst. There could also be the TCI state indication, in addition or instead of SSB position in burst.

[0177] The above examples, which have OD-SSB field, and / or a specific field for a parameter for a given OD-SSB always contain respective fields for each serving cell UE is configured with. Another option is to combine the examples with the C fields, and one of examples with the fields described above. There the C field is used to indicate for which serving cells the rest of the fields are included in the transmitted MAC CE.

[0178] According to some examples of embodiments herein, there is MAC CE for each SCell for which OD-SSB is activated / deactivated, or the configuration is changed as exemplified below. For example, the MAC-CE field includes the SCell Identity and / or Index with certain number of bits. Additionally, for that SCell the OD-SSB field may then point to a preconfigured set of RRC parameters, such as an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations. In the example shown in Figure 9a, an activation / deactivation bit (0 / 1) is included for informing the UE 121 about the status of the OD-SSB provision. While in another example, the A / D bit is not necessary there or could be reserved and instead as in an embodiment above a code-point in the OD-SSB, e.g., 00, indicates deactivation.

[0179] According to some examples of embodiments herein, additionally one or more parameters may be specifically controlled via the MAC-CE, e.g., by a parameter field, as shown in Figure 9b. For example, the MAC-CE may additionally control the ssb- PositionsInBurst for that SCell. There could also be the TCI state indication, in addition or instead of SSB position in burst.

[0180] According to some examples of embodiments herein, different / separate MAC CEs are used for on-demand SSB activation / deactivation and on-demand SSB configuration indication / adaptation.

[0181] According to some examples of embodiments herein, if UE 121 receives a first MAC CE indicating one of a number of candidate on-demand SSB configurations prior to, or at the same time as, receiving a second MAC CE indicating on-demand SSB activation, then UE 121 assumes that on-demand SSB is transmitted according to the OD-SSB configuration indicated by the first MAC CE.

[0182] According to some examples of embodiments herein, if UE 121 receives a second MAC CE indicating on-demand SSB activation prior to receiving a first MAC CE indicating one of a number of candidate OD-SSB configurations, then UE 121 assumes a default OD-SSB configuration.

[0183] According to some examples of embodiments herein, the default OD-SSB configuration is a predetermined one of the OD-SSB configurations. E.g., if each of the candidate OD-SSB configurations are associated with a unique index, then the default on- demand SSB configuration is the candidate OD-SSB configuration with the lowest index. According to some examples of embodiments herein, the default OD-SSB configuration is a predetermined / specified OD-SSB configurations. E.g., the default SSB periodicity is 20 ms, unless otherwise configured and / or indicated.

[0184] M AC-based TCI indication

[0185] According to some examples of embodiments herein, the network, such as the network node 110, may explicitly indicate the TCI state of the activated OD-SSB. Such TCI state may be indicated either separately or together with OD-SSB indication.

[0186] According to some examples of embodiments herein, the network may explicitly indicate the TCI state of the activated OD-SSBs for multiple OD-SSB Serving Cells. If the indicated OD-SSB Serving Cell is configured as part of a simultaneousTCI-UpdateList, this MAC CE applies to all the Serving Cells.

[0187] According to some examples of embodiments herein, if no TCI indication, the UE 121 assumes that the activated OD-SSB is QCLed to the always-on SSB.

[0188] According to some examples of embodiments herein, if no TCI indication, the UE 121 assumes that the activated OD-SSB is QCLed, including timing / frequency and / or spatial domain QCL relation, to the always-on SSB if the OD-ssb-PositionsInBurst has the same SSB index as the ssb-PositionsInBurst for always-on SSB.

[0189] According to some examples of embodiments herein, if no TCI indication, the UE 121 assumes that the OD-SSB being activated has the same spatial relation to the previous deactivated OD-SSB.

[0190] According to some examples of embodiments herein, if no TCI indication, the UE 121 assumes that the OD-SSB being activated has the same spatial relation to the previous deactivated OD-SSB if the OD-ssb-PositionsInBurst has the same SSB index as the previous deactivated OD-SSB.

[0191] According to some examples of embodiments herein, if no explicit TCI indication, the UE 121 assumes no prior timing / frequency / spatial domain information to the activated OD-SSB. UE will perform beam sweeping to obtain the best beam pair based on the indicated OD-ssb-PositionsInBurst.

[0192] The QCL relation here includes both timing / frequency domain(QCL Type-C) and / or spatial domain(QCL Type-D) QCL relation.

[0193] Candidate OD-SSB set

[0194] According to some examples of embodiments herein, the network, such as the network node 110 may indicate a set of multiple OD-SSBs as a candidate OD-SSB set to UE 121 together with the activated OD-SSB by MAC-CE. This may mean that the UE 121 needs to monitor the related timing / frequency / spatial information within the candidate OD- SSB set. If the network activates an OD-SSB within such as candidate OD-SSB set, the UE 121 follows a fast OD-SSB activation. Otherwise, the UE 121follows a slow OD-SSB activation.

[0195] 1 Introduction

[0196] In RAN#105, the WID for network energy savings in Rel-19 was revised 0. The first objective concerns the on-demand SSB SCell operation, as shown below.

[0197] The list of RAN1 agreements is available in the Appendix.

[0198] 2 Configuration and signalling aspects

[0199] This contribution focuses on the first objective highlighted in the above WID. In particular, the contribution addresses the aspects concerning the configuration, signaling, and activation / deactivation of on-demand SSB transmissions on SCells. According to the WID, the UE is in connected mode and configured with CA and, hence, it is configured with a PCell and one or more SCell(s). Note that the PCell is always activated and not dormant. The SCell(s) can be activated and dormant / not dormant, or deactivated.

[0200] 2.1 MAC CE for on-demand SSB

[0201] RAN1 has sent RAN2 LS on the MAC CE aspects with the following content:

[0202] RAN1 has discussed signaling mechanisms to indicate on-demand SSB transmission and has reached agreements to support indication by both RRC and MAC CE signaling. Agreement (RAN 1 #118)

[0203] For a cell supporting on-demand SSB SCell operation,

[0204] • Support RRC based signaling to indicate on-demand SSB transmission on the cell at least for the case where this RRC also configures the SCell, activates the SCell, and provides on-demand SSB configuration. o FFS: Whether to support RRC based signaling for other cases.

[0205] • Support MAC CE based signaling to indicate on-demand SSB transmission on the cell for Scenarios #2 and #2A.

[0206] Note: Deactivation and adaptation of on-demand SSB transmission can be separately discussed.

[0207] Agreement (RAN 1 #118)

[0208] For a cell supporting on-demand SSB SCell operation, at least for the following parameter(s), multiple candidate values can be configured by RRC and the applicable value can be indicated by MAC CE for on-demand SSB transmission indication for the cell.

[0209] • Periodicity of the on-demand SSB

[0210] • FFS: Any other relevant parameters

[0211] Agreement (RAN1#116bis)

[0212] For a cell supporting on-demand SSB SCell operation, further study the following options.

[0213] • Option 1: Separate signaling between legacy / existing signaling (e.g., RRC, MAC CE) providing SCell activation / deactivation and signaling providing On-demand SSB transmission indication.

[0214] • Option 2: A single signaling in which both SCell activation / deactivation and On- demand SSB transmission indication are provided. o FFS: Details of the signaling

[0215] • Other options are not precluded.

[0216] • FFS: Details on On-demand SSB transmission indication

[0217] To provide more context for RAN2, the following are relevant RAN1 agreements on Cases and Scenarios for on-demand SSB SCell operation.

[0218] Agreement (RAN 1 #116) Regarding the UE assumption on SSB transmission on a cell supporting on-demand SSB SCell operation, the following cases are identified for further study:

[0219] • Case #1 : No always-on SSB on the cell

[0220] • Case #2: Always-on SSB is periodically transmitted on the cell

[0221] • FFS: Whether always-on SSB and on-demand SSB are not cell-defining SSB if transmitted.

[0222] FFS: Which scenario the above applies for

[0223] Agreement (RAN 1 #116)

[0224] For the following identified scenarios for on-demand SSB SCell operation, focus future RAN1 discussion to down-select (both may be selected) between the two scenarios.

[0225] • Scenario #2: SCell is configured to a UE but before the UE receives SCell activation command (e.g., as defined in TS 38.321)

[0226] • Scenario #3: After UE receives SCell activation command (e.g., as defined in TS 38.321) o This does not preclude SCell for which activation is completed o FFS: The case where SCell activation is completed

[0227] FFS: Application timing between NW triggering message and on demand SSB transmission

[0228] Agreement (RAN1#116bis)

[0229] For the identified scenarios and cases (as per RAN1#116 agreement), on-demand

[0230] SSB can be triggered by gNB at least for the following scenarios / cases:

[0231] Scenario #2 and Case #1

[0232] Scenario #2 and Case #2

[0233] Scenario #2A and Case #1

[0234] Scenario #2A and Case #2

[0235] FFS: Scenario #3A and Case #1

[0236] FFS: Scenario #3A and Case #2

[0237] FFS: Scenario #3B and Case #1

[0238] FFS: Scenario #3B and Case #2

[0239] For Case #1 , once on-demand SSB is triggered, its transmission is in a periodic manner. o Note: This does not imply periodic on-demand SSB is transmitted indefinitely after triggered.

[0240] • Notes: o Scenario #2A refers to

[0241] ■ “When UE receives SCell activation command (e.g., as defined in TS 38.321)” o Scenario #3A refers to

[0242] ■ “After UE receives SCell activation command (e.g., as defined in TS 38.321) until SCell activation is completed” o Scenario #3B refers to

[0243] ■ “When SCell activation is completed and SCell is activated” or

[0244] ■ “After SCell activation is completed and SCell is activated” o For discussion purpose under Al 9.5.1 , always-on SSB is SSB supported in Rel-18 specifications. o Timing for on-demand SSB transmission (e.g. when the triggered SSB starts and ends) will be separately discussed.

[0245] RAN1 respectfully requests RAN2 to design MAC CE based signaling to indicate on-demand SSB transmission for Scenarios #2 and #2A.

[0246] RAN1 is working on the further details needed for RRC and MAC CE based signaling to indicate on-demand SSB transmission and will inform RAN2 as further agreements are made.

[0247] In the context of the MAC CE, RAN2 made the following agreements:

[0248] • Scenarios on OD-SSB: o RAN2 start the discussion from Scenario 2 / 2A and wait for RAN1 conclusion on Scenario 3A / 3B.

[0249] • OD-SSB transmission indication: o RRC based OD-SSB transmission indication is used to indicate at least the initial activation / deactivation state of OD-SSB configuration. FFS on reconfiguration. o New MAC-CE for OD-SSB transmission indication is introduced. We will not change legacy SCell activation / deactivation MAC CE. FFS if we need further optimization for scenario 2A. RAN1 has asked RAN2 to design the MAC CE based signalling to indicate on- demand SSB transmission for #2 and #2A. The RAN1 agreements with relevant content as input for the design are:

[0250] Agreement (RAN 1 #118)

[0251] For a cell supporting on-demand SSB SCell operation, at least for the following parameter(s), multiple candidate values can be configured by RRC and the applicable value can be indicated by MAC CE for on-demand SSB transmission indication for the cell.

[0252] • Periodicity of the on-demand SSB

[0253] • FFS: Any other relevant parameters

[0254] Seems that RAN1 would like to see separate handle for each value of the OnDemand SSB configuration and has agreed that at least the periodicity is one such parameter. This type of design means that there is a separate field in the MAC CE for each RRC parameter of the on-demand SSB configuration. However, since the only parameter indicated so far is periodicity it is difficult to assess if this type of design is feasible or not. Another type of design would be that there are N amount of OnDemand SSB configurations, configured via RRC signalling, with different parameter values and the MAC CE points out one of the configurations to be activated / deactivated. Yet another option is to have M “base configurations” configured by RRC and a few separate parameters to be selected / configured directly by the MAC CE. Further, The MAC CE may activate OnDemand SSB, and / or indicate specific parameters for it, per SCell, or for a list of SCells. Which way to design the MAC CE depends on the complexity needed for each activated OnDemand SSB. Our preference would be to aim to simple MAC CE where control of all OnDemand SSBs of all SCells could be indicated in one MAC CE.

[0255] Observation 1 For now, RAN1 has concluded on only one OnDemand SSB related configuration parameter, OnDemand SSB periodicity.

[0256] Observation 1 Depending on the number of individual parameters related to OnDemand SSB configuration, it may not be feasible to separately control each of those in a MAC CE.

[0257] Proposal 1 RAN2 should aim for a MAC CE where control of all OnDemand SSBs of all SCells could be indicated in one MAC CE. Proposal 2 Wait for RAN1 to progress with OnDemand SSB design before discussing the MAC CE details further.

[0258] 2.2 RRC configuration for OnDemand SSB

[0259] Concerning the configuration aspects, the discussion in RAN1#117 meeting concluded with the following agreements:

[0260] Agreement

[0261] • For a cell supporting on-demand SSB SCell operation, at least the following for on-demand SSB via higher layer RRC signaling is supported. o Frequency of the on-demand SSB o SSB positions within an on-demand SSB burst by using signaling similar to ssb-Positions / nBurst o Periodicity of the on-demand SSB o FFS: Whether more than one on-demand SSB configurations can be configured for the cell to UE o FFS: Whether the RRC is newly introduced or existing RRC is reused

[0262] As highlighted in the agreement above, one of the possible solutions is that the network provides the UE with different options for the OnDemand SSB transmission patterns by an RRC configuration. These options for the SSB transmission patterns could be given outside of the SCell configuration since we think that the SSB patterns can be commonly configured for several SCells. Furthermore, to support additional flexibility, the configurations could be different for FR1 and FR2. In this way, configurations for FR1 and FR2 would be shared among serving cells operating on FR1 and FR2, respectively. It is important to note that while the options for the SSB transmission patterns would be per FR, the activation of a certain SSB transmission pattern could be different for different SCells. This way of configuring on-demand SSB per FR requires fewer bits compared to, for example, configuring OnDemand SSB per SCell. Additionally, we think that FR1 and FR2 have different characteristics (e.g., number of potential beams employed in each FR, SCS) and as such this scheme allows for more flexibility than, for example, configuring the same OnDemand SSB for both FR1 and FR2. For example, as the maximum number of beams is different in FR1 and FR2, the potential number of deployed OnDemand SSB beams would vary. This could lead to different periodicities and therefore different starting point / offsets for the OnDemand SSBs. Therefore, configuring OnDemand SSB per FR can be seen as a solution that is compact while still provides a reasonable level of flexibility.

[0263] Proposal 3 Define OnDemand SSB configuration per FR which is applicable for all SCells in that FR.

[0264] 3 L3 measurements

[0265] RAN2 agreements are:

[0266] • Measurement on OD-SSB: o Measurement based on OD-SSB in both case 1 and case 2 will be considered, (case 1 and case 2 defined in RAN1). o For Case #1, the UE does not expect to measure SSB when on-demand SSB transmission is deactivated. In other words, the UE expects to measure SSB when on-demand SSB transmission is activated. o RAN2 does not handle the issue raised in R2-2407414 in OD-SSB based measurements.

[0267] R2-2407414: Proposal 3: RAN2 WG to discuss the issue of false measurement report triggering due to no SSB transmission when on-demand SSB is deactivated.

[0268] ■=> RAN2 does not handle this issue in OD-SSB

[0269] • RAN2 study how the UE to perform L3 measurement according to OD-SSB L3 RRM configuration.

[0270] Via its serving cell configuration the UE has the configuration for OnDemand SSB, and receives the MAC CE for activation of the OnDemand SSB reception. Since the UE has this information, it is not evident any enhancement is needed for L3 RRM configuration.

[0271] Current RAN1 agreement on this always on and OnDemand SSB is as follows:

[0272] RAN1 #116bis Agreement

[0273] • For a cell supporting on-demand SSB SCell operation, o Note: It is up to gNB implementation whether always-on SSB (if transmitted) on the cell is cell-defining SSB or not. o For on-demand SSB on the cell, downselect between the following alternatives ■ Alt-1: It is up to gNB implementation whether on-demand SSB is cell-defining SSB or not.

[0274] ■ Alt-2: On-demand SSB is limited to non-cell-defining SSB.

[0275] • FFS: Further limitations to on-demand SSB

[0276] RAN1 #118 Agreement

[0277] • For a cell supporting on-demand SSB SCell operation, at least the following is supported o On-demand SSB on the cell is not located on synchronization raster, o On-demand SSB on the cell is non-cell-defining SSB

[0278] • FFS: Additional support of OD-SSB for CD-SSB located on sync-raster

[0279] As can be seen the discussion is not finished. Further aspect is whether these different SSBs are on same channel raster or not. Since especially this frequency aspect is open, it is premature to try to conclude on this matter in RAN2:

[0280] Proposal 4 RAN2 to wait for RAN1 / RAN4 to progress on the design for

[0281] OnDemand SSB

[0282] 4 Conclusion

[0283] In this contribution we discuss the second objective highlighted in the WID. Based on the discussion in the previous sections we made the following observations:

[0284] Observation 1 For now, RAN1 has concluded on only one OnDemand

[0285] SSB related configuration parameter, OnDemand SSB periodicity.

[0286] Observation 2 Depending on the number of individual parameters related to OnDemand SSB configuration, it may not be feasible to separately control each of those in a MAC CE.

[0287] Based on the discussion in the previous sections we propose the following:

[0288] Proposal 1 RAN2 should aim for a MAC CE where control of all

[0289] OnDemand SSBs of all SCells could be indicated in one MAC CE. Proposal 2 Wait for RAN1 to progress with OnDemand SSB design before discussing the MAC CE details further.

[0290] Proposal 3 Define OnDemand SSB configuration per FR which is applicable for all SCells in that FR.

[0291] Proposal 4 RAN2 to wait for RAN1 / RAN4 to progress on the design for OnDemand SSB

[0292] References

[0293] RP-242354, “ Revised WID: Enhancements of network energy savings for NR”, RAN#105, October 2024.

[0294] Appendix

[0295] RAN 1 #116 Agreements

[0296] Agreement

[0297] Regarding the UE assumption on SSB transmission on a cell supporting on-demand SSB SCell operation, the following cases are identified for further study:

[0298] • Case #1 : No always-on SSB on the cell

[0299] • Case #2: Always-on SSB is periodically transmitted on the cell

[0300] • FFS: Whether always-on SSB and on-demand SSB are not cell-defining SSB if transmitted.

[0301] FFS: Which scenario the above applies for

[0302] Agreement

[0303] RAN1 to strive for a common design for on-demand SSB operation considering all applicable CA configurations.

[0304] Agreement

[0305] For the following identified scenarios for on-demand SSB SCell operation, focus future RAN1 discussion to down-select (both may be selected) between the two scenarios.

[0306] Scenario #2: SCell is configured to a UE but before the UE receives SCell activation command (e.g., as defined in TS 38.321) • Scenario #3: After UE receives SCell activation command (e.g., as defined in TS 38.321) o This does not preclude SCell for which activation is completed o FFS: The case where SCell activation is completed

[0307] FFS: Application timing between NW triggering message and on demand SSB transmission

[0308] Agreement

[0309] Support on-demand SSB SCell operation triggered by gNB.

[0310] FFS Details of associated signaling / indication / configuration provided to UE

[0311] Agreement

[0312] • For SSB burst(s) triggered by on-demand SSB SCell operation, study at least the following options. o Option 1: UE expects that on-demand SSB burst(s) is periodically transmitted from time instance A. o Option 1A: UE expects that on-demand SSB burst(s) is periodically transmitted from time instance A until gNB turns OFF the on demand SSB o Option 2: UE expects that on-demand SSB burst(s) is transmitted from time instance A to time instance B and not transmitted after time instance B. o Option 3: UE expects that on-demand SSB burst(s) is transmitted N times after time instance A and not transmitted after N on-demand SSB bursts are transmitted. o Option 4: UE expects that on-demand SSB burst(s) is transmitted with a periodicity from time instance A to time instance B and with the other periodicity after time instance B. o FFS: The combination of above options o FFS: How to define time instance A / B and the value of N per option o FFS: Each option is applicable to which Cases or Scenarios (as per the previous agreement)

[0313] RAN1#116bis Agreements

[0314] Agreement

[0315] For the identified scenarios and cases (as per RAN1#116 agreement), on-demand SSB can be triggered by gNB at least for the following scenarios / cases: Scenario #2 and Case #1

[0316] Scenario #2 and Case #2

[0317] Scenario #2A and Case #1

[0318] Scenario #2A and Case #2

[0319] FFS: Scenario #3A and Case #1

[0320] FFS: Scenario #3A and Case #2

[0321] FFS: Scenario #3B and Case #1

[0322] FFS: Scenario #3B and Case #2

[0323] For Case #1 , once on-demand SSB is triggered, its transmission is in a periodic manner. o Note: This does not imply periodic on-demand SSB is transmitted indefinitely after triggered.

[0324] • Notes: o Scenario #2A refers to

[0325] ■ “When UE receives SCell activation command (e.g., as defined in TS 38.321)” o Scenario #3A refers to

[0326] ■ “After UE receives SCell activation command (e.g., as defined in TS 38.321) until SCell activation is completed” o Scenario #3B refers to

[0327] ■ “When SCell activation is completed and SCell is activated” or

[0328] ■ “After SCell activation is completed and SCell is activated” o For discussion purpose under Al 9.5.1, always-on SSB is SSB supported in Rel-18 specifications. o Timing for on-demand SSB transmission (e.g. when the triggered SSB starts and ends) will be separately discussed.

[0329] Agreement

[0330] • For a cell supporting on-demand SSB SCell operation, o Note: It is up to gNB implementation whether always-on SSB (if transmitted) on the cell is cell-defining SSB or not. o For on-demand SSB on the cell, downselect between the following alternatives

[0331] Alt-1: It is up to gNB implementation whether on-demand SSB is cell-defining SSB or not. ■ Alt-2: On-demand SSB is limited to non-cell-defining SSB.

[0332] • FFS: Further limitations to on-demand SSB

[0333] Agreement

[0334] • For a cell supporting on-demand SSB SCell operation, o L1 and / or L3 measurement based on on-demand SSB is supported for the cell.

[0335] ■ FFS further details on L1 and / or L3 measurement

[0336] Agreement

[0337] The following agreement from RAN1#116 is modified (in red)

[0338] • For SSB burst(s) indicated by on-demand SSB SCell operation, study at least the following options. o Option 1: UE expects that on-demand SSB burst(s) is periodically transmitted from time instance A. o Option 1A: UE expects that on-demand SSB burst(s) is periodically transmitted from time instance A until gNB turns OFF the on demand SSB o Option 2: UE expects that on-demand SSB burst(s) is transmitted from time instance A to time instance B and not transmitted after time instance B. o Option 3: UE expects that on-demand SSB burst(s) is transmitted N times after time instance A and not transmitted after N on-demand SSB bursts are transmitted. o Option 4: UE expects that on-demand SSB burst(s) is transmitted with a periodicity from time instance A to time instance B and with the other periodicity after time instance B. o FFS: The combination of above options o FFS: How to define time instance A / B and the value of N per option o FFS: Each option is applicable to which Cases or Scenarios (as per the previous agreement)

[0339] Agreement

[0340] For a cell supporting on-demand SSB SCell operation, further study the following options. • Option 1: Separate signaling between legacy / existing signaling (e.g., RRC, MAC CE) providing SCell activation / deactivation and signaling providing On-demand SSB transmission indication.

[0341] • Option 2: A single signaling in which both SCell activation / deactivation and On- demand SSB transmission indication are provided. o FFS: Details of the signaling

[0342] • Other options are not precluded.

[0343] • FFS: Details on On-demand SSB transmission indication

[0344] RAN 1 #117 Agreements

[0345] Agreement

[0346] • For a cell supporting on-demand SSB SCell operation, o Support RRC based signaling to indicate on-demand SSB transmission on the cell. o Support MAC CE based signaling to indicate on-demand SSB transmission on the cell. o FFS: Whether to support DCI based signaling to indicate on-demand SSB transmission on the cell.

[0347] ■ This DCI signaling does not provide SCell activation / deactivation.

[0348] ■ If supported, details on DCI including UE-specific or group- common DCI, DCI contents, etc. o FFS: Scenarios where the above signalings are applicable

[0349] Agreement

[0350] • For a cell supporting on-demand SSB SCell operation, at least the following for on-demand SSB via higher layer RRC signaling is supported. o Frequency of the on-demand SSB o SSB positions within an on-demand SSB burst by using signaling similar to ssb-Positions / nBurst o Periodicity of the on-demand SSB o FFS: Whether more than one on-demand SSB configurations can be configured for the cell to UE o FFS: Whether the RRC is newly introduced or existing RRC is reused

[0351] Agreement • At least support L1 measurement based on on-demand SSB o For L1 measurement based on on-demand SSB, periodic, semi- persistent, [and aperiodic] L1 measurement reports based on existing CSI framework are supported.

[0352] ■ FFS on potential enhancements of CSI report configuration and / or triggering / activation mechanisms for L1 measurement based on on-demand SSB

[0353] Agreement

[0354] For SSB burst(s) indicated by on-demand SSB SCell operation via MAC CE, UE expects that on-demand SSB burst(s) is transmitted from time instance A which is determined as follows.

[0355] • Alt 3-1 : Time instance A is [the slot boundary of] the first SSB time domain position [of actually transmitted on-demand SSB burst] which is T [slots or symbols] after the [slot or symbol] where UE receives a signalling from gNB to indicate on-demand SSB transmission o The SSB time domain positions of on-demand SSB burst are configured by gNB.

[0356] • FFS: Details of the value of T (> 0) including possibility of T comprising of multiple components

[0357] • Note: The value of T is not less than existing timeline required for UE’s MAC CE processing for SCell activation

[0358] • FFS: Whether the value of T is predefined or indicated / configured by gNB

[0359] • FFS: Details of “the [slot or symbol] where UE receives a signalling from gNB” or “the [slot or symbol] where UE transmits HARQ-ACK corresponding to a signalling from gNB to trigger on-demand SSB”

[0360] Above applies at least for the case where SCell with on demand SSB transmission and cell with signalling transmission have the same numerology.

[0361] Agreement

[0362] • For a cell supporting on-demand SSB SCell operation, at least the followings for on-demand SSB are known to UE. o Sub-carrier spacing of the on-demand SSB o Physical Cell ID of the on-demand SSB o Location of on-demand SSB burst o Downlink transmit power of on-demand SSB o FFS: Other parameters o FFS: Whether each of above parameters is configured / indicated explicitly or not

[0363] RAN 1 #118 Agreements

[0364] Agreement

[0365] • Update the previous RAN1 agreement as follows. o At least support L1 measurement based on on-demand SSB

[0366] ■ For L1 measurement based on on-demand SSB, periodic, semi- persistent, [and aperiodic] L1 measurement reports based on existing CSI framework are supported.

[0367] • FFS on potential enhancements of CSI report configuration and / or triggering / activation mechanisms for L1 measurement based on on-demand SSB

[0368] • The support of LTM is a separate discussion point

[0369] Agreement

[0370] For a cell supporting on-demand SSB SCell operation,

[0371] • Support RRC based signaling to indicate on-demand SSB transmission on the cell at least for the case where this RRC also configures the SCell, activates the SCell, and provides on-demand SSB configuration. o FFS: Whether to support RRC based signaling for other cases.

[0372] • Support MAC CE based signaling to indicate on-demand SSB transmission on the cell for Scenarios #2 and #2A.

[0373] Note: Deactivation and adaptation of on-demand SSB transmission can be separately discussed.

[0374] Agreement

[0375] For a cell supporting on-demand SSB SCell operation, at least for the following parameter(s), multiple candidate values can be configured by RRC and the applicable value can be indicated by MAC CE for on-demand SSB transmission indication for the cell.

[0376] Periodicity of the on-demand SSB FFS: Any other relevant parameters

[0377] Agreement For a cell supporting on-demand SSB SCell operation, at least the following is supported

[0378] • On-demand SSB on the cell is not located on synchronization raster.

[0379] • On-demand SSB on the cell is non-cell-defining SSB

[0380] FFS: Additional support of OD-SSB for CD-SSB located on sync-raster

[0381] Agreement

[0382] Support L3 measurement based on on-demand SSB

[0383] • Further work on L3 measurement is up to RAN2 / RAN4

[0384] Agreement

[0385] LS to RAN2 for on-demand SSB SCell operation is agreed. Final LS in R1 -2407438.

[0386] Agreement

[0387] The previous RAN1 agreement made in RAN1#117 is revised as follows.

[0388] • For SSB burst(s) indicated by on-demand SSB SCell operation via MAC CE, UE expects that on-demand SSB burst(s) is transmitted from time instance A which is determined as follows. o Alt 3-1 : Time instance A is the beginning of the first slot containing [candidate SSB index 0 or the first actually transmitted SSB index] of on- demand SSB burst [the slot boundary of] the first SSB time domain position [of actually transmitted on-demand SSB burst] which is at least T [slots or symbols] after the [slot or symbol] where UE receives a signalling from gNB to indicate on-demand SSB transmission

[0389] ■ The SSB time domain positions of on-demand SSB burst are configured by gNB. e — FFS: Details of the value of T (> 0) including possibility of T comprising of multiple components o Note: The value of T is not less than existing timeline required for UE’s MAC CE processing for SCell activation o (Working assumption): T is not less than T_min=m + 2N^frame'll+'\ where slot n+m is a slot indicated for PUCCH transmission with HARQ- QCK information when the UE receives MAC CE signaling to indicate on- demand SSB transmission ending in slot n, JS asjgfj gj in current specification. RAN4 to confirm that T_min can be equal t e — FFS: Whether the value of T is predefined or indicated / configured by nNR o (Working assumption) T=T_min e — FFS: Details of “the [slot or symbol] where UE receives a signalling from gNB” or “the [slot or symbol] where UE transmits HARQ-ACK corresponding to a signalling from gNB to trigger on-demand SSB”

[0390] • Above applies at least for the case where SCell with on demand SSB transmission and cell with signalling transmission have the same numerology.

[0391] Agreement

[0392] LS on timeline for On-demand SSB operation on SCell is agreed in R1 -2407565.

[0393] To perform the method actions above, the network node 110 is e.g., configured to handle SSB signaling in the wireless communication network 100. The network node 110 may comprise an arrangement depicted in Figure 10.

[0394] The network node 110 may comprise an input and output interface 1000 configured to communicate with each other. The input and output interface 1000 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0395] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 1010 of a processing circuitry in the network node 110 depicted in Figure 10, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the network node 110. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the network node 110.

[0396] The network node 110 and / or processor 1010 is e.g., configured to handle SSB signaling in the wireless communication network 100.

[0397] The network node 110 and / or processor 1010 is e.g., configured to send an RRC message to the UE 121. The RRC message is adapted to comprise one or more configurations for OD-SSB in one or more serving cells. The network node 110 and / or processor 1010 is e.g., configured to send a message to the UE (121). The message is adapted to comprise a MAC CE controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

[0398] In some embodiments, the one or more OD-SSB configurations are adapted to comprise any one or more out of:

[0399] - one or more OD-SSB configurations per serving cell,

[0400] - one or more common OD-SSB configurations for all of the one or more serving cells, and

[0401] - one or more common OD-SSB configurations for a subset of the one or more serving cells.

[0402] In some embodiments, the MAC CE is adapted to comprise a first number of bits, wherein each of the one or more serving cells is adapted to be associated with a specific bit of the first number of bits, and wherein the respective bits is adapted to indicate whether an OD-SSB for a serving cell should be activated or deactivated.

[0403] In some embodiments, the MAC CE is further adapted to comprise a second bit, which second bit is indicative of whether the first number of bits further indicates an activation / deactivation status of the one or more serving cells.

[0404] In some embodiments, the MAC CE is adapted to comprise a respective first field for one or more activated OD-SSBs, wherein the respective first fields control the transmission of the activated OD-SSBs.

[0405] In some embodiments, the respective first fields is adapted to comprise an index or identity, which index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations.

[0406] In some embodiments, the respective first fields is adapted to comprise two or more subfields, and wherein an OD-SSB subfield indicates:

[0407] - an index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations, and wherein a parameter subfield indicates:

[0408] - a parameter value of a parameter in the indicated OD-SSB configuration.

[0409] In some embodiments, the network node (110) and / or processor 1010 is configured to send the message comprising the MAC CE by sending separate MAC CE for each activated / deactivated OD-SSB, or for each OD-SSB which configuration is changed, wherein the respective separate MAC CE is adapted to comprise a cell identity field and an OD-SSB field, wherein the cell identity field comprises an identity of index indicating an serving cell, and wherein the OD-SSB field comprises an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations.

[0410] In some embodiments, the respective separate MAC CE is adapted to comprise a parameter field adapted to indicate a parameter value of a parameter in the indicated OD- SSB configuration.

[0411] In some embodiments, the network node (110) and / or processor 1010 is configured to send the message comprising the MAC CE by sending separate MAC CEs for OD-SSB activation / deactivation and OD-SSB configuration.

[0412] In some embodiments, the network node (110) and / or processor 1010 is configured to send the message comprising the MAC CE by further indicating a Transmission Configuration Indicator, TCI, state for activated OD-SSBs in the one or more serving cells.

[0413] In some embodiments, the network node (110) and / or processor 1010 is configured to send the message comprising the MAC CE by further indicating a set of candidate OS- SSBs.

[0414] The network node 110 may further comprise respective a memory 1020 comprising one or more memory units. The memory 1020 comprises instructions executable by the processor 10020 in the network node 110.

[0415] The memory 1020 is arranged to be used to store instructions, data, configurations, MAC CEs, OD-SSBs, indications, parameters, applications to perform the methods herein when being executed in the network node 110.

[0416] In some embodiments, a computer program 1030 comprises instructions, which when executed by the at least one processor 1010, cause the at least one processor 1010 of the network node 110 to perform the actions above.

[0417] In some embodiments, a respective carrier 1040 comprises the respective computer program 1030, wherein the carrier 1040 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0418] Thus, embodiments herein may disclose the network node 110 e.g., configured to handle SSB signaling in the wireless communication network 100. The network node 110 comprises the processor 1010 and the memory 1020, said memory 1020 comprising instructions executable by said processor 1010 whereby said network node 110 is operative to perform any of the methods herein.

[0419] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a base station, for example.

[0420] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and nonvolatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0421] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0422] To perform the method actions above, the UE 121 is e.g., configured to handle SSB signaling in the wireless communication network 100. The UE 121 may comprise an arrangement depicted in Figure 11. The UE 121 may comprise an input and output interface 1100 configured to communicate with each other. The input and output interface 1100 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0423] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 1110 of a processing circuitry in the UE 121 depicted in Figure 11 , together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the UE 121. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the UE 121.

[0424] The UE (121) and / or processor 1110 is e.g., configured to handle SSB signaling in the wireless communication network 100.

[0425] The UE (121) and / or processor 1110 is e.g., configured to receive a RRC message from the network node (110). The RRC message is adapted to comprise one or more configurations for OD-SSB in one or more serving cells.

[0426] The UE (121) and / or processor 1110 is e.g., configured to receive a message from the network node (110). The message is adapted to comprise a MAC CE controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

[0427] In some embodiments, the one or more OD-SSB configurations is adapted to comprise any one or more out of:

[0428] - one or more OD-SSB configurations per serving cell,

[0429] - one or more common OD-SSB configurations for all of the one or more serving cells, and

[0430] - one or more common OD-SSB configurations for a subset of the one or more serving cells.

[0431] In some embodiments, the MAC CE is adapted to comprise a first number of bits, wherein each of the one or more serving cells is adapted to be associated with a specific bit of the first number of bits, and wherein the respective bits is adapted to indicate whether an OD-SSB for a serving cell should be activated or deactivated. In some embodiments, the MAC CE is further adapted to comprise a second bit, which second bit is indicative of whether the first number of bits further indicates an activation / deactivation status of the one or more serving cells.

[0432] In some embodiments, the MAC CE is adapted to comprise a respective first field for one or more activated OD-SSBs, wherein the respective first fields control the transmission of the activated OD-SSBs.

[0433] In some embodiments, the respective first fields is adapted to comprise an index or identity, which index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations.

[0434] In some embodiments, the respective first fields is adapted to comprise two or more subfields, and wherein an OD-SSB subfield indicates:

[0435] - an index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations, and wherein a parameter subfield indicates:

[0436] - a parameter value of a parameter in the indicated OD-SSB configuration.

[0437] In some embodiments, the UE (121) and / or processor 1110 is configured to receive the message comprising the MAC CE by receiving separate MAC CE for each activated / deactivated OD-SSB, or for each OD-SSB which configuration is changed, wherein the respective separate MAC CE comprises a cell identity field and an OD-SSB field, wherein the cell identity field comprises an identity of index indicating an serving cell, and wherein the OD-SSB field comprises an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations.

[0438] In some embodiments, the respective separate MAC CE is adapted to comprise a parameter field adapted to indicate a parameter value of a parameter in the indicated OD- SSB configuration.

[0439] In some embodiments, the UE (121) and / or processor 1110 is configured to receive the message comprising the MAC CE by receiving separate MAC CEs for OD-SSB activation / deactivation and OD-SSB configuration.

[0440] In some embodiments, the UE (121) and / or processor is configured to receive the message comprising the MAC CE by further receiving an indication adapted to indicate a Transmission Configuration Indicator, TCI, state for activated OD-SSBs in the one or more serving cells.

[0441] In some embodiments, the UE (121) and / or processor is configured to receive the message comprising the MAC CE by further receiving an indication adapted to indicate a set of candidate OS-SSBs. The UE 121 may further comprise respective a memory 1120 comprising one or more memory units. The memory 1120 comprises instructions executable by the processor 1110 in the UE 121.

[0442] The memory 1120 is arranged to be used to store instructions, data, configurations, MAC CEs, OD-SSBs, indications, parameters, applications to perform the methods herein when being executed in the UE 121.

[0443] In some embodiments, a computer program 1130 comprises instructions, which when executed by the at least one processor 1110, cause the at least one processor 1110 of the UE 121 to perform the actions above.

[0444] In some embodiments, a respective carrier 1140 comprises the respective computer program 1130, wherein the carrier 1140 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0445] Thus, embodiments herein may disclose the UE 121 e.g., configured to handle SSB signaling in the wireless communication network 100. The UE 121 comprises the processor 1110 and the memory 1120, said memory 1120 comprising instructions executable by said processor 1110 whereby said UE 121 is operative to perform any of the methods herein.

[0446] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a base station, for example.

[0447] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and nonvolatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0448] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0449] Embodiments

[0450] Below, some example Embodiments 1-52 are shortly described. See e.g., Figures 5-11.

[0451] Embodiment 1. A method performed by a network node 110 e.g., for handling Synchronization Signal Block, SSB, signaling in wireless communication network 100, the method comprising any one or more out of: sending 501 a Radio Resource Control, RRC, message to a User Equipment, UE, 121, which RRC message comprises one or more configurations for On-Demand Synchronization Signal Block, OD-SSB, in one or more serving cells, sending 502 a message to the UE 121, which message comprises a Medium Access Control, MAC, Control Element, CE, controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

[0452] Embodiment 2. The method according to embodiment 1 , wherein the one or more OD-SSB configurations comprises any one or more out of: - one or more OD-SSB configurations per serving cell,

[0453] - one or more common OD-SSB configurations for all of the one or more serving cells, and

[0454] - one or more common OD-SSB configurations for a subset of the one or more serving cells.

[0455] Embodiment 3. The method according to any of embodiments 1-2, wherein the MAC CE comprises a first number of bits, wherein each of the one or more serving cells is associated with a specific bit of the first number of bits, and wherein the respective bit indicate whether an OD-SSB for a serving cell should be activated or deactivated.

[0456] Embodiment 4. The method according to embodiment 3, wherein the MAC CE further comprises a second bit, which second bit is indicative of whether the first number of bits further indicates an activation / deactivation status of the one or more serving cells.

[0457] Embodiment 5. The method according to any of embodiments 1-4, wherein the MAC CE comprises a respective first field for one or more activated OD-SSBs, wherein the respective first fields control the transmission of the activated OD-SSBs.

[0458] Embodiment 6. The method according to embodiment 5, wherein the respective first fields comprise an index or identity, which index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations.

[0459] Embodiment 7. The method according to any of embodiments 5-6, wherein the respective first fields comprise two or more subfields, and wherein an OD-SSB subfield indicates:

[0460] - an index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations, and wherein a parameter subfield indicates:

[0461] - a parameter value of a parameter in the indicated OD-SSB configuration.

[0462] Embodiment 8. The method according to any of embodiments 1-7, wherein sending the message comprising the MAC CE comprises sending separate MAC CE for each activated / deactivated OD-SSB, or for each OD-SSB which configuration is changed, wherein the respective separate MAC CE comprises a cell identity field and an OD-SSB field, wherein the cell identity field comprises an identity of index indicating an serving cell, and wherein the OD-SSB field comprises an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations.

[0463] Embodiment 9. The method according to embodiment 8, wherein the respective separate MAC CE comprises a parameter field indicating a parameter value of a parameter in the indicated OD-SSB configuration.

[0464] Embodiment 10. The method according to any of embodiments 1-9, wherein sending the message comprising the MAC CE comprises sending separate MAC CEs for OD-SSB activation / deactivation and OD-SSB configuration.

[0465] Embodiment 11. The method according to any of embodiments 1-10, wherein sending the message comprising the MAC CE further comprises indicating a Transmission Configuration Indicator, TCI, state for activated OD-SSBs in the one or more serving cells.

[0466] Embodiment 12. The method according to any of embodiments 1-11, wherein sending the message comprising the MAC CE further comprises indicating a set of candidate OS-SSBs.

[0467] Embodiment 13. A computer program 1030 comprising instructions, which when executed by a processor 1010, causes the processor 1010 to perform actions according to any of the embodiments 1-12.

[0468] Embodiment 14. A carrier 1040 comprising the computer program 1030 of embodiment 13, wherein the carrier 1040 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0469] Embodiment 15. A method performed by a User Equipment 121 e.g., for handling Synchronization Signal Block, SSB, signaling in wireless communication network 100, the method comprising any one or more out of: receiving 601 a Radio Resource Control, RRC, message from a network node 110, which RRC message comprises one or more configurations for On-Demand Synchronization Signal Block, OD-SSB, in one or more serving cells, receiving 602 a message from the network node 110, which message comprises a Medium Access Control, MAC, Control Element, CE, controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

[0470] Embodiment 16. The method according to embodiment 15, wherein the one or more OD-SSB configurations comprises any one or more out of:

[0471] - one or more OD-SSB configurations per serving cell,

[0472] - one or more common OD-SSB configurations for all of the one or more serving cells, and

[0473] - one or more common OD-SSB configurations for a subset of the one or more serving cells.

[0474] Embodiment 17. The method according to any of embodiments 15-16, wherein the MAC CE comprises a first number of bits, wherein each of the one or more serving cells is associated with a specific bit of the first number of bits, and wherein the respective bit indicates whether an OD-SSB for a serving cell should be activated or deactivated.

[0475] Embodiment 18. The method according to embodiment 17, wherein the MAC CE further comprises a second bit, which second bit is indicative of whether the first number of bits further indicates an activation / deactivation status of the one or more serving cells.

[0476] Embodiment 19. The method according to any of embodiment 15-18, wherein the MAC CE comprises a respective first field for one or more activated OD-SSBs, wherein the respective first fields control the transmission of the activated OD-SSBs.

[0477] Embodiment 20. The method according to embodiment 19, wherein the respective first fields comprise an index or identity, which index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations.

[0478] Embodiment 21. The method according to any of embodiments 19-20, wherein the respective first fields comprise two or more subfields, and wherein an OD-SSB subfield indicates: - an index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations, and wherein a parameter subfield indicates:

[0479] - a parameter value of a parameter in the indicated OD-SSB configuration.

[0480] Embodiment 22. The method according to any of embodiments 15-21, wherein receiving the message comprising the MAC CE comprises receiving separate MAC CE for each activated / deactivated OD-SSB, or for each OD-SSB which configuration is changed, wherein the respective separate MAC CE comprises a cell identity field and an OD-SSB field, wherein the cell identity field comprises an identity of index indicating an serving cell, and wherein the OD-SSB field comprises an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations.

[0481] Embodiment 23. The method according to embodiment 22, wherein the respective separate MAC CE comprises a parameter field indicating a parameter value of a parameter in the indicated OD-SSB configuration.

[0482] Embodiment 24. The method according to any of embodiments 15-23, wherein receiving the message comprising the MAC CE comprises receiving separate MAC CEs for OD-SSB activation / deactivation and OD-SSB configuration.

[0483] Embodiment 25. The method according to any of embodiments 15-24, wherein receiving the message comprising the MAC CE further comprises receiving an indication indicating a Transmission Configuration Indicator, TCI, state for activated OD-SSBs in the one or more serving cells.

[0484] Embodiment 26. The method according to any of embodiments 15-25, wherein receiving the message comprising the MAC CE further comprises receiving an indication indicating a set of candidate OS-SSBs.

[0485] Embodiment 27. A computer program 1130 comprising instructions, which when executed by a processor 1110, causes the processor 1110 to perform actions according to any of the embodiments 15-26. Embodiment 28. A carrier 1140 comprising the computer program 1130 of embodiment 27, wherein the carrier 1140 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0486] Embodiment 29. A network node 110 e.g., configured to handle Synchronization Signal Block, SSB, signaling in wireless communication network 100, the network node 110 further being configured to any one or more out of: send a Radio Resource Control, RRC, message to a User Equipment, UE, 121, which RRC message is adapted to comprise one or more configurations for On-Demand Synchronization Signal Block, OD-SSB, in one or more serving cells, send a message to the UE 121 , which message is adapted to comprise a Medium Access Control, MAC, Control Element, CE, controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

[0487] Embodiment 30. The network node 110 according to embodiment 29, wherein the one or more OD-SSB configurations are adapted to comprise any one or more out of:

[0488] - one or more OD-SSB configurations per serving cell,

[0489] - one or more common OD-SSB configurations for all of the one or more serving cells, and

[0490] - one or more common OD-SSB configurations for a subset of the one or more serving cells.

[0491] Embodiment 31. The network node 110 according to any of embodiments 29-30, wherein the MAC CE is adapted to comprise a first number of bits, wherein each of the one or more serving cells is adapted to be associated with a specific bit of the first number of bits, and wherein the respective bits is adapted to indicate whether an OD-SSB for a serving cell should be activated or deactivated.

[0492] Embodiment 32. The network node 110 according to embodiment 31 , wherein the MAC CE is further adapted to comprise a second bit, which second bit is indicative of whether the first number of bits further indicates an activation / deactivation status of the one or more serving cells. Embodiment 33. The network node 110 according to any of embodiment 29-32, wherein the MAC CE is adapted to comprise a respective first field for one or more activated OD-SSBs, wherein the respective first fields control the transmission of the activated OD-SSBs.

[0493] Embodiment 34. The network node 110 according to embodiment 33, wherein the respective first fields is adapted to comprise an index or identity, which index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations.

[0494] Embodiment 35. The network node 110 according to any of embodiments 33-34, wherein the respective first fields is adapted to comprise two or more subfields, and wherein an OD-SSB subfield indicates:

[0495] - an index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations, and wherein a parameter subfield indicates:

[0496] - a parameter value of a parameter in the indicated OD-SSB configuration.

[0497] Embodiment 36. The network node 110 according to any of embodiments 29-35, wherein the network node 110 is configured to send the message comprising the MAC CE by sending separate MAC CE for each activated / deactivated OD-SSB, or for each OD- SSB which configuration is changed, wherein the respective separate MAC CE is adapted to comprise a cell identity field and an OD-SSB field, wherein the cell identity field comprises an identity of index indicating an serving cell, and wherein the OD-SSB field comprises an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations.

[0498] Embodiment 37. The network node 110 according to embodiment 36, wherein the respective separate MAC CE is adapted to comprise a parameter field adapted to indicate a parameter value of a parameter in the indicated OD-SSB configuration.

[0499] Embodiment 38. The network node 110 according to any of embodiments 29-37, wherein the network node 110 is configured to send the message comprising the MAC CE by sending separate MAC CEs for OD-SSB activation / deactivation and OD-SSB configuration. Embodiment 39. The network node 110 according to any of embodiments 29-38, wherein the network node 110 is configured to send the message comprising the MAC CE by further indicating a Transmission Configuration Indicator, TCI, state for activated OD- SSBs in the one or more serving cells.

[0500] Embodiment 40. The network node 110 according to any of embodiments 29-39, wherein the network node 110 is configured to send the message comprising the MAC CE by further indicating a set of candidate OS-SSBs.

[0501] Embodiment 41. A User Equipment 121 e.g., configured to handle Synchronization Signal Block, SSB, signaling in wireless communication network 100, the UE 121 further being configured to any one or more out of: receive a Radio Resource Control, RRC, message from a network node 110, which RRC message is adapted to comprise one or more configurations for On-Demand Synchronization Signal Block, OD-SSB, in one or more serving cells, receive a message from the network node 110, which message is adapted to comprise a Medium Access Control, MAC, Control Element, CE, controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

[0502] Embodiment 42. The UE 121 according to embodiment 41 , wherein the one or more OD-SSB configurations is adapted to comprise any one or more out of:

[0503] - one or more OD-SSB configurations per serving cell,

[0504] - one or more common OD-SSB configurations for all of the one or more serving cells, and

[0505] - one or more common OD-SSB configurations for a subset of the one or more serving cells.

[0506] Embodiment 43. The UE 121 according to any of embodiments 41-12, wherein the MAC CE is adapted to comprise a first number of bits, wherein each of the one or more serving cells is adapted to be associated with a specific bit of the first number of bits, and wherein the respective bits is adapted to indicate whether an OD-SSB for a serving cell should be activated or deactivated. Embodiment 44. The UE 121 according to embodiment 43, wherein the MAC CE is further adapted to comprise a second bit, which second bit is indicative of whether the first number of bits further indicates an activation / deactivation status of the one or more serving cells.

[0507] Embodiment 45. The UE 121 according to any of embodiment 41-44, wherein the MAC CE is adapted to comprise a respective first field for one or more activated OD- SSBs, wherein the respective first fields control the transmission of the activated OD- SSBs.

[0508] Embodiment 46. The UE 121 according to embodiment 45, wherein the respective first fields is adapted to comprise an index or identity, which index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations.

[0509] Embodiment 47. The UE 121 according to any of embodiments 45-46, wherein the respective first fields is adapted to comprise two or more subfields, and wherein an OD- SSB subfield indicates:

[0510] - an index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations, and wherein a parameter subfield indicates:

[0511] - a parameter value of a parameter in the indicated OD-SSB configuration.

[0512] Embodiment 48. The UE 121 according to any of embodiments 29-47, wherein the UE 121 is configured to receive the message comprising the MAC CE by receiving separate MAC CE for each activated / deactivated OD-SSB, or for each OD-SSB which configuration is changed, wherein the respective separate MAC CE comprises a cell identity field and an OD-SSB field, wherein the cell identity field comprises an identity of index indicating an serving cell, and wherein the OD-SSB field comprises an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations.

[0513] Embodiment 49. The UE 121 according to embodiment 48, wherein the respective separate MAC CE is adapted to comprise a parameter field adapted to indicate a parameter value of a parameter in the indicated OD-SSB configuration. Embodiment 50. The UE 121 according to any of embodiments 29-49, wherein the UE 121 is configured to receive the message comprising the MAC CE by receiving separate MAC CEs for OD-SSB activation / deactivation and OD-SSB configuration.

[0514] Embodiment 51. The UE 121 according to any of embodiments 29-50, wherein the UE 121 is configured to receive the message comprising the MAC CE by further receiving an indication adapted to indicate a Transmission Configuration Indicator, TCI, state for activated OD-SSBs in the one or more serving cells.

[0515] Embodiment 52. The UE 121 according to any of embodiments 29-51, wherein the UE 121 is configured to receive the message comprising the MAC CE by further receiving an indication adapted to indicate a set of candidate OS-SSBs.

[0516] ADDITIONAL EXPLANATION

[0517] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0518] Figure 12 shows an example of a communication system QQ100 in accordance with some embodiments.

[0519] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0520] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O- CLI-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0521] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0522] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0523] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more host computing systems, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

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

[0525] As a whole, the communication system QQ100 of Figure 12 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0526] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

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

[0528] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0529] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0530] Figure 13 shows a UE QQ200 in accordance with some embodiments. The UE QQ200 presents additional details of some embodiments of the UE QQ112 of Figure 1. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehiclemounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0531] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0532] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 13. 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.

[0533] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

[0534] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0535] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0536] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0537] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0538] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

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

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

[0541] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0542] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure 13.

[0543] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0544] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0545] Figure 14 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O- RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0546] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0547] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0548] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 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 NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

[0549] The processing circuitry QQ302 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 QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

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

[0551] The memory QQ304 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 the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0552] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0553] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0554] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0555] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0556] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0557] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 14 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300. In some embodiments providing a core network node, such as core network node 108 of FIG. QQ1, some components, such as the radio front-end circuitry QQ318 and the RF transceiver circuitry QQ312 may be omitted.

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

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

[0560] Hardware QQ404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ408a and QQ408b (one or more of which may be generally referred to as VMs QQ408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ406 may present a virtual operating platform that appears like networking hardware to the VMs QQ408.

[0561] The VMs QQ408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ406. Different embodiments of the instance of a virtual appliance QQ402 may be implemented on one or more of VMs QQ408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0562] In the context of NFV, a VM QQ408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ408, and that part of hardware QQ404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ408 on top of the hardware QQ404 and corresponds to the application QQ402.

[0563] Hardware QQ404 may be implemented in a standalone network node with generic or specific components. Hardware QQ404 may implement some functions via virtualization. Alternatively, hardware QQ404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ410, which, among others, oversees lifecycle management of applications QQ402. In some embodiments, hardware QQ404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ412 which may alternatively be used for communication between hardware nodes and radio units.

[0564] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0565] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0566] When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of". The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

Claims

76CLAIMS1. A method performed by a network node (110) for handling Synchronization Signal Block, SSB, signaling in a wireless communication network (100), the method comprising: sending (501) a Radio Resource Control, RRC, message to a User Equipment, UE,(121), which RRC message comprises one or more configurations for On-Demand Synchronization Signal Block, OD-SSB, in one or more serving cells, sending (502) a message to the UE (121), which message comprises a Medium Access Control, MAC, Control Element, CE, controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

2. The method according to claim 1, wherein the one or more OD-SSB configurations comprises any one or more out of:- one or more OD-SSB configurations per serving cell,- one or more common OD-SSB configurations for all of the one or more serving cells, and- one or more common OD-SSB configurations for a subset of the one or more serving cells.

3. The method according to any of claims 1-2, wherein the MAC CE comprises a first number of bits, wherein each of the one or more serving cells is associated with a specific bit of the first number of bits, and wherein the respective bit indicate whether an OD-SSB for a serving cell should be activated or deactivated.

4. The method according to claim 3, wherein the MAC CE further comprises a second bit, which second bit is indicative of whether the first number of bits further indicates an activation / deactivation status of the one or more serving cells.

5. The method according to any of claims 1-4, wherein the MAC CE comprises a respective first field for one or more activated OD-SSBs, wherein the respective first fields control the transmission of the activated OD-SSBs.

6. The method according to claim 5, wherein the respective first fields comprise an index or identity, which index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations.

777. The method according to any of claims 5-6, wherein the respective first fields comprise two or more subfields, and wherein an OD-SSB subfield indicates:- an index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations, and wherein a parameter subfield indicates:- a parameter value of a parameter in the indicated OD-SSB configuration.

8. The method according to any of claims 1-7, wherein sending the message comprising the MAC CE comprises sending separate MAC CE for each activated / deactivated OD-SSB, or for each OD-SSB which configuration is changed, wherein the respective separate MAC CE comprises a cell identity field and an OD-SSB field, wherein the cell identity field comprises an identity of index indicating an serving cell, and wherein the OD-SSB field comprises an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations.

9. The method according to claim 8, wherein the respective separate MAC CE comprises a parameter field indicating a parameter value of a parameter in the indicated OD-SSB configuration.

10. The method according to any of claims 1-9, wherein sending the message comprising the MAC CE comprises sending separate MAC CEs for OD-SSB activation / deactivation and OD-SSB configuration.

11. The method according to any of claims 1-10, wherein sending the message comprising the MAC CE further comprises indicating a Transmission Configuration Indicator, TCI, state for activated OD-SSBs in the one or more serving cells.

12. The method according to any of claims 1-11 , wherein sending the message comprising the MAC CE further comprises indicating a set of candidate OS-SSBs.

13. A computer program (1030) comprising instructions, which when executed by a processor (1010), causes the processor (1010) to perform actions according to any of the claims 1-12.7814. A carrier (1040) comprising the computer program (1030) of claim 13, wherein the carrier (1040) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer- readable storage medium.

15. A method performed by a User Equipment (121) for handling Synchronization Signal Block, SSB, signaling in a wireless communication network (100), the method comprising: receiving (601) a Radio Resource Control, RRC, message from a network node (110), which RRC message comprises one or more configurations for On-Demand Synchronization Signal Block, OD-SSB, in one or more serving cells, receiving (602) a message from the network node (110), which message comprises a Medium Access Control, MAC, Control Element, CE, controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

16. The method according to claim 15, wherein the one or more OD-SSB configurations comprises any one or more out of:- one or more OD-SSB configurations per serving cell,- one or more common OD-SSB configurations for all of the one or more serving cells, and- one or more common OD-SSB configurations for a subset of the one or more serving cells.

17. The method according to any of claims 15-16, wherein the MAC CE comprises a first number of bits, wherein each of the one or more serving cells is associated with a specific bit of the first number of bits, and wherein the respective bit indicates whether an OD-SSB for a serving cell should be activated or deactivated.

18. The method according to claim 17, wherein the MAC CE further comprises a second bit, which second bit is indicative of whether the first number of bits further indicates an activation / deactivation status of the one or more serving cells.7919. The method according to any of claim 15-18, wherein the MAC CE comprises a respective first field for one or more activated OD-SSBs, wherein the respective first fields control the transmission of the activated OD-SSBs.

20. The method according to claim 19, wherein the respective first fields comprise an index or identity, which index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations.

21. The method according to any of claims 19-20, wherein the respective first fields comprise two or more subfields, and wherein an OD-SSB subfield indicates:- an index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations, and wherein a parameter subfield indicates:- a parameter value of a parameter in the indicated OD-SSB configuration.

22. The method according to any of claims 15-21 , wherein receiving the message comprising the MAC CE comprises receiving separate MAC CE for each activated / deactivated OD-SSB, or for each OD-SSB which configuration is changed, wherein the respective separate MAC CE comprises a cell identity field and an OD-SSB field, wherein the cell identity field comprises an identity of index indicating an serving cell, and wherein the OD-SSB field comprises an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations.

23. The method according to claim 22, wherein the respective separate MAC CE comprises a parameter field indicating a parameter value of a parameter in the indicated OD-SSB configuration.

24. The method according to any of claims 15-23, wherein receiving the message comprising the MAC CE comprises receiving separate MAC CEs for OD-SSB activation / deactivation and OD-SSB configuration.

25. The method according to any of claims 15-24, wherein receiving the message comprising the MAC CE further comprises receiving an indication indicating a Transmission Configuration Indicator, TCI, state for activated OD-SSBs in the one or more serving cells.8026. The method according to any of claims 15-25, wherein receiving the message comprising the MAC CE further comprises receiving an indication indicating a set of candidate OS-SSBs.

27. A computer program (1130) comprising instructions, which when executed by a processor (1110), causes the processor (1110) to perform actions according to any of the claims 15-26.

28. A carrier (1140) comprising the computer program (1130) of claim 27, wherein the carrier (1140) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer- readable storage medium.

29. A network node (110) configured to handle Synchronization Signal Block, SSB, signaling in a wireless communication network (100), the network node (110) further being configured: send a Radio Resource Control, RRC, message to a User Equipment, UE, (121), which RRC message is adapted to comprise one or more configurations for On-Demand Synchronization Signal Block, OD-SSB, in one or more serving cells, send a message to the UE (121), which message is adapted to comprise a Medium Access Control, MAC, Control Element, CE, controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

30. The network node (110) according to claim 29, wherein the one or more OD-SSB configurations are adapted to comprise any one or more out of:- one or more OD-SSB configurations per serving cell,- one or more common OD-SSB configurations for all of the one or more serving cells, and- one or more common OD-SSB configurations for a subset of the one or more serving cells.

31. The network node (110) according to any of claims 29-30, wherein the MAC CE is adapted to comprise a first number of bits, wherein each of the one or more serving cells is adapted to be associated with a specific bit of the first number of bits, and wherein the81 respective bits is adapted to indicate whether an OD-SSB for a serving cell should be activated or deactivated.

32. The network node (110) according to claim 31 , wherein the MAC CE is further adapted to comprise a second bit, which second bit is indicative of whether the first number of bits further indicates an activation / deactivation status of the one or more serving cells.

33. The network node (110) according to any of claim 29-32, wherein the MAC CE is adapted to comprise a respective first field for one or more activated OD-SSBs, wherein the respective first fields control the transmission of the activated OD-SSBs.

34. The network node (110) according to claim 33, wherein the respective first fields is adapted to comprise an index or identity, which index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations.

35. The network node (110) according to any of claims 33-34, wherein the respective first fields is adapted to comprise two or more subfields, and wherein an OD-SSB subfield indicates:- an index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations, and wherein a parameter subfield indicates:- a parameter value of a parameter in the indicated OD-SSB configuration.

36. The network node (110) according to any of claims 29-35, wherein the network node (110) is configured to send the message comprising the MAC CE by sending separate MAC CE for each activated / deactivated OD-SSB, or for each OD-SSB which configuration is changed, wherein the respective separate MAC CE is adapted to comprise a cell identity field and an OD-SSB field, wherein the cell identity field comprises an identity of index indicating an serving cell, and wherein the OD-SSB field comprises an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations.8237. The network node (110) according to claim 36, wherein the respective separate MAC CE is adapted to comprise a parameter field adapted to indicate a parameter value of a parameter in the indicated OD-SSB configuration.

38. The network node (110) according to any of claims 29-37, wherein the network node (110) is configured to send the message comprising the MAC CE by sending separate MAC CEs for OD-SSB activation / deactivation and OD-SSB configuration.

39. The network node (110) according to any of claims 29-38, wherein the network node (110) is configured to send the message comprising the MAC CE by further indicating a Transmission Configuration Indicator, TCI, state for activated OD-SSBs in the one or more serving cells.

40. The network node (110) according to any of claims 29-39, wherein the network node (110) is configured to send the message comprising the MAC CE by further indicating a set of candidate OS-SSBs.

41. The network node (110) according to any of claims 29-40, wherein the network node (110) comprises at least one processor (1010) and a memory (1020) containing program code executable by the at least one processor (1010), whereby execution of the program code by the at least one processor (1010) causes the network node (110) to perform a method according to any of embodiments 1 to 12.

42. A User Equipment (121) configured to handle Synchronization Signal Block, SSB, signaling in a wireless communication network (100), the UE (121) further being configured to: receive a Radio Resource Control, RRC, message from a network node (110), which RRC message is adapted to comprise one or more configurations for On-Demand Synchronization Signal Block, OD-SSB, in one or more serving cells, receive a message from the network node (110), which message is adapted to comprise a Medium Access Control, MAC, Control Element, CE, controlling an OD-SSB transmission based on the one or more OD-SSB configurations for the one or more serving cells.

43. The UE (121) according to claim 42, wherein the one or more OD-SSB configurations is adapted to comprise any one or more out of:- one or more OD-SSB configurations per serving cell,- one or more common OD-SSB configurations for all of the one or more serving cells, and- one or more common OD-SSB configurations for a subset of the one or more serving cells.

44. The UE (121) according to any of claims42-43, wherein the MAC CE is adapted to comprise a first number of bits, wherein each of the one or more serving cells is adapted to be associated with a specific bit of the first number of bits, and wherein the respective bits is adapted to indicate whether an OD-SSB for a serving cell should be activated or deactivated.

45. The UE (121) according to claim 44, wherein the MAC CE is further adapted to comprise a second bit, which second bit is indicative of whether the first number of bits further indicates an activation / deactivation status of the one or more serving cells.

46. The UE (121) according to any of claim 42-45, wherein the MAC CE is adapted to comprise a respective first field for one or more activated OD-SSBs, wherein the respective first fields control the transmission of the activated OD-SSBs.

47. The UE (121) according to claim 46, wherein the respective first fields is adapted to comprise an index or identity, which index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations.

48. The UE (121) according to any of claims 46-47, wherein the respective first fields is adapted to comprise two or more subfields, and wherein an OD-SSB subfield indicates:- an index or identity indicates an OD-SSB configuration of the one or more received OD-SSB configurations, and wherein a parameter subfield indicates:- a parameter value of a parameter in the indicated OD-SSB configuration.

49. The UE (121) according to any of claims 42-48, wherein the UE (121) is configured to receive the message comprising the MAC CE by receiving separate MAC CE for eachactivated / deactivated OD-SSB, or for each OD-SSB which configuration is changed, wherein the respective separate MAC CE comprises a cell identity field and an OD-SSB field, wherein the cell identity field comprises an identity of index indicating an serving cell, and wherein the OD-SSB field comprises an identity or index indicating an OD-SSB configuration of the one or more received OD-SSB configurations.

50. The UE (121) according to claim 49, wherein the respective separate MAC CE is adapted to comprise a parameter field adapted to indicate a parameter value of a parameter in the indicated OD-SSB configuration.

51. The UE (121) according to any of claims 42-50, wherein the UE (121) is configured to receive the message comprising the MAC CE by receiving separate MAC CEs for OD- SSB activation / deactivation and OD-SSB configuration.

52. The UE (121) according to any of claims 42-51, wherein the UE (121) is configured to receive the message comprising the MAC CE by further receiving an indication adapted to indicate a Transmission Configuration Indicator, TCI, state for activated OD-SSBs in the one or more serving cells.

53. The UE (121) according to any of claims 42-52, wherein the UE (121) is configured to receive the message comprising the MAC CE by further receiving an indication adapted to indicate a set of candidate OS-SSBs.

54. The UE (121) according to any of claims 42-53, wherein the UE (121) comprises at least one processor (1110), and a memory (1120) containing program code executable by the at least one processor (1110), whereby execution of the program code by the at least one processor (1120) causes the UE (121) to perform a method according to any of embodiments 15 to 26.

Images