Method for receiving of on-demand ssb

Abstract

Embodiments of the present disclosure relate to methods, devices and computer readable storage medium for communication of a synchronization signal block. In a method, a terminal device receives an on-demand synchronization signal block in first resource and receives a cell-defining synchronization signal block in second resources.

Description

METHOD FOR RECEIVING OF ON-DEMAND SSB This application claims the benefit of PCT application numbered PCT / CN2024 / 077619, filed 19 / 02 / 2024, the disclosure of which is hereby incorporated herein by reference in its entirety. TECHNICAL FIELD

[0001] The The present disclosure relates generally to telecommunication, and more particularly to on-demand SSB receiving and transmission. BACKGROUND Legacy SSB structure

[0002] The Rel-15 NR SSB consists of 4 OFDM symbols where symbols 1 and 3 carry PSS and SSS, respectively, and symbols 2-4 carry PBCH containing the MIB payload, as shown in Figure 1. Legacy MIB configuration

[0003] The Master Information Block (MIB) includes the system information transmitted from the NW on the BCH. Below is the MIB information element (IE) in ASN.1 format: MIB ::= SEQUENCE { systemFrameNumber BIT STRING (SIZE (6)), subCarrierSpacingCommon ENUMERATED {scs15or60, scs30or120}, ssb-SubcarrierOffset INTEGER (0..15), dmrs-TypeA-Position ENUMERATED {pos2, pos3}, pdcch-ConfigSIB1 PDCCH-ConfigSIB1, cellBarred ENUMERATED {barred, notBarred}, intraFreqReselection ENUMERATED {allowed, notAllowed}, spare BIT STRING (SIZE (1)) }

[0004] Where: MIB field descriptions cellBarred Value barred means that the cell is barred, as defined in TS 38.304

[0020] . This field is ignored by IAB-MT. This field is ignored for connectivity to NTN. …pdcch-ConfigSIB1 Determines a common ControlResourceSet (CORESET), a common search space and necessary PDCCH parameters. If the field ssb-SubcarrierOffset indicates that SIB1 is absent, the field pdcch-ConfigSIB1 indicates the frequency positions where the UE may find SS / PBCH block with SIB1 or the frequency range where the network does not provide SS / PBCH block with SIB1 (see TS 38.213

[0013] , clause 13). ssb-SubcarrierOffset Corresponds to kSSB (see TS 38.213

[0013] ), which is the frequency domain offset between SSB and the overall resource block grid in number of subcarriers. (See TS 38.211

[0016] , clause 7.4.3.1). For operation with shared spectrum channel access in FR1 (see 37.213

[0048] ), this field corresponds to k̅_"SSB" , and kSSB is obtained from k ̅_"SSB" (see TS 38.211

[0016] , clause 7.4.3.1); the LSB of this field is used also for deriving the QCL relation between SS / PBCH blocks as specified in TS 38.213

[0013] , clause 4.1. The value range of this field may be extended by an additional most significant bit encoded within PBCH as specified in TS 38.213

[0013] . This field may indicate that this cell does not provide SIB1 and that there is hence no CORESET#0 configured in MIB (see TS 38.213

[0013] , clause 13). In this case, the field pdcch-ConfigSIB1 may indicate the frequency positions where the UE may (not) find a SS / PBCH with a control resource set and search space for SIB1 (see TS 38.213

[0013] , clause 13). subCarrierSpacingCommon Subcarrier spacing for SIB1, Msg.2 / 4 and MsgB for initial access, paging and broadcast SI- messages. If the UE acquires this MIB on an FR1 carrier frequency, the value scs15or60 corresponds to 15 kHz and the value scs30or120 corresponds to 30 kHz. If the UE acquires this MIB on an FR2 carrier frequency, the value scs15or60 corresponds to 60 kHz and the value scs30or120 corresponds to 120 kHz. For operation with shared spectrum channel access in FR1 (see 37.213

[0048] ) and for operation in FR2-2, the subcarrier spacing for SIB1, Msg.2 / 4 and MsgB for initial access, paging and broadcast SI-messages is same as that for the corresponding SSB. For operation with shared spectrum channel access, this field instead is used for deriving the QCL relation between SS / PBCH blocks as specified in TS 38.213

[0013] , clause 4.1. …

[0005] There is one spare bit available on the MIB that can be used for future purposes.

[0006] The IE PDCCH-ConfigSIB1 (see IE below) within the MIB is used to configure CORESET#0 and search space#0. PDCCH-ConfigSIB1 ::= SEQUENCE { controlResourceSetZero ControlResourceSetZero, searchSpaceZero SearchSpaceZero }

[0007] Where: PDCCH-ConfigSIB1 field descriptions controlResourceSetZero Determines a common ControlResourceSet (CORESET) with ID #0, see TS 38.213

[0013] , clause 13. searchSpaceZero Determines a common search space with ID #0, see TS 38.213

[0013] , clause 13.

[0008] The ssb-SubcarrierOffset described above within the MIB defines the 4 LSB (Least Significant Bits) of the subcarrier offset (Kssb) with value range 0..11 in FR2 and 0..23 in FR1. In case of FR1, since 5 bits are needed to convey Kssb, a 5th bit is included in the PBCH payload. Whether a cell contains SIB1 (aka RMSI or Type0-PDCCH CSS) is given by ssb- SubcarrierOffset. Only if ssb-SubcarrierOffset < 24 (for FR1) or if ssb-SubcarrierOffset < 12 (for FR2), the pdcch-ConfigSIB1 indicates the PDCCH configuration for SIB1 reception on the same cell (see 3GPP 38.211, section 7.4.3.1). SIB1 missing in a cell

[0009] If a SIB1 is not transmitted in a cell, the existing specifications state that a UE shall treat a cell not providing SIB1 as barred. The UE shall: 1> if in RRC_IDLE or in RRC_INACTIVE or in RRC_CONNECTED while T311 is running: 2> if the UE is unable to acquire the MIB: … 2> else if the UE is unable to acquire the SIB1:3> consider the cell as barred in accordance with TS 38.304

[0020] ;

[0010] In legacy NR scenarios, SSBs are typically configured statically, with e.g. 20 ms period and Legacy SSBs and NW coverage

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

[0012] 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, or based on a UE requesting them. On-demands SSBs may also be one-shot transmissions or limited-duration SSB bursts, without a recurrent structure. They may be transmitted at the same or at a different power level and spatial configuration than the baseline SSB.

[0013] Some scenarios where on-demand SSBs are expected to be useful include: • Scell quality measurements upon Scell configuration • Synchronization upon Scell activation • Timing / Frequency tracking for an active serving cell • RRM measurements on serving or neighbor cells • L1-RSRP / RLM / BFD / CBD measurements on serving cell • Preparation for PO monitoring and paging reception • Preparation for UL access using PRACH • Etc.

[0014] There currently exist certain challenge(s).

[0015] Legacy UEs cannot be informed about the new on-demand SSB provision frameworks. When on-demand SSBs are activated for advanced UEs, these SSBs may also be detected by legacy UEs. However, these UEs are not aware of the temporary nature of on- demand SSBs. If the cell is configured with a certain baseline SSB period, say X ms, a legacy UE detecting an on-demand SSB at a certain time and frequency resource would expect that SSB will be available again in same resources X ms later. If the SSB is then not available, the UE may not be able to perform necessary operations due to e.g. not being able to sync in time before signal reception.

[0016] Even more severely, a UE detecting an on-demand SSB transmitted at a higher power may assume NW coverage at a certain location. If the baseline SSB power is lower, or the period is longer, the UE may not be able to access the NW in an emergency, leading to life- threatening situations and operator liability.

[0017] To ensure predictable SSB availability and consistent coverage experience to legacy UEs, there is a need for new on-demand SSB transmission schemes. These SSBs must be structurally sufficiently similar to legacy SSBs to allow substantial reuse of existing reception HW and algorithms, but they cannot be inadvertently interpreted as valid baseline SSBs by legacy UEs attempting initial access.

[0018] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.

[0019] On-demand SSB transmission is modified compared to legacy cell-defining SSBs (CD-SSBs). They are transmitted using transmission resources, information contents, or signal structures not recognized by legacy UEs, or not leading legacy UEs to assume presence of additional CD-SSBs.

[0020] Types of proposed modifications or configuration measures include: • Non-GSCN-raster frequency resources (frequency-hiding) • Reserved timing resources (time-hiding) • Lack of associated SIB1, or unusable SIB1 pointer • Other modifications to MIB structure • Using NCD-SSB structure • Modified PSS, SSS, or PBCH DMRS sequences • BWP differentiation (e.g. for connected mode operation) • Sub-20-ms OD-SSB may also be frequency aligned with 20-ms CD-SSB

[0021] The present disclosure presents methods for avoiding that legacy UEs interpret on- demand SSBs as baseline SSBs.

[0022] Certain embodiments may provide one or more of the following technical advantage(s).

[0023] According to one aspect of the present disclosure, a method performed by an advanced UE is provided which includes: receiving SSB configuration from a NB and then receiving a CD-SSB from a secondary cell according to the configuration. The configuration also includes resources for OD-SSB which are not located on frequency resources of a GSCN raster.

[0024] According to one aspect of the present disclosure, a method performed by a network node serving a cell includes: transmitting an SSB configuration in the cell, and transmitting CD-SSBs according to the SSB configuration. The SSB configuration also includes resources for OD-SSBs which are not located on frequency resources of a GSCN raster.

[0025] According to one aspect of the present disclosure, a terminal device (UE) is provided including a processor and a memory which containing instructions executable by the processor, so that the UE is operative to perform any method UE embodiment disclosed herein.

[0026] According to one aspect of the present disclosure, a network node (NB) serving a cell including a processor and a memory which containing instructions executable by the processor and a memory which containing instructions executable by the processor, so that the NB is operative to perform any method NB embodiment disclosed herein .

[0027] Besides the advanced UE can receive both on-demand SSBs and cell-defined SSBs, legacy UEs do not react to the presence of on-demand SSBs and do not develop any assumptions about these SSB being available at a later time. This avoids erroneous scheduling of processing steps for signal reception and transmission, ensuring robust functioning of legacy UEs. Erroneous assumptions about cell coverage and perceived coverage fluctuations are also avoided. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 shows an SSB structure according to background of the present disclosure.

[0029] Figure 2 illustrates an example of frequency and time positions of CD SSB and OD SSB resources according to some embodiments of the present disclosure.

[0030] Figure 3 illustrates another example of frequency and / or time positions of CD SSB and OD SSB resources according to some embodiments of the present disclosure.

[0031] Figure 4 is a functional block diagram illustrating an example of a communication system including an access network and terminal devices according to some embodiments of the present disclosure.

[0032] Figure 5 is a functional block diagram illustrating some components of a termindal device configured to receive SSBs in order to perform communication according to some embodiments of the present disclosure.

[0033] Figure 6 is a functional block diagram illustrating some components of a network node configuring a terminal device for SSB reception in order to perform communication according to some embodiments of the present disclosure.

[0034] Figure 7 is a flow diagram illustrating a method, implemented by a terminal devcie, for receiving a cell-defined SSB and an on-demand SSB from an SCell according to some embodiments of the present disclosure.

[0035] Figure 8 is a flow diagram illustrating a method, implemented by a network node, for configuring and transmitting cell-defined SSBs and on-demand SSBs according to some embodiments of the present disclosure. DETAILED DESCRIPTION

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

[0037] It is important that the on-demand SSB provision does not impact the perceived idle mode coverage, which would be the case if on-demand SSB transmissions were mistakenly interpreted as CD-SSBs that the UE is allowed to camp on. Without a careful design, on- demand SSBs would confuse a legacy UE in idle mode, and possibly also in connected mode operations.

[0038] The following embodiments presume that an advanced UE has been configured with appropriate on-demand SSB (OD-SSB) resources and it does not need to determine whether a given SSB is an OD-SSB. The solutions thus focus on the objective of hiding OD- SSBs from legacy UEs and not on enabling advanced UEs to identify them as such. In the following, multiple SSB modification categories are presented that may be used for that purpose. Combinations of two or more of the listed options / categories may also be used.

[0039] According to some embodiments of the present disclosure, a method performed by an advanced UE is provided as shown by Figure 7 which includes: receiving SSBconfiguration from a NB and then receiving a CD-SSB from a secondary cell according to the configuration. The configuration also includes resources for OD-SSB which are not located on frequency resources of a GSCN raster.

[0040] In a further embodiment, the configuration comprises SMTC dedicated for OD- SSBs. In a further embodiment, the SMTC indicates a shorter time window than that of a SMTC for CD-SSBs.

[0041] In another embodiment, the advanced UE determines whether the configured resources for CD-SSBs overlap with those for OD-SSBs. If at least a part is overlapping, the advanced UE skip receiving the OD-SSB transmitted on the overlapped resources.

[0042] In another embodiment, after receiving the OD-SSB, the advanced UE performs SCell related activities, such as receiving downlink data, SCell activation, or inter / intra- frequency hopping to the SCell.

[0043] According to some embodiments of the present disclosure, a method performed by a network node serving a cell as shown in Figure 8 includes: transmitting an SSB configuration in the cell, and transmitting CD-SSBs according to the SSB configuration. The SSB configuration also includes resources for OD-SSBs which are not located on frequency resources of a GSCN raster.

[0044] In a further embodiment, the SSB configuration also includes SMTC dedicated for the OD-SSBs which indicates a shorter time window that that of a SMTC configured for the CD-SSBs.

[0045] In another embodiment, the resources configured for the OD-SSBs locate in an initial DL BWP of the cell or in another BWP extending outside of the initial BWP of the cell.

[0046] In another embodiment, the network node determines whether the resources configured for OD-SSBs and CD-SSBs are at least partial overlapping. If yes, the network node does not transmit OD-SSBs on the overlapping resource. Non-GSCN-raster frequency resources (frequency-hiding)

[0047] In one embodiment, the OD-SSB are transmitted at frequencies that are not on the global synchronization channel number, GSCN, search raster. The internal structure of the OD- SSB may be similar to a legacy SSB but since they are off the initial search raster, idle mode UEs will not find them.

[0048] An advanced UE, utilizing such OD-SSB, may frequency-hop between the legacy and OD-SSB occasions. The frequency locations are preferably configured within the carrier / cell BW, and the UE may separate narrow time-varying frequency regions in time or frequency domain for further correlation processing.Reserved timing resources (time-hiding)

[0049] In one embodiment, the OD-SSB may be placed at time locations that are implicitly or explicitly defined as reserved resources. The UE may be provided info about the reserved resources, where it should not be performing initial search or other legacy SSB reception, via NW signaling, e.g. as part of SI broadcast or via dedicated RRC signaling. The reserved resource info may also be used by the UE for rate matching around these regions in case of PDSCH reception.

[0050] The provided reserved resource configuration may apply to the current cell, additional neighbor cells, a region of the NW, or the entire NW. The UE may thus receive advance info for relevant parts of the NW once it has connected to or camped on a cell in the NW.

[0051] In another embodiment, when NW configures the MeasObjectNR to UE, it can include onDemandSMTC which can only be identified by advanced UE supporting the Rel-19 NES feature. Normally, the onDemandSMTC is shorter than the legacy SS / PBCH Block Measurement Timing Configuration 1 (SMTC1), SMTC2. Legacy UE will perform measurements based on SMTC configuration, but the advanced UE can use the onDemandSMTC to perform measurement.

[0052] In another embodiment, the NW may avoid transmitting the OD-SSB for those slots and symbols mentioned in 38.213 section 4.1 for cell search. The specs in 38.213 mentioned how to detect the first symbols and succeeding symbols of SSBs depending on numerology. The NW may transmit the OD-SSB in the symbols and slots that are not included in the cell search so that legacy UEs will not be able to detect it. If ever legacy UEs will detect one of the OD-SSB and decode the PBCH DMRS, the legacy UE will ignore it because SSB index and half frame information are different from the specs or it may not be conveyed as mentioned in modified PBCH-DMRS section of this IvD. OD-SSB is frequency aligned with CD-SSB for the case when CD-SSB is present

[0053] In one embodiment, for the case when CD-SSB is already present in a configured serving cell (and, possibly, used for initial access), the OD-SSB are not hidden. Instead, to prevent legacy UE from locking on to an incorrect SSB frequency (GSCN value), the OD-SSB is frequency aligned with the CD-SSB. Therefore, in one embodiment, the OD-SSB is configured with an absolute radio frequency channel number, ARFCN, value that is equal to the ARFCN value of the CD-SSB (e.g., as configured by higher-layer parameter absoluteFrequencySSB in downlinkConfigCommon in ServingCellConfigCommon IE). In oneembodiment, the OD-SSB is explicitly configured with said ARFCN value. In an alternate embodiment, the OD-SSB inherits the ARFCN value configured for the SCell.

[0054] Clause 4.1 of 3GPP TS 38.213 states the following: “For initial cell selection, a UE may assume that half frames with SS / PBCH blocks occur with a periodicity of 2 frames”. Hence, as long as CD-SSB is configured with a periodicity that is smaller than or equal to 2 frames (i.e., 20 ms) the UE would still be able to perform initial access even if SSB is occasionally transmitted at a higher rate.

[0055] Legacy NW nodes using large antenna arrays may configure CD-SSBs such that there is a large number of SSB transmissions (beams) within an SSB burst (e.g., configured by field ssb-PositionsInBurst in ServingCellConfigCommon). Without OD-SSB, to support beam sweeping, the NW has to configure a large number of beams for CD-SSB, which consumes large overhead. With OD-SSB, on the other hand, CD-SSB may be configured with a smaller number, e.g., 1, of SSB beams within an SSB burst, and the NW-side Tx spatial filter of said SSB beam may be a broad beam for one or more UEs to perform, e.g., RRM measurements on. On the contrary, the OD-SSB may be configured with a larger number, e.g., 32, of beams within an SSB burst, where the NW-side Tx spatial filter of each said beam within an SSB burst may be a narrow beam. In this way, NW can use (dense) OD-SSB only for beam refinement and (sparse) CD-SSB for other purposes, which reduces NW overhead compared to legacy behavior as the best Tx spatial filter is expected to change at a time scale that is significantly longer than CD-SSB periodicity.

[0056] Another benefit with this approach is for potentially faster SCell activation. E.g., CD-SSB of 20 ms periodicity may be complemented with OD-SSB of 5 ms periodicity during, e.g., SCell activation, for providing more measurement opportunities to UE(s). On example of this is shown in Figure 2.

[0057] Figure 2 shows OD-SSB on same frequency as CD-SSB, for the case when CD- SSB is present in the cell. Note that there could be multiple SSB transmissions within each SSB burst set.

[0058] In one embodiment, if OD-SSB overlaps with CD-SSB, the OD-SSB is not transmitted.

[0059] In one embodiment, the payload of the OD-SSB is the same as the payload of the CD-SSB. BWP differentiation

[0060] In one embodiment, the OD-SSB is contained within a configured BWP of an SCell.

[0061] In one embodiment, the OD-SSB may be e.g. not on the GSCN raster but contained in the initial (DL) BWP of the SCell, e.g. to facilitate joint reception of CD-SSB and OD-SSB that may include narrow-band receiver hopping. The main benefit with this approach is that on-demand SSB may be used mainly for SCell activation, and initial BWP is the BWP that UE will use after SCell activation. Hence, UE can measure SSB transmissions in the same bandwidth and with the same numerology as it will use for receiving other DL transmissions during / after SCell activation. In one embodiment, the initial BWP in an SCell for a UE configured with on-demand SSB is different from the initial BWP in an SCell for a UE not configured with on-demand SSB.

[0062] In one embodiment, the NW may configure advanced UEs with a second BWP that extends outside the default BWP used by legacy UEs. In one embodiment, the OD-SSBs may be placed in the part of the second BWP that does not overlap with the default BWP. This option may be used to ensure OD-SSB hiding from legacy UEs in connected mode operation.

[0063] In one example, NW configures CD-SSB as a sparse periodicity for both legacy UEs and advanced UEs access in. When the advanced UEs need to perform procedures with high rate SSB transmission, NW will indicate BWP switching to the dedicated BWP with on- demand SSB transmission for the advanced UEs.

[0064] Figure 3 shows normal SSB transmission in initial BWP with OD-SSB in dedicated BWP.

[0065] In one embodiment, the frequency position of the OD-SSB is configured via an ARFCN value (i.e., on the NR-ARFCN grid).

[0066] In another embodiment, the frequency position of the OD-SSB is relative to the edge of the dedicated BWP. In one example, the OD-SSB is configured with at least one of a resource block offset and a resource element offset from the BWP edge (i.e., the first resource element of the first resource block within the BWP). No associated SIB1

[0067] In one embodiment, SIB1 is not provided in association with the OD-SSB. As per the 3GPP specification, if unable to acquire SIB1, a legacy UE considers the cell as barred and will not attempt access.

[0068] In one example, the ssb-SubcarrierOffset parameter in the MIB may be used to indicate that the cell does not provide SIB1, based on legacy signaling. The pdcch-ConfigSIB1 parameter may then further be used to indicate the location of a legacy CD-SSB for this NW.

[0069] In another example, the value of ssb-SubcarrierOffset may be set to a reserved value (e.g., Kssb=30 in FR1 and Kssb=14 in FR2). In a related example, the pdcch-ConfigSIB1value may be set to a reserved value, if there are reserved values defined for the current SCS configuration. A legacy UE during initial search then realizes that a valid SIB1 configuration is not provided.

[0070] In another example, the NW may configure the MIB contents so that the SIB1 reception-related parameters (pdcch-ConfigSIB1, Kssb / ssb-SubcarrierOffset, etc.) appear valid but point to a location with no SIB1 and thus result in unsuccessful SIB1 reception. A legacy UE during initial search then experiences SIB1 reception failure and moves on to test a next potential legacy SSB location. NCD-SSB structure

[0071] In one embodiment, the OD-SSBs are configured as NCD-SSBs. This may be equivalent to combining one or more above mentioned options, e.g. off-raster frequency location, and no associated SIB1 signaled via ssb-SubcarrierOffset.

[0072] OD-SSBs implemented as an NCD-SSB should preferably not be possible to detect by mistake by an idle mode UE searching for CD-SSBs. Preferably, the cell uses NCD-SSBs that are placed off the idle mode search grid. If the cell uses OD-SSB locations on the GSCN raster, the UE will perform additional processing to attempt SIB1 detection, which, while functionally not problematic, may reduce UE energy efficiency and increase search latency. Other modified MIB contents

[0073] In one embodiment, existing MIB contents are otherwise modified, compared to what is expected by a legacy UE, to indicate that the received SSB (OD-SSB) is not feasible for access, e.g. since SSB location wrt. the carrier is not properly defined, SIB1 resources are not defined, or MIB parameter values constitute incompatible combinations.

[0074] (Note that the spare bit cannot be used for signaling towards legacy UEs since they are not checking it, and there is no associated indication defined.) Modified PSS

[0075] In one embodiment, the PSS sequence of the OD-SSB is modified compared to legacy SSBs. In Rel-15 SSB design, the 3 PSS sequences are defined as follows:

[0076] Ina PSS using different initial conditions, or using different cyclic shift values, or different recursion coefficients for x(i) creation, etc.

[0077] The modified PSS sequences may be designed so as to maintain low cross- correlation properties wrt. the legacy sequences. Modified SSS

[0078] In one embodiment, the SSS sequence of the OD-SSB is modified compared to legacy SSBs. In Rel-15 SSB design, the 336 SSS sequences are defined as follows:using different initial conditions, or using different cyclic shift values, or different recursion coefficients for x(i) creation, etc.

[0080] The modified SSS sequences may be designed so as to maintain low cross- correlation properties wrt. the legacy sequences. Modified PBCH-DMRS

[0081] In one embodiment, the PBCH-DMRS sequence of the OD-SSB is modified compared to legacy SSBs. In Rel-15 SSB design, the PBCH DMRS sequences are defined as follows:

[0082] In one example, the modified DMRS may be created by generating the DMRS sequence using different initialization cinit. Alternatively, a fixed sequence not included in Rel- 15 sequence possibilities may be used for all OD-SSBs since the SSB index and half-frame information may need not be conveyed in these SSBs.

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

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

[0085] 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 anO-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 or indirect 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.

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

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

[0088] 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 Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security EdgeProtection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

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

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

[0091] In some examples, the telecommunication network 402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications 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 telecommunications network 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 IoT services to yet further UEs.

[0092] 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-RAT or multi-standard mode. Forexample, 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).

[0093] In the example, the 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 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 adding additional 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.

[0094] 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 an 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 network node 410b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0095] 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 IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, 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 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

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

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

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

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

[0101] The memory 510 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 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 maystore, for use by the UE 500, any of a variety of various operating systems or combinations of operating systems.

[0102] 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 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 (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘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.

[0103] 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., antenna 522) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0104] In the illustrated embodiment, communication functions of the communication interface 512 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 beimplemented 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.

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

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

[0107] A UE, when in the form of an Internet of Things (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 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 head-mounted display for Augmented Reality (AR) or Virtual Reality (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 inthe 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.

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

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

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

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

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

[0113] The network node 600 includes a processing circuitry 602, a 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 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 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 radio access technologies (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, 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 600.

[0114] The processing circuitry 602 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 600 components, such as the memory 604, to provide network node 600 functionality.

[0115] 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 radio frequency (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 RF transceiver circuitry 612 and baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units.

[0116] 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, 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 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 memory 604 is integrated.

[0117] 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. Radio front-end circuitry 618 comprises filters 620 and amplifiers 622. The radio front-end circuitry 618 may be connected to an antenna 610 and processing circuitry 602. The radio front-end circuitry may be configured to condition signals communicated between antenna 610 and 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 filters 620 and / or 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 may comprise different components and / or different combinations of components.

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

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

[0120] The antenna 610, 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. 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. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0121] The power source 608 provides power to the various components of 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, 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 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.

[0122] Although the computing devices described herein (e.g., UEs, network nodes, hosts) 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.

[0123] 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.EMBODIMENTS Group A Embodiments 1. A method performed by a first terminal device for reception of a synchronization signal block, the method comprising: receiving a first synchronization signal block in first resources; and receiving a second synchronization signal block in second resources. 2. The method of embodiment 1, wherein the first synchronization signal block comprises an on-demand synchronization signal block, and the second synchronization signal block comprises a cell-defining synchronization signal block. 3. The method of embodiment 1 or 2, wherein the first resources exclude frequency resources on a global synchronization channel number, GSCN, raster. 4. The method of embodiment 3, wherein the first synchronization signal block and the second synchronization signal block are received by frequency-hopping. 5. The method of embodiment 3 or 4, wherein the first resources include frequency resources located within at least one of a carrier bandwidth or a cell bandwidth. 6. The method of any of embodiments 3 to 5, wherein the first resources include separated narrow time-varying frequency regions in at least one of a time domain or a frequency domain. 7. The method of embodiment 1 or 2, wherein the first resources include reserved time resources. 8. The method of embodiment 7, wherein the reserved time resources are associated with at least one of a current cell, one or more neighbor cells, a region of a network or a network. 9. The method of embodiment 7 or 8, wherein the reserved time resources include symbols and / or slots unavailable for cell search.10. The method of any of embodiments 7 to 9, further comprising: receiving a measurement timing configuration for the first synchronization signal block, a length of the measurement timing configuration being shorter than a threshold, wherein the first synchronization signal block is received by performing measurements based on the measurement timing configuration. 11. The method of embodiment 10, wherein the measurement timing configuration comprises a synchronization signal, SS, physical broadcast channel, PBCH, block measurement timing configuration. 12. The method of embodiment 1 or 2, wherein the first resources are frequency-aligned with the second resources. 13. The method of embodiment 12, wherein a value of a first frequency channel number associated with the first resources is equal to a value of a second frequency channel number associated with the second resources. 14. The method of embodiment 12, further comprising: receiving a configuration of a value of a first frequency channel number associated with the first resources. 15. The method of embodiment 12, wherein a first frequency channel number associated with the first resources is equal to a value of a third frequency channel number configured for a secondary cell. 16. The method of any of embodiments 13 to 15, wherein the frequency channel number comprises an absolute radio frequency channel number, ARFC. 17. The method of embodiment 12, wherein receiving the second synchronization signal block comprises: receiving a first bust of the first synchronization signal with a number of first beams, the number of first beams being greater than a threshold. 18. The method of embodiment 17, wherein a width of the first beam is narrower than athreshold. 19. The method of embodiment 12, wherein receiving the second synchronization signal block comprises: receiving a second burst of the second synchronization signal with a number of second beams, the number of second beam being less than a threshold. 20. The method of embodiment 19, wherein a width of the second beam is broader than a threshold. 21. The method of embodiment 12, wherein one or more first synchronization signals are received between two second synchronization signals. 22. The method of embodiment 21, further comprising: in accordance with a determination that the synchronization signal overlaps with the second synchronization signal, skipping reception of the first synchronization signal. 23. The method of embodiment 21, wherein payload of the first synchronization signal is the same as payload of the second synchronization signal. 24. The method of embodiment 1 or 2, wherein the first frequency resources are contained within a bandwidth part configured for a secondary cell. 25. The method of embodiment 24, wherein the first resources exclude frequency resources on a global synchronization channel number, GSCN, raster and include frequency resources contained in a first initial bandwidth part of the secondary cell. 26. The method of embodiment 25, wherein the first initial bandwidth in the secondary cell for the first terminal device is different from a second initial bandwidth in a secondary cell for a second terminal device configured with no first synchronization signal. 27. The method of embodiment 26, wherein the first initial bandwidth extends outside the second initial bandwidth.28. The method of embodiment 27, wherein the first synchronization signal is received in a part of the first initial bandwidth, the part of the first initial bandwidth being non-overlapping with the second initial bandwidth. 29. The method of embodiment 1 or 2, wherein a first periodicity of the first synchronization signal block is shorter than a second periodicity of the second synchronization signal block, and the first synchronization signal block is received on a dedicated bandwidth part. 30. The method of embodiment 29, wherein a frequency position of the first synchronization signal block is configured via a value of absolute radio frequency channel number. 31. The method of embodiment 29, wherein a frequency position of the first synchronization signal block is indicated with an offset with respect to an edge of the dedicated bandwidth part. 32. The method of embodiment 31, wherein the offset comprises at least one of a resource block offset or a resource element block. 33. The method of embodiment 1 or 2, wherein no system information block is provided in association with the first synchronization signal block. 34. The method of embodiment 1 or 2, further comprising: receiving, in a master information block, a first indication that no system information block is provided in a cell; and receiving, in the master information block, a second indication of a resource location of the second synchronization signal block. 35. The method of embodiment 34, wherein the first indication is carried in a first parameter indicating a subcarrier offset, a value of the first parameter be set as a reserved value; and / or the second indication is carried in a second parameter indicating a physical downlink control channel configuration, a value of the second be set as a reserved value. 36. The method of embodiment 1 or 2, wherein a valid parameter related to reception of asystem information block is pointing to a resource location with no system information block. 37. The method of embodiment 36, wherein receiving the second synchronization signal block comprises: receiving the second synchronization signal block in a potential resource location of the second synchronization signal block, based on reception of a system information block being failed. 38. The method of embodiment 1 or 2, wherein the first synchronization signal block is configured as a non-cell-defining synchronization signal block. 39. The method of embodiment 1 or 2, wherein a first signal sequence of the first synchronization signal block is different from a second signal sequence of the second synchronization signal block. 40. The method of embodiment 39, wherein the first signal sequence is generated using at least one of: a different initial condition from an initial condition for generating the second signal sequence of the second synchronization signal block; a different cyclic shift value from a cyclic shift value for generating the second signal sequence; or a different recursion coefficient from a recursion coefficient for generating the second signal sequence. 41. The method of embodiment 39, wherein the first signal sequence is designed to maintain first cross-correlation properties, the first cross-correlation properties being lower than a second first cross-correlation properties of the second signal sequence. 42. The method of any of embodiments 39 to 41, where the signal sequence comprises at least one of a primary synchronization signal, a secondary synchronization signal sequence. 43. The method of embodiment 39 or 40, wherein the signal sequence comprises a demodulation reference signal sequence.44. The method of embodiment 43, wherein the demodulation reference signal sequence comprises a fixed signal sequence excluded from a predefined set of candidate signal sequences, the fixed sequence excluding a synchronization signal block index and half-frame information. 45. The method of any of embodiments 1 to 44, wherein the first terminal device is configured with the first synchronization signal block. 46. The method of any of embodiments 1 to 45, wherein the synchronization signal block comprises a synchronization signal, SS, physical broadcast channel, PBCH, block. Group B Embodiments 47. A method performed by a second terminal device for reception of a synchronization signal block, the method comprising: receiving a second synchronization signal block in second resources. 48. The method of embodiment 47, further comprising: receiving, from a network device, information about first resources for a first synchronization signal block. 49. The method of embodiment 48, wherein the information is received via at least one of system information or dedicated signaling. 50. The method of embodiment 48 or 49, wherein the first resources include reserved time resources. 51. The method of embodiment 50, wherein the reserved time resources are associated with at least one of a current cell, one or more neighbor cells, a region of a network or a network. 52. The method of any of embodiments 48 to 51, wherein the second resources exclude the first resources. 53. The method of any of embodiments 48 to 52, further comprising: performing rate matching using the first resources, for data reception.54. The method of any of embodiments 48 to 53, wherein the reserved time resources include symbols and / or slots unavailable for cell search. 55. The method of embodiment 47, the second resources are frequency-aligned with first resources for a first synchronization signal block. 56. The method of embodiment 55, wherein a value of a first frequency channel number associated with the first resources is equal to a value of a second frequency channel number associated with the second resources. 57. The method of embodiment 56, wherein a first frequency channel number associated with the first resources is equal to a value of a third frequency channel number configured for a secondary cell. 58. The method of embodiment 57, wherein the frequency channel number comprises an absolute radio frequency channel number, ARFC. 59. The method of embodiment 55, wherein receiving the second synchronization signal block comprises: receiving a second burst of the second synchronization signal with a number of second beams, the number of second beam being less than a threshold. 60. The method of embodiment 59, wherein a width of the second beam is broader than a threshold. 61. The method of embodiment 47, wherein the first resources are contained within a configured bandwidth part of a secondary cell. 62. The method of embodiment 47, further comprising receiving, in a master information block, a first indication that no system information block is provided in a cell; and receiving, in the master information block, a second indication of a resource location of the second synchronization signal block.63. The method of embodiment 62, wherein the first indication is carried in a first parameter indicating a subcarrier offset, a value of the first parameter be set as a reserved value. 64. The method of embodiment 63, wherein the second indication is carried in a second parameter indicating a physical downlink control channel configuration, a value of the second be set as a reserved value. 65. The method of embodiment 47, wherein a valid parameter related to reception of a system information block is pointing to a resource location with no system information block. 66. The method of embodiment 65, wherein receiving the second synchronization signal block comprises: receiving the second synchronization signal block in a potential resource location of the second synchronization signal block, based on reception of a system information block being failed. 67. The method of embodiment 47, wherein a first synchronization signal block is configured as a non-cell-defining synchronization signal block. 68. The method of embodiment 47, wherein a parameter in a master information block is reused to indicate that a received first synchronization signal block is unfeasible for cell access. 69. The method of embodiment 68, wherein the parameter indicates at least one of: a carrier for the received first synchronization signal block being improperly defined, resources of a system information block being undefined, or values of parameters in the master information block constituting incompatible combinations. 70. The method of embodiment 47, wherein a first signal sequence of a first synchronization signal block is different from a second signal sequence of the second synchronization signal block.71. The method of embodiment 70, wherein the first signal sequence is generated using at least one of: a different initial condition from an initial condition for generating the second signal sequence of the second synchronization signal block; a different cyclic shift value from a cyclic shift value for generating the second signal sequence; or a different recursion coefficient from a recursion coefficient for generating the second signal sequence. 72. The method of embodiment 70, wherein the first signal sequence is designed to maintain first cross-correlation properties, the first cross-correlation properties being lower than a second first cross-correlation properties of the second signal sequence. 73. The method of any of embodiments 70 to 72, where the signal sequence comprises at least one of a primary synchronization signal, a secondary synchronization signal sequence. 74. The method of embodiment 70 or 71, wherein the signal sequence comprises a demodulation reference signal sequence. 75. The method of embodiment 74, wherein the demodulation reference signal sequence comprises a fixed signal sequence excluded from a predefined set of candidate signal sequences, the fixed sequence excluding a synchronization signal block index and half-frame information. 76. The method of any of embodiment 48 to 75, wherein the first synchronization signal block comprises an on-demand synchronization signal block, and the second synchronization signal block comprises a cell-defining synchronization signal block. 77. The method of any of embodiments 48 to 76, wherein the second terminal device is configured with no first synchronization signal block. 78. The method of any of embodiments 48 to 77, wherein the synchronization signal block comprises a synchronization signal, SS, physical broadcast channel, PBCH, block.Group C Embodiments 79. A method performed by a network device for transmission of a synchronization signal block, the method comprising: transmitting a first synchronization signal block in first resources; and transmitting a second synchronization signal block in second resources. 80. The method of embodiment 79, wherein the first synchronization signal block comprises an on-demand synchronization signal block, and the second synchronization signal block comprises a cell-defining synchronization signal block. 81. The method of embodiment 79 or 80, wherein the first resources exclude frequency resources on a global synchronization channel number, GSCN, raster. 82. The method of embodiment 81, wherein the first resources include frequency resources located within at least one of a carrier bandwidth or a cell bandwidth. 83. The method of embodiment 81 or 82, wherein the first resources include separated narrow time-varying frequency regions in at least one of a time domain or a frequency domain. 84. The method of embodiment 79 or 80, wherein the first resources include reserved time resources. 85. The method of embodiment 84, wherein the reserved time resources are associated with at least one of a current cell, one or more neighbor cells, a region of a network or a network. 86. The method of embodiment 84 or 85, wherein the reserved time resources include symbols and / or slots unavailable for cell search. 87. The method of any of embodiments 84 to 86, further comprising: transmitting a measurement timing configuration for the first synchronization signal block, a length of the measurement timing configuration being shorter than a threshold. 88. The method of embodiment 87, wherein the measurement timing configuration comprises a synchronization signal, SS, physical broadcast channel, PBCH, block measurement timingconfiguration. 89. The method of embodiment 79 or 80, wherein the first resources are frequency-aligned with the second resources. 90. The method of embodiment 89, wherein a value of a first frequency channel number associated with the first resources is equal to a value of a second frequency channel number associated with the second resources. 91. The method of embodiment 89, further comprising: transmitting a configuration of a value of a first frequency channel number associated with the first resources. 92. The method of embodiment 89, wherein a first frequency channel number associated with the first resources is equal to a value of a third frequency channel number configured for a secondary cell. 93. The method of any of embodiments 90 to 92, wherein the frequency channel number comprises an absolute radio frequency channel number, ARFC. 94. The method of embodiment 89, wherein receiving the second synchronization signal block comprises: transmitting a first bust of the first synchronization signal with a number of first beams, the number of first beams being greater than a threshold. 95. The method of embodiment 94, wherein a width of the first beam is narrower than a threshold. 96. The method of embodiment 89, wherein receiving the second synchronization signal block comprises: transmitting a second burst of the second synchronization signal with a number of second beams, the number of second beam being less than a threshold. 97. The method of embodiment 96, wherein a width of the second beam is broader than athreshold. 98. The method of embodiment 89, wherein one or more first synchronization signals are transmitted between two second synchronization signals. 99. The method of embodiment 98, wherein payload of the first synchronization signal is the same as payload of the second synchronization signal. 100. The method of embodiment 79 or 80, wherein the first frequency resources are contained within a bandwidth part configured for a secondary cell. 101. The method of embodiment 100, wherein the first resources exclude frequency resources on a global synchronization channel number, GSCN, raster and include frequency resources contained in a first initial bandwidth part of the secondary cell. 102. The method of embodiment 101, wherein the first initial bandwidth in the secondary cell for the first terminal device is different from a second initial bandwidth in a secondary cell for a second terminal device configured with no first synchronization signal. 103. The method of embodiment 102, wherein the first initial bandwidth extends outside the second initial bandwidth. 104. The method of embodiment 103, wherein the first synchronization signal is transmitted in a part of the first initial bandwidth, the part of the first initial bandwidth being non- overlapping with the second initial bandwidth. 105. The method of embodiment 79 or 80, wherein a first periodicity of the first synchronization signal block is shorter than a second periodicity of the second synchronization signal block, and the first synchronization signal block is transmitted on a dedicated bandwidth part. 106. The method of embodiment 105, wherein a frequency position of the first synchronization signal block is configured via a value of absolute radio frequency channel number.107. The method of embodiment 105, wherein a frequency position of the first synchronization signal block is indicated with an offset with respect to an edge of the dedicated bandwidth part. 108. The method of embodiment 107, wherein the offset comprises at least one of a resource block offset or a resource element block. 109. The method of embodiment 79 or 80, wherein no system information block is provided in association with the first synchronization signal block. 110. The method of embodiment 79 or 80, further comprising: transmitting, in a master information block, a first indication that no system information block is provided in a cell; and transmitting, in the master information block, a second indication of a resource location of the second synchronization signal block. 111. The method of embodiment 110, wherein the first indication is carried in a first parameter indicating a subcarrier offset, a value of the first parameter be set as a reserved value. 112. The method of embodiment 111, wherein the second indication is carried in a second parameter indicating a physical downlink control channel configuration, a value of the second be set as a reserved value. 113. The method of embodiment 79 or 80, wherein a valid parameter related to reception of a system information block is pointing to a resource location with no system information block. 114. The method of embodiment 113, wherein receiving the second synchronization signal block comprises: transmitting the second synchronization signal block in a potential resource location of the second synchronization signal block, based on reception of a system information block being failed.115. The method of embodiment 79 or 80, wherein the first synchronization signal block is configured as a non-cell-defining synchronization signal block. 116. The method of embodiment 79 or 80, wherein a first signal sequence of the first synchronization signal block is different from a second signal sequence of the second synchronization signal block. 117. The method of embodiment 116, wherein the first signal sequence is generated using at least one of: a different initial condition from an initial condition for generating the second signal sequence of the second synchronization signal block; a different cyclic shift value from a cyclic shift value for generating the second signal sequence; or a different recursion coefficient from a recursion coefficient for generating the second signal sequence. 118. The method of embodiment 117, wherein the first signal sequence is designed to maintain first cross-correlation properties, the first cross-correlation properties being lower than a second first cross-correlation properties of the second signal sequence. 119. The method of any of embodiments 116 to 118, where the signal sequence comprises at least one of a primary synchronization signal, a secondary synchronization signal sequence. 120. The method of embodiment 116 or 117, wherein the signal sequence comprises a demodulation reference signal sequence. 121. The method of embodiment 120, wherein the demodulation reference signal sequence comprises a fixed signal sequence excluded from a predefined set of candidate signal sequences. 122. The method of embodiment 79 or 80, further comprising: transmitting information about first resources for the first synchronization signal block.123. The method of embodiment 122, wherein the information is transmitted via at least one of system information or dedicated signaling. 124. The method of embodiment 79 or 80, wherein a parameter in a master information block is reused to indicate, to a second terminal device configured with no first synchronization signal block, that the received first synchronization signal block is unfeasible for cell access. 125. The method of embodiment 124, wherein the parameter indicates at least one of: a carrier for the received first synchronization signal block being improperly defined, resources of a system information block being undefined, or values of parameters in the master information block constituting incompatible combinations. 126. The method of any of embodiments 79 to 125, wherein the synchronization signal block comprises a synchronization signal, SS, physical broadcast channel, PBCH, block. Group D Embodiments 127. A first terminal device for reception of a synchronization signal block, the first terminal device comprising: a processor; and a memory, the memory containing instructions executable by the processor, whereby the first terminal device is operative to perform any of the steps of any of the Group A embodiments. 128. A second terminal device for reception of a synchronization signal block, the second terminal device comprising: a processor; and a memory, the memory containing instructions executable by the processor, whereby the second terminal device is operative to perform any of the steps of any of the Group C embodiments. 129. A network device, comprising: a processor; anda memory, the memory containing instructions executable by the processor, whereby the network device is operative to a memory, the memory containing instructions executable by the processor, whereby the first terminal device is operative to perform any of the steps of any of the Group C embodiments. 130. A computer-readable storage medium having instructions stored thereon, the instructions, which, when executed by at least one processor of a device, causes the device to perform any of the steps of any of the Group A, B and C embodiments.

Claims

WHAT IS CLAIMED IS:

1. A method performed in a terminal device in a telecommunication network, comprising: receiving a configuration for synchronization signal blocks, SSBs; receiving a cell-defining, CD, SSB, in second time-frequency resources from a secondary cell, SCell, for the terminal device, according to the configuration; and wherein the configuration further comprises first time-frequency resources for on- demand, OD, SSBs from the SCell, and the first time-frequency resources are not located on frequency resources of a global synchronization channel number, GSCN, raster.

2. The method according to claim 1, further comprising: after receiving the CD SSB, performing frequency hopping onto the first time- frequency resources for receiving an OD SSB from the SCell; or prior to reception of the CD SSB, receiving an OD SSB from the SCell on the first time-frequency resources, and performing frequency hopping onto the second time-frequency resources.

3. The method according to claims 1 or 2, wherein the configuration further comprising: SS / PBCH Block Measurement Timing Configuration, SMTC, dedicated for OD SSBs.

4. The method according to claim 3, wherein the SMTC for OD SSBs indicates a shorter time window than a time window of a SMTC configured for CD SSBs.

5. The method according to any of the claims 2 to 4, wherein the first time-frequency resources are located in an initial downlink bandwidth part, BWP, of the SCell; after receiving the OD-SSB, the method further comprises at least one of: performing cell activation for the SCell, receiving downlink data from the SCell, and performing intra-band frequency hopping in the SCell.

6. The method according to any of the claims 1 to 4, wherein the first time-frequency resources are located in a second BWP extending outside an initial BWP of an SCell for theterminal device.

7. The method according to any of the preceding claims, wherein the first resources comprise separated narrow time-varying frequency regions in at least one of a time domain or a frequency domain.

8. The method according to any of the preceding claims, further comprising: determining that the first time-frequency resources overlap with the second time- frequency resources; and skipping reception of an OD SSB transmitted on the overlapped resources.

9. A method performed in a network node serving a cell in a telecommunication network, comprising: transmitting a configuration for synchronization signal blocks, SSBs of the cell, for a terminal device, wherein the configuration indicating first resources for on-demand, OD, SSBs and second resources for cell-defining, CD, SSBs for the terminal device; transmitting a CD SSB in the second resources, wherein the first time-frequency resources are not located on frequency resources of a global synchronization channel number, GSCN, raster.

10. The method according to claim 9, wherein the configuration further comprising: SS / PBCH Block Measurement Timing Configuration, SMTC, dedicated for OD SSBs, wherein the SMTC for OD SSBs indicates a shorter time window than a time window of a SMTC configured for CD SSBs.

11. The method according to claims 9 or 10, wherein the first time-frequency resources are located: in an initial downlink bandwidth part, BWP, of the cell; or in a second BWP extending outside the initial BWP of the cell.

12. The method according to any of claims 9 to 11, wherein the first resources comprise separated narrow time-varying frequency regions in at least one of a time domain or a frequency domain.

13. The method according to any of the claims 9 to 12, further comprising:determining that the first time-frequency resources overlap with the second time- frequency resources; and skipping transmission of OD SSBs on the overlapped resources.

14. The method according to any of the claims 9 to 13, wherein in the configuration, an OD SSB is configured with an absolute radio frequency channel number, ARFCN, value that is equal to the ARFCN value of an CD SSB.

15. A terminal device, comprising: a processor; and a memory, the memory containing instructions executable by the processor, whereby the terminal device is operative to perform any of the steps of any of the claims 1 to 8.

Images