Cell measurements in network

Abstract

There is disclosed a method, for a UE, for configuring neighbour NTN cell measurements in a network. The method comprises: receiving, from a base station, a message comprising configuration for the UE

Description

BACKGROUND Field Certain examples of the present disclosure provide one or more techniques for handling cell measurements in a network. For example, certain examples of the present disclosure provide one or more techniques for configuring, and / or reporting capability for, a neighbour cell measurement in a 3rd Generation Partnership Project (3GPP) 4th Generation (4G) and / or 5th Generation (5G) Terrestrial Network (TN) and / or Non Terrestrial Network (NTN). Description of the Related Art Herein, the following documents may be referenced and the contents thereof are incorporated into the present disclosure: [1] 3GPP TS 38.331 V17.6.0 [2] 3GPP TS 36.331 V17.6.0 [3] 3GPP R2-2313780 [4] 3GPP TS 36.306 V17.4.0 Various acronyms, abbreviations and definitions used in the present disclosure are defined at the end of this description. Overview of NTN One of the areas currently under development in 3GPP 5G wireless technology is support for NTNs. An NTN is a network in which one or more nodes (e.g. a Next Generation Radio Access Network (NG-RAN) node) are provided by a non-terrestrial infrastructure, for example a satellite or High Altitude Platform Station (HAPS). Advantages of using an NTN include (i) extending coverage to regions, such as remote areas, with limited or no coverage from more traditional terrestrial networks, (ii) providing continuous coverage in the event of inoperability of traditional terrestrial networks, such as during natural disasters, and (iii) enhancing overall reliability, resilience and capacity when used in conjunction with existing terrestrial networks. Figure 1 illustrates an exemplary NTN Release 17 architecture and scenario. A satellite network implementing a network node provides coverage through one or more radio beams forming a “footprint” on the surface of the Earth defining a coverage area or cell. An NTN cell may be Earth-moving (i.e. moving over the Earth’s surface according to the motion of the satellite, for example in the case of a Lower Earth Orbit (LEO) satellite), Earth-fixed (i.e. a fixed area of the Earth’s surface, for example in the case of a Geosynchronous Equatorial Orbit (GEO) satellite) or quasi-Earth-fixed (i.e. a fixed area of the Earth’s surface but is maintained for only a limited time as the satellite passes by). Internet of Things (loT) NTN was a 3GPP study and work item in 3GPP Release 17 (RP-202689, RAN#90 December 2020) to provide NTN access for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) loT devices (e.g. Narrowband (NB)-loT and Long Term Evolution Machine Type Communication (LTE-M), including enhanced Machine Type Communication (eMTC)). As noted in 3GPP RP-202689, loT operation is critical in remote areas with low / no cellular connectivity for many different industries. The capabilities of NB-loT and eMTC are a good fit for many applications but some applications may require satellite connectivity to provide coverage beyond terrestrial deployments. New Radio (NR) NTN was a work item in Release 17 to specify adaptation to allow NR to function over NTN (RP-211557, RAN#91-e March 2021). Following the work items in Release 17 there were work items to enhance NR NTN (RP-220953, RAN#95-e March 2022) and loT NTN (RP-220979, RAN#95-e March 2022) in Release 18. Due to the movement of satellites in a non-stationary orbit (e.g. LEO), the cells that a User Equipment (UE) see will be moving (i.e. Earth-moving cells). This results in frequent UE handover from one cell to another, and this handover of service will happen constantly. In view of this, mobility is one of the key issues in both NR NTN and loT NTN. Overview of NB-loT and LTE-M NB-loT is a 3GPP-defined network based on 4th Generation (4G) E-UTRAN that supports ultra-low complexity devices with very narrow bandwidth that was introduced in 3GPP Release 13. The use case of NB-loT is to serve massive loT application, where requirements for instance are to support enhanced coverage, power-efficient operation and a large number of devices. Some of the features introduced are: Support for enhanced coverage through low bandwidth and extreme amounts of repetitions. Power efficient operation by allowing the UE to sleep for very long times, relaxed requirements and more efficient signal to establish with a cell. LTE-M or eMTC is a 3GPP-defined network that is an extension of 4G E-UTRAN that supports low-complexity devices with more narrow bandwidths compared to normal LTE and further simplifications of procedures. Similar to NB-loT, the use case is to serve massive loT, but with more capabilities. Instead of being an entirely new type of device with major air interface changes as in NB-loT, the LTE-M inherits most feature of a regular LTE device, but with some adaptations for low complexity considerations. Overview of NTN System Information As NTN has a number of NTN-specific information elements that are only required when accessing an NTN cell, and also due to the relatively large information elements, it was agreed that new System Information Blocks (SIBs) are needed. In NR NTN, SIB19 contains the required information to access an NTN cell: ------------------------------3GPP TS 38.331 V17.6.0 [1]------------------------------ SIB19 SIB19 contains satellite assistance information for NTN access. SIB19 information element .......rV / 111 11 —' 1 1> 1 i ' I I - / •■! . i '."--I I' r / f er / nceLC'iiil:.-.- / 17 ntn-lIeighC^lL 7; All g / i-it-rV 1 itelFiriCiit i: .-IE:: / / rn ion iitl- ■ -.:--11 :.: ■ - . . 1 •• : 1 ,.:.7 / 1 Fief m.n : = / -:- cat i ori-rl ~ ' . .< rr-r > iBHsiiTgBgiOTSSBSW ntn-UeighCelt 7:. / / 1 :- / 1 / tE::t ---It jn / 7 / - / =ighC / llCc-rif igLii 1- / 1 : ITH-n-i ghoell'‘c nf i i-_l ::= . . nt n-Ciiifig-rl- / 7 / -7:ntig-rl carrierFieq-rl- 7.F.F Z / -ValuelIR ph / f / elllf-r / - Fn / a7 / 1117 _________________________________________SIB19 field descriptions_________________________________________I distanceThresh Distance from the serving cell reference location and is used in location-based measurement initiation in I RRC IDLE and RRC INACTIVE, as defined in TS 38.304 f20]. Each step represents 50m. i ntn-Config Provides parameters needed for the UE to access NR via NTN access such as Ephemeris data, common i TA parameters, k_offset: validity duration for UL sync information and epoch. I nin-NeighCeiiConngLisi, ntn-NeighCeiiCon^gUstExi Provides a list of NTN neighbour cells including their ntn-Config, carrier frequency and PhysCellld. This set I includes all elements of ntn-NeighCellConfigList and all elements of ntn-NeighCellConfigListExt. If ntn- | Config is absent for an entry in ntn-NeighCellConfigListExt, the ntn-Config provided in the entry at the same i position in ntn-NeighCellConfigList applies. Network provides ntn-Config for the first entry of ntn- i NeighCellConfigList. If the ntn-Config is absent for any other entry in ntn-NeighCellConfigList, the ntn- i Config provided in the previous entry in ntn-NeighCellConfigUst applies. I referenceLocaiion ] Reference location of the serving cell provided via NTN quasi-Earth fixed system and is used in location- I based measurement initiation in RRC IDLE and RRC_ INACTIVE, as defined in TS 38.304

[20] , i t-Service Indicates the time information on when a cell provided via NTN quasi-Earth fixed system is going to stop | serving the area it is currently covering. The field indicates a time in multiples of 10 ms after 00:00:00 on I Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31,1899 and Monday, | January 1, 1900). The exact stop time is between the time indicated by the value of this field minus 1 and ; the time indicated by the value of this field. i 3GPPTS 38.331 V17.6.0 [1] In loT NTN, SIB31 contains the required information to access an loT NTN cell: ------------------------------3GPP TS 36.331 V17.6.0 [2]------------------------------ SystemlnformationBlockType31 The IE SystemlnformationBlockType31 contains satellite assistance information for the serving cell. SystemlnformationBlockType 31 is only signalled in a NTN cell. SystemlnformationBlockType31 information element ephemerisInfi ctatev’eCT orbitalPs iiiiiiiiiiiiiii ill i -1' run : ri I i -1'inn ui । “i'inn : I, 3t art! Flat art ci.ib I k-IIac-rll :-rl^ ::= FEQVEHCE -1~ CHOICE ; a Epl t-.cci = lt3t~”~ctor3~rl"? iOBkOllllllllllllllllllllllllllllSpOiOiO®^ = -.3-^-17 CEocEFCE ELIT E--^EZ [ rf E, .lr, ,-:4 7, 3 70, ,2 7 7 CEL-E' ZE ' I IE0ER i> '. . 1> CZ ) , EEE-IER (0..7) IHTEC-ER ::..1013), IHTEIER 1..71-) • PIP ’IIP.L, — IP i • r ■I 'I I ol I >11, — 11 ■ ■ - i ‘4 ■ I p p p '<|, — || . -. 15, a ' 0, a 3 7, s 4 0, 3110, 3100, 3I4'J, 37:: CFTIoMAL, — Hees ; SystemlnformationBlockType31 field descriptions i epochtime ; Epoch time of the satellite ephemeris data and common TA parameters, see TS 36.213

[23] , The reference ] i point for epoch time of the serving satellite ephemeris and Common TA parameters is the uplink time I i synchronization reference point. I i epochTime is the starting time of a DL subframe indicated by startSFN and startSubframe. For serving cell, ] i the startSFN indicates the current SFN or the next upcoming SFN after the frame where the message I ; indicating the epochTime is received. ] i If the field is absent, the UE uses the starting time of the DL subframe corresponding to the end of the SI i i window during which the SI message carrying SIB31 (-NB) is transmitted. I i E-UTRAN always includes epochTime when SIB31(-NB) is provided through dedicated signalling. i ; In case of handover or conditional handover, this field is based on the timing of the target cell, i.e. the i ; startSFN and startSubFrame number indicated in this field refers to the SFN and sub-frame of the target i i cell, and UE considers the target cell epoch time (indicated by the startSFN and startSubFrame in this field) i ; to be the frame nearest to the frame where RRCConnectionReconfiguration message is received. I i k-Mac I ; Scheduling offset used when downlink and uplink frame timing are not aligned at the eNB, see TS 36.213 I ;

[23] , Unit in ms. ] i If the field if absent, the UE uses the (default) value of 0. I ................................. i Scheduling offset used in the timing relationships in NTN, see TS 36.213

[23] , Unit in ms...........................................: i nia-Common ] ; Network-controlled common TA, see TS 36.213

[23] , Unit of ps. i i Step of 32.55208 xio-3ps. Actual value = field value *32.55208 x1 O'3 i i If the field is absent, the UE uses the (default) value of 0. I i nta-CommonDrift i Drift rate of the common TA, see TS 36.213

[23] , Unit of ps / s. i I Step of 0.2 xi O'3 ps / s. Actual value = field value * 0.2 *1 O'3 i i If the field is absent, the UE uses the (default) value of 0._________________________________________________________________________________________ i I nia-CommonDriftVariation i Drift rate variation ofthe common TA, see TS 36.213

[23] . Unit of ps / s2. i i Step of 0.2 *10 4 ps / s2 Actual value = field value * 0.2 xio 4. i I If the field is absent, the UE uses the (default) value of 0. i i orbiialParameiers i Instantaneous values ofthe satellite orbital parameters. The signalled values are only valid for the duration i i as defined by ul-SyncValidityDuration and epochTime. I ------------------------------3GPP TS 36.331 V17.6.0 [2]------------------------------ The system information contains the following: - Serving cell ephemeris elements. This allows the UE to calculate the satellite position for doppler and time pre-compensation. This information may be provided in two 5 formats: o Position, Velocity, Time (PVT) format. This describes a (X,Y,Z) position as well as a speed vector (vX, vY, vZ). o Orbital parameters. This describes the orbital movements of the satellite which is then used to infer the satellite position. 10 - Timing Advance (TA) common parameters. This provides the common timing advance parameters which is introduced to compensate for the feeder link delays. The signalling comprises the following (in total taking up 57 bits): o Absolute TA common (23 bits). o Drift of the TA common, defining how the TA common drifts, i.e. the first 15 derivative of the TA common (19 bits). o Variation of the TA common, defining how the TA common varies, i.e. the second derivative of the TA common (15 bits). - Synchronization validity duration. This is used to define how long the ephemeris and TA common is valid. Epoch time. This defines when the synchronization validity duration should start. K-Offset. This is a scheduling offset for timing relationship in NTN. - K-Mac. This is a scheduling offset used when the downlink and uplink frame timing is not aligned. NR NTN specific information also includes (as part of 3GPP TS 38.331): o T-Service (signalled in SIB3 in loT NTN). o Reference location and distance threshold. This is used for location-based measurement initiation in RRC IDLE and RRC Connected mode. o Neighbour cell ephemeris. This is used for idle mode measurements. Overview of NTN System Information Acquisition As ephemeris information constantly changes due to the movement of the NTN payload (e.g. satellite), there is a need to make sure that the UE is correctly synchronized. Thus, whenever a UE connects to an eNB, the UE needs to read the system information (e.g. SIB19 or SIB31). In loT NTN, every time SIB31 is read, a timer (T317) associated with the ephemeris element is started. At expiry of T317, the UE is no longer considered synchronized and should reacquire SIB31 in order to stay synchronized. In loT NTN, since an loT UE (LTE-M and NB-loT UE) is not expected to be able to acquire system information in connected mode, the UE tunes away and is likely unreachable while reading SIB31. If the loT NTN UE is unable to read the SIB31 within a timer (T318) with a configured duration, the UE performs Radio Link Failure (RLF) similar to other cases where RLF is performed. This operation can be seen in Figure 2. In NR NTN, the UE shall ensure that it has a recent ephemeris (SIB19 in NR) by reading the SIB in time by UE implementation. The T317 timer is different compared to a normal timer in Radio Resource Control (RRC) as it is not started at having received the SIB31. This is because the ephemeris has an epoch time, which is the reference point in time of when the ephemeris is defined. Thus the T317 is started from the epoch time, which may be in the past or in the future relative to have received SIB31. This means that in an UE implementation, the timer may be started with a different value with what was signalled according to what was signalled in the field ul-SyncValidityDuration in SIB31. Overview of loT NTN neighbour cell ephemeris SIB In Release 18 Wl enhancements on loT NTN, it was agreed to introduce neighbour cell ephemeris. In 3GPP R2-2313780 [3], the agreed SIB is the following: 3GPP R2-2313780 [3] SystemlnformationBlockTypeXX The IE SystemlnformationBlockTypeXX contains satellite assistance information for neighbour cells. SystemlnformationBlockTypeXXinformation element -- ?’Cin PTIET neiTl-i'31idit_-l . pill in-rlL iHeigKlAiAggiiieiTAgd EUL. E-PTE2 [31, 31", 31", all, all, all, !Ieed OP 1 ItelLlriOlitl: .-LE.pee.iSieri OCTET TIPIIIO OPTIOIHL, — II-e- A , 3 11, 310, 3 3 1, 3 4 : , , -1_", 31 >1, 3-4", -0PTI01IAL, OPTI0HAL, Tl.p -. ,01101..11-111- . -l ll i ilil it Mil .: : . :i. i ii.,’ I - i i 11 • i io. : ’ i .ITimiAL, — Lee.- 1 "PTTOIIAT,, II""1 "F islTifBOiiiiggilgissiiip 1 Til UAL, 1PTIOIIAL, I PT 101 LAL, — Lee: OP llgillilll yxxyxxy. -- A.-niOTi’P SystemlnformationBlockTypeXX field descriptions epochtime Epoch time of the neighbour satellite ephemeris data and common TA parameters, see TS 36.213

[23] , The reference point for epoch time of the neighbour satellite ephemeris and Common TA parameters is the uplink time synchronization reference point. epochTime is the starting time of a DL subframe indicated by startSFN and startSubframe. If this field is absent, the UE uses epoch time of the serving cell, otherwise the field is based on the timing of the serving cell, i.e. the SFN and sub-frame number indicated in this field refers to the SFN and sub-frame of the serving cell. The startSFN indicates the SFN nearest to the frame where the message indicating the epochTime is received.____________________________ k-Mac Scheduling offset used when downlink and uplink frame timing are not aligned at the eNB, see TS 36.213

[23] , Unit in ms. If the field if absent, the UE uses the (default) value of 0. k Offset Scheduling offset used in the timing relationships in NTN, see TS 36.213 [23). Unit in ms. neigh ValidityDuration Validity duration of the neighbour satellite ephemeris data and common TA parameters, i.e. maximum time duration (from epochTime) during which the UE can apply the satellite ephemeris without acquiring new satellite ephemeris, see TS 36.213

[23] , Unit in second. Value s5 corresponds to 5 seconds, value s1Ocorresponds to 10 seconds and so on. If this field is absent, the UE uses validity duration from the serving cell assistance information.________________________ nia-Common Network-controlled common TA, see TS 36.213

[23] , Unit of ps. Step of 32.55208 xio 3ps. Actual value = field value * 32.55208 xw3. If the field is absent, the UE uses the [default) value of 0. n ta-CommonDrift Drift rate of the common TA, see TS 36.213

[23] , Unit of ps / s. Step of 0.2 xiO'3 ps / s. Actual value = field value * 0.2 xio 3. If the field is absent, the UE uses the (default) value of 0._______________________________________________________________ nia-CommonDriffVariation Drift rate variation ofthe common TA, see TS 36.213

[23] . Unit of ps / s2. Step of 0.2 *10z ps / s2 Actual value = field value *0.2 xio^. If the field is absent, the UE uses the (default) value of 0._______________________________________________________________ t-ServiceSiartNeigh Indicates the earliest time when the area covered by the current serving cell is going to be covered by the neighbour cell(s) served by the satellite indicated by satelliteld. This field is only present for the neighbour cell(s) provided via NTN quasi-Earth fixed system. 3GPP R2-2313780 [3] Each element of the field neighSatellitelnfoList, the neighSatellitelnfo, is referred to as a neighbour satellite assistance info element. 5 In order to associate a broadcasted neighbour satellite assistance information with a cell or a frequency, as signalled in SIB3 or SIB5, a satellite Identity (ID) is introduced. Thus for each frequency in SIB5, the network can signal a list of satellite IDs that correspond to neighbour satellite assistance elements in SIBxx. Thus when the UE attempts to detect cells on a frequency in idle mode, the UE will use the ephemeris to try to detect cells at a specific timing 10 and frequency offsets. Thus if there are two satellite IDs signalled in for a frequency, when the UE attempts to detect cells, it will search two different timing and frequency offsets corresponding to the satellite positions as derived by the ephemeris. The UE may also attempt to detect other cells. The field neighValidityDuration is the validity duration of all of the neighbour satellite 15 ephemeris data and the common TA parameters of all of the neighbour satellite assistance elements. This can be used by the UE to determine roughly when to re-acquire the SIBxx both in RRC idle and RRC connected. When (re-)acquiring the SIBxx, in RRC connected, the UE may use the already existing timer T318 to acquire the SIBxx. The T318 is already used to acquire the SIB31 according to Release 17 specifications. There are also some specifications and special considerations for this purpose: - If the UE acquires SIBxx during T318, the T318does not stop when SIB31 is acquired. - The T318 is stopped when both SIB31 and SIBxx are acquired. - When the T318 expires, RLF is only performed when SIB31 has not been acquired. Overview of NTN Ephemeris Formats There are three ways of signalling the ephemeris in NTN: 1. PVT format, 2. Orbital ephemeris elements, and 3. TLE ephemeris elements (only used for Discontinuous Coverage in loT NTN). PVT Format PVT format signals XYZ position along with the speed vector vXYZ. This can be seen in the following information element: ------------------------------3GPP TS 36.331 V17.6.0 [2] EphemerisStateVectors The IE EphemerisStateVectors provides satellite ephemeris in format of position and velocity state vectors in ECEF. EphemerisStateVectors information element po 111 o n7.-rl “ OOilsOsOI po3ition5-rl~ •'ale ...• Xt ion;.’I.-.1 : i im / pip; , - p. - \ . . .ppp; j.i.il ) ‘ i I.-,::I. .11. - 7-.-- .-. p :: .I.IITEGEIi - l.P.-;: 1 . . 1: id ij: I ) — AEH13TOF EphemerisStateVectors field descriptions positionX, positionY, positionZ X, Y, Z coordinate of satellite position state vector in ECEF. Unit in meter. Step of 1.3 m. Actual value = field value *1.3. velociiyVX, veiocifyVY, veiocityVZ X, Y, Z coordinate of satellite velocity state vector in ECEF. Unit in meter / second. Step of 0.06 m / s. Actual value = field value * 0.06.________________________________________________________________ ------------------------------3GPP TS 36.331 V17.6.0 [2]------------------------------ The position elements (X, Y, Z respectively) each occupy 26 bits and the speed elements (vX, vY, vZ) each occupy 18 bits. Altogether they occupy 132 bits. Orbital Ephemeris Format The ephemeris orbital parameters (also referred to as Keplerian format) provide parameters that indicate how a celestial body moves in space, which allows for accurate synchronization and prediction of future NTN payload position. Ephemeris orbital elements are signalled by the following elements (164 bits total): SemiMajorAxis (33 bits) - Eccentricity (20 bits) - Periapsis (28 bits) Longitude (28 bits) Inclination (27 bits) - Anomaly (28 bits) TLE Orbital Parameters The Two-Line Element (TLE) parameters are based on TLE set, which is industry-acknowledged data format for signalling the movement of a celestial body. Whereas the PVT and orbital ephemeris formats may be used to perform accurate synchronization, TLE parameters may be used primarily for long term prediction. For example, the TLE parameters allow for accurate satellite-pass prediction of up to several days in the future. A full set of TLE parameters can occupy more than 50 Bytes of data containing many fields not required in 3GPP. Therefore, a reduced set of TLE parameters may be used instead, for example based on the following (totalling 189 bits): Inclination (21 bits) - Argument of perigee (22 bits) - Right ascension of the ascending node (22 bits) - Mean anomaly (22 bits) Eccentricity (24 bits) Mean Motion (34 bits) B* signalled by (i) a decimal (18 bits), and (ii) an exponent (5 bits) Epoch star (21 bits) Overview of E-UTRAN and eMTC connected mode mobility E-UTRAN connected mode mobility functions similar to other cellular standards and connected mode mobility is also supported for E-UTRAN eMTC. A standard connected mode handover is performed only when triggered by the eNB. A typical procedure is described below and illustrated in Figure 3. 1. A UE is configured with measurement configuration via RRCConnectionReconfiguration. 2. UE performs neighbour cell measurements, which are configured by the network. 3. A measurement report (of a neighbour cell) is triggered (3a) and sent to eNB (3b). 4. Inter-node procedures, whereby the Source eNB sends a Handover Request to Target eNB after having decided whether to trigger a handover and the Target eNB send a Handover Request Acknowledge to Source eNB. 5. The Source eNB triggers a handover command which is sent to UE. This handover command comprises the RRC message RRCConnectionReconfiguration, containing the mobilityControlinfo field. 6. UE prepares for handover and performs a handover via the random access procedure. A measurement configuration comprises a set of measurement objects and measurement reporting configuration for RRM purposes. These measurement objects define the configurations of the measurements that a UE shall perform in RRC connected. A measurement object is related to an either a frequency or a RAT. There is, for instance, inter-RAT E-UTRA measurement object (MeasObjectEUTRA), which may configure intra or interfrequency measurements. The MeasObjectEUTRA contains configurations, such as the carrier frequency, measurement bandwidth, neighbour cell configurations, specific cells to measure, cells not to measure and report and many more configurations. There are also Inter-RAT measurement object that contains all of the necessary configurations to perform connected mode measurements of NR (MeasObjectNR), UTRA (MeasObjectUTRA), GERAN (MeasObjectGERAN), CDMA2000 (MeasObjectCDMA2000), or WLAN (MeasObjectWLAN). The measurement reporting configuration contains rules that define when a measurement report containing measurements shall be sent. These are typically defined by measurement reporting triggering conditions (also called measurement events), thresholds, and configuring what measure shall be reported. The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention. SUMMARY It is an aim of certain examples of the present disclosure to address, solve and / or mitigate, at least partly, at least one of the problems and / or disadvantages associated with the related art, for example at least one of the problems and / or disadvantages described herein. It is an aim of certain examples of the present disclosure to provide at least one advantage over the related art, for example at least one of the advantages described herein. The present invention is defined in the independent claims. Advantageous features are defined in the dependent claims. Embodiments or examples disclosed in the description and / or figures falling outside the scope of the claims are to be understood as examples useful for understanding the present invention. Other aspects, advantages and salient features of the invention will become apparent to those skilled in the art from the following detailed description taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 illustrates an exemplary NTN Release 17 architecture and scenario; Figure 2 illustrates an exemplary ephemeris synchronization operation; in Figure 2(a) SIB31 functions as normal, and in Figure 2(b) UE fails to read SIB31 during T318 which then expires and triggers RLF; Figure 3 illustrates an exemplary handover procedure; Figure 4 illustrates an example of signalling neighbour satellite / cell assistance information in NTN; Figure 5 illustrates an example of a terrestrial cell signalling neighbouring satellite assistance information to a UE connected to a terrestrial network; Figure 6 illustrates an example of configuring a UE to measure NTN cells in RRC connected; Figure 7 illustrates an example of configuring a UE to measurement specific NTN cells and ephemeris using satellite IDs; Figure 8 illustrates examples of rules and methods when acquiring SIBxx in a terrestrial network where SIB31 is not broadcasted; Figure 9 illustrates an example of signalling capabilities in order to set up NTN measurements in a terrestrial network; Figure 10 is a flowchart of an exemplary method, for a UE, for configuring neighbour NTN cell measurements in a network; Figure 11 is a flowchart of an exemplary method, for a base station, for configuring neighbour NTN cell measurements in a network; and Figure 12 is a block diagram of an exemplary network entity that may be used in certain examples of the present disclosure. DETAILED DESCRIPTION The following description of examples of the present disclosure, with reference to the accompanying drawings, is provided to assist in a comprehensive understanding of the present invention, as defined by the claims. The description includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the scope of the invention. The same or similar components may be designated by the same or similar reference numerals, although they may be illustrated in different drawings. Detailed descriptions of techniques, structures, functions, operations or processes known in the art may be omitted for clarity and conciseness, and to avoid obscuring the subject matter of the present invention. The terms and words used herein are not limited to the bibliographical or standard meanings, but, are merely used to enable a clear and consistent understanding of the invention. Throughout the description and claims of this specification, the words “comprise”, “include” and “contain” and variations of the words, for example “comprising” and “comprises”, means “including but not limited to”, and is not intended to (and does not) exclude other features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof. Throughout the description and claims of this specification, the singular form, for example “a”, “an” and “the”, encompasses the plural unless the context otherwise requires. For example, reference to “an object” includes reference to one or more of such objects. Throughout the description and claims of this specification, language in the general form of “X for Y” (where Y is some action, process, operation, function, activity or step and X is some means for carrying out that action, process, operation, function, activity or step) encompasses means X adapted, configured or arranged specifically, but not necessarily exclusively, to do Y. Features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof described or disclosed in conjunction with a particular aspect, embodiment, example or claim are to be understood to be applicable to any other aspect, embodiment, example or claim described herein unless incompatible therewith. The skilled person will appreciate that the techniques described herein may be used in any suitable combination. Certain examples of the present disclosure provide one or more techniques for handling cell measurements in a network. For example, certain examples of the present disclosure provide one or more techniques for configuring, and / or reporting capability for, a neighbour cell measurement in a 3GPP 4G and / or 5G TN and / or NTN. However, the skilled person will appreciate that the present invention is not limited to these examples, and may be applied in any suitable system or standard, for example one or more existing and / or future generation wireless communication systems or standards, including any existing or future releases of the same standards specification, for example 3GPP 5G, 5G-advanced or 6th Generation (6G). The functionality of the various network entities and other features disclosed herein may be applied to corresponding or equivalent entities or features in the same or any other suitable communication systems or standards. Corresponding or equivalent entities or features may be regarded as entities or features that perform the same or similar role, function or purpose within the network. For example, the functionality of a base station or the like (e.g. eNB, gNB, NB, RAN node, access point, wireless point, transmission / reception point, central unit, distributed unit, radio unit, remote radio head, etc.) in the examples below may be applied to any other suitable type of entity performing RAN functions, and the functionality of a UE or the like (e.g. electronic device, user device, mobile station, subscriber station, customer premises equipment, terminal, remote terminal, wireless terminal, vehicle terminal, etc.) in the examples below may be applied to any other suitable type of device. A particular network entity may be implemented as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure. The skilled person will appreciate that the present invention is not limited to the specific examples disclosed herein. For example: • The techniques disclosed herein are not limited to 3GPP 4G and / or 5G. • One or more entities in the examples disclosed herein may be replaced with one or more alternative entities performing equivalent or corresponding functions, processes or operations. • One or more of the messages in the examples disclosed herein may be replaced with one or more alternative messages, signals or other type of information carriers that communicate equivalent or corresponding information. • One or more further elements or entities may be added to the examples disclosed herein. • One or more non-essential elements or entities may be omitted in certain examples. • The functions, processes or operations of a particular entity in one example may be divided between two or more separate entities in an alternative example. • The functions, processes or operations of two or more separate entities in one example may be performed by a single entity in an alternative example. • Information carried by a particular message in one example may be carried by two or more separate messages in an alternative example. • Information carried by two or more separate messages in one example may be carried by a single message in an alternative example. • The order in which operations are performed and / or the order in which messages are transmitted may be modified, if possible, in alternative examples. Certain examples of the present disclosure may be provided in the form of an apparatus / device / network entity configured to perform one or more defined network functions and / or a method therefor. Certain examples of the present disclosure may be provided in the form of a system (e.g. network or wireless communication system) comprising one or more such apparatuses / devices / network entities, and / or a method therefor. Certain examples of the present disclosure provide a UE and / or a base station (e.g. eNB, gNB) configured to perform a method according to any example, aspect, embodiment and / or claim disclosed herein. Certain examples of the present disclosure provide a network (or wireless communication system) comprising a UE, base station (e.g. eNB, gNB, etc.), and / or any other suitable network entity / entities according to any examples, aspects, embodiments and / or claims disclosed herein. Certain examples of the present disclosure provide a computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according to any example, aspect, embodiment and / or claim disclosed herein. Certain examples of the present disclosure provide a computer or processor-readable data carrier having stored thereon a computer program according to any example, aspect, embodiment and / or claim disclosed herein. Various examples of the present disclosure will now be described in more detail. Both in NR NTN and loT NTN, the possibility to signal neighbour satellite assistance information for the purpose of neighbour cell measurements have been introduced. This can be seen in Figure 4. This was introduced in Rel-17 for NR NTN and Rel-18 for loT NTN. However, for loT NTN, there are still some missing aspects related to how to configure a neighbouring cell measurement, for example: How is a UE configured to measure a neighbouring cell? o What information fields need to be used, and how should they be used? o How does a network indicate what neighbour satellite assistance information to use? o Are there any special measurement considerations for NTN? Furthermore, in Rel-18 the possibility to signal the above introduced neighbour satellite assistance in a terrestrial network was also introduced. The purpose of this is to allow for UEs in idle, inactive and connected mode to efficiently measure neighbouring NTN cells while the UE is camping or is connected to a terrestrial cell. Without introducing this enhancement, the mobility from TN to NTN may be very challenging. The use case of introducing this enhancement is that controlled mobility from a terrestrial network and a non-terrestrial network may occur, either when the UE is RRC idle or RRC connected. This is useful for instance when the UE is located in a rural region with poor coverage, for instance in areas where it is not economically feasible to extend terrestrial coverage to. A figure of this scenario can be seen Figure 5. However, in order for this to work, there are still several challenges and missing methods and algorithms that are addressed by various examples of the present disclosure: - A UE reporting what type of NTN cell measurement it supports when camping or connected to a terrestrial network How to configure a UE to measure an NTN cell when connected to a terrestrial cell? How to acquire the new SIB when in connected to a terrestrial network? Certain examples of the present disclosure provide one or more techniques for reporting capabilities and / or configuring connected mode measurements of NTN cells, both when the UE is connected to an NTN cell, and when it is connected to a terrestrial cell. Certain examples of the present disclosure provide a method, for a UE, for configuring neighbour NTN cell measurements in a network, the method comprising: receiving, from a base station, a message comprising configuration for the UE to perform one or more neighbour NTN cell measurements; performing one or more neighbour NTN cell measurements according to the configuration; and transmitting, to the base station, a measurement report based on the measurements, wherein the configuration comprises a measurement object defining configurations of measurements that a UE shall perform, and wherein the measurement object comprises one or more satellite IDs for associating a neighbour cell or frequency to neighbour cell satellite assistance information. Certain examples of the present disclosure provide a method, for a base station, for configuring neighbour NTN cell measurements in a network, the method comprising: transmitting, to a UE, a message comprising configuration for the UE to perform one or more neighbour NTN cell measurements; and receiving, from the UE, a measurement report based on one or more neighbour NTN cell measurements performed by the UE according to the configuration, wherein the configuration comprises a measurement object defining configurations of measurements that the UE shall perform, and wherein the measurement object comprises one or more satellite IDs for associating a neighbour cell or frequency to neighbour cell satellite assistance information. In certain examples, the method for the UE may further comprise: if a handover request indicating an NTN cell is received from the base station, performing handover to the NTN cell. In certain examples, the method for the base station may further comprise: determining whether to trigger handover of the UE to an NTN cell based on the measurement report. In certain examples, the UE may be in connected mode. In certain examples, the UE may be a NB-loT UE or an eMTC UE. In certain examples, the measurement object (e.g. MeasObjectEUTRA) may specify information applicable for intra-frequency or inter-frequency E-UTRA cells. In certain examples, the message may be an RRCConnectionReconfiguration message. In certain examples, the one or more satellite IDs may comprise a satellite ID per cell. In certain examples, the measurement object may further comprise one or more IDs (e.g. cellsToAddModList) indicating cells the UE may attempt to measure. In certain examples, the satellite assistance information may comprise ephemeris. In certain examples, the neighbour cell satellite assistance information may be signalled in a certain SIB (e.g. SIB33). In certain examples, the base station may be associated with an NTN cell or a TN cell. In various examples, the ephemeris is not only applicable for satellite payloads, but can also apply to other platforms such a HAPS. Accordingly, references herein to “satellite ephemeris” may apply not only to satellites, but also to other NTN platforms and / or payloads. In the present disclosure, “New SIB”, “SIBxx”and similar, refer to the System Information Block that is being introduced for loT NTN that contains neighbour satellite assistance information such as ephemeris, for the purpose of neighbour cell measurements. In future specifications the name of this SIB may for instance be SystemlnformationBlockType33, SystemlnformationBlockType34, or any other suitable naming. As the techniques disclosed herein also apply to NB-loT, any references to any types of SIB may also encompass the NB-loT version(s), which may end with “-NB” (SystemlnformationBlockType31 -> SystemlnformationBlockType31-NB). Thus SIBxx may include SIB33(-NB) or SIB34(-NB). While “terrestrial network” is used in the present disclosure, the skilled person will appreciate that the techniques disclosed herein may be applied, not only to a terrestrial network, but also any suitable type of network that is not an NTN network, for example an Air-To-Ground network or similar. Therefore, references to TN or TN cell may include references to a non-NTN or non-NTN cell. In the present disclosure, the wording “RRC connected”, “connected mode” and “RRC_CONNECTED” may be used interchangably. Similarly, “idle mode”, “RRC idle” and ”RRC_IDLE” may be used interchangeably. In certain examples, when “idle mode” is mentioned, this may also encompass “inactive mode”, “RRC inactive” and / or “RRC_INACTIVE”, as the actions performed in these states in general are the same or similar. In the present disclosure, references to “monitoring” may include the idle / inactive mode action of detecting and measuring a cell on a frequency, while “measuring” may include the action of detecting and measuring in connected mode. In certain examples the terms may be used interchangeably. Various examples of the present disclosure are described in terms of LTE loT. However, the skilled person will appreciate that the various techniques described herein may also be applied more widely, for example to NG-RAN nodes, such as gNBs, NG-eNBs (eNBs connected via 5GC), and all related, newly defined and / or existing RRC signaling and / or messages, X2, Xn, S1, NG, and / or F1 signalling and / or messages, and / or related network entities (e.g. MME, AMF, other). For instance, references to a measurement object may include references to a measurement object for E-UTRAN or for NR, i.e. MeasObjectEUTRA or MeasObjectNR. The skilled person will appreciate that the various techniques disclosed herein may also be applied to NR NTN. Configuring NTN neighbour cell measurements Figure 6 illustrates an example of configuring a UE to measure NTN cells in RRC connected. For configuring NTN neighbour cell measurements, there are some enhancements required that are different from configuring terrestrial neighbour cell measurements in a terrestrial network. This is mostly related to the fact that the ephemeris and neighbour cell assistance information is required to measure an NTN cell efficiently, which is signalled in a new SIB. For each neighbour satellite assistance element in new SIB, there is a satellite identifier that identifies the neighbour satellite assistance information, i.e. the ephemeris. This is also signalled for specific frequencies in SIB3 / SIB5, making it possible to tie a inter / intra-frequency to a neighbour satellite, making it possible to know how to track a specific frequency. This is also signalled in SIB31, because there may be the case that there are multiple cells at different frequencies that originate from the same satellite as the serving cell. These issues are relevant in an NTN cell as well in a terrestrial cell when configuring to measure an NTN cell. In certain examples of the present disclosure, the satellite ID (satelliteld in SystemlnformationBlockType31 or SystemlnformationBlockTypeXX) in SIB31 is always present if the new SIB is signalled. This can be expressed as ‘ satelliteld is always present if SystemlnformationBlockTypeXX is signalled”. If the SIBxx is dedicatedly signalled, then the network ensures that the satellite ID is delivered to the UE. Similarly, the satellite ID in SIB31 is always signalled if there are satellite ID(s) signalled in SIB3 and SIB5. In order to measure neighbour satellite in connected mode, there similarly needs to be a satellite ID configured in Measurement Objects (MeasObject), which is the configuration where connected mode measurements are configured. To allow for a UE to measure a neighbouring NTN cell in connected mode, there may need to be considerations on how the satellite ID(s) are signalled. In certain examples of the present disclosure, since a measurement objects indicates that the UE shall measure a frequency along with a set of cells, a set of satellite IDs, per cell may be signalled. This is configured as a list of satellite IDs, which is a parallel list with the current cellsToAddModList which includes currently includes the celllndex, physCellld and celllndividualOffset. As it is a parallel list, the length of the list of satellite IDs would have to have the same length as that of the list of cells. If a satellite ID is not configured for a specific cell, the UE assumes that the cell is a terrestrial cell. An example of this technique can be seen in specification example 1a below. Alternatively or additionally, if there is no satellite IDs signalled for a frequency at all, the UE interprets this as if the frequency of a measurement object is a terrestrial network. Similarly, if there are one or more satellite IDs signalled for a frequency, the UE may interpret this as the frequency only being an NTN frequency. In certain examples of the present disclosure, the MeasObject only indicates a single satellite ID per measurement object. Similarly, if the network does not configure a satellite ID in the measurement object, the UE assumes that the cell or the measurement object is for a terrestrial cell. This may also need to include the condition that whether SIBxx is configured, which would be mean that the full condition would be that if SIBxx is broadcasted and no satellite ID is configured for the measurement object. Similarly, for inter-RAT measurements connected mode measurements, such as measuring NR NTN cells, the satellite ID may be configured as part of the NR measurement object, i.e. MeasObjectNR. An example of this can be seen in specification example 1b below. In certain examples of the present disclosure, when a UE is configured to measure NTN cell(s), the UE only attempts to acquire the cells that are indicated by the measurement object, i.e. through cellsToAddModList and allowedCellsToAddModList. This is important as the UE may not be able to attempt to detect other cells, as the different timing and frequency offset may make this very challenging. Thus the UE may not detect and measure other cells than what are signalled. The condition for this can for instance be that “if the UE is configured to measure an NTN cell, the UE only measures on the cells explicitly indicated by the measObject for the frequency”, or “if a satelliteld is configured for the measObject, the UE only measures on the cells indicated by the measObject for the frequency”. An example of how this can be captured in specifications is given in specification example 1c below and in Figure 7. In certain examples of the present disclosure, it is explicitly configured that the UE only needs to attempt to detect the cells as specified in the measurement object. This can be an optional flag measureOnlylndicatedCells. This also means that only the cells that have been indicated are reported in a measurement report. One restriction on configuring neighbour cell measurements needed in an NTN cell would be how many different neighbouring cell ephemeris that are needed to be tracked. This for instance would put a limitation to how many different satellitelds that can be a part of a measurement object. For instance, if a UE is asked to measure 4 cells in connected mode, the restriction may be that only 2 different types of different satellite IDs may be signalled. This may or may not include the serving cell ephemeris. This may be important as tracking a lot of different satellites with different frequency and timing offsets is difficult for a UE and is independent on the number of cells that are tracked. Configuring NTN measurements in a terrestrial network Configuring a UE in a terrestrial network to measure an NTN cell may similarly follow the above technigues. However, for configuring measurements of NTN cells, there may need to be some restrictions. One such restriction may for instance be that a network is not allowed to configure an NTN cell as part of a conditional handover configuration for a UE connected to a terrestrial cell, i.e. an NTN cell is not configured as part of CondReconfig. An example of this can be seen in specification example 1d below. The new SIB can be both broadcasted in a non-terrestrial network as well as a terrestrial network. As the new SIB was originally introduced to broadcast neighbour satellite assistance information in a non-terrestrial network, there needs to be some considerations when signalling it in a terrestrial network. One signalled field in the neighValidityDuration, which is the duration in which neighbour satellite assistance information is considered valid. If it is not present, then the UE shall use the ul-SyncValidityDuration signalled in SIB31. However, as the SIB31 is not signalled in a terrestrial network, if the field is not present, then there is the issue that UE would not know which value to apply. Thus in certain examples of the present disclosure, when the new SIB is broadcasted in a terrestrial network, the neighbouring validity duration (neighValidityDuration) is always signalled, thus always present. An example of this can be seen in specification example 1e below. In certain examples (e.g. alternative examples), the neighbouring validity duration, if not signalled, is set to a fixed value. This value can for instance be 1 minute, or 1 hour. This allows for very fixed and clear requirements on how often the new SIB shall be acquired. Acquiring new SIB in connected mode in a terrestrial network When a UE is configured to measure a non-terrestrial network in connected mode, the UE may also be required to regularly acquire the new SIB. Ina non-terrestrial network, the UE may acquire the SIB in connected mode during the timer T318. The T318 timer is started when timer T317 expires, and the T317 timer is started according to acquiring SIB31. However, SIB31 is important to broadcast the serving cell satellite assistance information, which is not needed as the cell is now a terrestrial network. Thus the issue is how to acquire the new SIB in this case. In certain examples of the present disclosure, the UE starts the timer T317 when successfully acquiring SIBxx in terrestrial network. This would be the action upon reception of SystemlnformationBlockTypeXX in a terrestrial network. The value of T317 would use neighValidityDuration instead of the ul-SyncValidityDuration in SIB31, which is not broadcasted. In certain examples of the present disclosure, another timer, a new T3xx is started when acquiring the new SIB in a terrestrial network and T318 is started as usual. In certain examples of the present disclosure, the UE does not attempt to acquire SIB31 while T318 is running while in a terrestrial network. In other words, the UE acquires the SIB31 only in a non-terrestrial network. An alternative description is that the acquires SIB31, if SIB31 broadcasted. In certain examples of the present disclosure, the UE does not declare RLF if T318 has expired and the neither SIB31 or new SIB has been acquired in terrestrial network. It can also be that when T318 expires in a terrestrial network, the UE does not perform RLF. This can be expressed as T318 only expiring if the UE is in a non-terrestrial network, and if the T318 expires in a terrestrial network, the UE only stops attempting to acquire SIBxx. In certain examples of the present disclosure, the uplink synchronization is not lost during T318 if T318 runs in a terrestrial network. This would be expressed as the uplink synchronisation is only lost when T318 expires in a non-terrestrial network. In certain examples of the present disclosure, the UE stops the timer T318 when only SIBxx has been acquired, and not SIB31. This can alternatively be described as timer T318 being stopped when both SIB31, if broadcasted, and SIBxx has been acquired. Examples of the above behaviour can be seen in specification example 3 below and in Figure 8. In certain examples, the above behaviour, which is very different from how a UE would operate and acquire the system information, may have as a number of conditions one or more of: Operating in a terrestrial network o Alternative descriptions could be “if UE is connected to an NTN celt’ - Operating in a network that broadcasts new SIB but not SIB31 o For instance “if systemlnformationBlockType31(-NB) is not broadcasted’ If SIB31 is not broadcasted Configured via a flag acquireTN-SIBxx which indicates the above behaviour, otherwise the UE does for instance not acquire SIBxx in RRC connected. UE capabilities related to monitoring NTN from TN As disclosed above, the UE may monitor the NTN from a terrestrial network. In order for the network to be aware of this capability, the capability of monitoring or measuring the NTN cells from a TN cell can be signalled to the network. These type of capabilities may not be a loT NTN-related capability, as it would be signalled in an terrestrial network. As part of this capability, the UE would be capable of tracking time and frequency offsets. This capability may be apply both for an NR UE, i.e. to measure a NR NTN cell from NR TN cell or an loT NTN UE, i.e. measuring an loT NTN (E-UTRAN) cell from a TN E-UTRAN cell. Figure 9 illustrates an example of signalling capabilities in order to set up NTN measurements in a terrestrial network. Similarly, if a UE is capable of measuring NR NTN cells while in a E-UTRAN terrestrial network, this may also be signalled by the UE. There may also need to be detailed information on what the UE is capable of monitoring. Whether the UE is capable of monitoring Geosynchronous Orbit (GSO) or Non-Geosynchronous Orbit (NGSO). This could be needed as the requirements on tracking the satellite and the timing and frequency offset are different depending on whether the satellite is stationary or non-stationary. The GSO satellite position is generally quite stable, whereas the NGSO is either moving slowly or extremely quickly. The distinction could for instance be made that the UE is capable of monitoring GEO, Medium Earth Orbit (MEO) or LEO. A UE could for instance only be capable of monitoring GEO-stationary satellites, as the LEO satellites move too fast requiring more advanced signal processing to compensate for the doppler frequency offset caused by the fast movement. There can thus be capabilities for each GSO or NGSO, or for GEO, MEO and LEO. In NR NTN and loT NTN there is already a capability ntn-SupportScenario that specifies which scenario that a UE supports measuring GSO or NGSO. In certain examples of the present disclosure this capability, along with the capability indicating ue supports monitoring or measuring NTN cell from TN cell, indicates that the UE supports monitoring or measuring an NTN cell of a specific type, i.e. GSO and NGSO. The UE may also signal whether the UE is capable to monitor NTN cells from idle mode or connected mode. This may be important as the increased complexity of monitoring NTN may only be feasible in one of the modes, i.e. only in idle / inactive mode, but not in connected mode. Similarly, there may be a capability indicating whether a UE can monitor intra- or inter-NTN frequencies. As an extension for UEs connecting to eNB via 5GC, the UE may also signal whether it can monitor NTN cells in RRC inactive. The signalling can for instance be one capability for connected mode, and one capability for both idle and inactive mode. Examples of these capabilities can be seen in specification example 3 below. As an example of how to combine the above techniques, a UE may for instance indicate whether it is capable of one or more of: Monitoring an loT NTN NGSO cell from an E-UTRAN TN cell in idle or inactive mode Monitoring an loT NTN GSO cell from an E-UTRAN TN cell in idle or inactive mode Measuring an loT NTN NGSO cell from an E-UTRAN TN cell in connected mode Measuring an loT NTN GSO cell from an E-UTRAN TN cell in connected mode - Monitoring an NR NTN NGSO cell from an E-UTRAN TN cell in idle or inactive mode - Monitoring an NR NTN GSO cell from an E-UTRAN TN cell in idle or inactive mode Measuring an NR NTN NGSO cell from an E-UTRAN TN cell in connected mode Measuring an NR NTN GSO cell from an E-UTRAN TN cell in connected mode Monitoring an NR NTN NGSO cell from an NR TN cell in idle and inactive mode Monitoring an NR NTN GSO cell from an NR TN cell in idle and inactive mode - Measuring an NR NTN NGSO cell from an NR TN cell in connected mode - Measuring an NR NTN GSO cell from an NR TN cell in connected mode There may also be capabilities indicating whether a UE can monitor and evaluate an NTN cell from a terrestrial network in a Conditional Handover Configuration. This is due to the increased complexity related to monitoring for NTN. The UE may also indicate whether it is capable of simultaneously monitoring a terrestrial network cell and an NTN cell, or whether measurement gaps are required. The UE may also indicate how many NTN cells or satellites that a UE can measure when in a terrestrial network. This can for instance be coupled with how many NTN cells it can measure while measure other terrestrial cells. As an example of how this can be defined, if a UE normally may measure up to 8 terrestrial neighbouring cells, then when configured to measure both terrestrial and NTN neighbouring cells, the number of terrestrial cells can be 4 and NTN cells can be 2, i.e. one NTN cells counts as 2 terrestrial cells. This is due to the extra power consumption likely required for a non-terrestrial cell. The UE may also indicate whether it is capable of acquiring SIB33 in connected mode during T318. For a non-loT device i.e. an E-UTRAN LTE device, this capability may be not be signalled as the UE is in general capable of acquiring SIB in RRC Connected. Figure 10 is a flowchart of an exemplary method, for a UE, for configuring neighbour NTN cell measurements in a network. Referring to Figure 10, in a first operation 1001, the UE receives, from a base station, a message comprising configuration for the UE to perform one or more neighbour NTN cell measurements. The configuration comprises a measurement object defining configurations of measurements that a UE shall perform. The measurement object comprises one or more satellite IDs for associating a neighbour cell or frequency to neighbour cell satellite assistance information. In a second operation 1002, the UE performs one or more neighbour NTN cell measurements according to the configuration. In a third operation 1003, the UE Transmit, to the base station, a measurement report based on the measurements. Figure 11 is a flowchart of an exemplary method, for a base station, for configuring neighbour NTN cell measurements in a network. Referring to Figure 11, in a first operation 1101, the base station transmits, to a UE, a message comprising configuration for the UE to perform one or more neighbour NTN cell measurements. The configuration comprises a measurement object defining configurations of measurements that a UE shall perform. The measurement object comprises one or more satellite IDs for associating a neighbour cell or frequency to neighbour cell satellite assistance information. In a second operation 1102, the base station receives, from the UE, a measurement report based on one or more neighbour NTN cell measurements performed by the UE according to the configuration. Specification Examples Example 1a Changes to specification 3GPP TS 36.331 are indicated below in red / grey: 3GPP TS 36.331 V17.6.0 example MeasObJectEUTRA The IE MeasObJectEUTRA specifies information applicable for intra-frequency or inter-frequency E-UTRA cells. MeasObJectEUTRA information element — A3H13TART lescUhj <5CtEUTRA :: = '.'.j r i. j.cri.' ixri rEQl-EH-E- : .-1--1 il m EI Uln , IllllOi Illicit -ill ".--dl 1- 1.-:Ra::-1.: 1 :: PIT.:-.(- 111" Oil, 1 .-.-I; -: ■. ;n n- I jli'---l 1-n: I g tHsalEi-tq -- Cell Hat -aillaOt'Riiiiovillst — Excluded Hat rUlUdrd'MlAdA. iBBBBBBBBBBi -•1L1H • l! k i. 1 i.111' h ' i ' i t } 11 u'.'-ju-j-uj't nV nn Vnrt 1 , -- ‘V : 'V.V-: ] ] Ct till’ i n , rVriLiot C --11 - ~ C' AV W d L i c t --villndWW AhFAHLT iEV, B-PTIOIIAL, OPT I ORAL, OPTIO1IAL, nd Oli inlUdad'Ollla 7 :A1:: .-I-dLl 5 t E.-nalUdldClllaO-lOdall: 11131 OPTICU-L, -.- ill: ii in i'.b ■ .-.-- i : on : 1 n i pt l ' o i h ,, — ■ -- >11 ........' 0 I : : : . I , 11 f 0' '■ I I - i 1 >' ■ nA 1--11,01,, -- II :-- m. a ,-'ubt_ . tn'.'-'iiHgll'tgli-i_ Ha Till 11 huH it 1-:o_Jl ijli-oloi -401- .0 00000010000000000001::::1^ [ t'-'idel.andF-,?R0-.5r3-rll E 1 -1 LEA1I OE-TIOIIAL — :: nd PTE-R0RQ [[ allTTT-0tnal:?Aiii5--tLial-rH 01111.-dt::Liat OE-TIOIIAL, —Inn:. Oil .alt 000-01115 1 aAldM-rdList-ill Alt-HT-CallaT-aAddl ItdLii 1-110 OP0IO1IAL, 1110-110 OEO_ On ( ;.:-:l.n: :-:.(111-11:111.101:11-- (nku, ar I', ::.-1 "O, in.-: 'O'-o, OOOOOOOOOOOSIOllIilililililiiillid riduoedlliaa-RiL’t-jL-iiianti-L’ll B-OOLE.Al'I OEH'llIAL, -- Uta: OI( lilial I1,0-0: .-.it j-t-l_ Ilaaa I ?-0tnfig-i’H -1ETI01I.AL — Pm Oli aH,:'"td0tL_31. R?iiic--'aLia t-rla 1 illIndioLia 1 oE'OIolIAL, allt'-’t-TCaHa 1: Aldi It-dLia 1-rll AH-A-tdCall = T-:AddII: .-Hat-rli OE-TIOIIAL, ltS||i|lBlllllliiiiiBiSSSSSSSSioBBBBBBiSSSSSSSS^ i lul । -1’- -t. - 1 : - - I - RI IT : : -i -1 1 --ll-'d-'-' , - 11 I I • r I .--0-: -' - •'a I i i--EI I'l'K' - . - - ,-J'0 I'. 11II, fifiiiiiiiiiiiiBiiiiiiiiiiiiiiiii iBiBBBBBBBBBBBBBBLiillllBBBBBBBBBBoBBBBBBBBiilllllBioiiBBBBBBBBBBBBBBBBBBIIIIBBi tn-Piiiimail: ; 10,:'R5iiic--.-e-Lia t-rli T::-?.ea aur-aeET-tlllaaaLia t-tl-. OEOIOUAL, — Paia 011 tt-RaAEAa?: alTtA.ddList-rll T::-Raa E-UE-aaPt-a’ll laasLiat-al 4 OP0IO1IAL, — Ilia Oli f iiiibiiia-1 .i::i a Ort-niir-rl 4 H'OLEAII OEOIOHAL O|-0T-“>l 10 | -- :-.-,,--1 OR 1 1 .. V:T 01 -ri': 1 1 .-:1 'VMM'-J ESllISTISAaSMSitES®® Ed'IE fjf: -Valu^ElITRl ESIEEiijiflSfEOO®® 'E :3IEE ::: e Ill®: OF Cill-sT'jAddno :®tSeH:Oo®aa» '-11 T -Mail 1 :: .0011:-:1--1 EIS FEydEnCE I MeasObjectEUTRA field descriptions aHowedCeHsToAddModList Ust pf cells_^ ajlowedCeiisfoRemoveUsi List of cells to remove from the list of allow-listed cells. aitilf-^ List of cells to add / modify in the cell list for which the alternative time to trigger specified by alternativeTimeTcTnqger in reportConfigEUTRA, if configured, applies. altTTT-CeUsToRemoVeList................................................................................................................................................................... List of cells to remove from the list of cells for alternatiye time to trigger. carrierFreq Identifies E-UTRA carrier frequency for which this configuration is valid. E-UTRAN does not configure more than one measurement object for the same physical frequency regardless of the E-ARFCN used to indicate this. CarrierFreq-r13 is included only when the extension list measObjectToAddModListExt-r13 is used. If carrierFreq-r13 is present, carrierFreq (i.e., without suffix) shall be set to value maxEARFCN. ceiilndex Entry index in the ceii list. An entry may concern a range of ceils, in which case this value applies to the entire range. ceUlndividualOffset i Cell individual offset applicable to a specific cell. Value dB-24 corresponds to -24 dB, dB-22 corresponds to -22 i dB and so on. ceiisToAddModLisi List of cells to add / modify in the cell list. cellsToAddModList-v1610 indicates list of RSS assistance information which is used for the corresponding physCellld. If E-UTRAN includes cellsToAddModList-v1610 or it includes the same number of entries, and listed in the same order, as in cellsToAddModList (i.e. without suffix). .......... saref / ffeAT The satellite ID used io associate a cell to a neighbour satellite assistance information as signalled in Sysfem / nforma^onKoc / rTypeXX. lithe field is not present for a ceii and Systern / nformat / onB / oc / rTyp^ signalled, the UE considers the ceil to be a terrestrial ceii. .....".......................................................................................................................................................................................... Changes to specification 3GPP TS 36.331 are indicated below in red / grey: --------------------------3GPP TS 36.331 V17.6.0 example -------------------------- MeasObjectNR The IE MeasObjectNR specifies information applicable for inter-RAT NR neighbouring cells. MeasObjectNR information element — AFH1FTART manRU-Indeii'Fell 1_el-rlb I IsnF.F-Inde.-.'I'ellQu aIHR-sl : CTTIOHRL, He®d|§g|g|g|sssss||||||issssss|lllll||sssssss|lllll|sSss|||l|l|||ssss offeetFreq-rl;I Q-OffaetR.anqeInteER.RT DEFAULT u, e::-aludedCel la T : F e_. :—eList-rlb Tel llnder.List OPT I DUAL, eneludedOel 1ST a At ?: '-.-’dList - El b ?el IsTcA.ddl IrdListl'F -rl: OPTIO1IAL, |gg|gifggggggggggiigb|g|||||ggggggggggggggggggg|||||||ggg:ggggggggggggggggi^ quantityC ent a aOet-rlF 1' TETER I 1 . . Hianyu.antdete' A-nlT i, 1 1 a H-I'Hlii-A aRa - 'tUFTD-dl r <HTF,E <1 . . tu A A • ’ UFTDi / OF Phy.'a* 1 1',R- U " Ol'TlOllAL, -- :a‘A or [| -.--Ill'll,' ■. ; -■ I ■ -i l ' '- ■ I-1 I ' • yu'- I I I IIIR-H L A T I OIL L, gi<gsgiii:gigggggggiiiiiiiiiiiiigiLiLiLg:gigigiiiiiiiiiiiiiiigggggggiiiiiiiiiiiiiggggg;g;LLiLiLiL dexi-.'e35=-T.-:ae:bFromCell-xl5 SOOLEAH OPTIONAL, as-R0FI-T“es t e-uent-rl b 11-RF3I-1 Ieaa ureinent-_l 1 OITIOILAL, HgSdlsgHlSSSSSSSSSSAAAAAL bandHR-rlt CHClOE { IgggggggggggggggggiagggggggggggggggggggggggggigiitiOTTiililililililil setup FreqEandlndiuat-brHR-rl a I OPTIOHAL — Ae; Oli ili^iiiiiiiililoAgii!!iiigggggggiiiiiiiigggggg||s^ 1 liil - :-i Ai >1 I ■ [HR- : 1 • 1 I >i[ Iv I ' .1A I RI IT'- .- I ■: : . '11R - 1 1 I opTU'll.-d. -- 1 1-1 .'b <1 ddlA ! I . • igiggigigigigigiggbbigiiiiiigigigigigigigiiii^^^^ giiisisisiiiiisisisisisisisisisisisigiiigiiiiiiis giiiiiiiiitSAgAAAig-AsmgiiggsBsiWBiWiKjiiSgigigigigigigi ceiiaToAddlkiList-ElG Cell = 1; A? A IcdLiatHR-rlc IFTII-HAL — Hee? IT R|?-'.I-.-i 111 i-.iFbi'.-11R—i it : : •• in-- i.:T I in I ir i'" ■ ’ : 1 . •s ubc a rr ie rip a a ? a y F PE - rl b LEOUHI'I-A ■_ I im'-AF-R-i 1 b, LllHIIER-..n_ -nib, I Hu a, J , [[ tfb-T:lRu ..--elf CHUTE release TULL, setup FFE-T: I Ie as ure-rl 5 } OPTIOHAL iFFFFFbigggggggFFFFFFgigigFFFb^ -Ab-pr bl I11 I.U'O-F ..’II nllF'-ilF ELF--- . nQ-‘L-Fu I at u-nllF - A. .••'h 11 --0,1).1--10 i utii"' .uni.i-1'■:■.d i 11-1-.:,--.A,- i:.; 1.:T। 1 ill 1-,'dI,I,: 11-1R-r I --- 3:11-:-1--.,.:11 I'.-riOLt-! Ie-.. s' — ।'. .i id 11 -i i - -.ibi •--• .-- - । nt . ..:1-1-,.,.. iLiai 0 A- 'ell. T-.lv in. Li.fill-.^-' UubUEUOE FILE (I...-..: rib OPTIOHAL -- -: --: FharedEyeetrum SiSFg|ligigggggggggFFFi||||ggFFFFgggb^ ;.--U 4<o} , Teed OH OPTTOHAT,, -- -Ana. -A:dl-1- „:ILi ,-:1 1-11-.-1-1-- I'PT > 111 H a. >- 1 1’ Lli,. '-.-I = ubaarri~i'Ft - :1. ilFF-rli EHUI1ER-FEI li-lzlRa, hHnltd) OETIOIIAL, a.-b-pi.aiti-i:,' '1-' ■■lOiHR-rl'T ,-,^-1---111:1.^1^1111.-1.1^-^1- ^I-TI<11IAL, -- 'E. 3 ha rede peatman .-lb~E-.-iti._r., '1- '-11.-Im Aldi R nLltMIF-^ E FE~E = lit i-HbCL-'All = F - ^ : A 1_ 4Li = tjlR-rl^ ■ 'tciid Fi.arecFp.eatrum L-F iti r, A- = _1 I R~m ~L1 tlIF-__“ FEJIElfE .FIFE ,1.. - >><>F El. •'It opTTA IRE — '--I Ft i radtpi .-t r. im FtlljTu.lddfEdEiiiliA-rll : : FLi. - A J1 = L 11. .in i .' 1^.' • <A ‘ il T .d UI _• FeidSTbAdaWdEisbHRpO .................... .............................. ....................... :eliObAdOOHR~il aelllndet-El.: j-.hvaaallld-rli REQUEHCE Fir,-1 EeiiE :lIF-rlF •> I LiJ'aa.IdMi.iJIIR-: ; 1 :: ad I Tr.d>-■•-r I .; physCa 11 Id -1'1 E a e 111 nd i a i d i: .51 b i r _=• e t -1-1 >: RlFi'.df.R i 1 . .mi:1?' 1 IM' ■. '■ , Fi-.yi 1=1 lldllR-rl 5, 'i-Fl 1.-: nt Range MeasObjectNR field descriptions bandNR................................................................................................................................................................................................................................... Indicates the frequency band of the NR carrier frequency configured in this MeasObjectNR. This field is always set to setup when the network configures measurements with this MeasObjectNR. ; carrierFreq i Identifies the SSB frequency to be measured. E-UTRAN does not configure more than one measurement object for i the same SSB frequency. i ceiilndividualOffset i Cell individual offset applicable to a specific cell.______________________________________________________________________________ deriveSSBindexFromCeii The field indicates whether the UE may use, to derive the SSB index of a cell on the indicated SSB frequency and subcarrier spacing, the timing of the NR serving cell with the same SSB frequency and subcarrier spacing if configured. Otherwise, the field indicates whether the UE may use the timing of any detected cell with the same SSB frequency and subcarrier spacing. measDurationNR ; Number of consecutive symbols for which the Physical Layer reports samples of RSSI (see TS 38.215

[89] ). Value i sym1 corresponds to one symbol, sym14or12 corresponds to 14 symbols of the reference numerology for NCP and I 12 symbols for ECP, and so on. If measDurationNR-r17 is present, the UE shall ignore measDurationNR-r16. i quaniityCon^gSei ; Indicates the n-th element of quantityConfigNRList provided in MeasConfig.___________________________________________ refSCS-CP-NR..................................................................................................................................................................................................................i Indicates a reference subcaqier spacing and cyclic prefix to be used for RSSI to: rmtc-FrequencyNR Indicates the center frequency of the measured bandwidth (see TS 38.215 £89]). rmic-PeriodiciiyNR Indicates the RSSI measurement timing configuration (RMTC) periodicity (see TS 38.215

[89] ). Value ms40 corresponds to 40 ms .periodicity, ms80 corresponds to 80j ms .penqdicily^ and so on. rmtc-SubframedffsetNR Indicates the RSSI measurement timing configuration (RMTC) subframe offset (see TS 38.215 [89)). If not configured, the UE chooses a random value as rmtc-SubframeOffsetNR for measDurationNR which shall be selected to be between 0 and the configured rmtc-PeriodicityNR with equal probability. rsConfigSSB Indicates the SSB configuration for measuring the set of SS blocks within the SMTC measurement duration. sate / / / Wd The satellite ID used to associate a cell to a neighbour satellite assistance information as signalled in Sysfem / nfc?7??abonB / ockTypaXX. If the field is not present for a ceil and Systemfofo?7??abon8focA7ypaXX is signalled, the UE considers me ceil io oe a terrestrial ceii. ssb-PosiiionQCL-NR Indicates the QCL relationship between SS / PBCH blocks for a specific neighbor cell as specified in TS 38.213

[88] , clause 4.1. If provided, the cell specific value overwrites the common value signalled by ssb-PositionQCL-CommonNR in MeasObjectNR for the indicated cell.______________________________________________________________________________ ssb PositionQCL-CommonNR Indicates the QCL relationship between SS / PBCH blocks for NR neighbor cells as specified in TS 38.213

[88] , clause 4.1. If ssb-PositionQCL-CommonNR-r17 is present, the UE shall ignore ssb-PositionQCL-CommonNR-r16. subcarrierSpacingSSB Subcarrier spacing of SSB. Only the following values are applicable depending on the used frequency: i FR1: 15 or 30 kHz i FR2-1: 120 or 240 kHz i FR2-2: 120, 480, or 960 kHz i rmic-BandwidihNR ; Indicates the bandwidth for the RSSI measurement.______________________________________________________________ threshRS Index List of thresholds for consolidation of L1 measurements per RS index. Conditional presence SharedSpectrum SharedSpectrum2 Explanation The field is optional Need ON if NR operates with shared spectrum channel access; otherwise, it is not present. The field is mandatory present if NR operates with shared spectrum channel access; otherwise, it is not present. Changes to specification 3GPP TS 36.331 are indicated below in red / grey: --------------------------3GPP TS 36.331 V17.6.0 example -------------------------- 5.5.1 Introduction .. . OMITTED . .. The measurement procedures distinguish the following types of cells: 1. The serving cell(s) - these are the PCell and one or more SCells, if configured for a UE supporting CA or DC. Likewise, NR serving cell(s) are the NR PCell, NR PSCell and NR SCells, if the UE is configured with MR-DC. 2. Listed cells - these are cells listed within the measurement object(s) or, for inter-RAT WLAN, the WLANs matching the WLAN identifiers configured in the measurement object or the WLAN the UE is connected to. 3. Detected cells - these are cells that are not listed within the measurement object(s) but are detected by the UE on the carrier frequency(ies) indicated by the measurement object(s) or, for inter-RAT WLAN, the WLANs not included in the measObJect WLAN but meeting the triggering requirements. NOTE X: For measurement objects measuring NTN cells, the UE only performs measurements on the listed cells indicated by the measurement object. For E-UTRA, the UE measures and reports on the serving cel 1(s). listed cells, detected cells, transmission resource pools for V2X sidelink communication and, for RSSI and channel occupancy measurements, the UE measures and reports on any reception on the indicated frequency. For inter-RAT NR, the UE measures and reports on detected cells and, if configured with MR-DC, on NR serving cell(s) and, for RSSI and channel occupancy measurements, the UE measures and reports on the indicated frequency. For inter-RAT UTRA, the UE measures and reports on listed cells and optionally on cells that are within a range for which reporting is allowed by E-UTRAN. For inter-RAT GERAN, the UE measures and reports on detected cells. For inter-RAT CDMA2000, the UE measures and reports on listed cells. For inter-RAT WLAN, the UE measures and reports on listed cells. NOTE 2: For inter-RAT UTRA and CDMA2000. the UE measures and reports also on detected cells for the purpose of SON. NOTE 3: This specification is based on the assumption that typically CSG cells of home deployment type are not indicated within the neighbour list. Furthermore, the assumption is that for non-home deployments, the physical cell identity is unique within the area of a large macro cell (i.e. as for UTRAN). Whenever the procedural specification, other than contained in clause 5.5.2, refers to a field it concerns a field included in the VarMeasConfig unless explicitly stated otherwise i.e. only the measurement configuration procedure covers the direct UE action related to the received measConfig. . . . OMITTED . .. 5.5.3      Performing measurements 5.5.3.1      General . . . OMITTED . . . The UE shall: .. . OMITTED . .. 2> else: 3> if a measurement gap configuration is setup; or 3> if the UE does not require measurement gaps to perform the concerned measurements: 4> if s-Measure is not configured; or 4> if the UE is not in NE-DC and the PCell RSRP. after layer 3 filtering, is lower than s- Measure-. or 4> if the UE is in NE-DC and the PSCell RSRP, after layer 3 filtering, is lower than s-Measure-, or 4> if the associated measObject concerns NR; or 4> if measDS-Config is configured in the associated measObject. 5> if the UE supports CSI-RS based discovery signals measurement; and 5> if the event Id in the associated reportConflg is set to eventO I or eve mt'2. or if reportStrongestCSI-RSs is set to true in the associated reportConflg-. 6> perform the corresponding measurements of CSI-RS resources on the frequency indicated in the concerned measObject, applying the discovery signals measurement timing configuration in accordance with measDS-Config in the concerned measObject, 6> if reportCRS-Meas is set to true in the associated reportConflg, perform the corresponding measurements of neighbouring cells on the frequencies indicated in the concerned measObject as follows: 7> for neighbouring cells on the primary frequency, apply the time domain measurement resource restriction in accordance with measSubframePatternConfigNeigh, if configured in the concerned measObject, 7> apply the discovery’ signals measurement timing configuration in accordance with measDS-Config in the concerned measObject. 5> else: 6> perform the corresponding measurements of neighbouring cells on the frequencies and RATs indicated in the concerned measObject as follows: 7> for neighbouring cells on the primary frequency, apply the time domain measurement resource restriction in accordance with measSubframePatternConfigNeigh, if configured in the concerned measObject, 7> if the UE supports CRS based discovery signals measurement, apply the discovery signals measurement timing configuration in accordance with measDS-Config, if configured in the concerned measObject, 7> for measObject configured with satdlheld, the UE only measures on tire cells uiuicmed m o / iaaM(jate.st <oi me rieipitncv, Changes to specification 3GPP TS 36.331 are indicated below in red / grey: --------------------------3GPP TS 36.331 V17.6.0 example -------------------------- 5.3.5.9      Conditional reconfiguration 5.3.5.9.1 General The network configures the UE with conditional reconfiguration (i.e. conditional handover, conditional PSCell addition, or inter-SN conditional PSCell change) including per candidate target cell an RRCConnectionReconfiguration to be stored and to be applied upon the fulfilment of an associated execution condition. The network shall ensure to not configure a UE in a terrestrial network with an MTN cell as a candidate cell as The UE shall: 1> if the received conditionalReconfiguration includes the condReconfigurationToRemoveList'. 2> perform the conditional reconfiguration removal procedure as specified in 5.3.5.9.2; 1> if the received conditionalReconfiguration includes the condReconfigurationToAddModList. 2> perform the conditional reconfiguration addition / modification procedure as specified in 5.3.5.9.3; --------------------------3GPP TS 36.331 V17.6.0 exampls -------------------------- Example 1e Changes to specification 3GPP TS 36.331 are indicated below in red / grey: --------------------------3GPP TS 36.331 V17.6.0 example -------------------------- SystemlnformationBlockTypeXX The IE SystemlnformationBlockTypeXX contains satellite assistance information for neighbour cells. SystemlnformationBlockTypeXXinformation element re:.luidti_ ret- nrecihretellirelrereire - rl 1 I 4- 1 J11’ "i 1 i ' .1 i I T • : :-41-1 IS lire re.ret~.iiit eirireiret-rre sin: re-;. .- [ .re, .ire, re re : t re, - i", --re, &PTIOHAL, -- litre &?- i.rere re.i.re iteigWateiiitelr.freist-iTS : : = re ere re .rerere. .irerere-re-■ re iirererereiutre: f.-re ::= reEQUEireE { retreiire reirere -: re- Upl.v:. 3-in .rec-re renrere, -- ire=.- re nt =!-■ Yuni,.. .2 94^ / E4TIOHAL -- svt3 5 ep'jchlime-rl?. ftartRFli-rif: .-taLtcUhFF? —> ZEFEAER (u . EAEEPEF nj. .102.3) , iiiiiiiiiiiiii OPTIDUAL, -- DITEGES. '1..51 J -- t-t’ t"ri ■” Pt n 'I'-rl Tin - ~ 1 rTToii-r, -- IAnA 10 SystemlnformationBlockTypeXXfield descriptions epochtime Epoch time of the neighbour satellite ephemeris data and common TA parameters, see TS 36.213

[23] , The reference point for epoch time of the neighbour satellite ephemeris and Common TA parameters is the uplink time synchronization reference point. epochTime is the starting time of a DL subframe indicated by startSFN and startSubframe. If this field is absent, the UE uses epoch time of the serving cell, otherwise the field is based on the timing of the serving cell, i.e. the SEN and sub-frame number indicated in this field refers to the SEN and sub-frame of the serving cell. The startSFN indicates the SEN nearest to the frame where the message indicating the epochTime is received.____________________________ k-Mac Scheduling offset used when downlink and uplink frame timing are not aligned at the eNB, see TS 36.213

[23] , Unit in ms. If the field if absent, the UE uses the (default) value of 0. k-Offset Scheduling offset used jn the ti^mmgjela^ neigh ValidityDuration Validity duration of the neighbour satellite ephemeris data and common TA parameters, i.e. maximum time duration (from epochTime) during which the UE can apply the satellite ephemeris without acquiring new satellite ephemeris, see TS 36.213

[23] , Unit in second. Value s5 corresponds to 5 seconds, value s10corresponds to 10 seconds and so on. If this field is absent the UE uses validity duration from the serving cell assistance information. When broadcasted in a nta-Common Network-controlled common TA, see TS 36.213

[23] , Unit of ps. Step of 32.55208 xw3ps. Actual value = field value * 32.55208 xw3 If the field is absent, the UE uses the (default) value of 0. n ta-CommonDrift Drift rate of the common TA, see TS 36.213

[23] , Unit of ps / s. Step of 0.2 x 103 ps / s. Actual value = field value* 0.2 *103. If the field is absent, the UE uses the (default) value of 0.________________________________________________________________ nia-CommonDriftVariation Drift rate variation of the common TA, see TS 36.213

[23] , Unit of ps / s2. Step of 0.2 xi O’4 ps / s2 Actual value = field value * 0.2 xiO'4 If the field is absent, the UE uses the (default) value of 0.________________________________________________________________ i-ServiceStartNeigh Indicates the earliest time when the area covered by the current serving cell is going to be covered by the neighbour cell(s) served by the satellite indicated by satelliteld. This field is only present for the neighbour cell(s) provided via NTN quasi-Earth fixed system._________________________________________________________________________________ 15 --------------------------3GPP TS 36.331 V17.6.0 example -------------------------- Changes to the specification text in 3GPP R2-2313780 are indicated below in red / grey: --------------------------3GPP R2-2313780 example -------------------------- 5.2.2.xx     Actions upon reception of SystemlnformationBlockTypeXX Upon receiving SystemlnfortnaiionBlockTypeXX (SystemltrfotTOationB^ in a cell where SysteminformationBlockType? i is not broadcast: start or restart timer 1317 with the duration neigh I '’alidityDuratioH. 5.3.18          T317 expiry The UE shall: I >if in RRC^CONNECTED and not performing GNSS measurement: 2> in an NTN, inform lower layers that the UL synchronisation is lost; 2> start tinier T318; 2> acquire SystemlnformationBlockType31 (SystemlnformationBlockType31 -NB in NB-IoT). if broadcasted, as specified in 5.2.2; 2> if the UE acquires SystemlnformationBlockTypeXX (SystemlnformationBlockTypeXX-NB in NB-IoT) as specified in 5.2.2: 3> inform lower layers when UL synchronisation is restored upon successful acquisition of SystemInformationBlockType31 (SystemInformationBlockType31-NB in NB-IoT); 3> stop timer T318 when both SystemInformationBlockType31 (SystemInformationBlockType31-NB in NB-IoT), if broadcasted, and SystemlnformationBlockTypeXX (SystemlnformationBlockTypeXX-NB in NB-IoT) are acquired; 2> else: 3> upon successful acquisition of SystemInformationBlockType31 (SystcmInformalionBlockTypc31-NB in NB-IoT): 4> stop timer T318; 4> inform lower layers when UL synchronisation is restored. NOTE 1: SystemlnformationBlockType31 (SystemInformationBlockType31-NB inNB-IoT) may be broadcast on a different narrowband or different NB-IoT carrier than the one configured to the UE. NOTE 2: The exact time when UL synchronisation is restored (after SystemInformationBlockType31 or Systemin forma in NB-IoT is acquired) is left to UE implementation, which can be from the subframe indicated by epochTime and optionally before the subframe indicated by epochTime. NOTE 3: For UEs not capable of performing system information acquisition and GNSS measurement at the same time, if the UE cannot complete acquisition of SystemlnformationBlockType31 (SystemlnformationBlockType31-NB) before the start of GNSS measurement gap, acquisition of SysteminformationBlockType31 (SystemInformationBlockType31-NB') may be postponed until GNSS measurement is completed, and T318 is restarted after GNSS measurement is completed. 5.3.11.3 Detection of radio link failure The UE shall: 1> in case any DAPS bearer is configured, only the target PCell is considered in the following; 1> upon T310 expiry; or 5 1 >upon T312 expiry; or 1> in an NTNuponT318 expiry anASystemInfomiationBlockType31 (SystemInformattonBlockType31-NB in NB-loT) not acquired; or 1> upon reaching t-Service if t-Service is broadcast; or 1> upon random access problem indication from MCG MAC while neither T300, T301, T304 nor T311 is 10 running; or 1> upon indication from MCG RLC, which is allowed to be send on PCell, that the maximum number of retransmissions has been reached for an SRB or DRB: . . . OMITTED . .. 15 Timer Start Stop At expiry T317 NOTE1 Start or restart from the subframe indicated by epochTime upon reception of SystemlnformationBlockType3 1 (SystemlnformationBlockType 31-NB in NB-loT), or upon reception of RRCConnectionReconfiguratio n message for the target cell including mobilityControlInfo, or upon conditional reconfiguration execution i.e. when applying a stored RRCConnectionReconfiguratio n message for the target cell including mobilityControlInfo, or when acquiring X when Sysrem / nformaffonB / oo / rType-3 Stop T317, if it is running, for the source cell upon reception of RRCConnectionReconfiguration message including mobilityControlInfo, or upon conditional reconfiguration execution i.e. when applying a stored RRCConnectionReconfiguration message including m obilityCon trot Info. Perform the actions as specified in 5.3.18. T318 NOTE1 Upon starting acquisition of Systeminformation BlockType3 1 (SystemlnformationBlockType 31-NB in NB-loT) or upon starting acquisition of Sysfom / RftwralfonBfockTy’peX’ Xin RRC_CONNECTED " Upon successful acquisition of System Information BlockType31 (System lnformationBlockType31 -NB in NB-loT) if broadcast and SystemlnformationBlockTypeXX (System InformationBlockTypeX X-NB in NB-loT) if broadcast, in RRC_CONNECTED If security is not activated and the UE is not a NB-loT UE that supports RRC connection reestablishment for the Control Plane CloT EPS optimisation: go to RRC_IDLE else: initiate the connection reestablishment procedure as specified in 5.3.7. Examples of new capabilities: --------------------------3GPP TS 36.306 V17.4.0 [4] example -------------------------- 4.3.x.y ntn-Measurements-r18 This field indicates whether a UE supports being configured to perform measurements of NTN cells while connected to a non-NTN cell. Measuring an NTN cell includes the capability of the UE to track and compensate for time and frequency offset using the neighbour cell assistance information. This also includes the capability to acquire SystemlnformationBlockTypeXX. 4.3.x.y ntn-NR-Measurements-r18 This field indicates whether a UE supports being configured to perform inter-RAT measurements of NR NTN cells while connected to a non-NTN cell. Measuring an NR NTN cell includes the capability of the UE to track and compensate for time and frequency offset using the neighbour cell assistance information. This also includes the capability' to acquire SystemlnformationBlockTypeXX. 4.3.x.y ntn-MeasurementsGSO-r18 This field indicates whether a UE supports being configured to perform measurements of GSO NTN cells while connected to a non-NTN cell. Measuring an NTN cell includes the capability of the UE to track and compensate for time and frequency offset using the neighbour cell assistance information. This also includes the capability' to acquire SystemlnformationBlockTypeXX. A UE supporting this feature shall also set the ntn-ScenarioSupport accordingly. 4.3.X.Z ntn-MeasurementsNGSO-r18 This field indicates whether a UE supports being configured to perform measurements of NGSO NTN cells while connected to a non-NTN cell. Measuring an NTN cell includes tire capability of tire UE to track and compensate for time and frequency offset using the neighbour cell assistance information. This also includes the capability to acquire SystemlnformationBlockTypeXX. A UE supporting this feature shall also set the ntn-ScenarioSupport accordingly. --------------------------3GPP TS 36.306 V17.4.0 [4] example -------------------------- Figure 12 is a block diagram of an exemplary network entity that may be used in examples of the present disclosure. For example, a UE and / or base station (e.g. eNB, gNB) in the examples of Figures 1-11 may comprise an entity of Figure 12. The skilled person will appreciate that a network entity may be implemented, for example, as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure. The entity 1200 comprises a processor (or controller) 1201, a transmitter 1203 and a receiver 1205. The receiver 1205 is configured for receiving one or more messages from one or more other network entities, for example as described above. The transmitter 1203 is configured for transmitting one or more messages to one or more other network entities, for example as described above. The processor 1201 is configured for performing one or more operations, for example according to the operations as described above. The techniques described herein may be implemented using any suitably configured apparatus and / or system. Such an apparatus and / or system may be configured to perform a method according to any aspect, embodiment, example or claim disclosed herein. Such an apparatus may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). The one or more elements may be implemented in the form of hardware, software, or any combination of hardware and software. It will be appreciated that examples of the present disclosure may be implemented in the form of hardware, software or any combination of hardware and software. Any such software may be stored in the form of volatile or non-volatile storage, for example a storage device like a ROM, whether erasable or rewritable or not, or in the form of memory such as, for example, RAM, memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a CD, DVD, magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are embodiments of machine-readable storage that are suitable for storing a program or programs comprising instructions that, when executed, implement certain examples of the present disclosure. Accordingly, certain examples provide a program comprising code for implementing a method, apparatus or system according to any example, embodiment, aspect and / or claim disclosed herein, and / or a machine-readable storage storing such a program. Still further, such programs may be conveyed electronically via any medium, for example a communication signal carried over a wired or wireless connection. While the invention has been shown and described with reference to certain examples, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the invention, as defined by the appended claims. Abbreviations / Definitions In the present disclosure, the following acronyms / definitions may be used. 3GPP 4G 3rd Generation Partnership Project 4th Generation 5 5G 5th Generation 5GC 5G Core 6G 6th Generation AMF Access and Mobility Management Function CDMA Code Division Multiple Access 10 EDGE Enhanced Data rates for GSM Evolution eMTC enhanced Machine Type Communications eNB Base Station E-UTRA Evolved Universal Terrestrial Radio Access E-UTRAN Evolved Universal Terrestrial Radio Access Network 15 GEO Geosynchronous Equatorial Orbit GERAN GSM EDGE Radio Access Network gNB 5G Base Station GSM Groupe Special Mobile GSO Geosynchronous Orbit 20 HAPS High Altitude Platform Station ID Identity / ldentifi cation IE Information Element loT Internet of Things LEO Lower Earth Orbit 25 LTE Long Term Evolution LTE-M Long Term Evolution Machine Type Communication MEO Medium Earth Orbit MME Mobile Management Entity MTC Machine-Type Communications 30 NB Base Station NB Narrowband NG Next Generation NG-RAN Next Generation Radio Access Network NGSO Non-Geosynchronous Orbit 35 NR New Radio NTN Non-Terrestrial Network PVT Position, Velocity, Time RAN Radio Access Network RAT Radio Access Technology 40 Rei Release RLF Radio Link Failure RRC Radio Resource Control RRM Radio Resource Management SIB System Information Block 45 TA Timing Advance TLE Two-Line Element TN Terrestrial Network TS Technical Specification Txxx Timer xxx 50 UE User Equipment UL Uplink WLAN Wireless Local Area Network X2 / Xn Interface between RAN nodes

Claims

1. A method, for a UE, for configuring neighbour NTN cell measurements in a network, the method comprising:receiving, from a base station, a message comprising configuration for the UE to perform one or more neighbour NTN cell measurements;performing one or more neighbour NTN cell measurements according to the configuration; andtransmitting, to the base station, a measurement report based on the measurements,wherein the configuration comprises a measurement object defining configurations of measurements that a UE shall perform, andwherein the measurement object comprises one or more satellite IDs for associating a neighbour cell or frequency to neighbour cell satellite assistance information.

2. A method, for a base station, for configuring neighbour NTN cell measurements in a network, the method comprising:transmitting, to a UE, a message comprising configuration for the UE to perform one or more neighbour NTN cell measurements; andreceiving, from the UE, a measurement report based on one or more neighbourNTN cell measurements performed by the UE according to the configuration, wherein the configuration comprises a measurement object defining configurations of measurements that the UE shall perform, andwherein the measurement object comprises one or more satellite IDs for associating a neighbour cell or frequency to neighbour cell satellite assistance information.

3. A method according to claim 1, further comprising: if a handover request indicating an NTN cell is received from the base station, performing handover to the NTN cell.

4. A method according to claim 2, further comprising: determining whether to trigger handover of the UE to an NTN cell based on the measurement report.

5. A method according to any preceding claim, wherein the UE is in connected mode.

6. A method according to any preceding claim, wherein the UE is a NB-loT UE or aneMTC UE.

7. A method according to any preceding claim, wherein the measurement object (e.g. MeasObjectEUTRA) specifies information applicable for intra-frequency or inter-frequency E-UTRA cells.

8. A method according to any preceding claim, wherein the message is an RRCConnectionReconfiguration message.

9. A method according to any preceding claim, wherein the one or more satellite IDs comprise a satellite ID per cell.

10. A method according to any preceding claim, wherein the measurement object further comprises one or more IDs (e.g. cellsToAddModList) indicating cells the UE may attempt to measure.

11. A method according to any preceding claim, wherein the satellite assistance information comprises ephemeris.

12. A method according to any preceding claim, wherein the neighbour cell satellite assistance information is signalled in a certain SIB (e.g. SIB33).

13. A method according to any preceding claim, wherein the base station is associated with an NTN cell or a TN cell.

14. A UE configured to perform a method according to any of claims 1, 3 and 5 to 13.

15. A base station configured to perform a method according to any of claims 2 and 4 to13.

16. A network (or wireless communication system) comprising a base station according to claim 15 and a UE according to claim 14.

17. A computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according to any of claims 1 to 13.

18. A computer or processor-readable data carrier having stored thereon a computer program according to claim 17.

Images