SSB-based measurement time configuration in communications
By relaxing the proximity distance between SMTC occasions and enabling parallel measurements, the solution addresses the challenge of high differential Doppler effects in non-terrestrial networks, improving measurement efficiency for RedCap UEs and capable devices.
Patent Information
- Application Number
- PCT/EP2026/062698
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-04
- Publication Date
- 2026-11-12
AI Technical Summary
In non-terrestrial networks, the high differential Doppler effect between approaching and receding satellites complicates simultaneous measurements by user devices, making it difficult to perform accurate radio resource management due to overlapping SMTC occasions.
The solution involves relaxing the proximity distance between consecutive SMTC occasions for RedCap UEs, allowing them to measure multiple satellites within a single SMTC period by adjusting the collision window from 4 ms to 5 ms, and enabling parallel measurements without scheduling restrictions for capable UEs.
This approach enhances the ability of user devices to perform simultaneous measurements across multiple satellites, reducing measurement complexity and improving radio resource management efficiency in non-terrestrial networks.
Smart Images

Figure EP2026062698_12112026_PF_FP_ABST
Abstract
Description
[0001] SSB-BASED MEASUREMENT TIME CONFIGURATION IN COMMUNICATIONS
[0002] FIELD
[0003] The following example embodiments relate to wireless communication, and to non-terrestrial networks.
[0004] BACKGROUND
[0005] If a satellite of a non-terrestrial network, NTN, is approaching a user device, while another satellite of the NTN is moving away, a doppler shift difference between the two satellites may create difficulties for the user device to measure the two NTN cells at the same time.
[0006] SUMMARY
[0007] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims.
[0008] BRIEF DESCRIPTION OF THE DRAWINGS
[0009] In the following, various example embodiments will be described in greater detail with reference to the accompanying drawings, in which
[0010] FIG. 1 A illustrates an example of a non-terrestrial network;
[0011] FIG. 1 B illustrates an example of a system in a mobility scenario;
[0012] FIG. 2 illustrates an SMTC configuration;
[0013] FIG. 3 illustrates exemplary signalling;
[0014] FIGs 4A, 4B and 5 illustrate a flow chart; and
[0015] FIG. 6 illustrates an example of an apparatus.
[0016] DETAILED DESCRIPTION
[0017] The following embodiments are exemplifying. Although the specification may refer to “an”, “one”, or “some” embodiment(s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodiment(s), or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments within the scope of the claims. Furthermore, the words "comprising" and "including" should be understood as not limiting the described embodiments to consist of only those features that have been mentioned, and such embodiments may also contain features that have not been specifically mentioned. Reference numbers, in the description and / or in the claims, serve to illustrate the embodiments with reference to the drawings, without limiting theembodiments to these examples only.
[0018] Further, it should be appreciated that, as used herein, the terms “the at least one” and “the one or more” mean “any one of the at least one” and “any one of the one or more”, respectively. Furthermore, as used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0019] Some example embodiments described herein may be implemented in a wireless communication network comprising a radio access network based on one or more of the following radio access technologies (RATs): fifth generation (5G), 5G new radio (NR), 5G-Advanced (i.e., 3GPP NR Rel-18 and beyond), sixth generation (6G), or seventh generation (7G). Some examples of radio access networks include the universal mobile telecommunications system (UMTS) radio access network (UTRAN), the evolved universal terrestrial radio access network (E-UTRA), or the next generation radio access network (NG-RAN).
[0020] It should be noted that the embodiments are not restricted to the wireless communication network given as an example, but a person skilled in the art may also apply the solution to other wireless communication networks or systems provided with necessary properties.
[0021] FIG. 1 A illustrates a simplified example of a non-terrestrial network (NTN), such as a satellite communication network, showing some physical and logical entities. The connections shown in FIG. 1 A may be physical connections or logical connections. It is apparent to a person skilled in the art that the network may also comprise other physical and logical entities than those shown in FIG. 1A.
[0022] The example embodiments described herein are not, however, restricted to the wireless communication network given as an example, but the example embodiments described herein may be applied to other wireless communication networks provided with necessary properties.
[0023] FIG. 1A shows user equipment (UE) 100 configured to be in a wireless connection on one or more communication channels in a radio cell 121 with a satellite 106 of a non-terrestrial network.
[0024] A non-terrestrial network may refer to a network, or a segment of networks, using radio frequency (RF) resources managed / controlled by a satellite 106. The satellite 106 may provide communication services on Earth (or on another planet) via one or more satellite beams. The one or more satellite beams create one or more cells 121 over a given service area bounded by the field of view of the satellite 106. The beam footprints (i.e., the cells 121) may be elliptical in shape. The satellite 106 may be used to provide communication coverage over a very large area (e.g., with a diameter of tens, hundreds, or even thousands of kilometers) that may be otherwise unreachable by cellular networks.
[0025] The satellite 106 may be, for example, a low earth orbit (LEO) satellite, a geostationary earthorbit (GEO) satellite, an unmanned aerial vehicle (UAV), a high-altitude platform system (HAPS), or any other spaceborne or airborne device used for communication.
[0026] As an example, the satellite 106 may be a LEO satellite at an altitude between 160 to 2000 kilometers above the surface of the Earth. At such an altitude, the satellite may be moving at a speed of approximately 7.5 kilometers per second relative to the Earth. For a LEO satellite, the beam footprint (i.e., cell 121) may have a radius between 100 to 1000 kilometers. The cell 121 may be an Earth-fixed cell (EFC), a quasi-Earth-fixed cell, or an Earth-moving cell (EMC).
[0027] An EFC means that the satellite 106 continuously adjusts the satellite beam pointing direction (beam steering) to fix the cell 121 and beam to a specific point on Earth as the satellite 106 is moving. In other words, in this case, the position of the cell 121 does not change over time, and it consistently covers the same geographic area.
[0028] A quasi-Earth-fixed cell, on the other hand, refers to a cell whose coverage area appears to be nearly fixed relative to the Earth's surface but may experience slight movements or adjustments. This can occur due to factors like the satellite's orbital characteristics or minor adjustments in its position. While the cell is not entirely stationary in this case, its movement is minimal enough that it can be considered almost fixed from the perspective of users on the ground. The quasi-Earth-fixed cells may apply to non-geostationary satellites, because the satellite (e.g., LEO satellite) at some point will be low on the horizon relative to the fixed cell. Thus, only geostationary satellites can have truly Earth-fixed cells.
[0029] An EMC means that the satellite beam pointing direction is fixed, and thus the beam footprint (i.e., the cell 121) is continuously moving on Earth according to the movement of the satellite 106. In other words, in this case, the satellite 106 does not adjust the beam steering, but instead the cell coverage sweeps the Earth as the satellite 106 moves. In EMC-based NTN, the mobility is mainly due to satellite movement as the satellite 106 moves much faster than the UE(s) 100 on the ground.
[0030] There may be a service link 130 (i.e., a radio link) between the satellite 106 and one or more UEs 100 within the targeted service area for communication between the satellite 106 and the one or more UEs O.
[0031] Furthermore, there may be a feeder link 140 (i.e., another radio link or an optical link) between the satellite 106 and a ground-based NTN gateway (GW) 104 for communication between the satellite 106 and the gateway 104. In other words, the feeder link 140 is a connection between the satellite 106 and the NTN gateway 104. The NTN gateway 104 may comprise a base station, such as an evolved NodeB (abbreviated as eNB or eNodeB), or a next generation evolved NodeB (abbreviated as ng-eNB), or a next generation NodeB (abbreviated as gNB or gNodeB). The NTN gateway 104 may be connected to a core network and / or an external data network 113 (e.g., the internet).In a transparent architecture of the non-terrestrial network, the access node (NTN gateway) 104 of the non-terrestrial network is located on ground (i.e., the base station 104 is on Earth). In this case, the satellite 106 may just forward the signals it receives from the NTN gateway 104 to one or more UEs 100, and vice versa (i.e., the satellite 106 may act as a repeater between the one or more UEs 100 and the NTN gateway 104). In the transparent architecture, there may be a feeder link (i.e., a radio link) 140 between the satellite 106 and the ground-based NTN gateway 104, as well as a service link 130 (i.e., another radio link) between the satellite 106 and the one or more UEs 100 within the targeted service area. The transparent architecture may also be referred to as a transparent payload architecture.
[0032] Alternatively, in a regenerative architecture of the non-terrestrial network, the access node of the non-terrestrial network (i.e., partial or full base station functionality) is onboard the satellite 106 itself (e.g., the satellite 106 may comprise a gNB). In this architecture, no ground-based NTN gateway 104 or feeder link 140 is needed. This means that the satellite 106 does more than just forwards signals: it can process the signals it receives, perform functions such as decoding, demodulation, and remodulation, and then transmit the processed signals to one or more UEs 100 over the service link 130. The regenerative architecture may also be referred to as having regenerative payloads.
[0033] The one or more UEs 100 may have global navigation satellite system (GNSS) support, which means that the one or more UEs 100 may have access to GNSS location information and / or GNSS time information. The global positioning system (GPS) is an example of a GNSS. The GNSS support enables the one or more UEs 100 to obtain an understanding of the time and / or frequency relations between itself and the satellite 106 and / or NTN gateway 104 for synchronization purposes. The GNSS information may also be used for mobility purposes and / or country identification. The satellite 106 may be a separate entity from the GNSS. The GNSS may also provide input to other network node(s) in the NTN system, so that the network node(s) are able to determine the position of the satellite at any given time. In an alternative example, the UE 100 may have a hard-coded location information, in case the UE is not moving. In another example, the UE 100 may determine the UE location based on 3GPP positioning reference signals or other 3GPP positioning mechanisms such as network-estimated UE position.
[0034] The satellite 106 may comprise a computing device configured to control the radio resources of the satellite 106 and to be in a wireless connection with one or more UEs 100. The satellite 106 may include or be coupled to transceivers. From the transceivers of the satellite 106, a connection may be provided to an antenna unit that establishes a bi-directional radio link to one or more UEs 100. The antenna unit may comprise an antenna or antenna element, or a plurality of antennas or antenna elements.
[0035] The wireless connection (e.g., radio link) from a UE 100 to the satellite 106 may be called uplink (UL) or reverse link, and the wireless connection (e.g., radio link) from the satellite 106 to the UE 100 maybe called downlink (DL) or forward link.
[0036] The non-terrestrial network may comprise more than one satellite 106, in which case the satellites may also be configured to communicate with one another over wireless links. These links between satellites may be used for sending and / or receiving control plane signaling and also for routing data from one satellite to another satellite.
[0037] The illustrated UE 100 is one type of an apparatus to which resources on the air interface may be allocated and assigned. The UE 100 may also be called a wireless communication device, a subscriber unit, a mobile station, a remote terminal, an access terminal, a user terminal, a terminal device, or a user device, just to mention but a few names. The UE 100 may be a computing device operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of computing devices: a mobile phone, a smartphone, a personal digital assistant (PDA), a handset, a computing device comprising a wireless modem (e.g., an alarm or measurement device, etc.), a laptop computer, a desktop computer, a tablet, a game console, a notebook, a multimedia device, a reduced capability (RedCap) device, a wearable device (e.g., a watch, earphones or eyeglasses) with radio parts, a household appliance with radio parts, a sensor comprising a wireless modem, or a computing device comprising a wireless modem integrated in a vehicle or in a house.
[0038] It should be appreciated that the UE 100 may also be a nearly exclusive uplink-only device, of which an example may be a camera or video camera loading images or video clips to a network. The UE 100 may also be a device having capability to operate in an Internet of Things (loT) network, which is a scenario in which objects may be provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction.
[0039] FIG. 1B illustrates an example of a system, to which some example embodiments may be applied. FIG. 1B may be understood to depict a part of the non-terrestrial network of FIG. 1A, but with greater accuracy with respect to a mobility scenario.
[0040] Referring to FIG. 1B, during a handover (or cell re-selection), the connection of a UE 100 is transferred from the current serving cell (source cell) 121 controlled by a source node (e.g., a satellite) 106 to a target cell 122 controlled by a target node (e.g., another satellite) 106B, while preserving the ongoing voice call or data session. Herein the source cell 121 and the target cell 122 may be NTN cells. In one further example, the serving cell 121 and the target cell 122 may be provided by the same satellite 106. The target cell 122 may also be referred to as a neighbor cell.
[0041] In one example, the handover procedure may be initiated by the network (e.g., the source node 106), when certain pre-defined conditions are met, such as when the signal quality of the current serving cell (source cell) 121 falls below a specified threshold, or when the signal quality of the target cell (neighbor cell)122 becomes better than that of the current serving cell 121 by a pre-defined offset. The decision to perform a handover may be based on various factors, including radio measurements such as reference signal received power (RSRP) and / or reference signal received quality (RSRQ), network load, UE mobility, locationbased thresholds, time-based windows, and network configuration parameters.
[0042] There are various types of handover procedures. For example, a conditional handover (CHO) may be defined as a handover that is executed by the UE 100, when one or more handover execution conditions are met. In other words, in the case of CHO, the UE 100 receives (e.g., from the source node 106) a handover command with a CHO configuration indicating one or more handover execution conditions such as RSRP, distance and time, but the UE 100 does not execute the handover command until the one or more handover execution conditions are met. The UE 100 may start evaluating the one or more handover execution conditions upon receiving the CHO configuration, and stop evaluating the one or more handover execution conditions once a handover is executed.
[0043] The handover may be an intra-radio-access-technology (intra-RAT) handover or an inter-radio-access-technology (inter-RAT) handover. The handover may also be an intra-frequency cell change or an inter-frequency cell change. An intra-RAT handover means that the source cell 121 and the target cell 122 are based on the same radio access technology. For example, in an intra-NR handover, both the source node 104 and the target node 104B may be gNBs (i.e., NR base stations). An inter-RAT handover means thatthe source cell 121 and the target cell 122 are based on different radio access technologies. For example, in an inter-RAT handover, the source node 104 may be an eNB or ng-eNB (i.e., 4G base station), and the target node 104B may be a gNB (i.e., NR base station), or vice versa.
[0044] In case of EFC, there are two different kinds of mobility events (or handovers). The first kind of handover refers to the case where the fixed cell 121 (e.g., quasi earth fixed cell) is replaced by another fixed cell 122, when the serving satellite 106 moves too low in the horizon. In case of transparent architecture, this can even be done by resynchronization without change of the physical cell identity (PCI), in which case it is not considered as an actual handover. In the case of regenerative architecture, there is an actual handover (i.e., change of PCI), but the event is very predictable. Likewise, cell re-selections can be performed based on the known change of satellite coverage. The end of coverage from an EFC may be indicated by a parameter called t-service, which defines the time when the cell stops serving the area where the UE 100 is located in. There may also be a parameter t-serviceStart defining when another cell starts serving the area.
[0045] The other kind of handover is due to UE movement, where a UE 100 simply crosses the border of the serving cell 121 and performs a handover or cell re-selection to the target cell 122.
[0046] In case of EMC, a UE 100 at the trailing part 150 of the border of the cell 121, opposite to the movement direction 160 of the satellite 106 (i.e., opposite to the leading part 170 of the cell border), is morelikely to experience mobility events due to cell movement and the UE’s own movement.
[0047] The leading part 170 of the cell border refers to the area of the cell border that is in the direction 160 of the satellite's movement. Conversely, the trailing part 150 of the cell border is the area of the cell border that is opposite to the satellite's movement direction 160. When the UE 100 is at or close to the trailing part 150 of the cell border, it is more likely to experience mobility events due to the movement of the satellite 106 (and the movement of the UE itself). This is because the cell coverage area is constantly shifting as the satellite 106 moves.
[0048] In all cases of mobility, the UE 100 needs to perform radio measurements (e.g., RSRP and / or RSRQ measurements) on the serving cell 121 and / or on the neighbor cell 122. In order to do so, the UE 100 acquires information related to the mobility events through the system information blocks (SIBs), which are broadcasted at regular time intervals on the cell 121. For example, the following SIBs may be defined as mobility-related SIBs: SIB2, SIB3, SIB4, and SIB5. In other words, these SIBs comprise information related to mobility. SIB2 comprises cell re-selection information common for intra-frequency, inter-frequency and / or inter-RAT cell re-selection (i.e., applicable for more than one type of cell re-selection but not necessarily all), as well as intra-frequency cell re-selection information, other than neighbor cell related. SIB3 comprises neighbor cell related information relevant only for intra-frequency cell re-selection. The information element (IE) within SIB3 includes cells with specific re-selection parameters as well as exclude-listed cells. SIB4 comprises information relevant for inter-frequency cell re-selection (i.e., information about other NR frequencies and inter-frequency neighbouring cells relevant for cell re-selection), which can also be used for NR idle / inactive measurements. The IE within SIB4 includes cell re-selection parameters common for a frequency, as well as cell-specific re-selection parameters. SIB5 comprises information relevant only for inter-RAT cell re-selection, i.e., information about E-UTRA frequencies and E-UTRA’s neighbouring cells relevant for cell re-selection. The IE within SIB5 includes cell re-selection parameters common for a frequency. The UE 100 may be configured with a validity time for a given SIB. For example, the UE may only need to read the SIB every 3 hours, unless it is changed.
[0049] In NTN, cells may be large, and a UE that is stationary and / or away from the cell border is not likely to see a mobility event, except in case of EFC around the time of the cell change. SIB1 and SIB2 can be configured for limited mobility. For example, SIB1 can be configured for barring neighbor cells or specifying a preferred cell. As another example, mobility-related parameters in SIB2 can be adjusted to deprioritize cell re-selection.
[0050] Reduced capability (RedCap) operations may be applied in non-terrestrial networks (NTN). In NTN, especially in low-Earth orbit scenarios, a satellite may be at an altitude of 300 to 1800 km, and have a speed as high as 7.5 km / s. Because of such high speeds, the doppler effect on the network carrier may bemuch higher in the NTN when compared to the levels observed at terrestrial networks. This may become even more relevant when two satellites are considered to cover the same area where the UE is located. This may happen, for example, in a scenario where there is an outbound first satellite, broadcasting the serving cell, soon to be out of reach of the UE, and a second satellite which is incoming and provides neighbor cells that might provide continuous coverage for the UE. The maximum doppler shift seen in each of the cells, considering a satellite at an altitude of 300 km, may be equal to as high as 24 ppm (parts per million). As one of the satellites may be approaching the UE, while the other is moving away, the doppler shift difference between the two satellites may be as high as 48 ppm. This may create difficulties for the UE to measure the two cells at the same time.
[0051] An SSB-based measurement time configuration (SMTC) period refers to a full configuration of the SMTC which may include periodicity and offset as well as the size of an SMTC window. The SMTC period may also be referred to as an SMTC configuration. The SMTC window refers to one instance of an SMTC configuration. The SMTC window may also be referred to as an SMTC occasion. The offset between the SMTC occasions may be referred to as a proximity distance or time interval or collision window. SSB refers to a synchronization signalling block. These are illustrated in FIG. 2.
[0052] The issue of the high differential doppler effect between two satellites has been addressed by different solutions.
[0053] MaxNumber-NGSO-SatellitesWithinOneSMTC-r17 indicates the number of different NGSO satellites for target cells that the UE supports of simultaneous measurements within a SMTC with value n1 corresponds to 1, value n2 corresponds to 2 and so on.
[0054] ParallelMeasurementWithoutRestriction-r17 indicates whether the UE supports measurements on cells belonging to different satellites as the serving cell in parallel with normal operation (i.e. data / control transmission and / or reception, and layer-1 (L1) measurements) of serving cell without scheduling restrictions. The feature is applicable only when the serving satellite is a non-geostationary orbit (NGSO) satellite. If the serving cell belongs to a GSO satellite, the scheduling restriction is not applied on the premise that a mixed type of satellites on the same frequency layer is not supported. If not reported, for measurements in parallel with normal operation of serving cell scheduling restrictions shall apply.
[0055] ParallelSMTC-r17 indicates whether the UE supports NTN SSB-based RRM measurements on target cells belonging to 4 SMTCs on a single frequency carrier. If the UE does not include this field but includes nonTerrestrialNetwork-r17, the UE supports NTN SSB-based RRM measurements on target cells belonging to 2 SMTCs on a single frequency carrier.
[0056] MaxNumber-NGSO-SatellitesWithinOneSMTC-r17 indicates how many satellites may be measured within one configured SMTC (SSB-Based Measurement Time Configuration), which means thatby configuring only one SMTC, the UE may measure several satellites within that SMTC. ParallelMeasurementWithoutRestriction-r17 indicates that if the UE is measuring a neighbor NGSO (LEO) satellite, then, due to the huge doppler shifts expected at the UE receiver, the UE has to indicate that the UE supports the parallel measurements without scheduling restrictions, otherwise, scheduling restrictions is applicable (i.e., UE cannot be scheduled while measuring cells in different satellites).
[0057] ParallelSMTC-r17 indicates how many different SMTCs (i.e. multiple SMTC windows, multiple SMTC offsets, etc) may be configured at the UE.
[0058] When the UE is configured with multiple SMTCs configurations (i.e. multiple SMTC offsets) or multiple measurement gaps, the UE may sort out what to do in case of collision between measurement gaps or SMTC occasions. The distance between consecutive two measurement gaps may also be considered for the determination of the collision, as the UE may “retune” the receiver and “process” the information received in one SMTC before adjusting to the next SMTC occasion.
[0059] A collision between occasions of multiple SMTCs may occur. When the UE is configured with more than one SMTC on a satellite access node (SAN) carrier, two SMTC occasions outside the measurement gap may be considered colliding, if at least one of the following conditions is met:
[0060] - the two SMTC occasions are fully or partially overlapping in time domain, or - the magnitude of the distance between two SMTC occasions in time domain is less than or equal to 4 ms.
[0061] The distance between two SMTC occasions may be defined as the time difference between the ending point of the earlier SMTC occasion and the starting point of the later SMTC occasion. The collision rule may be used to determine the total measurement time in the UE.
[0062] The UE may be able to identify a new detectable intra-frequency cell within Tidentity,intra_without_index if the UE is not indicated to report SSB-based RRM measurement result with the associated SSB index (reportQuantityRsIndexes or maxNrofRSIndexesToReport is not configured), or the UE is indicated that the neighbour cell is synchronous with the serving cell (deriveSSB-lndexFromCell is enabled). Otherwise the UE may be able to identify a new detectable intra frequency cell within Tidentify,intra_with_index. The UE may be able to identify a new detectable intra frequency SS block of an already detected cell within Tidentify, jntra_without_index.
[0063] T iden tify_intra_wi thou t_index - (T PSS / SSS_sync_intra+T SSB_measurement_period_intra) fTIS
[0064] Tidentify_intra_with_index - (TpsS / SSS_sync_intra+TsSB_measurement_period_intra + TSSB_time_indeX_intra) fTIS Wherein:
[0065] Tpss / sss. _sync_intra is a time period used in PSS / SSS detection given in Table 1. PSS refers to primary synchronization signal, and SSS refers to a secondary synchronization signal (SSS).
[0066] TssBjimejndexjntra is a time period used to acquire the index of the SSB being measured given inTable 2.
[0067] TssB_measurement_Period_intra is equal to a measurement period of the SSB-based measurement given in Table 1.
[0068] KmuitLSMTc is a scaling factor for the measurement of multiple SMTCs or multiple satellites, and if SMTCs do not overlap with each other,
[0069] KmuitLSMTc = 1 , if GEO satellites are measured on the carrier;
[0070] I
[0071] Kmulti SMTC ~ T - .
[0072]
[0073] if LEO satellites are measured on the carrier;
[0074] if SMTCs partially overlap with each other,
[0075] KmuitLSMTc = NsMTc.overiap, if only GEO satellites are measured on the carrier;
[0076]
[0077] if only LEO satellites are measured on the carrier;
[0078] where:
[0079] NLEO.I is the number of LEO satellites to be measured within i-th SMTC,
[0080] NLEo.simui is the number of LEO satellites that UE can measure in parallel within an SMTC, NsMTc.overiap is the number of SMTCs that partially overlap with each other.
[0081] CSSFmtra is a carrier specific scaling factor and is determined according to CSSFoutside_gaP,i. CSSF refers to a carrier-specific scaling factor.
[0082] If the high layer signalling of SMTC2 is configured, the assumed periodicity of intra-frequency SMTC occasions corresponds to the value of higher layer parameter SMTC2. Otherwise, the assumed periodicity of intra-frequency SMTC occasions corresponds to the value of higher layer parameter SMTC1.
[0083] Kp is the scaling factor for an SSB frequency layer to be measured without measurement gaps. Kp=Ntotai_sAN / Navaiiabie_sAN, where Navaiiabie_sAN and Ntotai_sAN are calculated as follows:
[0084] For a window W of duration max(SMTC period, MGRPjnax), where if the UE supports parallelMeasurementGap-r17 and is configured with concurrent measurement gaps, MGRPjnax is the maximum measurement gap repetition period (MGRP) across all configured per-UE measurement gap. Otherwise, MGRP nax is the MGRP of configured measurement gap. Starting from the beginning of any SMTC occasion:
[0085] NtotaijAN is the total number of SMTC occasions within the window, including those overlapped and non-overlapped with measurement gap occasions within the window, and
[0086] NavaiiabiejAN is the number of SMTC occasions within the window W that do not collide with anynon-dropped MG occasion within or outside the window W, after accounting for measurement gap collisions by applying the measurement gap collision rule. The collision rule between SMTC occasion and measurement gap occasion may be defined.
[0087] Kp = [1] when Navaiiabie.sAN = 0 and measurement gap sharing may apply. Kp = 1 when intrafrequency SMTC is fully non overlapping with measurement gaps. For calculation of Kp, if the high layer signalling of SMTC2 is configured, for cells indicated in the pci-List parameter in SMTC2, the SMTC periodicity corresponds to the value of higher layer parameter SMTC2; for the other cells, the SMTC periodicity corresponds to the value of higher layer parameter SMTC1.
[0088] Kiayeri_measurement is scaling factor for sharing between L3 and L1 measurement, and Kiayeri_measurement =1, if GEO satellites are measured on the carrier, or if LEO satellites are measured on the carrier and UE supports parallelMeasurementWithoutRestriction, otherwise
[0089] Klayer1_measurement - 1 ,
[0090] if all of the reference signals configured for radio link monitoring (RLM), beam failure detection (BFD), candidate beam detection (CBD) or L1-RSRP for beam reporting outside measurement gap are not fully overlapped by intra-frequency SMTC occasions, or
[0091] if all of the reference signal configured for RLM, BFD, CBD or L1-RSRP for beam reporting outside measurement gap and fully-overlapped by intra-frequency SMTC occasions are not overlapped with any of the SSB symbols and the RSSI symbols, and 1 symbol before each consecutive SSB symbols and the RSSI symbols, and 1 symbol after each consecutive SSB symbols and the RSSI symbols, given that SSB-ToMeasure and SS-RSSI-Measurement are configured, and RSSI symbols are indicated by SS-RSSI-Measurement;
[0092] Klayer1_measurement -1.5, Otherwise.
[0093] If the above-mentioned reference signal configured for L1-RSRP measurement is aperiodic channel state information reference signal (CSI-RS) resource, longer cell identification delay may be expected. If the higher layer signalling of SMTC2 is present and SMTC1 is fully overlapping with measurement gaps and SMTC2 is partially overlapping with measurement gaps, requirements are not specified for Tidentity.intra_wi thou t_index Or T identify_intra_with_index.Table 1. Time period for PSS / SSS detection (frequency range FR1)
[0094] DRX cycle T PSS / SSS_syni€_irrtra
[0095] No DRX max( 600 ms, celH 5 x Kp x x Knwhi_sMTc x SMTC period )Hote 1X CSSFintra
[0096] DRX cyde< 320 ms cdc oOO rm ceiq 1 5 x 5 x Ce licrx Kmuiti_sMTcX
[0097] r a> !S t-1TC per ir id L'RX cydeii * CSSF -f
[0098] DRX cycle >320 ms ceil(5 x Kp x x x DRX cycle x CSSF^ntrsNOTE 1: If eifferetit SMTC pernb dt es are o -nfigired f< a different cel s, the SMTC period in the requirement is tie > n ie used by the cell beu ig ider itT ed
[0099]
[0100] Table 2. Time period for time index detection (FR1)
[0101] DRX cycle
[0102] No DRX mox(120 ms, ceil( 3 x KpX x SMTC period)
[0103] 1X CSSFjntra
[0104] DRX cyde< 320^ ms 20 ms, ceil (1 „5 x 3 x Kp x x x rriax(SMTC period. DRX cycle)) x CSShntra
[0105] DPA C\ de '320 ms Ceild x K|_ \ U-ey x K, ■ DRX c\de > CSSFintra
[0106] N' 'TE 1 It oitfereut SMTC perr -O’cit es afe o 'iitigmed tm d trerent cel s, the SMTC pern id in the requirement L Vie i ne used by the cell being identd ed
[0107]
[0108] DRX refers to discontinuous reception.
[0109] The UE is allowed to skip measurements on intra-frequency cells, in the interval between t-serviceStart and the satellite switch completion, when it is performing soft satellite switching with resynchronization. In this case, for the measurement initiated but not completed before the beginning interval, the total time to detection can be longer. The requirements are not applicable when the overall overhead ratio due to scheduling restriction caused by all configured SMTCs (i.e. scheduling restriction overhead of all SMTCs in one SMTC periodicity), is larger than 75%.
[0110] When (e)RedCap UE is configured with more than one SMTCs on a SAN carrier, two SMTC occasions outside measurement gap are considered colliding if at least one of the following conditions is met: the two SMTC occasions are fully or partially overlapping in time domain, or the magnitude of the distance between two SMTC occasions in time domain is less than or equals to Y ms, where Y = 5 ms. The collision window may be enhanced from 4 to 5 ms, to accommodate to the more simplistic and less capable RedCap receiver (which contains reduced capabilities). This may pose a limitation on the number of SMTCs (and theirrespective offsets) that are configurable by the network without enlarging significantly the total time RedCap UEs need to complete measurements. The RedCap receivers have less processing capacity and if the proximity distance is not relaxed, to cope with the current proximity distance, the RedCap UEs may not be willing to implement multiple satellite measurements within the same SMTC (maxNumber-NGSO-SatellitesWithinOneSMTC-r17 > 1). The issue may be whether to relax the proximity distance (from 4 to 5 ms) for RedCap UEs at the expense of network complexity, as the network needs to handle this UE type and the regular NTN UE supporting 4 ms, or to have a scenario where most RedCap UEs do not implement the feature for multiple satellite measurements within a SMTC. A worst case may be to agree in relaxing the proximity distance rule, but still most RedCap UEs may not implement the capability to measure multiple satellites within the same SMTC.
[0111] In an embodiment, relaxation of a proximity distance between consecutive SMTCs (or between SMTCs and measurement gaps) may be made conditional on the UE supporting the measurement of multiple satellites within one SMTC and being configured to measure multiple satellites in at least one SMTC during a SMTC period. A relaxation rule may depend on both the number of parallel SMTCs to be measured and the number of satellites in one SMTC.
[0112] In an embodiment, an apparatus, such as the UE, may receive, from a satellite of a nonterrestrial network, NTN, an SSB-based measurement time configuration, SMTC, related to SSB-based radio resource management, RRM, measurements on at least one target cell provided by the NTN, wherein the SMTC includes related SMTC occasions, wherein the SMTC indicates a number of parallel SMTCs to be measured timely in parallel and / or a number of satellites to be measured in one SMTC. The apparatus may determine whether two SMTC occasions are considered to collide based on a magnitude of a proximity distance between two SMTC occasions in a time domain, wherein the two SMTC occasions are considered to collide upon the proximity distance being less than or equal to a first threshold value to be determined, wherein the first threshold value is one of at least two different values. The apparatus may determine the first threshold value based on the number of satellites the apparatus is capable of measuring within one SMTC and a number of configured measurements. In response to determining that two SMTC occasions are considered to collide, the apparatus may perform measurements on a first SMTC occasion, without performing measurements on a second SMTC occasion.
[0113] In an embodiment, an apparatus, such as the UE, may receive, from a satellite of a nonterrestrial network, NTN, an SSB-based measurement time configuration, SMTC, related to SSB-based radio resource management, RRM, measurements on at least one target cell provided by the NTN, wherein the SMTC includes related SMTC occasions. The SMTC may indicate a number of satellites to be measured in one SMTC. Upon a configured number of satellites to be measured in one SMTC being more than one, theapparatus may determine whether two SMTC occasions are considered to collide based on a magnitude of a proximity distance between two SMTC occasions in a time domain. The two SMTC occasions may be considered to collide upon the proximity distance being less than or equal to a first threshold value and higher than a second threshold value. In response to determining that the two SMTC occasions are considered to collide, the apparatus may reduce a configured number of satellites to be measured in one SMTC, and perform measurements on the reduced number of satellites.
[0114] In an embodiment, the apparatus may determine the first threshold value based on the number of satellites the apparatus is capable of measuring within one SMTC and a number of configured measurements. In response to determining that the two SMTC occasions are considered to collide, the apparatus may perform measurements on a first SMTC occasion, without performing measurements on a second SMTC occasion.
[0115] In an embodiment, the apparatus may perform relaxation of the proximity distance between consecutive SMTC occasions, upon the apparatus supporting measurement of multiple satellites within one SMTC occasion and being configured to measure the multiple satellites in at least one SMTC occasion during a SMTC period. The proximity distance may be a time interval, or a collision window, between consecutive SMTC occasions. The apparatus may calculate a relaxation of the proximity distance, based on the number of parallel SMTC occasions to be measured and on the number of satellites in one SMTC occasion. The apparatus may determine a relaxation rule based on apparatus capabilities. The proximity distance may be dependent on the number of satellites the apparatus is capable of measuring within one SMTC occasion. A total proximity distance is dependent on a total number of satellites to be measured across the SMTC occasions within a SMTC period.
[0116] In an embodiment, upon the apparatus being capable of measuring two satellites in one SMTC occasion and being configured to measure more than one satellite in one SMTC occasion, the proximity distance may be 5 ms. The proximity distance is relaxed from 4 ms to 5 ms.
[0117] In an embodiment, upon the apparatus being capable of measuring three satellites in one SMTC occasion and being configured to measure three satellites within one SMTC occasion, the proximity distance may be 6 ms.
[0118] In an embodiment, upon a configured number of satellites to be measured in one SMTC being more than one, the apparatus may determine whether two SMTC occasions are considered to collide based on the magnitude of the proximity distance between the two SMTC occasions in the time domain, wherein the two SMTC occasions are considered to collide upon the proximity distance being less than or equal to the first threshold value and higher than a second threshold value. In response to determining that two SMTCoccasions are considered to collide, the apparatus may reduce the configured number of satellites to be measured in one SMTC, and perform measurements on the reduced number of satellites.
[0119] In an embodiment, a method is disclosed comprising: receiving, by an apparatus from a satellite of a non-terrestrial network, NTN, an SSB-based measurement time configuration, SMTC, related to SSB-based radio resource management, RRM, measurements on at least one target cell provided by the NTN, wherein the SMTC includes related SMTC occasions, wherein the SMTC indicates a number of parallel SMTCs to be measured timely in parallel and / or a number of satellites to be measured in one SMTC; determining, by the apparatus, whether two SMTC occasions are considered to collide based on the magnitude of a proximity distance between two SMTC occasions in a time domain, wherein the two SMTC occasions are considered to collide upon the proximity distance being less than or equal to a threshold value to be determined, wherein the threshold value is one of at least two different values; determining, by the apparatus, the threshold value based on the number of satellites the apparatus is capable of measuring within one SMTC and a number of configured measurements; in response to determining that two SMTC occasions are considered to collide, performing, by the apparatus, measurements on a first SMTC occasion, without performing measurements on a second SMTC occasion.
[0120] In an embodiment, a non-transitory computer readable medium is disclosed, comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method.
[0121] FIG. 3 illustrates exemplary signalling. Referring to FIG. 3, an apparatus, such a user device or user equipment UE 100, may exchange 301, with a network device or network node, information on capabilities of the UE for supporting receiving multiple satellites within one SMTC and for supporting parallel SMTCs. The UE may be a RedCap UE. The network node may be a satellite or an access node of the NTN. The network node may be a satellite access node (SAN). The UE may be capable of supporting a connection towards a cell provided by a satellite of a non-terrestrial network, NTN. The network node may transmit 302 a UE capability enquiry message to the UE. The UE may receive the message 302, and transmit 303 the UE capability information to the network node. The message 303 may indicate the UE capability to receive multiple satellites within an SMTC and the UE capability to receive parallel SMTCs. The network node may receive the message 303, and transmit a RRC reconfiguration message 304 to the UE. The message 304 may include SMTC configuration for the satellites. The UE may receive the message 304, and transmit a RRC reconfiguration complete message 305 to the network node. The network node may receive the message 305. The UE may determine 306a collision rule based on the UE capabilities. If the UE supports and is configured with multiple satellites in one SMTC, and if the UE supports and is configured with parallel SMTCs, the UE may calculate relaxation of the proximity distance between consecutive SMTC occasions.Specifically the UE may determine 306 whether two SMTC occasions are considered to collide based on a magnitude of a proximity distance between two SMTC occasions in a time domain, wherein the two SMTC occasions are considered to collide upon the proximity distance being less than or equal to a first threshold value to be determined, wherein the first threshold value is one of at least two different values. The UE may determine 306 the first threshold value based on the number of satellites the apparatus is capable of measuring within one SMTC and a number of configured measurements. In response to determining that two SMTC occasions are considered to collide, the UE may perform 306 measurements on a first SMTC occasion, without performing measurements on a second SMTC occasion.
[0122] The network node may transmit 307 a measurement report request message to the UE. The UE may receive the message 307, and transmit 308 a target cell measurement report to the network node. The network node may receive the message 308.
[0123] In an embodiment, the number of parallel SMTCs to be measured timely in parallel, and / or a number of satellites to be measured in one SMTC, may be a natural number which may have a value of 1, or 2, or 3, or 4, etc. In an embodiment, the number of parallel SMTCs to be measured timely in parallel may be 2 or 3. In an embodiment, the number of satellites to be measured in one SMTC may be 1, or 2, or 3, etc.
[0124] In case the configured number of satellites to be measured in one SMTC is more than one, the UE may determine that the two SMTC occasions are considered to collide upon the magnitude of the proximity distance between two SMTC occasions in time domain being less than or equal to the determined threshold and higher than a second threshold. In response to determining that the two SMTC occasions are considered to collide, the UE may reduce the configured number of satellites to be measured in one SMTC, and perform measurements on the reduced number. A first threshold value may be e.g. 5 ms and a second threshold may be e.g. 4 ms. The threshold value may have other values as well, e.g. determining a time window, e.g. [4 ms, 6 ms], [4 ms, 5 ms], [5 ms, 6 ms], etc.
[0125] FIG. 4A illustrates an exemplary method. Referring to FIG. 4A, an apparatus, such a user device or user equipment UE 100, may be able to support 41 A multiple SMTCs. It may be checked 42A whether the UE is configured to measure multiple SMTCs. If not, the UE may determine 46A that no relaxation of the proximity distance is performed. If yes, it may be checked 43A whether the UE is configured to measure multiple satellites in one SMTC occasion. If not, the UE may determine 46A that no relaxation of the proximity distance is performed. If yes, the UE may determine 44A that the two SMTC occasions are considered to collide based on the proximity distance between the two SMTC occasions in a time domain. In response to determining that the two SMTC occasions are considered to collide, the UE may, at 45A, calculate a relaxation of the proximity distance, based on the number of parallel SMTC occasions to be measured and on the number of satellites in one SMTC occasion.FIG. 4B illustrates an exemplary method. Referring to FIG. 4B, an apparatus, such a user device or user equipment UE 100, may be able to support 41 B multiple SMTCs. It may be checked 42B whether the UE is configured to measure multiple SMTCs. If not, the UE may determine 46B that no relaxation of the proximity distance is performed, i.e. non-relaxed requirements may be applied. If yes, it may be checked 43B whether the UE is configured to measure multiple satellites in one SMTC occasion. If not, the UE may determine 46B that no relaxation of the proximity distance is performed. If yes, it may be checked 44B whether the time interval between two SMTCs is between 4 ms and 5 ms. If not, the UE may determine 46B that no relaxation of the proximity distance is performed. If yes, it may be determined 45B that the number of satellites the UE is to measure in one SMTC is to be reduced.
[0126] FIG. 5 illustrates an exemplary method. Referring to FIG. 5, an apparatus, such a user device or user equipment UE 100, may receive 501, from a satellite of a non-terrestrial network, NTN, an SSB-based measurement time configuration, SMTC, related to SSB-based radio resource management, RRM, measurements on at least one target cell provided by the NTN, The SMTC may include related SMTC occasions. The SMTC may indicate a number of parallel SMTCs to be measured timely in parallel and / or a numberof satellites to be measured in one SMTC. The UE may determine 501 whether two SMTC occasions are considered to collide based on a magnitude of a proximity distance between two SMTC occasions in a time domain. The two SMTC occasions may be considered to collide upon the proximity distance being less than or equal to a first threshold value to be determined, wherein the first threshold value is one of at least two different values. The UE may determine 501 the first threshold value based on the number of satellites the apparatus is capable of measuring within one SMTC and a number of configured measurements. In response to determining that two SMTC occasions are considered to collide, the UE may perform 502 measurements on a first SMTC occasion, without performing measurements on a second SMTC occasion.
[0127] The blocks and related functions described above by means of FIGS. 2 and 6 are in no absolute chronological order, and some of them may be performed simultaneously or in an order differing from the described one. Other functions can also be executed between them or within them, and other information may be sent, and / or other rules applied. Some of the blocks or part of the blocks can also be left out or replaced by a corresponding block or part of the block.
[0128] FIG. 6 illustrates an example of an apparatus 400 comprising means for performing one or more of the example embodiments described above. For example, the apparatus 400 may be an apparatus such as, or comprising, or comprised in, a user device (i.e., UE) 100.
[0129] The apparatus 400 may comprise a circuitry or a chipset applicable for realizing one or more of the example embodiments described above. For example, the apparatus 400 may comprise at least one processor 410. The at least one processor 410 interprets instructions (e.g., computer program instructions)and processes data. The at least one processor 410 may comprise one or more programmable processors. The at least one processor 410 may comprise programmable hardware with embedded firmware and may, alternatively or additionally, comprise one or more application-specific integrated circuits (ASICs).
[0130] The at least one processor 410 is coupled to at least one memory 420. The at least one processor is configured to read and write data to and from the at least one memory 420. The at least one memory 420 may comprise one or more memory units. The memory units may be volatile or non-volatile. It is to be noted that there may be one or more units of non-volatile memory and one or more units of volatile memory or, alternatively, one or more units of non-volatile memory, or, alternatively, one or more units of volatile memory. Volatile memory may be for example random-access memory (RAM), dynamic randomaccess memory (DRAM) or synchronous dynamic random-access memory (SDRAM). Non-volatile memory may be for example read-only memory (ROM), programmable read-only memory (PROM), electronically erasable programmable read-only memory (EEPROM), flash memory, optical storage or magnetic storage. In general, memories may be referred to as non-transitory computer readable media. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM). The at least one memory 420 stores computer readable instructions that are executed by the at least one processor 410 to perform one or more of the example embodiments described above. For example, non-volatile memory stores the computer readable instructions, and the at least one processor 410 executes the instructions using volatile memory for temporary storage of data and / or instructions. The computer readable instructions may refer to computer program code.
[0131] The computer readable instructions may have been pre-stored to the at least one memory 420 or, alternatively or additionally, they may be received, by the apparatus, via an electromagnetic carrier signal and / or may be copied from a physical entity such as a computer program product. Execution of the computer readable instructions by the at least one processor 410 causes the apparatus 400 to perform one or more of the example embodiments described above. That is, the at least one processor and the at least one memory storing the instructions may provide the means for providing or causing the performance of any of the methods and / or blocks described above.
[0132] In the context of this document, a “memory” or “computer-readable media” or “computer-readable medium” may be any non-transitory media or medium or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).
[0133] The apparatus 400 may further comprise, or be connected to, an input unit 430. The input unit430 may comprise one or more interfaces for receiving input. The one or more interfaces may comprise, for example, at least one of: one or more temperature, motion and / or orientation sensors, one or more cameras, one or more accelerometers, one or more microphones, one or more buttons and / or one or more touch detection units. Further, the input unit 430 may comprise an interface to which external devices may connect to.
[0134] The apparatus 400 may also comprise an output unit 440. The output unit may comprise or be connected to one or more displays capable of rendering visual content, such as a light emitting diode (LED) display, a liquid crystal display (LCD) and / or a liquid crystal on silicon (LCoS) display. The output unit 440 may further comprise one or more audio outputs. The one or more audio outputs may be for example loudspeakers.
[0135] The apparatus 400 further comprises a connectivity unit 450. The connectivity unit 450 enables wireless connectivity to one or more external devices. The connectivity unit 450 comprises at least one transmitter and at least one receiver that may be integrated to the apparatus 400 or that the apparatus 400 may be connected to. The at least one transmitter comprises at least one transmission antenna, and the at least one receiver comprises at least one receiving antenna. The connectivity unit 450 may comprise an integrated circuit or a set of integrated circuits that provide the wireless communication capability for the apparatus 400. Alternatively, the wireless connectivity may be a hardwired application-specific integrated circuit (ASIC). The connectivity unit 450 may also provide means for performing at least some of the blocks or functions of one or more example embodiments described above. The connectivity unit 450 may comprise one or more components, such as: power amplifier, digital front end (DFE), analog-to-digital converter (ADC), digital-to-analog converter (DAC), frequency converter, (de)modulator, and / or encoder / decoder circuitries, controlled by the corresponding controlling units.
[0136] It is to be noted that the apparatus 400 may further comprise various components not illustrated in FIG. 4. The various components may be hardware components and / or software components.
[0137] As used in this application, the term “circuitry” may refer to one or more or all of the following: a) hardware-only circuit implementations (such as implementations in analog, digital and / or quantum circuitry); and b) combinations of hardware circuit(s) and software, such as (as applicable): i) a combination of analog, digital and / or quantum hardware circuit(s) with software / firmware and ii) any or all portions of hardware processor(s) (including digital and / or quantum processor(s)) with software, and memory(ies) that work together to cause an apparatus, such as a mobile device, computing device, or server, to perform various functions; and c) any or all portions of hardware circuit(s), such as microprocessor(s), processor(s) and / or quantum processor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0138] The techniques and methods described herein may be implemented by various means. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or combinations thereof. For a hardware implementation, the apparatus(es) of example embodiments may be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), graphics processing units (GPUs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof. For firmware or software, the implementation can be carried out through modules of at least one chipset (for example procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in a memory unit and executed by processors. The memory unit may be implemented within the processor or externally to the processor. In the latter case, it can be communicatively coupled to the processor via various means, as is known in the art. Additionally, the components of the systems described herein may be rearranged and / or complemented by additional components in order to facilitate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise configurations set forth in the given figures, as will be appreciated by one skilled in the art.
[0139] It will be understood by a person skilled in the art that, as technology advances, the proposed concept may be implemented in various ways within the scope of the claims. The embodiments are not limited to the example embodiments described above, but may vary within the scope of the claims. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate, not to restrict, the embodiments.
Claims
CLAIMS1. An apparatus for communication with a satellite of a non-terrestrial network, NTN, the apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive, from a satellite of the non-terrestrial network, NTN, an SSB-based measurement time configuration, SMTC, related to SSB-based radio resource management, RRM, measurements on at least one target cell provided by the NTN, wherein the SMTC includes related SMTC occasions, wherein the SMTC indicates a number of parallel SMTCs to be measured timely in parallel and / or a number of satellites to be measured in one SMTC;determine whether two SMTC occasions are considered to collide based on a magnitude of a proximity distance between two SMTC occasions in a time domain, wherein the two SMTC occasions are considered to collide upon the proximity distance being less than or equal to a first threshold value to be determined, wherein the first threshold value is one of at least two different values;determine the first threshold value based on the number of satellites the apparatus is capable of measuring within one SMTC and a number of configured measurements; andin response to determining that the two SMTC occasions are considered to collide, perform measurements on a first SMTC occasion, without performing measurements on a second SMTC occasion.
2. An apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive, from a satellite of a non-terrestrial network, NTN, an SSB-based measurement time configuration, SMTC, related to SSB-based radio resource management, RRM, measurements on at least one target cell provided by the NTN, wherein the SMTC includes related SMTC occasions, wherein the SMTC indicates a number of satellites to be measured in one SMTC;upon a configured number of satellites to be measured in one SMTC being more than one, determine whether two SMTC occasions are considered to collide based on a magnitude of a proximity distance between two SMTC occasions in a time domain, wherein the two SMTC occasions are considered to collide upon the proximity distance being less than or equal to a first threshold value and higher than a second threshold value; andin response to determining that the two SMTC occasions are considered to collide, reduce a configured number of satellites to be measured in one SMTC, and perform measurements on the reduced number of satellites.
3. Apparatus according to claim 2, being caused to:determine the first threshold value based on the number of satellites the apparatus is capable of measuring within one SMTC and a number of configured measurements;in response to determining that the two SMTC occasions are considered to collide, perform measurements on a first SMTC occasion, without performing measurements on a second SMTC occasion.
4. Apparatus according to any preceding claim, being caused to:perform relaxation of the proximity distance between consecutive SMTC occasions, upon the apparatus supporting measurement of multiple satellites within one SMTC occasion and being configured to measure the multiple satellites in at least one SMTC occasion during a SMTC period.
5. Apparatus according to any preceding claim, wherein:the proximity distance is a time interval, or a collision window, between consecutive SMTC occasions.
6. Apparatus according to any preceding claim, being caused to:calculate a relaxation of the proximity distance, based on the number of parallel SMTC occasions to be measured and on the number of satellites in one SMTC occasion.
7. Apparatus according to any preceding claim, being caused to:determine a relaxation rule based on apparatus capabilities.
8. Apparatus according to any preceding claim, wherein:the proximity distance is dependent on the number of satellites the apparatus is capable of measuring within one SMTC occasion.
9. Apparatus according to any preceding claim, wherein:a total proximity distance is dependent on a total number of satellites to be measured across the SMTC occasions within a SMTC period.
10. Apparatus according to any preceding claim, wherein:upon the apparatus being capable of measuring two satellites in one SMTC occasion and being configured to measure more than one satellite in one SMTC occasion, the proximity distance is 5 ms.
11. Apparatus according to claim 10, wherein:the proximity distance is relaxed from 4 ms to 5 ms.
12. Apparatus according to any preceding claim 1 to 9, wherein:upon the apparatus being capable of measuring three satellites in one SMTC occasion and being configured to measure three satellites within one SMTC occasion, the proximity distance is 6 ms.
13. Apparatus according to any preceding claim, wherein:the apparatus is or comprises a user device with reduced capability, RedCap.
