SSB pattern and rate adaptation in network energy saving

Abstract

Embodiments of a method in a first network node. The method comprising one or more of: sending, to a second network node, a request to activate one or more SSBs; and receiving, from the second network node, feedback on the request.

Description

SSB PATTERN AND RATE ADAPTATION IN NETWORK ENERGY SAVING Technical Field

[0001] The present disclosure relates to network management and in particular to SSB pattern and rate adaptation in network energy saving. Background Network energy consumption and 3GPP Work Item

[0002] Network energy consumption is a considerable challenge of 5G systems today. A major contributor to the network energy consumption is the radio unit of the RAN. The network energy consumption for NR is said to be less than for LTE due to the lean design of NR, i.e., no CRS and a SSB periodicity of 20 ms by default. However, current NR implementations often consume more energy compared to LTE, partly due to a larger bandwidth, BW, a shorter transmission time interval, TTI, and a massive number of antenna ports, among other things, increasing L1 processing needs many times over. The network energy consumption is still (too) high even at times when cells and beams are lightly loaded or serve no traffic or users at all.

[0003] The 3GPP has approved in Release 19 a new Work Item “Enhancements of network energy savings for NR”, which includes the following objectives: 1. Specify procedures and signaling method(s) to support on-demand SSB SCell operation for UEs in connected mode configured with CA, for both intra- / inter-band CA. [RAN1 / 2 / 3 / 4] • Specify triggering method(s) (select from UE uplink wake-up-signal using an existing signal / channel, cell on / off indication via backhaul, Scell activation / deactivation signaling) • Note1: On-demand SSB transmission can be used by UE for at least SCell time / frequency synchronization, L1 / L3 measurements and SCell activation, and is supported for FR1 and FR2 in non-shared spectrum. 2. Study procedures and signaling method(s) to support on-demand SIB1 for UEs in idle / inactive mode, including: [RAN1 / 2 / 3] • Triggering method by uplink wake-up-signal using an existing signal / channel. • Wake-up-signal configuration provisioning to UE - Note: No modification of SSB will be discussed under this objective • Information exchange between gNBs at least for the configuration of wake-up signal, if necessary.• Checkpoint for normative work in RAN#105 3. Specify adaptation of common signal / channel transmissions. [RAN1 / 2 / 3 / 4] • Adaptation of SSB in time domain, e.g. adapting periodicity • Adaptation of PRACH in time domain • Study adaptation of PRACH in spatial domain, e.g. non-uniform PRACH resources per SSB, and specify if found beneficial - This study is to be done in 2Q’2024 only • Adaptation of paging occasions including confining the paging occasions in the time domain - Note: there shall be no paging latency increase • Note: there shall be no negative impact to legacy UEs, unless significant benefits are shown 4. Specify the corresponding core requirements, for the above features [RAN4]. SMTC (SSB MTC) in 3GPP specification

[0004] SSB based measurements are configured along with a measurement timing configuration (SMTC) per carrier, which provides periodicity, duration and offset information on a window of up to 5ms where the measurements on the configured inter- frequency carrier are to be performed.

[0005] To inform the UE about the SSB measurement periodicity, in NR a SSB measurement time configuration (SMTC) is introduced. SMTC consists of SMTC periodicity and SMTC window length. In NR, since different beams can be configured to cover different spatial implementation, UEs do not need to measure all the spatial directions. The beams to be measured can be controlled or configurable through SMTC window. SMTC window length indicates the location of the SSB to be measured within the SSB burst set. The signaling of SMTC window informs the UE of the timing and periodicity of SSBs that the UE can use for measurements. The SMTC window periodicity can be configured from the value set {5, 10, 20, 40, 80, 160} ms, matching the possible SSB periodicities. Excerpt from 3GPP 38.331 V18.0.0 Begins6.3.2 Radio resource control information elements […] – SSB-MTC The IE SSB-MTC is used to configure measurement timing configurations, i.e., timing occasions at which the UE measures SSBs. SSB-MTC information element -- ASN1START -- TAG-SSB-MTC-START SSB-MTC ::= SEQUENCE { periodicityAndOffset CHOICE { sf5 INTEGER (0..4), sf10 INTEGER (0..9), sf20 INTEGER (0..19), sf40 INTEGER (0..39), sf80 INTEGER (0..79), sf160 INTEGER (0..159) }, duration ENUMERATED { sf1, sf2, sf3, sf4, sf5 } } […] 11.2.2 Message definitions […] – MeasurementTimingConfiguration The MeasurementTimingConfiguration message is used to convey assistance information for measurement timing. Direction: en-gNB to eNB, eNB to en-gNB, gNB to gNB, ng-eNB to gNB, gNB to ng-eNB, ng-eNB to ng-eNB, gNB DU to gNB CU, and gNB CU to gNB DU. MeasurementTimingConfiguration message […]MeasTiming field descriptions carrierFreq, ssbSubcarrierSpacing Indicates the frequency and subcarrier spacing of the SS block of the cell for which this message is included, or of other SS blocks within the same carrier. ssb-MeasurementTimingConfiguration Indicates the SMTC which can be used to search for SSB of the cell for which the message is included. When the message is included in "Served NR Cell Information" (see TS 36.423

[0037] ), "Served Cell Information NR" (see TS 38.423

[0035] ), or "Served Cell Information" (see TS 38.473

[0036] ), the timing is based on the cell for which the message is included. When the message is included in "NR Neighbour Information" (see TS 36.423

[0037] ), or "Served Cell Information" (see TS 38.423

[0035] ), the timing is based on the cell indicated in the "Served NR Cell Information" or "Served Cell Information NR" with which the "NR Neighbour Information" or "Neighbour Information NR" is provided. When the message is included in "CU to DU RRC Information", the timing is based on the cell indicated by SpCell ID with which the message is included. If the field is provided by an NTN cell, the offset (derived from parameter periodicityAndOffset) is based on the assumption that the NTN payload to gNB propagation delay of the cell for which the message is included equals to 0 ms. ss-RSSI-Measurement Provides the configuration which can be used for RSSI measurements of the cell for which the message is included. Excerpt from 3GPP 38.331 V18.0.0 Ends SSB-MTC over F1AP

[0006] Measurement Timing Configuration is included in the “Served Cell Information” sent from gNB-DU to gNB-CU during F1 SETUP REQUEST and gNB-DU CONFIGRUATION UPDATE. It provides the Measurement Timing Configuration Information about the cells configured in the gNB-DU. Excerpt from 3GPP 38.473 V18.0.0 Begins 9.2.1.4 F1 SETUP REQUEST This message is sent by the gNB-DU to transfer information associated to an F1-C interface instance. NOTE: If a TNL association is shared among several F1-C interface instances, several F1 Setup procedures are issued via the same TNL association after that TNL association has become operational. Direction: gNB-DU → gNB-CU IE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality Message Type M 9.3.1.1 YES reject Transaction ID M 9.3.1.23 YES reject gNB-DU ID M 9.3.1.9 YES reject gNB-DU Name O PrintableString( YES ignore SIZE(1..150,...)) gNB-DU Served Cells 0..1 List of cells YES rejectIE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality List configured in the gNB-DU >gNB-DU Served 1.. EACH reject Cells Item <maxCelli ngNBDU> >>Served Cell M 9.3.1.10 Information about - Information the cells configured in the gNB-DU >>gNB-DU System O 9.3.1.18 RRC container - Information with system information owned by gNB-DU gNB-DU RRC version M RRC version YES reject 9.3.1.70 Transport Layer O 9.3.2.5 YES ignore Address Info BAP Address O 9.3.1.111 Indicates a BAP YES ignore address assigned to the IAB-node. Extended gNB-DU O 9.3.1.205 YES ignore Name RRC Terminating IAB- O Global gNB ID The Global gNB ID YES ignore Donor gNB-ID 9.3.1.305 of a mobile IAB- node’s RRC- terminating IAB donor. This IE is only present if the mobile IAB-node’s RRC terminating IAB-donor-CU is different from the gNB-CU receiving this message. Mobile IAB-MT User O 9.3.1.307 YES ignore Location Information Range bound Explanation maxCellingNBDU Maximum no. cells that can be served by a gNB-DU. Value is 512. […] 9.2.1.7 GNB-DU CONFIGURATION UPDATE This message is sent by the gNB-DU to transfer updated information associated to an F1-C interface instance. NOTE: If F1-C signalling transport is shared among several F1-C interface instances, this message may transfer updated information associated to several F1-C interface instances. Direction: gNB-DU → gNB-CU IE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description CriticalityIE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality Message Type M 9.3.1.1 YES reject Transaction ID M 9.3.1.23 YES reject Served Cells To Add 0..1 Complete list of YES reject List added cells served by the gNB-DU >Served Cells To 1.. EACH reject Add Item <maxCelli ngNBDU> >>Served Cell M 9.3.1.10 Information about - Information the cells configured in the gNB-DU >>gNB-DU System O 9.3.1.18 RRC container - Information with system information owned by gNB-DU Served Cells To 0..1 Complete list of YES reject Modify List modified cells served by the gNB-DU >Served Cells To 1.. EACH reject Modify Item <maxCelli ngNBDU> >>Old NR CGI M NR CGI - 9.3.1.12 >>Served Cell M 9.3.1.10 Information about - Information the cells configured in the gNB-DU >>gNB-DU System O 9.3.1.18 RRC container - Information with system information owned by gNB-DU Served Cells To Delete 0..1 Complete list of YES reject List deleted cells served by the gNB-DU >Served Cells To 1.. EACH reject Delete Item <maxCelli ngNBDU> >>Old NR CGI M NR CGI - 9.3.1.12 Cells Status List 0..1 Complete list of YES reject active cells >Cells Status Item 0.. EACH reject <maxCelli ngNBDU> >>NR CGI M 9.3.1.12 - >>Service Status M 9.3.1.68 - Dedicated SI Delivery 0..1 List of UEs unable YES ignore Needed UE List to receive system information from broadcast >Dedicated SI 1.. EACH ignore Delivery Needed UE <maxnoof Item UEIDs>IE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality >>gNB-CU UE F1AP M 9.3.1.4 - ID >>NR CGI M 9.3.1.12 - gNB-DU ID O 9.3.1.9 YES reject gNB-DU TNL 0..1 YES reject Association To Remove List >gNB-DU TNL 1..<maxno EACH reject Association To ofTNLAss Remove Item IEs ociation> >>TNL Association M CP Transport Transport Layer - - Transport Layer Layer Address Address of the Address 9.3.2.4 gNB-DU. >>TNL Association O CP Transport Transport Layer - - Transport Layer Layer Address Address of the Address gNB-CU 9.3.2.4 gNB-CU Transport Layer O 9.3.2.5 YES ignore Address Info Coverage Modification O 9.3.1.213 YES Ignore Notification gNB-DU Name O PrintableString( Human readable YES ignore SIZE(1..150,...)) name of the gNB- DU. Extended gNB-DU O 9.3.1.205 YES ignore Name RRC Terminating IAB- O 9.3.1.306 Indicates the YES ignore Donor Related Info information related to a mobile IAB- node’s RRC- terminating IAB- donor. Mobile IAB-MT User O 9.3.1.307 YES ignore Location Information Range bound Explanation maxCellingNBDU Maximum no. cells that can be served by a gNB-DU. Value is 512. maxnoofUEIDs Maximum no. of UEs that can be served by a gNB-DU. Value is 65536. maxnoofTNLAssociations Maximum numbers of TNL Associations between the gNB-CU and the gNB-DU. Value is 32. Excerpt from 3GPP 38.473 V18.0.0 Ends SSB-MTC over XnAP

[0007] Measurement Timing Configuration is included in the Served Cell Information NR and sent between the gNBs having Xn connection.Excerpt from 3GPP 38.423 V18.0.0 Begins 9.2.2.11 Served Cell Information NR This IE contains cell configuration information of an NR cell that a neighbouring NG-RAN node may need for the Xn AP interface. IE / Group Name Presenc Range IE type and Semantics description e reference NR-PCI M INTEGER NR Physical Cell ID (0..1007, …) NR CGI M 9.2.2.7 TAC M 9.2.2.5 Tracking Area Code Skip the unrelated Measurement M OCTET STRING Includes the Timing MeasurementTimingConfiguration Configuration inter-node message for the served cell, as defined in TS 38.331

[0010] . Connectivity Support M 9.2.2.28 >CSI- RS MTC M 1.. This list explicitly expresses the CSI-RS Configuration List <maxnoof configurations contained in the MTC CSIRSconf igurations> >>CSI-RS Index M INTEGER (0..95) Index of CSI-RS as in MTC >>CSI-RS Status M ENUMERATED This IE indicates the CSI-RS (activated, transmission status of the configuration. deactivated, …) >>CSI-RS O 1.. This list expresses the cells and CSI-RSs Neighbour List <maxnoof neighbouring the CSI-RS in the CSI-RS CSIRSneig Index IE. hbourCells > >>>NR CGI M 9.2.2.7 >>>CSI-RS MTC O 1.. < This list expresses the CSI-RSs served Neighbour List maxnoofC by the NR CGI, which are neighbouring SIRSneigh the CSI-RS of the served cell and bourCellsI contained in the MTC indicated by the nMTC> neighbouring NR cell. >>>>CSI-RS M INTEGER (0..95) Index Excerpt from 3GPP 38.423 V18.0.0 Ends

[0008] There currently exist certain challenge(s). In Rel-19, for the sake of NW energy savings, work is ongoing on reducing time-domain transmissions in cells to achieve long enough gaps that provide deeper sleep opportunities for the gNBs. For example, the rate of SSBs transmission may be reduced from a typical 20ms periodicity to say 160ms. Although this brings good energy saving opportunities, occasionally it can have negative performance impact. One example is during handover of UEs between different cells, especially if theUEs are moving at fast speed. There is today no mechanism between gNBs to assist each other in this matter and adapt the SSB transmission characteristics (e.g., rate) on-demand.

[0009] In the current specification, the SSB measurements configuration is informed from gNB-DU to gNB-CU, or between the gNBs, it is not possible for gNB 1 or gNB-CU to request how (including which characteristics) gNB 2 or gNB-DU shall configure the SSBs during the activation of the SSBs. Hence, methods are needed to avoid the potential negative effects of such time-domain transmission optimizations. Summary

[0010] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In Rel-19, in certain scenarios such as during a handover assessment, one gNB may need to request another gNB to activate additional SSBs on- demand with certain characteristics such as SSB measurement relevant configurations, optionally including one or more of the SSB pattern, SSB rate, SSB window, and SSB type (e.g., cell defining vs non-cell—defining) to achieve on-demand SSB adaptation. Some embodiments herein provide solutions on how one gNB (gNB 1) could request the other gNB (gNB 2) to activate SSBs according to the desired characteristics e.g., (minimum / exact) rates / patterns / periodicity / window. The gNB 1 determines such SSB activation information based on the knowledge related to one or more of its load situation, the characteristic of UEs being served, and the demand from the UEs, or alike.

[0011] Accordingly, an aspect of the present disclosure provides a method performed by a first network node. The method comprises one or more of: sending (200), to a second network node, a request to activate one or more SSBs; and receiving (202), from the second network node, feedback on the request.

[0012] In some embodiments, the request comprises a Cell Activation Request.

[0013] In some embodiments, the request comprises characteristics such as SSB measurement relevant configurations, optionally including one or more of the SSB pattern, SSB rate, SSB window, and SSB type to achieve on-demand SSB adaptation.

[0014] In some embodiments, the SSB type comprises either cell defining vs non-cell— defining.

[0015] In some embodiments, the request comprises a Cell Activation Request.

[0016] In some embodiments, the request is determined based on a load situation of the first network node, the characteristic of UEs being served, the demand from the UEs, etc.

[0017] In some embodiments, the feedback on the request comprises a denial and optionally providing feedback indicating the possible / alternative SSB rate / pattern / periodicity the second network node could perform.

[0018] A further aspect of the present disclosure provides a method performed by a second network node. The method comprises one or more of: receiving (300), from a first network node, a request to activate one or more SSBs; and sending (302), to the second network node, feedback on the request.

[0019] In some embodiments, the request comprises a Cell Activation Request.

[0020] In some embodiments, the request comprises characteristics such as SSB measurement relevant configurations, optionally including one or more of the SSB pattern, SSB rate, SSB window, and SSB type to achieve on-demand SSB adaptation.

[0021] In some embodiments, the SSB type comprises either cell defining vs non-cell— defining.

[0022] In some embodiments, the request comprises a Cell Activation Request.

[0023] In some embodiments, the request is determined based on a load situation of the network node, the characteristic of UEs being served, the demand from the UEs, etc.

[0024] In some embodiments, the feedback on the request comprises a denial and optionally providing feedback indicating the possible / alternative SSB rate / pattern / periodicity the second network node could perform.

[0025] Embodiments of a base station, communication system, and a method in a communication system are also disclosed.

[0026] Some embodiments disclosed herein further provide a solution for the gNB 2 to provide feedback on the desired SSB configuration from gNB 1.

[0027] gNB 1 (in the split architecture, gNB-CU 1) determines to ask for the SSBs provision in gNB 2, with the on-demand SSB measurement timing configuration such as minimum SSB rate, SSB patterns, SSB periodicity. gNB 2 applies the desired configuration accordingly, if possible, else it may deny the request with optionally providing feedback indicating the possible / alternative SSB rate / pattern / periodicity it could perform, in Step 1d. Accordingly, in the split RAN architecture the gNB-CU requests the gNB-DU to activate the SSBs with the provided SSB timing configuration information. In the split architecture, gNB- CU2 requests the gNB-DU2, in Step 1b, to activate the on-demand SSBs accordingly and the feedback is sent from gNB-DU2 in Step 1c. Step 3 depicts the revocation of requested SSB rate / pattern / periodicity towards gNB 2 by gNB 1. Alternatively, step 1 could be repeated, requesting to replace previously indicated SSB characteristics, based on which gNB 2 may accept or deny the request. It is assumed that it is not necessary to reflect any hierarchy among gNBs in terms of exchange of desired SSB characteristics in signalling, but it is not precluded to be reflected by means of OAM.

[0028] Also note that the mapping of the new IEs (the new pieces of information introduced herein) to the existing messages of the Cell Activation procedure over Xn (defined in XnAP) as well as the gNB-CU Configuration Update procedure and the gNB-DU Configuration Update procedure over F1 (defined in F1AP) is merely a non-limiting example.

[0029] Certain embodiments may provide one or more of the following technical advantage(s). The solution allows the gNBs to enjoy sleep states with minimal SSB transmissions, but when necessary request on-demand SSBs activation with specific characteristics such as minimum rates, SSB patterns, SSB periodicity. The node (including nodes of the split architecture, including gNB-CU / gNB-DU) receiving the desired / on- demand SSB activation with the related configuration is able to provide feedback.

[0030] The teachings of certain embodiments may improve the efficiency of the cells and cooperation. Brief Description of the Drawings

[0031] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain principles of the disclosure.

[0032] Figure 1 illustrates some embodiments of multiple network nodes communicating.

[0033] Figure 2 illustrates a method performed by a first network node.

[0034] Figure 3 illustrates a method performed by a second network node.

[0035] Figure 4 shows an example of a communication system in accordance with some embodiments of the present disclosure;

[0036] Figure 5 shows a User Equipment device (UE) in accordance with some embodiments of the present disclosure;

[0037] Figure 6 shows a network node in accordance with some embodiments of the present disclosure; and

[0038] Figure 7 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized in accordance with some embodiments of the present disclosure. Detailed Description

[0039] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0040] At least some of the following abbreviations and terms may be used in this disclosure. • 2D Two Dimensional • 3GPP 3rd Generation Partnership Project • 5G 5th Generation • 6G 6thGeneration • AAS Antenna Array System • ABS Almost Blank Subframe • AoA Angle of Arrival • AoD Angle of Departure • ARQ Automatic Repeat Request • ASIC Application Specific Integrated Circuit • AWGN Additive White Gaussian Noise • BCCH Broadcast Control Channel • BCH Broadcast Channel • BF Beamforming • BLER Block Error Rate • BW Beamwidth • CA Carrier Aggregation • CC Carrier Component • CCCH SDU Common Control Channel SDU • CCO Coverage and Capacity Optimization • CDMA Code Division Multiplex Access • CGI Cell Global Identity • CIR Channel Impulse Response • CP Cyclic Prefix • CPICH Common Pilot Channel • CPU Central Processing Unit• CQI Channel Quality Information • C-RNTI Cell RNTI • CSI Channel State Information • dB Decibel • DCCH Dedicated Control Channel • DCI Downlink Control Information • DFT Discrete Fourier Transform • DL Downlink • DM Demodulation • DMRS Demodulation Reference Signal • DRX Discontinuous Reception • DSP Digital Signal Processor • DTCH Dedicated Traffic Channel • DTX Discontinuous Transmission • DUT Device Under Test • Ec / No Received energy per chip divided by the power density in the band • ECGI Evolved CGI • E-CID Enhanced Cell-ID (positioning method) • eMBMS Evolved Multimedia Broadcast Multicast Services • eNB E-UTRAN NodeB • ePDCCH Enhanced Physical Downlink Control Channel • E-SMLC Evolved Serving Mobile Location Center • E-UTRAN Evolved Universal Terrestrial Radio Access Network • FDD Frequency Division Duplex • FFS For Further Study • FIR Finite Impulse Response • FPGA Field Programmable Gate Array• gNB New Radio Base Station • gNB-CU gNB Centralized Unit • gNB-DU gNB Distributed Unit • GNSS Global Navigation Satellite System • HARQ Hybrid Automatic Repeat Request • HO Handover • HRPD High Rate Packet Data • HSPA High Speed Packet Access • ICC Information Carrying Capacity • IIR Infinite Impulse Response • LOS Line of Sight • LPP LTE Positioning Protocol • LTE Long Term Evolution • MAC Medium Access Control • ABS Almost Blank Subframe • MBSFN Multimedia Broadcast Multicast Service Single Frequency Network • MDT Minimization of Drive Tests • MIB Master Information Block • MIMO Multiple Input Multiple Output • MME Mobility Management Entity • MMSE Minimum Mean Square Error • MSC Mobile Switching Center • MTC Machine Type Communication • NPDCCH Narrowband Physical Downlink Control Channel • NR New Radio • O&M Operation and Maintenance • OCNG OFDMA Channel Noise Generator• OFDM Orthogonal Frequency Division Multiplexing • OFDMA Orthogonal Frequency Division Multiple Access • OSS Operations Support System • OTDOA Observed Time Difference of Arrival • OTT Over-the-Top • PBCH Physical Broadcast Channel • P-CCPCH Primary Common Control Physical Channel • PCell Primary Cell • PCFICH Physical Control Format Indicator Channel • PDCCH Physical Downlink Control Channel • PDCP Packet Data Convergence Protocol • PDP Power Delay Profile • PDSCH Physical Downlink Shared Channel • P-GW Packet Data Network Gateway • PHICH Physical Hybrid-ARQ Indicator Channel • PLMN Public Land Mobile Network • PMI Precoding Matrix Indicator • PRACH Physical Random Access Channel • PRS Positioning Reference Signal • PSS Primary Synchronization Signal • PUCCH Physical Uplink Control Channel • PUSCH Physical Uplink Shared Channel • QAM Quadrature Amplitude Modulation • RACH Random Access Channel • RAM Random Access Memory • RAN Radio Access Network • RAT Radio Access Technology • RLC Radio Link Control• RLM Radio Link Monitoring • RNC Radio Network Controller • RNTI Radio Network Temporary Identifier • ROM Read Only Memory • RRC Radio Resource Control • RRC Radio Resource Control • RRH Remote Radio Head • RRM Radio Resource Management • RS Reference Signal • RSCP Received Signal Code Power • RSRP Reference Symbol Received Power OR Reference Signal Received Power • RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality • RSSI Received Signal Strength Indicator • RSTD Reference Signal Time Difference • SCEF Service Capability Exposure Function • SCell Secondary Cell • SCH Synchronization Channel • SDAP Service Data Adaptation Protocol • SDU Service Data Unit • SFN System Frame Number • SGW Serving Gateway • SI System Information • SIB System Information Block • SINR Signal to Interference plus Noise Ratio • SNR Signal to Noise Ratio • SON Self-Organizing Network• SS Synchronization Signal • SSB Synchronization Signal Block • SSS Secondary Synchronization Signal • TBS Transmission Block Size • TDD Time Division Duplex • TDOA Time Difference of Arrival • TOA Time of Arrival • TSS Tertiary Synchronization Signal • TTI Transmission Time Interval • UE User Equipment • UL Uplink • ULA Uniform Linear Array • UMTS Universal Mobile Telecommunications System • URA Uniform Rectangular Array • USIM Universal Subscriber Identity Module • UTDOA Uplink Time Difference of Arrival • WCDMA Wideband CDMA • WLAN Wireless Local Area Network

[0041] Radio Node: As used herein, a “radio node” is either a radio access node or a wireless device.

[0042] Radio Access Node: As used herein, a “radio access node” or “radio network node” is any node in a radio access network of a cellular communications network that operates to wirelessly transmit and / or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), and a relay node.

[0043] Core Network Node: As used herein, a “core network node” is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), or the like.

[0044] Wireless Device: As used herein, a “wireless device” is any type of device that has access to (i.e., is served by) a cellular communications network by wirelessly transmitting (and / or receiving) signals to (and / or from) a radio access node. Some examples of a wireless device include, but are not limited to, a User Equipment device (UE) in a 3GPP network and a Machine Type Communication (MTC) device.

[0045] Network Node: As used herein, a “network node” is any node that is either part of the radio access network or the core network of a cellular communications network / system.

[0046] Cell: As used herein, a “cell” is a combination of radio resources (such as, for example, antenna port allocation, time and frequency) that a wireless device may use to exchange radio signals with a radio access node, which may be referred to as a host node or a serving node of the cell. However, it is important to note that beams may be used instead of cells, particularly with respect to 5G NR. As such, it should be appreciated that the techniques described herein are equally applicable to both cells and beams.

[0047] Note that references in this disclosure to various technical standards (such as 3GPP TS 38.211 V15.1.0 (2018-03) and 3GPP TS 38.214 V15.1.0 (2018-03), for example) should be understood to refer to the specific version(s) of such standard(s) that is(were) current at the time the present application was filed, and may also refer to applicable counterparts and successors of such versions.

[0048] The description herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0049] Throughout this document, the on-demand / desired SSB(s) including transmission characteristics is requested by one node from another node via a structure called “SSB Activation Configuration” herein.

[0050]

[0051] Systems and methods are disclosed herein that provide

[0052] In one embodiment, gNB-CU includes the “SSB Activation Configuration” including the SSB MTC and other information to be used by gNB-DU when the SSB is activated. See Figure 1. The SSB Activation Configuration includes one or more of: • SSB minimum Rate requested • SSB alternative Rate(s) (the receiving node is given several options, and in the associated feedback it can say which one it chose) • SSB patterns to be used • SSB duration to be activated • Type of SSBs to be provided (e.g., cell-defining vs non-cell-defining) • Time / frequency resources for the on-demand SSBs

[0053] Upon the reception of the configuration information, gNB-DU should activate the SSBs according to the requirements.

[0054] In one embodiment, if the receiving node cannot satisfy the request, it rejects the request.

[0055] In another embodiment, if the receiving node cannot satisfy the request, it proposes alternative characteristics of SSB(s) transmission that it can conform to instead of the characteristics requested.

[0056] In yet another embodiment, the requesting node may specify the behavior of the receiving node in case the receiving node cannot satisfy the request. For example, gNB 1 may specify in the request that if gNB 2 cannot satisfy the request, it should then simply reject the request (e.g. via introducing an option called "reject if not possible” or alike which can be provided by the requesting node). Alternatively, the requesting node may give thereceiving node the option (e.g. via introducing an option called "propose alternative if not possible” or alike which can be provided by the requesting node) to suggest alternative characteristics it can provide and / or confirm to instead.

[0057] In the embodiments in which the receiving node may provide alternative characteristics that it can conform to, the receiving node (e.g. gNB-DU) includes the “SSB Activation Configuration Feedback” to indicate how the requested SSB configuration is executed, see Figure 1. The SSB Activation Configuration Feedback includes one or more of: • SSB minimum Rate can be performed • SSB preferred configuration • SSB alternative Rates • SSB patterns to be used • SSB duration to be activated

[0058] Time / frequency resources for the SSBs

[0059] Note that in the above embodiments, a node can also be a gNB. E.g., gNB1 (requesting node) includes the above information when activating the SSBs over XnAP and gNB2 (receiving node) includes the feedback to gNB1.

[0060] Chapter 9.3.1.326 SSBs within the cell to be Activated List. This IE indicates the SSBs within the cell requested to be activated. The table below illustrates an example to include the SSB Activation configuration during SSB activation:IE / Group Name Presence Range IE type and Semantics reference description SSBs within the 1.. < cell to be maxnoofSSBAreas> Activated List Item >SSB Index M INTEGER Identifier of SSB (0..63) beam requested to be activated. >SSB O New INTEGER Including the Activation (0..63) SSB Configuration measurement timing configuration information

[0061] SSB Activation Configuration

[0062] This IE indicates the SSBs MTC configuration related information requested to be used during SSB activation. IE / Group Presence Range IE type and Semantics Name reference description SSB minimum O ENUMERATED Unit: ms Rate (5, 10, 20, 40, 80, 160, …) SSB O List of the The receiving alternative SSB Rates node is given Rate(s) several options, and in the associated feedback it can say which one it chose. SSB Patterns O Bitstring SSB Duration O INTEGER Type of SSBs O ENUMERATED to be ((cell-defining, provided non-cell- defining, …) Time / freq O resources for the on-demand SSBs

[0063] New 2 SSB Activation Configuration Feedback

[0064] This IE provides the feedback of the SSBs MTC configuration related information from the node activating the SSB. IE / Group Name Presence Range IE type and Semantics reference description SSB minimum O ENUMERATED Unit: ms Rate can be (5, 10, 20, 40, performed 80, 160, …) SSB alternative O List of the SSB Rates Rates SSB Patterns O Bitstring to be used SSB duration to O INTEGER be activated Time / freq O resources for the SSBs

[0065] TS 38.423, Chapter 9.1.3.7 CELL ACTIVATION REQUEST

[0066] This message is sent by the NG-RAN node1 to the peer NG-RAN node2 to request a previously switched-off cell(s) or SSB beam(s) to be re-activated. Direction: NG- RAN node1 - NG-RAN node2. IE / Group Name Presen Range IE type Semantics Criticali Assign ce and description ty ed referen Criticali ce ty Message Type M 9.2.3.1 YES reject CHOICE Served M YES reject Cells To Activate Skip the unrelated >NR Cells and YES ignore SSBs >>To Be 1 – Activated NR Cells and SSBs List >>>To Be 1.. < – Activated NR maxnoofCellsin Cells and NG-RANnode> SSBs item >>>>NR CGI M 9.2.2.7 – >>>>SSBs 0..1 – to beIE / Group Name Presen Range IE type Semantics Criticali Assign ce and description ty ed referen Criticali ce ty Activated List >>>>>SSB 1.. < – s to be maxnoofSSBAr Activated eas > Item >>>>>>SS M INTEG Identifier of – B Index ER the SSB (0..63) beam requested to be activated. >>>>>>SS O New 1 Ref – ignore B er to Activation Figure X: Configura SSB tion Activation Configurati on

[0067] 9.1.3.8 CELL ACTIVATION RESPONSE

[0068] This message is sent by an NG-RAN node2 to a peer NG-RAN node1 to indicate that one or more cell(s) previously switched-off has (have) been activated. Direction: NG- RAN node2 → NG-RAN node1. The following example includes SSB MTC configuration information over XnAP when gNB1 actives SSBs in gNB2. IE / Group Name Presen Range IE type Semantic Criticali Assign ce and s ty ed referen descripti Criticali ce on ty Message Type M 9.2.3.1 YES reject CHOICE M YES reject Activated Served Cells Skip the unrelated >NR Cells and YES ignore SSBsIE / Group Name Presen Range IE type Semantic Criticali Assign ce and s ty ed referen descripti Criticali ce on ty >>Activated 1 – NR Cells and SSBs List >>>Activated 1 .. < – NR Cells and maxnoofCellsin SSBs Item NG-RANnode> >>>>NR CGI M 9.2.2.7 – >>>>SSBs 0..1 – Activated List >>>>>SSB 1 .. < – Activated maxnoofSSBAr Item eas > >>>>>>SS M INTEGE Identifier – B Index R of the (0..63) activated SSB beam. >>>>>>SS M New 2 – B Activation Configurat ion Feedback

[0069] Figure 2 illustrates a method performed by a first network node. The method comprising one or more of: sending (200), to a second network node, a request to activate one or more SSBs; and receiving (202), from the second network node, feedback on the request.

[0070] Figure 3 illustrates a method performed by a second network node. The method comprising one or more of: receiving (300), from a first network node, a request to activate one or more SSBs; and sending (302), to the second network node, feedback on the request.

[0071] Figure 4 shows an example of a communication system 400 in accordance with some embodiments.

[0072] In the example, the communication system 400 includes a telecommunication network 402 that includes an access network 404, such as a Radio Access Network (RAN),and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes, such as network nodes 410A and 410B (one or more of which may be generally referred to as network nodes 410), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). 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 402 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 402 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 402, including one or more network nodes 410 and / or core network nodes 408.

[0073] Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O-CU-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 O-2 interface defined by the O- RAN Alliance or comparable technologies. The network nodes 410 facilitate direct orindirect connection of User Equipment (UE), such as by connecting UEs 412A, 412B, 412C, and 412D (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections.

[0074] 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 400 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 400 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0075] The UEs 412 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 410 and other communication devices. Similarly, the network nodes 410 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 412 and / or with other network nodes or equipment in the telecommunication network 402 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 402.

[0076] In the depicted example, the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. 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 406 includes one more core network nodes (e.g., core network node 408) 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 408. 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 MobilityManagement Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), 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).

[0077] The host 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and / or the telecommunication network 402, and may be operated by the service provider or on behalf of the service provider. The host 416 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.

[0078] As a whole, the communication system 400 of Figure 4 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 400 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 Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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.

[0079] In some examples, the telecommunication network 402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunicationnetwork 402 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 Internet of Things (IoT) services to yet further UEs.

[0080] In some examples, the UEs 412 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 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

[0081] In the example, a hub 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE 412C and / or 412D) and network nodes (e.g., network node 410B). In some examples, the hub 414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 414 may be a broadband router enabling access to the core network 406 for the UEs. As another example, the hub 414 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 410, or by executable code, script, process, or other instructions in the hub 414. As another example, the hub 414 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 414 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 414 then provides to the UE either directly, after performing local processing, and / or after addingadditional local content. In still another example, the hub 414 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.

[0082] The hub 414 may have a constant / persistent or intermittent connection to the network node 410B. The hub 414 may also allow for a different communication scheme and / or schedule between the hub 414 and UEs (e.g., UE 412C and / or 412D), and between the hub 414 and the core network 406. In other examples, the hub 414 is connected to the core network 406 and / or one or more UEs via a wired connection. Moreover, the hub 414 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 404 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 410 while still connected via the hub 414 via a wired or wireless connection. In some embodiments, the hub 414 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 410B. In other embodiments, the hub 414 may be a non- dedicated hub – that is, a device which is capable of operating to route communications between the UEs and the network node 410B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0083] Figure 5 shows a UE 500 in accordance with some embodiments. 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 Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0085] The UE 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input / output interface 506, a power source 508, memory 510, a communication interface 512, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 5. 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.

[0086] The processing circuitry 502 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 510. The processing circuitry 502 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 502 may include multiple Central Processing Units (CPUs).

[0087] In the example, the input / output interface 506 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or outputdevices. 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 500. 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.

[0088] In some embodiments, the power source 508 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 508 may further include power circuitry for delivering power from the power source 508 itself, and / or an external power source, to the various parts of the UE 500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 508. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 508 to make the power suitable for the respective components of the UE 500 to which power is supplied.

[0089] The memory 510 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 510 includes one or more application programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516. The memory 510 may store, for use by the UE 500, any of a variety of various operating systems or combinations of operating systems.

[0090] The memory 510 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’ The memory 510 may allow the UE 500 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 510, which may be or comprise a device-readable storage medium.

[0091] The processing circuitry 502 may be configured to communicate with an access network or other network using the communication interface 512. The communication interface 512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 522. The communication interface 512 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 518 and / or a receiver 520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., the antenna 522) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0092] In the illustrated embodiment, communication functions of the communication interface 512 may include cellular communication, WiFi communication, LPWANcommunication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, 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 according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

[0093] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 512, 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).

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

[0095] A UE, when in the form of an IoT 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 IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voicecontrolled 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 head-mounted display for Augmented Reality (AR) or VR, 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 IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 500 shown in Figure 5.

[0096] As yet another specific example, in an IoT 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-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

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

[0098] Figure 6 shows a network node 600 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, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

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

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

[0101] The network node 600 includes processing circuitry 602, memory 604, a communication interface 606, and a power source 608. The network node 600 may be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which may each havetheir own respective components. In certain scenarios in which the network node 600 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 600 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 604 for different RATs) and some components may be reused (e.g., a same antenna 610 may be shared by different RATs). The network node 600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (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 the network node 600.

[0102] The processing circuitry 602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 600 components, such as the memory 604, to provide network node 600 functionality.

[0103] In some embodiments, the processing circuitry 602 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 602 includes one or more of Radio Frequency (RF) transceiver circuitry 612 and baseband processing circuitry 614. In some embodiments, the RF transceiver circuitry 612 and the baseband processing circuitry 614 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 the RF transceiver circuitry 612 and the baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units.

[0104] The memory 604 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, RAM, ROM, mass storagemedia (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 602. The memory 604 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 602 and utilized by the network node 600. The memory 604 may be used to store any calculations made by the processing circuitry 602 and / or any data received via the communication interface 606. In some embodiments, the processing circuitry 602 and the memory 604 are integrated.

[0105] The communication interface 606 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 606 comprises port(s) / terminal(s) 616 to send and receive data, for example to and from a network over a wired connection. The communication interface 606 also includes radio front-end circuitry 618 that may be coupled to, or in certain embodiments a part of, the antenna 610. The radio front-end circuitry 618 comprises filters 620 and amplifiers 622. The radio front-end circuitry 618 may be connected to the antenna 610 and the processing circuitry 602. The radio front-end circuitry 618 may be configured to condition signals communicated between the antenna 610 and the processing circuitry 602. The radio front-end circuitry 618 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 618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 620 and / or the amplifiers 622. The radio signal may then be transmitted via the antenna 610. Similarly, when receiving data, the antenna 610 may collect radio signals which are then converted into digital data by the radio front- end circuitry 618. The digital data may be passed to the processing circuitry 602. In other embodiments, the communication interface 606 may comprise different components and / or different combinations of components.

[0106] In certain alternative embodiments, the network node 600 does not include separate radio front-end circuitry 618; instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes the one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612 as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown).

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

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

[0109] The power source 608 provides power to the various components of the network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein. For example, the network node 600 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby theexternal power source supplies power to power circuitry of the power source 608. As a further example, the power source 608 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.

[0110] Embodiments of the network node 600 may include additional components beyond those shown in Figure 6 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 600 may include user interface equipment to allow input of information into the network node 600 and to allow output of information from the network node 600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 600. In some embodiments providing a core network node, such as core network node 108 of FIG.4, some components, such as the radio front-end circuitry 618 and the RF transceiver circuitry 612 may be omitted.

[0111] Figure 7 is a block diagram illustrating a virtualization environment 700 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 virtualization environments 700 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, a UE, a core network node, or a 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 700 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization mayfacilitate distributed implementations of a network node, a UE, a core network node, or a host.

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

[0113] Hardware 704 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, an input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 706 (also referred to as hypervisors or Virtual Machine Monitors (VMMs)), provide VMs 708A and 708B (one or more of which may be generally referred to as VMs 708), and / or perform any of the functions, features, and / or benefits described in relation with some embodiments described herein. The virtualization layer 706 may present a virtual operating platform that appears like networking hardware to the VMs 708.

[0114] The VMs 708 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 706. Different embodiments of the instance of a virtual appliance 702 may be implemented on one or more of VMs 708, 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.

[0115] In the context of NFV, a VM 708 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 708, and that part of the hardware 704 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 networkfunction is responsible for handling specific network functions that run in one or more VMs 708 on top of the hardware 704 and corresponds to the application 702.

[0116] The hardware 704 may be implemented in a standalone network node with generic or specific components. The hardware 704 may implement some functions via virtualization. Alternatively, the hardware 704 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 710, which, among others, oversees lifecycle management of the applications 702. In some embodiments, the hardware 704 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 712 which may alternatively be used for communication between hardware nodes and radio units.

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

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

[0119] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is representative, and that alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.

[0120] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

Claims What is claimed is:

1. A method performed by a first network node, the method comprising one or more of: sending (200), to a second network node, a request to activate one or more SSBs; and receiving (202), from the second network node, feedback on the request.

2. The method of claim 1 wherein: the request comprises a Cell Activation Request.

3. The method of claim 1 or 2 wherein: the request comprises characteristics such as SSB measurement relevant configurations, optionally including one or more of the SSB pattern, SSB rate, SSB window, and SSB type to achieve on-demand SSB adaptation.

4. The method of any one of claim 1 to 3 wherein: the SSB type comprises either cell defining vs non-cell—defining.

5. The method of any one of claim 1 to 4 wherein: the request comprises a Cell Activation Request.

6. The method of any one of claim 1 to 5 wherein: the request is determined based on a load situation of the first network node, the characteristic of UEs being served, the demand from the UEs, etc.

7. The method of any one of claim 1 to 6 wherein: the feedback on the request comprises a denial and optionally providing feedback indicating the possible / alternative SSB rate / pattern / periodicity the second network node could perform.

8. A first network node, the first network node comprising: processing circuitry configured to perform any of the steps of any one of claims 1 to 7; and power supply circuitry configured to supply power to the processing circuitry.

9. The first network node of claim 8 wherein: the first network node comprises any one of: a gNB; a first gNB-CU; a first gNB-DU; a second gNB-CU; and a second gNB- DU.

10. The first network node of claim 8 wherein: the first network node operates in a New Radio, NR, radio network.

11. A method performed by a second network node, the method comprising one or more of: receiving (300), from a first network node, a request to activate one or more SSBs; and sending (302), to the second network node, feedback on the request.

12. The method of claim 11 wherein: the request comprises a Cell Activation Request.

13. The method of claim 11 or 12 wherein: the request comprises characteristics such as SSB measurement relevant configurations, optionally including one or more of the SSB pattern, SSB rate, SSB window, and SSB type to achieve on-demand SSB adaptation.

14. The method of any one of claims 11 to 13 wherein: the SSB type comprises either cell defining vs non-cell—defining.

15. The method of any one of claims 11 to 14 wherein: the request comprises a Cell Activation Request.

16. The method of any one of claims 11 to 15 wherein: the request is determined based on a load situation of the network node, the characteristic of UEs being served, the demand from the UEs, etc.

17. The method of any one of claims 11 to 16 wherein: the feedback on the request comprises a denial and optionally providing feedback indicating the possible / alternative SSB rate / pattern / periodicity the second network node could perform.

18. A second network node, the second network node comprising: processing circuitry configured to perform any of the steps of any one of claims 11 to 17; and power supply circuitry configured to supply power to the processing circuitry.

19. The second network node of claim 18 wherein: the second network node comprises any one of: a gNB; a first gNB-CU; a first gNB-DU; a second gNB-CU; and a second gNB-DU.

20. The second network node of claim 18 wherein: the second network node operates in a New Radio, NR, radio network.

Images