EP4666444A1 - Satellite assistance information provisioning from a terresterial network - Google Patents

Satellite assistance information provisioning from a terresterial network

Info

Publication number
EP4666444A1
EP4666444A1 EP24706208.6A EP24706208A EP4666444A1 EP 4666444 A1 EP4666444 A1 EP 4666444A1 EP 24706208 A EP24706208 A EP 24706208A EP 4666444 A1 EP4666444 A1 EP 4666444A1
Authority
EP
European Patent Office
Prior art keywords
satellite
ntn
assistance information
cell
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP24706208.6A
Other languages
German (de)
French (fr)
Inventor
Helka-Liina MÄÄTTÄNEN
Johan Rune
Ignacio Javier PASCUAL PELAYO
Ming Li
Emre YAVUZ
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP4666444A1 publication Critical patent/EP4666444A1/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H04W56/0015—Synchronization between nodes one node acting as a reference for the others
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/1851—Systems using a satellite or space-based relay
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/004—Synchronisation arrangements compensating for timing error of reception due to propagation delay
    • H04W56/0045—Synchronisation arrangements compensating for timing error of reception due to propagation delay compensating for timing error by altering transmission time

Definitions

  • EPS Evolved Packet System
  • LTE Long-Term Evolution
  • EPC Evolved Packet Core
  • Narrowband-Internet of Things (NB-IoT) and Long Term Evolution for Machines (LTE-M) are part of the LTE specifications and provide connectivity to massive machine type communications (mMTC) services.
  • mMTC massive machine type communications
  • 5GS 5G system
  • RAT radio access technology
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low latency communication
  • 5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC).
  • NR New Radio
  • 5GC 5G Core Network
  • the NR physical and higher layers reuse parts of the LTE specification and add needed components when motivated by the new use cases.
  • 3GPP also began preparing NR for operation in a Non- Terrestrial Network (NTN).
  • NTN Non- Terrestrial Network
  • the work was performed within the study item “NR to support Non-Terrestrial Networks” and resulted in 3GPP TR 38.811. See, 3GPP TR 38.811, Study on New Radio (NR) to support non-terrestrial networks.
  • NR New Radio
  • the work to prepare NR for operation in an NTN network continued with the study item “Solutions for NR to support Non-Terrestrial Network,” which resulted in 3GPP TR 38.821.
  • a satellite radio access network usually includes: a satellite that refers to a space-borne platform; an earth-based gateway that connects the satellite to a base station or a core network, depending on the choice of architecture; a feeder link that refers to the link between a gateway and a satellite; and an access link that refers to the link between a satellite and a UE.
  • a satellite may be categorized as low earth orbit (LEO), medium earth orbit (MEO), or geostationary earth orbit (GEO) satellite, as follows: LEO: typical heights ranging from 250 – 1,500 km, with orbital periods ranging from 90 – 120 minutes. MEO: typical heights ranging from 5,000 – 25,000 km, with orbital periods ranging from 3 – 15 hours. GEO: height at about 35,786 km, with an orbital period of 24 hours.
  • LEO typical heights ranging from 250 – 1,500 km, with orbital periods ranging from 90 – 120 minutes.
  • MEO typical heights ranging from 5,000 – 25,000 km, with orbital periods ranging from 3 – 15 hours.
  • GEO height at about 35,786 km, with an orbital period of 24 hours.
  • the significant orbit height means that satellite systems are characterized by a path loss that is significantly higher than what is expected in TNs.
  • a communication satellite typically generates several beams over a given area.
  • the footprint of a beam is usually in an elliptic shape, which has been traditionally considered as a cell.
  • the footprint of a beam is also often referred to as a spotbeam.
  • the spotbeam may move over the earth surface with the satellite movement or may be earth fixed with some beam pointing mechanism used by the satellite to compensate for its motion.
  • the size of a spotbeam depends on the system design, which may range from tens of kilometers to a few thousands of kilometers.
  • FIGURE 1 illustrates an example architecture of a satellite network with bent pipe transponders.
  • Ephemeris data (sometimes referred to as just “ephemeris”) is data that allows a UE (or other entity) to determine a satellite’s position and velocity.
  • the ephemeris data contains parameters related to the satellite’s orbit.
  • ephemeris data should be provided to the UE such as, for example, to assist with pointing a directional antenna (or an antenna beam) towards the satellite and to calculate a correct Timing Advance (TA) and Doppler shift.
  • TA Timing Advance
  • ephemeris data will be broadcast in the system information (SI) in each cell, included in an NTN specific System Information Block (SIB), which is labeled SIB19 in NR NTN and SIB31 IoT NTN.
  • SIB System Information Block
  • Exactly which set of parameters is chosen can be decided by the user and/or network provider, and many different representations are possible.
  • a choice of parameters used often in astronomy is the set (a, ⁇ , i, ⁇ , ⁇ , t).
  • the semi-major axis a and the eccentricity ⁇ describe the shape and size of the orbit ellipse;
  • the inclination i, the right ascension of the ascending node ⁇ , and the argument of periapsis ⁇ determine its position in space, and the epoch t determines a reference time (e.g. the time when the satellites moves through periapsis).
  • FIGURE 2 illustrate a set of parameters.
  • the Two-Line Elements use mean motion n and mean anomaly M instead of a and t.
  • a completely different set of parameters is the position and velocity vector (x, y, z, v x , v y , v z ) of a satellite. These are sometimes called orbital state vectors. They can be derived from the orbital elements and vice versa, since the information they contain is equivalent. All these formats (and many others) are possible choices for the format of ephemeris data to be used in NTN.
  • An aspect discussed during the 3GPP study item and captured in 3GPP TR 38.821 is the validity time of ephemeris data.
  • NTN-Specific Information in SI Due to the special operating conditions in a NTN, the SI broadcast in an NTN cell has to include NTN-specific information.
  • a new SIB (SIB19) is introduced in NR NTN that contains NTN-specific information.
  • the new SIB31 more or less corresponds to SIB19 in NR NTN.
  • SIB19 is defined in ASN.1 code in 3GPP TS 38.331 version 17.0.0.
  • the NTN-Config-r17 IE is defined in ASN.1 code in the same specification.
  • the EphemerisInfo IE is defined in ASN.1 code in the same specification.
  • the UE needs to measure the signal quality of the cell to perform cell selection or cell re-selection. While the UE is in RRC_Connected mode, it will report the measured results to the network.
  • the above procedures are performed based on the measurement configuration from the network, which includes the following parameters: ⁇ Measurement objects: A list of objects on which the UE shall perform the measurements.
  • ⁇ Reporting configuration A list of reporting configurations where there can be one or multiple reporting configurations per measurement object. Each measurement reporting configuration consists of the following: o Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be periodical or a single event description.
  • o RS type The RS that the UE uses for beam and cell measurement results (Synchronization Signal/Physical Broadcast Channel (SS/PBCH) block or Channel State Information-Reference Signal (CSI-RS)).
  • o Reporting format The quantities per cell and per beam that the UE includes in the measurement report (e.g., Reference Signal Received Power (RSRP)) and other associated information such as the maximum number of cells and the maximum number beams per cell to report.
  • RSRP Reference Signal Received Power
  • each configuration consists of the following: o Execution criteria: The criteria the UE uses for conditional reconfiguration execution.
  • RS Reference Signal
  • RS Reference Signal
  • Measurement identities For measurement reporting, a list of measurement identities where each measurement identity links one measurement object with one reporting configuration.
  • Quantity configurations The quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement.
  • Measurement gaps Periods that the UE may use to perform measurements.
  • a UE in RRC_CONNECTED maintains a measurement object list, a reporting configuration list, and a measurement identities list according to the 3GPP specification.
  • RAN4 agreements The latest RAN4 agreement include: ⁇ Define “availability of valid target satellite information as side condition” o Parameters listed in R2-2201884 are defined as the required target satellite information for measurement and mobility. ⁇ For measurement ⁇ Ephemeris ⁇ Epoch time ⁇ SMTCs ⁇ DL polarization information ⁇ Serving cell stop time and reference location for IDLE mode measurement trigger in NGSO fixed cell, if applicable ⁇ Under RAN1 discussion: o Feeder link delay (i.e., common TA and K_MAC) of the neighbor cell should also be provided to UE for neighbor cell SMTC adjustment o separate validity timers ⁇ For mobility ⁇ Target cell Ephemeris information ⁇ Epoch time of the ephemeris ⁇ Common TA ⁇ Validity timer information for target cell mobility ⁇ DL and UL Polarization information ⁇ K_offset ⁇ Kmac (to determine UE-gNB RTT and perform RACH to target) ⁇ If the side condition is not met, o Require
  • satellite assistance information for neighbor cells may be optionally included in SIB19 (in NR NTN) or SIB31 (in IoT NTN).
  • the UE is not required to perform neighbor cell measurements if the corresponding satellite assistance information is not present. This applies to both RRC_CONNECTED and RRC_IDLE modes.
  • the TN network need to provision the satellite information to the UEs.
  • RAN2 there is an ongoing discussion on whether/how it should be possible to transmit SIB19 from a TN cell.
  • a new mechanism is required to provide satellite assistance information (provided in SINB19 in an NTN cell) in a TN cell.
  • methods and systems are disclosed for providing the essential parts of SIB19 in NR NTN and SIB31 in IoT NTN to make measurements and enable mobility.
  • a method by a UE for receiving satellite assistance information from a TN includes receiving satellite assistance information from a network node serving the UE in a cell associated with the TN.
  • the satellite assistance information is associated with a satellite that is a candidate for serving the UE in a cell associated with a Non-Terrestrial Network, NTN.
  • the satellite assistance information is received via broadcast.
  • a UE for receiving satellite assistance information from a TN is configured to receive satellite assistance information from a network node serving the UE in a cell associated with the TN.
  • the satellite assistance information is associated with a satellite that is a candidate for serving the UE in a cell associated with a Non-Terrestrial Network, NTN.
  • the satellite assistance information is received via broadcast.
  • a method is provided by a network node associated with a TN for providing satellite assistance information for a satellite of an NTN.
  • the method includes transmitting, to a UE the satellite assistance information associated with a satellite that is a candidate for serving the UE in a cell associated with the NTN.
  • the network node is serving the UE in a cell associated with the TN, and the satellite information is transmitted via broadcast.
  • a network node associated with a TN for providing satellite assistance information for a satellite of a NTN is configured to transmit, to a UE the satellite assistance information associated with a satellite that is a candidate for serving the UE in a cell associated with the NTN.
  • the network node is serving the UE in a cell associated with the TN, and the satellite information is transmitted via broadcast.
  • certain embodiments may provide a technical advantage of enabling a proposed height dependent measurement reporting configuration that provides several candidate measurement reporting configurations for aerial UEs within certain height range and optimize the RRM configuration by adapting to the height of UEs.
  • Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.
  • FIGURE 1 illustrates an example architecture of a satellite network with bent pipe transponders
  • FIGURE 2 illustrate a set of parameters
  • FIGURE 3 illustrates an example wireless network, according to certain embodiments
  • FIGURE 4 illustrates an example network node, according to certain embodiments
  • FIGURE 5 illustrates an example wireless device, according to certain embodiments
  • FIGURE 6 illustrate an example user equipment, according to certain embodiments
  • FIGURE 7 illustrates another example wireless network, according to certain embodiments
  • FIGURE 8 illustrates a method by a UE for receiving satellite assistance information from a TN, according to certain embodiments
  • FIGURE 9 illustrates another example method by a UE for receiving satellite assistance information from a TN, according to certain embodiments
  • FIGURE 10 illustrates an example method by a NTN node serving a wireless device in a first cell, according to certain embodiments; and
  • node can be a network node or a UE.
  • NodeB NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g.
  • a node in a gNB, Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), Operations Support System (OSS), Self Organizing Network (SON), positioning node (e.g. E-SMLC), etc.
  • UE user equipment
  • UE user equipment
  • UE user equipment
  • Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, etc.
  • D2D device to device
  • V2V vehicular to vehicular
  • MTC UE machine type UE
  • MTC UE machine type UE
  • M2M machine to machine
  • PDA Personal Digital Assistant
  • Tablet mobile terminals
  • smart phone laptop embedded equipment
  • LME laptop mounted equipment
  • USB Unified Serial Bus
  • Network node may comprise base station, radio base station, base transceiver station, base station controller, network controller, evolved Node B (eNB), Node B, gNodeB (gNB), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), etc.
  • eNB evolved Node B
  • gNodeB gNodeB
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • Central Unit e.g. in a gNB
  • Distributed Unit e.g. in a gNB
  • Baseband Unit Centralized Baseband
  • C-RAN C-RAN
  • AP access point
  • radio access technology may refer to any RAT such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), narrow band internet of things (NB- IoT), WiFi, Bluetooth, next generation RAT, NR, 4G, 5G, etc.
  • UTRA Universal Terrestrial Radio Access Network
  • E-UTRA Evolved Universal Terrestrial Radio Access Network
  • NB- IoT narrow band internet of things
  • WiFi next generation RAT
  • Bluetooth next generation RAT
  • next generation RAT NR, 4G, 5G, etc.
  • signal or radio signal used herein can be any physical signal or physical channel.
  • DL physical signals examples include reference signal (RS) such as Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information-Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS) signals in SS/PBCH block (SSB), discovery reference signal (DRS), Cell Specific Reference Signal (CRS), Positioning Reference Signal (PRS), etc.
  • RS may be periodic. For example, RS occasions carrying one or more RSs may occur with certain periodicity such as, for example, 20 ms, 40 ms, etc.
  • the RS may also be aperiodic.
  • Each SSB carries NR-PSS, NR-SSS and NR-PBCH in four successive symbols.
  • One or multiple SSBs are transmit in one SSB burst which is repeated with certain periodicity such as, for example, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms.
  • the UE is configured with information about SSB on cells of certain carrier frequency by one or more SS/PBCH block measurement timing configuration (SMTC) configurations.
  • SMTC configuration comprising parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset with regard to reference time (e.g., serving cell’s SFN), etc.
  • SMTC occasion may also occur with certain periodicity such as, for example, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms.
  • uplink (UL) physical signals are reference signal such as SRS, DMRS etc.
  • the term physical channel refers to any channel carrying higher layer information such as, for example, data, control, etc.
  • Examples of physical channels are Physical Broadcast Channel (PBCH), Narrowband PBCH (NPBCH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), shortened PUCCH (sPUCCH), shortened PDSCH (sPDSCH), shortened PUCCH (sPUCCH), shortened PUSCH (sPUSCH), MTC PDCCH (MPDCCH), narrowband PDCCH (NPDCCH), Narrowband PDSCH (NPDSCH), E-PDCCH, Narrowband PUSCH (NPUSCH), etc.
  • time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time.
  • time resources are: symbol, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, slot, sub-slot, mini-slot, system frame number (SFN) cycle, hyper-SFN (H-SFN) cycle etc.
  • TTI transmission time interval
  • SFN system frame number
  • H-SFN hyper-SFN
  • a proposed height dependent measurement reporting configuration introduces one or more measurement reporting configuration for aerial UEs within certain height range and describes how the configurations are adopted, as well as some candidate parameters which could be included in the configuration sets. Also other approaches are presented on how the measurement and reporting of the UE can be controlled via the RRC configuration. More specifically, according to certain embodiments, the essential information for performing neighbor cell measurements in RRC_INACTIVE and RRC_IDLE state is acquired from SIB19 broadcast in an NR NTN cell.
  • SIB2 and/or SIB3 and/or SIB4 together with a list of Physical Cell Indicators (PCIs) and/or carrier frequencies.
  • PCIs Physical Cell Indicators
  • the essential information is, in accordance with the proposed methods, systems, and techniques, broadcast in SIB3 and/or SIB4 and/or SIB5.
  • satellite assistance information for an NTN neighbor cell may be transmitted in a new or different (SIB(s).
  • SIB2 may include common information relevant for intra-frequency, inter-frequency, and inter-RAT NTN neighbors.
  • SIB3 may be used in case the NTN neighbor operates in the same frequency as the serving cell.
  • SIB4 can be used for inter-frequency NTN neighbors and SIB5 for inter-RAT NTN neighbors (e.g., LTE NTN).
  • InterFreqNeighCellInfo-v1610 SEQUENCE ⁇ ssb-PositionQCL-r16 SSB-PositionQCL- Relation-r16 OPTIONAL - - Cond SharedSpectrum2 ⁇
  • InterFreqNeighCellInfo-v1710 SEQUENCE ⁇ ssb-PositionQCL-r17 SSB-PositionQCL- Relation-r17 OPTIONAL - - Cond SharedSpectrum2 ⁇
  • the above NTN-NeighCellConfig-r17 consists, instead of ntn-Config-r17 and may include a list of one or more parameters such as any one or more of (but not limited to): ⁇ NTN payload ephemeris ⁇ Epoch time of the ephemeris ⁇ SMTCs ⁇ DL and UL polarization information ⁇ Serving cell stop time ⁇ Reference location for NGSO fixed and moving cells, if applicable ⁇ Feeder link delay (i.e., common TA and Kmac) of the neighbor cell should also be provided to UE for neighbor cell SMTC adjustment ⁇ K_offset ⁇ Validity time information for ephemeris information, epoch time and Common TA parameters And instead of one PCI, a list of PCIs for which the list of parameters apply.
  • ⁇ NTN payload ephemeris ⁇ Epoch time of the ephemeris ⁇ SMTCs ⁇ DL and UL polarization information
  • ntn-NeighCellConfigList-r17 and ntn- NeighCellConfigListExt-v1720 IEs have been replaced by a single new list denoted as ntn-NeighCellConfigEnhancedList-r18.
  • InterFreqNeighCellInfo-v1610 SEQUENCE ⁇ ssb-PositionQCL-r16 SSB-PositionQCL- Relation-r16 OPTIONAL - - Cond SharedSpectrum2 ⁇
  • InterFreqNeighCellInfo-v1710 SEQUENCE ⁇ ssb-PositionQCL-r17 SSB-PositionQCL- Relation-r17 OPTIONAL - - Cond SharedSpectrum2 ⁇
  • SIB3 may include common information relevant for intra-frequency, inter-frequency, and inter-RAT NTN neighbors.
  • SIB4 may be used in case the NTN neighbor operates in the same frequency as the serving cell.
  • SIB5 can be used for inter-frequency and/or inter-RAT NTN neighbors (e.g., NR NTN).
  • the essential or relevant parts of the information contained in SIB19 (in NR) or SIB31 (in LTE) for each neighbor NTN satellite and /or cell are broadcast in a new SIB or in an existing SIB in a TN cell as an extension (wherein the utilized existing SIB is not a SIB whose presence (i.e.
  • Availability in a cell is also used to implicitly or explicitly indicate that the cell is an NTN cell) and are associated with an indication different from PCI or carrier frequency, e.g., satellite identifier (ID).
  • This indication is similarly added to the corresponding entry in InterFreqNeighCellInfo and/or IntraFreqNeighCellInfo, respectively, so that UE can identify the required satellite assistance information for the target NTN cell.
  • Changes of the dynamic satellite assistance information included as an extension in any legacy SIB should be exempt from the typical SI update mechanisms, which involves sending SI update notifications to UEs in the cell by repeated transmissions of a so-called Short Message, which is a Downlink Control Information (DCI) message sent on the PDCCH addressed to the Paging-Radio Network Temporary Identifier (P-RNTI) (i.e., the RNTI otherwise used for paging of UEs).
  • DCI Downlink Control Information
  • P-RNTI Paging-Radio Network Temporary Identifier
  • SIB19 (in NR) and/or SIB31 (in LTE) are used to broadcast the neighbor satellite assistance information also in TN cells. This is true despite the potential problem associated with it.
  • an NTN capable legacy UE may interpret the existence of SIB19 (in NR) or SIB31 (in LTE) as an indication of that the cell is an NR NTN cell or an IoT cell.
  • SIB19 (in NR) and/or SIB31 (in LTE) in the embodiments described herein is motivated by the reasoning that the advantage of being able to reuse existing specified functionality outweighs the disadvantage.
  • the legacy UEs implementing NR NTN and/or IoT NTN functionality in accordance with Release 17 of the 3GPP standard can be expected to be very few, and the ones that may be produced can be expected to soon be replaced by superior models implementing later releases of the 3GPP standard and potentially more streamlined hardware (e.g., smaller and more energy efficient hardware).
  • the potential problem associated with usage of SIB19 in an NR NTN cell may possibly never occur since the NR stage 2 specification for NR (i.e., 3GPP TS 38.300 version 17.3.0, Section 16.14.3.1) states that “The UE can determine the network type (terrestrial or non-terrestrial) implicitly by the existence of cellBarredNTN in SIB1”.
  • SIB19 in NR
  • SIB31 in LTE
  • the relevant satellite assistance information would instead be placed in legacy SIB(s), this would force such a UE to frequently reacquire this(these) legacy SIB(s), which, due to the potentially extensive content of this(these) legacy SIB(s), will cause undesirable overhead (e.g. in terms of processing and energy consumption) in the UE.
  • SIB19 in NR
  • SIB31 in LTE
  • usage of these SIBs should be different from their usage in NR NTN and IoT NTN.
  • a major difference between a TN cell and an NTN cell is that a TN cell is not served by a satellite. As a consequence, no satellite assistance information is needed for the serving cell.
  • ntn- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 are associated with the serving cell (disregarding the lateNonCriticalExtension field, whose purpose is to enable future extensions, and for which no content has yet been specified).
  • ntn- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs are thus the only IEs that are relevant when SIB19 is broadcast in a TN cell, while the other fields (which are all optional) are of no use and should be omitted.
  • ntn-Config Provides parameters needed for the UE to access NR via NTN access such as Ephemeris data, common TA parameters, k_offset, validity duration for UL sync information and epoch.
  • the serving cell is a TN cell
  • the field is absent in the information associated with the serving cell. Otherwise the field is optionally present (need R).
  • the following sentence could advantageously be added to some of the other SIB19 field descriptions (for the fields t-Service-r17, referenceLocation-r17 and distanceThreshold-r17) in 3GPP TS 38.331 version 17.3.0: “The field is absent when the serving cell is a TN cell.”
  • a new conditional presence tag could be introduced and associated with the ntn-Config-r17 field in the serving cell information in SIB19.
  • This new conditional presence tag could be called “NTN-cell”, for example, and would mean that the field is absent if the serving cell is a TN cell, otherwise the field is optionally present (need R).
  • This new SIB could be tailored for this purpose such as, for example, by reusing the neighbor cell/satellite related fields of SIB19, while omitting the fields related to the serving cell.
  • ntn-NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs have been replaced by a single new list denoted as ntn-NeighCellConfigEnhancedList-r18.
  • a UE is not expected to use the satellite assistance information for a neighbor cell to calculate its UE specific TA, but rather for autonomous adjustments of the SMTC associated with the neighbor cell (and possibly for determination of a receive beam or adjustment of a directional antenna, in case the UE uses such features for NTN monitoring).
  • This usage of the satellite assistance information can be performed with much lower accuracy of the satellite assistance information (i.e., greater errors in the satellite assistance information are tolerable) than UE autonomous TA calculation.
  • a longer validity time can be configured for the satellite assistance information associated with a neighbor cell than for the satellite assistance information associated with the serving cell.
  • the satellite assistance information for the serving cell is omitted when SIB19 is broadcast in a TN cell (because the serving cell is not served by a satellite)
  • this property could be better utilized if the current maximum configurable value of the validity time (i.e., the ntn-UlSyncValidityDuration-r17 field in the NTN-Config-r17 IE), which is 900 seconds in 3GPP TS 38.331 version 17.3.0, were to be increased (e.g., by adding one or more configurable values greater than 900 seconds such as, for example, to 1800 seconds).
  • the concerned fields are all included in the NTN-Config-r17 IE, and they all have the following sentence in their respective field description: “This field is excluded when determining changes in system information, i.e. changes to ⁇ field name> should neither result in system information change notifications nor in a modification of valueTag in SIB1.” In the above quoted sentence, “ ⁇ field name>“ represents the respective one of the concerned field names.
  • the concerned fields are: epochTime-r17 ntn-UlSyncValidityDuration-r17 ta-Common-r17 (in TA-Info-r17) ta-CommonDrift-r17 (in TA-Info-r17) ta-CommonDriftVariant-r17 (in TA-Info-r17) ephemerisInfo-r17
  • the exemption of these fields serves to avoid frequent SI change notifications, which would consume DL transmission resources as well as processing resources, and would have a negative impact on the UEs’ energy consumption.
  • Such notifications would also be superfluous, as a UE’s reacquisition of SIB19 in an NTN cell anyway is governed by the value of the ntn-UlSyncValidityDuration-r17 field and its internal timer T430.
  • SIB19 is broadcast in a TN cell, the situation becomes slightly different, because the neighbor NTN cells are served by moving satellites (except in the case of a geostationary satellite, which is not moving in relation to the TN cell), while the TN cell is not.
  • the neighbor NTN cells will change frequently due to cell switches (triggered by changes in the feeder link or the serving satellite) and moving NTN cells.
  • the list of neighbor NTN cells, as configured in the NTN-NeighCellConfigList-r17 IE and the ntn-NeighCellConfigListExt-v1720 IE will be relatively frequently updated. This motivates introduction of a mechanism serving to avoid changes in the set of NTN neighbor cells triggering SI change notifications to be sent (and updates of the valueTag associated with SIB19). Such changes include primarily changes of which list items the NTN-NeighCellConfigList-r17 and ntn-NeighCellConfigListExt- v1720 IEs contain, i.e.
  • a mechanism serving to avoid that the above-mentioned changes trigger SI change notifications to be sent (and updates of the valueTag associated with SIB19) could be, for example, one of the following: - One alternative could be to exclude changes of the ntn- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs in SIB19 from the SI changes that trigger SI change notifications and SIB19 valueTag update, and introduce an additional field in SIB19, indicating when the next update of the set of neighbor NTN cells included in the ntn-NeighCellConfigList-r17 and ntn- NeighCellConfigListExt-v1720 IEs will occur, e.g.
  • nextUpdateOfSetOfNeighbourCells-xx This new field could be an INTEGER indicating a UTC value or a number of seconds. The field may be optional and present only in TN cells. UEs which are interested in the ntn-NeighCellConfigList-r17 and ntn-NeighCellConfigListExt- v1720 IEs in SIB19 would then have the information they need to know when reacquisition of SIB19 is needed.
  • the relevant changes of the ntn-NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs in SIB19 that should not trigger SI change notifications and SIB19 valueTag update may be changes in the set of of which list items the NTN- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt- v1720 IEs contain, i.e. additions and removals of list items, and changes of the fields within a list item.
  • the execution of the update would not be restricted to a SI modification period border.
  • a UE that is interested in the ntn-NeighCellConfigList-r17 and ntn- NeighCellConfigListExt-v1720 IEs in SIB19 would reacquire the updated SIB19, while a UE that is not interested in the ntn- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs in SIB19 would ignore the SI change notification.
  • the indicator in the Short Message DCI could refer specifically to changes in the set of which list items the NTN-NeighCellConfigList-r17 IE and/or ntn- NeighCellConfigListExt-v1720 IE contain (i.e., additions and removals of list items) and changes of the fields within a list item.
  • Yet another alternative could be to exclude changes of the ntn- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs in SIB19 from the SI changes that trigger SI change notification and SIB19 valueTag update, but not introduce any new parameter in SIB19.
  • ntn-NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs in SIB19 that should not trigger SI change notifications and SIB19 valueTag update may be changes in the set of of which list items the NTN- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt- v1720 IEs contain, i.e.
  • UE Actions In a particular embodiment (targeting UEs in RRC_CONNECTED state), the essential or relevant parts of SIB19 (in NR) or SIB31 (in LTE) are given to the UE in the measurement object (i.e., the MeasObjectNR IE in NR or the MeasObjectEUTRA IE in LTE) together with a list of PCIs.
  • the measurement object i.e., the MeasObjectNR IE in NR or the MeasObjectEUTRA IE in LTE
  • only an indication e.g., satellite ID
  • is added to Measurement Object to assist the UE to identify the required satellite assistance information for the target NTN cell, which the UE obtains by other means such as, for example, reading SI or through dedicated Radio Resource Control (RRC) signaling.
  • RRC Radio Resource Control
  • the essential or relevant parts of SIB19 (in NR) or SIB31 (in LTE) are provided to UEs in RRC_CONNECTED mode via dedicated RRC signaling. For instance, as part of the RRCReconfiguration message including ReconfigurationWithSync that triggers handover execution and the parameter dedicatedSystemInformationDelivery.
  • a UE determines one of a plurality of states of the UE with respect to one or more than one of satellite assistance information and adaptively adjusts, updates, or changes one or more operations or aspects related to one or more of the following procedures on TN serving cell or NTN neighbor cell: ⁇ cell change procedure (e.g., cell reselection, cell selection, RRC connection re-establishment, etc.); ⁇ measurement procedure (e.g., measurement rate, number, periodicity, duration, total number of carriers/frequencies/cells/satellites to be measured, etc.) and/or ⁇ channel monitoring or reception procedure (e.g., paging reception, system information reception, etc.).
  • ⁇ cell change procedure e.g., cell reselection, cell selection, RRC connection re-establishment, etc.
  • ⁇ measurement procedure e.g., measurement rate, number, periodicity, duration, total number of carriers/frequencies/cells/satellites to be measured, etc.
  • UE may perform one or more of procedures on intra-frequency if no valid NTN assistance information is sent by serving TN cell and received by the UE, but requirements corresponding to the procedures can be relaxed.
  • UE shall perform one or more of procedures provided valid NTN assistance information sent by serving TN cell is received by the UE only when RSRP/RSRQ received in TN serving cell is higher than a threshold (TH_P1).
  • UE shall perform one or more of procedures provided UE doesn’t receive valid NTN assistance information sent by serving TN cell and RSRP/RSRQ received in TN serving cell is lower than a threshold (TH_P2), but requirements corresponding to the procedures can be relaxed.
  • UE shall perform one or more of procedures provided the time interval from the time instance when UE receives last NTN assistance information and starts procedures is less than a threshold (T_delta ) and RSRP/RSRQ received in TN serving cell is lower than a threshold (TH_P3), but requirements corresponding to the procedures can be relaxed.
  • UE operated in serving TN cell does not need to read the SI containing NTN assistance information always.
  • UE operated in serving TN cell shall read the SI containing NTN assistance information upon fulfilling some conditions such as, for example, a distance between UE position and TN cell boundary is shorter than a threshold (TH_D1) provided TN cell boundary information is known by the UE.
  • FIGURE 3 illustrates a wireless network 100 in accordance with some embodiments.
  • the wireless network 100 of FIGURE 3 only depicts network 106, network nodes 160 and 160b, and wireless devices (WDs) 110.
  • a wireless network 100 may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node 160 and WD 110 are depicted with additional detail.
  • the wireless network 100 may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network 100.
  • the wireless network 100 may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network 100 may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • wireless network 100 may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBee standards.
  • Network 106 may comprise one or more backhaul networks, core networks, Internet Protocol (IP) networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • IP Internet Protocol
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node 160 and WD 110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network 100.
  • the wireless network 100 may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • FIGURE 4 illustrates an example network node 160, according to certain embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162.
  • Network node 160 may be an NTN network node.
  • network node 160 illustrated in the example wireless network of FIGURE 4 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components.
  • a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node 160 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 160 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs).
  • Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.
  • Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node.
  • processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality.
  • processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 170 may include a system on a chip (SOC).
  • processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174.
  • radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units
  • some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170.
  • some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality.
  • Device readable medium 180 may comprise any form of volatile or non- volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170.
  • volatile or non- volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile
  • Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160.
  • Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190.
  • processing circuitry 170 and device readable medium 180 may be considered to be integrated.
  • Interface 190 is used in the wired or wireless communication of signalling and/or data between network node 160, network 106, and/or WDs 110.
  • interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection.
  • Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162.
  • Radio front end circuitry 192 comprises filters 198 and amplifiers 196.
  • Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170.
  • Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170.
  • Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components. In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192.
  • RF transceiver circuitry 172 may be considered a part of interface 190.
  • interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).
  • Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz.
  • An omni-directional antenna may be used to transmit/receive radio signals in any direction
  • a sector antenna may be used to transmit/receive radio signals from devices within a particular area
  • a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.
  • the use of more than one antenna may be referred to as MIMO.
  • antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.
  • Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment. Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein.
  • Power circuitry 187 may receive power from power source 186.
  • Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160.
  • network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187.
  • power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187.
  • network node 160 may include additional components beyond those shown in FIGURE 4 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.
  • FIGURE 5 illustrates an example WD 110, according to certain embodiments.
  • WD refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with UE. Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc.
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to- everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to- everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137.
  • WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few.
  • Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from WD 110 and be connectable to WD 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface.
  • interface 114 comprises radio front end circuitry 112 and antenna 111.
  • Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116.
  • Radio front end circuitry 114 is connected to antenna 111 and processing circuitry 120, and is configured to condition signals communicated between antenna 111 and processing circuitry 120.
  • Radio front end circuitry 112 may be coupled to or a part of antenna 111.
  • WD 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111.
  • some or all of RF transceiver circuitry 122 may be considered a part of interface 114.
  • Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 110 components, such as device readable medium 130, WD 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein.
  • processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.
  • processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126.
  • processing circuitry 120 of WD 110 may comprise a SOC.
  • RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 122 may be a part of interface 114.
  • RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.
  • processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium.
  • some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of WD 110, but are enjoyed by WD 110 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120.
  • Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120.
  • processing circuitry 120 and device readable medium 130 may be considered to be integrated.
  • User interface equipment 132 may provide components that allow for a human user to interact with WD 110. Such interaction may be of many forms, such as visual, audial, tactile, etc.
  • User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to WD 110.
  • the type of interaction may vary depending on the type of user interface equipment 132 installed in WD 110. For example, if WD 110 is a smart phone, the interaction may be via a touch screen; if WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits.
  • User interface equipment 132 is configured to allow input of information into WD 110, and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information.
  • User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry.
  • User interface equipment 132 is also configured to allow output of information from WD 110, and to allow processing circuitry 120 to output information from WD 110.
  • User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry.
  • WD 110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario.
  • Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 110 which need power from power source 136 to carry out any functionality described or indicated herein.
  • Power circuitry 137 may in certain embodiments comprise power management circuitry.
  • Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136.
  • Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of WD 110 to which power is supplied.
  • IGURE 6 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 200 may be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 200 as illustrated in FIGURE 6, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • FIGURE 6 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 233, and/or any other component, or any combination thereof.
  • Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in FIGURE 6, or only a subset of the components.
  • the level of integration between the components may vary from one UE to another UE.
  • certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 201 may be configured to process computer instructions and data.
  • Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware- implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general- purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 200 may be configured to use an output device via input/output interface 205.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE 200.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 211 may be configured to provide a communication interface to network 243a.
  • Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 243a may comprise a Wi-Fi network.
  • Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 219 may be configured to provide computer instructions or data to processing circuitry 201.
  • ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non- volatile memory.
  • Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227.
  • Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic
  • Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium.
  • processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231.
  • Network 243a and network 243b may be the same network or networks or different network or networks.
  • Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b.
  • communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network 243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 243b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.
  • AC alternating current
  • DC direct current
  • the features, benefits and/or functions described herein may be implemented in one of the components of UE 200 or partitioned across multiple components of UE 200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware.
  • communication subsystem 231 may be configured to include any of the components described herein.
  • processing circuitry 201 may be configured to communicate with any of such components over bus 202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein.
  • FIGURE 7 depicts a wireless network 1000 comprising different devices connected, either directly or indirectly, to the wireless network 1000 through one or more access network nodes, such as gNBs 1060a and 1060b.
  • the wireless network 1000 includes access network nodes such as gNBs 1060a and 1060b, UE 1010a, hub 1010b, remote devices 1015a and 1015b and server 1009.
  • UE 1010a and hub 1010b may be any of a wide variety of devices capable of communicating wirelessly with gNBs 1060’s.
  • hub 1010b is referred to as a hub, it may also be considered a UE (with hub functionality) because it is able to communicate wirelessly with gNB 1060b using a standard protocol, for example a wireless standard such as one provided by 3GPP.
  • a standard protocol for example a wireless standard such as one provided by 3GPP.
  • each of the devices illustrated in FIGURE 7 represent a wide variety of different devices that can be used in different scenarios as discussed in more detail below. Any of these devices which are able to communicate wirelessly with a gNB, eNB or any other similar 3GPP access node may be considered a wireless device or UE.
  • UE 1010a may be any of a variety of different devices that are able to wirelessly communicate with gNB 1060a. Some examples, which are listed in FIGURE 7, include a virtual reality (VR) headset, a sensor, an actuator, a monitoring device, a vehicle, or a remote controller. These examples are not exhaustive and include therein a wide variety of more specific devices, including a wide range of Internet of Things (IoT) devices.
  • UE 1010a is a VR headset
  • UE 1010a may be a cell phone that is used with a head mount or it may be a standalone or dedicated VR headset.
  • UE 1010a may be an augmented reality (AR) headset.
  • AR augmented reality
  • UE 1010a may be used for entertainment (e.g., gaming, videos, etc.), education/business (e.g., remote conferences, virtual lectures, etc.), medical (e.g., remote diagnostic, patient consultation, etc.), or any other use in which virtual or augmented content may be provided to a remote user.
  • UE 1010a may be receiving content via wireless connection 1070a with gNB 1060a.
  • UE 1010a may be a motion, gravitational, moisture, temperature, biometric, speed, door/window open, smoke, fire, volume, flow, or any other type of device that is able to detect or measure one or more conditions.
  • UE 1010a may also be able to capture conditions. For example, UE 1010a may capture images if it comprises a camera or sound if it comprises a microphone. Regardless of the type of sensor, UE 1010a may provide an output via wireless connection 1070a to gNB 1060a. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a triggering event e.g., when moisture is detected an alert is sent
  • a request e.g., a user initiated request
  • a continuous stream e.g., a live video feed of a patient.
  • UE 1010a may be a motor, switch, or any other device that may change states in response to receiving an input via wireless connection 1070a.
  • UE 1000a may be a vibrator that creates vibration to provide a user with haptic feedback.
  • UE 1000a may be a small motor that adjusts the control surfaces of a drone in flight or to a robotic arm performing a medical procedure.
  • UE 1000a may be a switch that remotely turns on another device, such as a light.
  • UE 1010a may be a drone, car, plane, ship, train, tractor, robot, or any other type of device comprising one or more sensors and/or actuators that may change its locations whether autonomously or at the direction of a user.
  • UE 1010a is a remotely controlled vehicle, such as a drone, it may receive instructions on movement, actuating, or sensing from a user via wireless connection 1070a and provide location, sensor or video information back to the user via wireless connection 1070a.
  • UE 1010a may receive alerts and other messages from other vehicles and/or infrastructure sensors via wireless connection 1070a as well provide its own telemetry data to others via wireless connection 1070a.
  • UE 1010a may be a device dedicated to controlling other devices or a general purpose computer with a program or application that provides control of other devices.
  • UE 1010a may send commands to a remote device via wireless connection 1070a.
  • UE 1010a may also receive feedback, telemetry, or other information from the remote device via wireless connection 1070a.
  • UE 1010a may present this received information to a user who may then issue commands for the remote device.
  • UE 1010a may receive via wireless connection 1070a a video signal from a remote surgical room and then issue commands via wireless connection 1070a to a remote surgical machine that can execute the commands. While only a single UE 1010a is illustrated in FIGURE 7, in practice any number of UEs may be used together with respect to a single use case.
  • a first UE 1010a may be a speed sensor used in a drone which provides the drone’s speed information to a second UE 1010a that is a remote control operating the drone.
  • a third UE 1010a that is an actuator may adjust a throttle on the drone to increase or decrease the speed.
  • the first (sensor) and third (actuator) UE 1010a’s may be a single UE that handles communication for both the speed sensor and the actuators or UE QQA 110a may comprise one or more of the above.
  • a hub such as hub 1010b, may be used to handle communication between the sensors and actuators and the controller.
  • Hub 1010b may be any of a variety of different devices that provides wireless access to gNB 1060b for one or more remote devices 1015a. Some examples of different types of hubs are listed in Figure QAA and include a controller, router, content source and analytics.
  • Hub 1010b may include memory to store data (e.g., video, audio, images, buffer, sensor data, file share) that is collected from, or is to be provided to, remote device 1015a.
  • Hub 1010b hub may include a processor, operating system, and server functionality.
  • Hub 1010b may include components for wireless communication to enable wireless connection 1071 to remote device 1015a and/or components for a fixed connection to remote device 1015b.
  • Hub 1010b may also include routing capabilities, firewall capabilities, a VPN-server or VPN-client. Hub 1010b may also allow for a different communication scheme and/or schedule between hub 1010b and remote devices 1015 and between hub 1010b and network 1006.
  • hub 1010b may be a broadband router enabling direct or indirect access to network 1006 for remote device 1015a.
  • hub 1010b may facilitate communication between remote devices 1015a and 1015b. This may be done with, or without, the communications passing through network 1006.
  • hub 1010b may simply forward the data from remote device 1015a or 1015b to network 1006.
  • hub 1010b may first filter, buffer, store, analyze or collate the data from remote device 1015a or 1015b before sending on the data to network 1006 or another remote device.
  • the data from network 1006 may pass directly through hub 1010b or it may first be processed by hub 1010b on the way to remote device 1015a or 1015b.
  • hub 1010b may be a controller that sends commands or instructions to one or more actuators in remote device 1015a.
  • the commands or instructions may be received from a second remote device 1015b, from gNB 1060b or by executable code, script or process instructions in hub 1010b.
  • hub 1010b may be a collection place for data from one or more remote devices 1015a and/or 1015b.
  • remote devices 1015a and/or 1015b may be a sensor, a camera, measurement equipment, or any other type of device discussed herein that may provide output or receive input.
  • Hub 1010b may act as a temporary storage for data from, for example remote device 1015b and, in some embodiments, may perform analysis, or other processing on the data.
  • Hub 1010b may have a constant/persistent or intermittent connection to gNB 1060b.
  • hub 1010b may be a content source.
  • remote device 1015a when remote device 1015a is a VR headset, display, loudspeaker or other media delivery device, hub 1010b may retrieve VR assets, video, audio, or other media via gNB 1060b which it then provides to remote device 1015a either directly, after some local processing, and/or after adding additional local content.
  • Remote device 1015a may be any of a variety of different devices, for example, remote device 1015a may be a device comprising one or more of sensors, actuators, and/or a screen.
  • Remote device 1015a may alternatively be a VR (or AR) headset, a Machine-2-Machine (M2M) device, an IoT device, an internet of Everything (IoE) device, or any other type of device which is capable of accessing a communication network wirelessly via a hub or a device capable of acting as a hub, which in the present context comprise providing network access to a device which is not able to communicate directly with communication network 1006 via gNB 1060a or 1060b.
  • remote device 1015a may be able to establish a wireless connection with gNB 1060a or 1060b yet nonetheless still connects via hub QQA 110b.
  • Remote device 1015b may be similar to remote device 1015a in most respects except that it has a wired connection to hub 1010b rather than a wireless connection, such as wireless connection 1071.
  • gNBs 1060a and 1060b may provide various wireless devices such as UE 1010a and hub 1010b with wireless access to network 1006.
  • Network 1006 may connect the various devices illustrated in FIGURE 7 including server 1009 which may host a variety of applications such as live and pre-recorded content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of remote devices 1015a, 1015b or UE 1010a, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function done by a server.
  • factory status information may be collected and analyzed by server 1009.
  • server 1009 may process audio and video data which may have been retrieved from UE 1010a for use in creating maps.
  • server 1009 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • server 1009 may store surveillance video uploaded by remote device 1015b via hub 1010b.
  • server 1009 may store media content such as video, audio, VR, or AR which it can broadcast, multicast or unicast to remote devices such as UE 1010a or remote device 1015a.
  • server 1009 may be used for energy pricing, for remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • FIGURE 8 illustrates a method 1200 by a UE 110 for receiving satellite assistance information from a TN, according to certain embodiments.
  • the method includes a receiving step at 1202.
  • the UE 110 may receive satellite assistance information from a network node 112 associated with the TN.
  • the satellite assistance information is associated with a satellite of an NTN.
  • FIGURE 9 illustrates another method 1300 by a UE 110 for receiving satellite assistance information from a TN, according to certain embodiments.
  • the method includes the UE receiving satellite assistance information from a network node 112 serving the UE 110 in a cell associated with the TN, at 1302.
  • the satellite assistance information is associated with a satellite that is a candidate for serving the UE 110 in a cell associated with an NTN.
  • the satellite assistance information is received via broadcast.
  • the satellite assistance information comprises essential system information for NTN.
  • the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the NTN payload ephemeris; at least one Synchronization Signal Block Measurement Timing Configuration, SMTC; downlink and/or uplink polarization information; a stop time associated with the cell associated with the TN; reference location for a fixed and/or moving cell; feeder link delay for SMTC adjustment of the cell associated with the NTN; Kmac; K_offset; and validity time information for the NTN payload ephemeris, the epoch time, and/or at least one Common Timing Advance parameter.
  • SMTC Synchronization Signal Block Measurement Timing Configuration
  • the UE 110 uses the satellite assistance information to locate a beam associated with the satellite that is the candidate for serving the UE 110 in the cell associated with the NTN. Additionally or alternatively, the UE 110 uses the satellite assistance information to adjust an SMTC associated with the satellite that is the candidate for serving the UE in the cell associated with the NTN. Additionally or alternatively, the UE 110 uses the satellite assistance information to adjust a directional antenna and/or synchronizes with the satellite that is the candidate for serving the UE in the cell associated with the NTN. In a particular embodiment, the satellite assistance information comprises or is comprised in a measurement reporting configuration configuring the UE 110 to perform at least one measurement.
  • the measurement reporting configuration applies to the satellite when the satellite is located at a height within a range.
  • the satellite comprises an aerial UE.
  • the measurement reporting configuration applies to the UE when at a height within a range.
  • the satellite assistance information is received in a SIB19 message, a SIB31 message, or other SIB.
  • the UE 110 receives at least one PCI or at least one carrier frequency associated with the satellite assistance information.
  • the satellite assistance information is associated with and/or received with a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies.
  • FIGURE 10 illustrates an example method 1400 by a network node 112 associated with a TN for for providing satellite assistance information for a satellite of a NTN, according to certain embodiments.
  • the method includes a transmitting step at 1302.
  • the network node 112 transmit, to a UE 110, the satellite assistance information associated with the NTN.
  • FIGURE 11 illustrates another example method 1500 by a network node associated with a TN for providing satellite assistance information for a satellite of a NTN, according to certain embodiments.
  • the method includes the network node transmitting, to a UE, the satellite assistance information associated with a satellite that is a candidate for serving the UE in a cell associated with the NTN, at step 1502.
  • the network node is serving the UE in a cell associated with the TN.
  • the satellite information is transmitted via broadcast.
  • the satellite assistance information comprises essential system information for NTN.
  • the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the NTN payload ephemeris; at least one Synchronization Signal Block Measurement Timing Configuration; downlink and/or uplink polarization information; a stop time associated with the cell associated with the TN; reference location for a fixed and/or moving cell; feeder link delay for SMTC adjustment of the cell associated with the NTN; Kmac; K_offset; and validity time information for the NTN payload ephemeris information, the epoch time, and/or at least one Common Timing Advance parameter.
  • the satellite assistance information comprises or is comprised in a measurement reporting configuration configuring the UE to perform at least one measurement.
  • the measurement reporting configuration applies to the satellite when the satellite is located at a height within a range.
  • the satellite comprises an aerial UE.
  • the measurement reporting configuration applies to the UE when at a height within a range.
  • the satellite assistance information is transmitted in a SIB19 message, a SIB31 message, or another SIB.
  • the network node 112 transmits at least one PCI or at least one carrier frequency associated with the satellite assistance information.
  • the satellite assistance information is associated with and/or transmitted with a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies.
  • a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • EXAMPLE EMBODIMENTS Group A Example Embodiments Example Embodiment A1. A method by a user equipment (UE) for receiving satellite assistance information from a Terrestrial Network (TN), the method comprising: any of the user equipment steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.
  • Example Embodiment A3 The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the network node.
  • Group B Example Embodiments
  • Example Embodiment B1. A method performed by a network node associated with a Terrestrial Network (TN) for providing satellite assistance information for a satellite of a Non-Terrestrial Network (NTN), the method comprising: any of the network node steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.
  • TN Terrestrial Network
  • NTN Non-Terrestrial Network
  • Example Embodiment B3 The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • Group C Example Embodiments Example Embodiment C1. A method by a user equipment (UE) for receiving satellite assistance information from a Terrestrial Network (TN), the method comprising: receiving satellite assistance information from a network node associated with the TN, the satellite assistance information being associated with a satellite of a Non-Terrestrial Network (NTN).
  • UE user equipment
  • NTN Non-Terrestrial Network
  • Example Embodiment C2 The method of Example Embodiment C1, wherein the satellite assistance information comprises essential system information.
  • Example Embodiment C2 wherein the satellite assistance information comprises ephemeris data.
  • Example Embodiment C4. The method of any one of Example Embodiments C1 to C3, wherein the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the ephemeris; at least one SMTC; DL and UL polarization information; serving cell stop time; reference location for NGSO fixed and/or moving cell; feeder link delay for neighbor cell SMTC adjustment; TA; Kmac; K_offset; validity time information for ephemeris information, epoch time, and/or Common TA parameters.
  • Example Embodiments C1 to C4 comprising at least one of: using the satellite assistance information to locate a beam associated with the satellite; using the satellite assistance information to adjust an SMTC associated with the satellite; using the satellite assistance information to adjust a directional antenna; and synchronizing with the satellite.
  • Example Embodiment C6 comprising at least one of: using the satellite assistance information to locate a beam associated with the satellite; using the satellite assistance information to adjust an SMTC associated with the satellite; using the satellite assistance information to adjust a directional antenna; and synchronizing with the satellite.
  • Example Embodiment C4 The method of any one of Example Embodiments C1 to C4, wherein the network node is serving the UE in a cell of the TN, and wherein the satellite is a candidate for serving the UE in a cell of the NTN, and wherein the method comprises: using the satellite assistance information to locate a beam associated with the cell of the NTN; using the satellite assistance information to adjust an SMTC associated with the cell of the NTN; using the satellite assistance information to adjust a directional antenna; and synchronizing with the cell of the NTN.
  • Example Embodiment C7 The method of any one of Example Embodiments C1 to C6, wherein the satellite assistance information comprises or is comprised in a measurement reporting configuration configuring the UE to perform at least one measurement.
  • Example Embodiment C7 wherein the measurement reporting configuration applies to the satellite when the satellite is located at a height within a range.
  • Example Embodiment C9. The method of Example Embodiment C8, wherein the satellite comprises an aerial UE.
  • Example Embodiment C10 The method of Example Embodiment C7, wherein the measurement reporting configuration applies to the UE when at a height within a range.
  • Example Embodiment C11. The method of any one of Example Embodiment C1 to C10, wherein the satellite assistance information is received in at least one of a SIB2 message, a SIB3 message, a SIB4 message, a SIB5 message, a SIB19 message, and/or a SIB31 message.
  • Example Embodiments C1 to C11 wherein the satellite assistance information is included in an information element (IE), the IE comprising at least one of: epochTime-r17, ntn- UlSyncValidityDuration-r17, ta-Common-r17 (in TA-Info-r17), ta-CommonDrift-r17 (in TA-Info-r17), ta-CommonDriftVariant-r17 (in TA-Info-r17), ephemerisInfo-r17, NTN-NeighCellConfigList-r17, NeighCellConfigListExt-v1720, and the NeighCellConfigEnhancedList-r18.
  • IE information element
  • Example Embodiment C13 The method of any one of Example Embodiments C1 to C12, comprising receiving at least one PCI or at least one carrier frequency to which the satellite assistance information applies.
  • Example Embodiment C14 The method of Example Embodiment C13, wherein the satellite assistance information and the at least one PCI and/or the at least one carrier frequency are received in one message.
  • Example Embodiment C15 The method of any one of Example Embodiments C1 to C14, wherein the satellite assistance information is associated with a validity time duration, and wherein the validity time duration is greater than 900 seconds.
  • Example Embodiment C16 The method of any one of Example Embodiments C1 to C12, comprising receiving at least one PCI or at least one carrier frequency to which the satellite assistance information applies.
  • Example Embodiment C14 The method of Example Embodiment C13, wherein the satellite assistance information and the at least one PCI and/or the at least one carrier frequency are received in one message.
  • Example Embodiment C15
  • Example Embodiment C15 The method of any one of Example Embodiments C1 to C15, wherein the satellite assistance information is associated with and/or received with a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies.
  • Example Embodiment C17 The method of any one of Example Embodiments C1 to C16, wherein the satellite assistance information is received via a dedicated RRC signaling message.
  • Example Embodiments C1 to C17 comprising determining one of a plurality of states of the UE with respect to the satellite assistance information and adaptively adjusting, updating, and/or changing one or more operations or parameters related to one or more of procedures, and wherein the one or more procedures comprises at least one of: a cell change procedure (such as, for example, cell reselection, cell selection, RRC connection re- establishment etc.); a measurement procedure (such as, for example, measurement rate, number, periodicity, duration, total number of carriers/frequencies/cells/satellites to be measured etc.); and/or a channel monitoring and/or reception procedure (such as, for example, paging reception, system information reception, etc.).
  • a cell change procedure such as, for example, cell reselection, cell selection, RRC connection re- establishment etc.
  • a measurement procedure such as, for example, measurement rate, number, periodicity, duration, total number of carriers/frequencies/cells/satellites to be measured
  • Example Embodiment C19 The method of Example Embodiment C18, comprising performing the one or more of procedures based on the satellite assistance information when RSRP and/or RSRQ received in a serving cell of the TN is higher than a threshold (TH_P1).
  • Example Embodiment C20 The method of Example Embodiment C18, comprising performing the one or more of procedures based on the satellite assistance information when RSRP and/or RSRQ received in a serving cell of the TN is lower than a threshold (TH_P2).
  • Example Embodiment C21 Example Embodiment C19. The method of Example Embodiment C18, comprising performing the one or more of procedures based on the satellite assistance information when RSRP and/or RSRQ received in a serving cell of the TN is higher than a threshold (TH_P1).
  • Example Embodiment C18 comprising performing one or more of procedures when a time interval from a time instance when the UE receives the satellite assistance information to when the UE starts a procedure is less than a threshold(T_delta ) and/or RSRP and/or RSRQ received in a serving cell of the TN is lower than a threshold (TH_P3).
  • Example Embodiment C22 The method of any one of Example Embodiments C1 to C21, comprising: determining that at least on condition is fulfilled; and reading and/or using the satellite assistance information based on the at least one condition being fulfilled.
  • Example Embodiment C23 comprising performing one or more of procedures when a time interval from a time instance when the UE receives the satellite assistance information to when the UE starts a procedure is less than a threshold(T_delta ) and/or RSRP and/or RSRQ received in a serving cell of the TN is lower than a threshold (TH_P3).
  • Example Embodiment C22 The
  • Example Embodiments C1 to C26 further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.
  • Example Embodiment C28. A user equipment comprising processing circuitry configured to perform any of the methods of Example Embodiments C1 to C27.
  • Example Embodiment C29. A user equipment configured to perform any of the methods of Example Embodiments C1 to C27.
  • a wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments C1 to C27.
  • Example Embodiment C31 A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments C1 to C27.
  • a computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments C1 to C27.
  • a non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments C1 to C27.
  • Group D Example Embodiments Example Embodiment D1.
  • UE user equipment
  • Example Embodiment D1 wherein the satellite assistance information comprises essential system information.
  • Example Embodiment D3. The method of any one of Example Embodiments D1 to D2, wherein the satellite assistance information comprises ephemeris data.
  • Example Embodiments D1 to D3 wherein the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the ephemeris; at least one SMTC; DL and UL polarization information; serving cell stop time; reference location for NGSO fixed and/or moving cell; feeder link delay for neighbor cell SMTC adjustment; TA; Kmac; K_offset; validity time information for ephemeris information, epoch time, and/or Common TA parameters.
  • the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the ephemeris; at least one SMTC; DL and UL polarization information; serving cell stop time; reference location for NGSO fixed and/or moving cell; feeder link delay for neighbor cell SMTC adjustment; TA; Kmac; K_offset; validity time information for ephemeris information, epoch time, and/or Common TA parameters.
  • Example Embodiments D1 to D4 comprising configuring the UE to perform at least one of: using the satellite assistance information to locate a beam associated with the satellite; using the satellite assistance information to adjust an SMTC associated with the satellite; using the satellite assistance information to adjust a directional antenna; and synchronizing with the satellite.
  • Example Embodiment D6 comprising configuring the UE to perform at least one of: using the satellite assistance information to locate a beam associated with the satellite; using the satellite assistance information to adjust an SMTC associated with the satellite; using the satellite assistance information to adjust a directional antenna; and synchronizing with the satellite.
  • Example Embodiments D1 to D4 wherein the network node is serving the UE in a cell of the TN, and wherein the satellite is a candidate target cell for serving the UE in a cell of the NTN, and wherein the method comprises configuring the UE to perform at least one of: using the satellite assistance information to locate a beam associated with the cell of the NTN; using the satellite assistance information to adjust an SMTC associated with the cell of the NTN; using the satellite assistance information to adjust a directional antenna; and synchronizing with the cell of the NTN.
  • Example Embodiment D7 Example Embodiment D7.
  • Example Embodiment D8 The method of Example Embodiment D7, wherein the measurement reporting configuration applies to the satellite when the satellite is located at a height within a range.
  • Example Embodiment D9. The method of Example Embodiment D8, wherein the satellite comprises an aerial UE.
  • Example Embodiment D10 The method of Example Embodiment D7, wherein the measurement reporting configuration applies to the UE when at a height within a range.
  • Example Embodiment D12 The method of any one of Example Embodiment D1 to D10, wherein the satellite assistance information is transmitted in at least one of a SIB2 message, a SIB3 message, a SIB4 message, a SIB5 message, a SIB19 message, and/or a SIB31 message.
  • Example Embodiments D1 to D11 wherein the satellite assistance information is transmitted in at least one information element (IE), the at least one IE comprising at least one of: epochTime- r17, ntn-UlSyncValidityDuration-r17, ta-Common-r17 (in TA-Info-r17), ta- CommonDrift-r17 (in TA-Info-r17), ta-CommonDriftVariant-r17 (in TA-Info-r17), ephemerisInfo-r17, NTN-NeighCellConfigList-r17, NeighCellConfigListExt-v1720, and the NeighCellConfigEnhancedList-r18.
  • IE information element
  • Example Embodiment D13 The method of any one of Example Embodiments D1 to D12, comprising transmitting at least one PCI or at least one carrier frequency to which the satellite assistance information applies.
  • Example Embodiment D14 The method of Example Embodiment D13, wherein the satellite assistance information and the at least one PCI and/or the at least one carrier frequency are transmitted in one message.
  • Example Embodiment D15 The method of any one of Example Embodiments D1 to C14, wherein the satellite assistance information is associated with a validity time duration, and wherein the validity time duration is greater than 900 seconds.
  • Example Embodiment D16 The method of any one of Example Embodiments D1 to D12, comprising transmitting at least one PCI or at least one carrier frequency to which the satellite assistance information applies.
  • Example Embodiment D14 The method of Example Embodiment D13, wherein the satellite assistance information and the at least one PCI and/or the at least one carrier frequency are transmitted in one message.
  • Example Embodiment D17 The method of any one of Example Embodiments D1 to D16, wherein the satellite assistance information is transmitted via a dedicated RRC signaling message.
  • Example Embodiment D18 The method of any one of Example Embodiments D1 to D15, wherein the satellite assistance information is associated with and/or transmitted with a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies.
  • Example Embodiment D17 The method of any one of Example Embodiments D1 to D16, wherein the satellite assistance information is transmitted via a dedicated RRC signaling message.
  • Example Embodiment D18 Example Embodiment D18.
  • Example Embodiments D1 to D17 comprising configuring the UE to determine one of a plurality of states of the UE with respect to the satellite assistance information and adaptively adjust, update, and/or change one or more operations or parameters related to one or more of procedures, and wherein the one or more procedures comprises at least one of: a cell change procedure (such as, for example, cell reselection, cell selection, RRC connection re-establishment etc.); a measurement procedure (such as, for example, measurement rate, number, periodicity, duration, total number of carriers/frequencies/cells/satellites to be measured etc.); and/or a channel monitoring and/or reception procedure (such as, for example, paging reception, system information reception, etc.).
  • a cell change procedure such as, for example, cell reselection, cell selection, RRC connection re-establishment etc.
  • a measurement procedure such as, for example, measurement rate, number, periodicity, duration, total number of carriers/frequencies/
  • Example Embodiment D19 The method of Example Embodiment D18, comprising configuring the UE to perform the one or more of procedures based on the satellite assistance information when a RSRP and/or RSRQ received in a serving cell of the TN is higher than a threshold (TH_P1).
  • Example Embodiment D20 The method of Example Embodiment D18, comprising configuring the UE to perform the one or more of procedures based on the satellite assistance information when a RSRP and/or RSRQ received in a serving cell of the TN is lower than a threshold (TH_P2).
  • Example Embodiment D21 Example Embodiment D21.
  • Example Embodiment D18 comprising configuring the UE to perform the one or more of procedures when a time interval from a time instance when the UE receives the satellite assistance information to when the UE starts a procedure is less than a threshold(T_delta ) and/or a RSRP and/or RSRQ received in a serving cell of the TN is lower than a threshold (TH_P3).
  • Example Embodiment D22 The method of any one of Example Embodiments D1 to D21, comprising configuring the UE to: determine that at least on condition is fulfilled; and read and/or use the satellite assistance information based on the at least one condition being fulfilled.
  • Example Embodiment D23 comprising configuring the UE to perform the one or more of procedures when a time interval from a time instance when the UE receives the satellite assistance information to when the UE starts a procedure is less than a threshold(T_delta ) and/or a RSRP and/or RSRQ received in a serving cell of the
  • Example Embodiment D22 wherein the at least one condition is fulfilled when a distance between a position of the UE and a boundary of a cell of the TN is less than a threshold(TH_D1).
  • Example Embodiment D24 The method of Example Embodiment D23, wherein the cell is a serving cell in which the UE is served by the network node of the TN.
  • Example Embodiment D25 The method of any one of Example Embodiments D1 to D24, wherein the satellite assistance information is transmitted when the UE is in an inactive or idle state.
  • Example Embodiment D26 The method of any one of Example Embodiments D1 to D25, wherein the UE is an aerial UE.
  • Example Embodiment D27 The method of any one of Example Embodiments D1 to D25, wherein the UE is an aerial UE.
  • Example Embodiment D28 A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments D1 to D27.
  • Example Embodiment D29 A network node configured to perform any of the methods of Example Embodiments D1 to D27.
  • Example Embodiment D30 A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments D1 to D27.
  • a computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments D1 to D27.
  • Example Embodiment D32 A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments D1 to D27.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

A method (1300) by a user equipment, UE (110), for receiving satellite assistance information from a Terrestrial Network, TN. The method includes receiving (1302) satellite assistance information from a network node (112) serving the UE in a cell associated with the TN. The satellite assistance information is associated with a satellite that is a candidate for serving the UE in a cell associated with a Non-Terrestrial Network, NTN. The satellite assistance information is received via broadcast.

Description

SATELLITE ASSISTANCE INFORMATION PROVISIONING FROM A TERRESTERIAL NETWORK TECHNICAL FIELD The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for satellite assistance information provisioning from a Terrestrial Network (TN). BACKGROUND In 3GPP Release 8, the Evolved Packet System (EPS) was specified. EPS is based on the Long-Term Evolution (LTE) radio network and the Evolved Packet Core (EPC). It was originally intended to provide voice and mobile broadband (MBB) services but has continuously evolved to broaden its functionality. Since Release 13, Narrowband-Internet of Things (NB-IoT) and Long Term Evolution for Machines (LTE-M) are part of the LTE specifications and provide connectivity to massive machine type communications (mMTC) services. In 3GPP Release 15, the first release of the 5G system (5GS) was specified. This is a new generation’s radio access technology (RAT) intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC) and mMTC. 5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC). The NR physical and higher layers reuse parts of the LTE specification and add needed components when motivated by the new use cases. One such component is the introduction of a sophisticated framework for beam forming and beam management to extend the support of the 3GPP technologies to a frequency range going beyond 6 GHz. In Release 15, 3GPP also began preparing NR for operation in a Non- Terrestrial Network (NTN). The work was performed within the study item “NR to support Non-Terrestrial Networks” and resulted in 3GPP TR 38.811. See, 3GPP TR 38.811, Study on New Radio (NR) to support non-terrestrial networks. In Release 16, the work to prepare NR for operation in an NTN network continued with the study item “Solutions for NR to support Non-Terrestrial Network,” which resulted in 3GPP TR 38.821. The Release 16 study item resulted in a Work Item being agreed for NR in Release 17, “Solutions for NR to support non-terrestrial networks (NTN)”, which is described in the Work Item Description RP-193234. See, TS 38.304 v17.3.0, NR; User Equipment (UE) procedures in idle mode and in RRC Inactive state (Release 17). A satellite radio access network usually includes: a satellite that refers to a space-borne platform; an earth-based gateway that connects the satellite to a base station or a core network, depending on the choice of architecture; a feeder link that refers to the link between a gateway and a satellite; and an access link that refers to the link between a satellite and a UE. Depending on the orbit altitude, a satellite may be categorized as low earth orbit (LEO), medium earth orbit (MEO), or geostationary earth orbit (GEO) satellite, as follows: LEO: typical heights ranging from 250 – 1,500 km, with orbital periods ranging from 90 – 120 minutes. MEO: typical heights ranging from 5,000 – 25,000 km, with orbital periods ranging from 3 – 15 hours. GEO: height at about 35,786 km, with an orbital period of 24 hours. The significant orbit height means that satellite systems are characterized by a path loss that is significantly higher than what is expected in TNs. To overcome pathloss, it is often required that the access and feeder links are operated in line of sight (LoS) conditions, and that the UE is equipped with an antenna offering high beam directivity. A communication satellite typically generates several beams over a given area. The footprint of a beam is usually in an elliptic shape, which has been traditionally considered as a cell. The footprint of a beam is also often referred to as a spotbeam. The spotbeam may move over the earth surface with the satellite movement or may be earth fixed with some beam pointing mechanism used by the satellite to compensate for its motion. The size of a spotbeam depends on the system design, which may range from tens of kilometers to a few thousands of kilometers. FIGURE 1 illustrates an example architecture of a satellite network with bent pipe transponders. In comparison to the beams observed in a terrestrial network, the NTN beam may be very wide and cover an area outside of the area defined by the served cell. Beams covering adjacent cells will overlap and cause significant levels of intercell interference. To overcome the large levels of interference, a typical approach is for NTN to configure different cells with different carrier frequencies and polarization modes. Ephemeris data (sometimes referred to as just “ephemeris”) is data that allows a UE (or other entity) to determine a satellite’s position and velocity. For example, the ephemeris data contains parameters related to the satellite’s orbit. There are several different formats defined for ephemeris data. In 3GPP TR 38.821, it has been captured that ephemeris data should be provided to the UE such as, for example, to assist with pointing a directional antenna (or an antenna beam) towards the satellite and to calculate a correct Timing Advance (TA) and Doppler shift. See, RP-181370, Study on solutions evaluation for NR to support non-terrestrial Network. In NR, NTN and Internet of Things (IoT) NTN, ephemeris data will be broadcast in the system information (SI) in each cell, included in an NTN specific System Information Block (SIB), which is labeled SIB19 in NR NTN and SIB31 IoT NTN. A satellite orbit can be fully described using six parameters. Exactly which set of parameters is chosen can be decided by the user and/or network provider, and many different representations are possible. For example, a choice of parameters used often in astronomy is the set (a, ε, i, Ω, ω, t). Here, the semi-major axis a and the eccentricity ε describe the shape and size of the orbit ellipse; the inclination i, the right ascension of the ascending node Ω, and the argument of periapsis ω determine its position in space, and the epoch t determines a reference time (e.g. the time when the satellites moves through periapsis). FIGURE 2 illustrate a set of parameters. As an example of a different parametrization, the Two-Line Elements (TLEs) use mean motion n and mean anomaly M instead of a and t. A completely different set of parameters is the position and velocity vector (x, y, z, vx, vy, vz) of a satellite. These are sometimes called orbital state vectors. They can be derived from the orbital elements and vice versa, since the information they contain is equivalent. All these formats (and many others) are possible choices for the format of ephemeris data to be used in NTN. An aspect discussed during the 3GPP study item and captured in 3GPP TR 38.821 is the validity time of ephemeris data. Predictions of satellite positions in general degrade with increasing age of the ephemeris data used due to atmospheric drag, maneuvering of the satellite, imperfections in the orbital models used, etc. Therefore, the publicly available TLE data are updated quite frequently. For example, the update frequency depends on the satellite and its orbit and ranges from weekly to multiple times a day for satellites on very low orbits, which are exposed to strong atmospheric drag and need to perform correctional maneuvers often. Even more frequent updates will be used in NR NTN (and IoT NTN) to allow the UE to determine/predict the satellite’s position (and velocity) accurately enough to satisfy the requirements in NTN such as, for example, to enable a UE to calculate an accurate enough UE-specific TA. NTN-Specific Information in SI Due to the special operating conditions in a NTN, the SI broadcast in an NTN cell has to include NTN-specific information. To serve this purpose, a new SIB (SIB19) is introduced in NR NTN that contains NTN-specific information. In IoT NTN, the new SIB31 more or less corresponds to SIB19 in NR NTN. In 3GPP TS 38.331 version 17.0.0, SIB19 is defined in ASN.1 code in 3GPP TS 38.331 version 17.0.0. Furthermore, the NTN-Config-r17 IE is defined in ASN.1 code in the same specification. The EphemerisInfo IE is defined in ASN.1 code in the same specification. Configuration for Measurement Reporting In a wireless network, the UE needs to measure the signal quality of the cell to perform cell selection or cell re-selection. While the UE is in RRC_Connected mode, it will report the measured results to the network. The above procedures are performed based on the measurement configuration from the network, which includes the following parameters: ^ Measurement objects: A list of objects on which the UE shall perform the measurements. ^ Reporting configuration: A list of reporting configurations where there can be one or multiple reporting configurations per measurement object. Each measurement reporting configuration consists of the following: o Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be periodical or a single event description. o RS type: The RS that the UE uses for beam and cell measurement results (Synchronization Signal/Physical Broadcast Channel (SS/PBCH) block or Channel State Information-Reference Signal (CSI-RS)). o Reporting format: The quantities per cell and per beam that the UE includes in the measurement report (e.g., Reference Signal Received Power (RSRP)) and other associated information such as the maximum number of cells and the maximum number beams per cell to report. In case of conditional reconfiguration, each configuration consists of the following: o Execution criteria: The criteria the UE uses for conditional reconfiguration execution. o Reference Signal (RS) type: The RS that the UE uses for obtaining beam and cell measurement results (SS/PBCH block- based or CSI-RS-based), used for evaluating conditional reconfiguration execution condition. ^ Measurement identities: For measurement reporting, a list of measurement identities where each measurement identity links one measurement object with one reporting configuration. ^ Quantity configurations: The quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement. ^ Measurement gaps: Periods that the UE may use to perform measurements. A UE in RRC_CONNECTED maintains a measurement object list, a reporting configuration list, and a measurement identities list according to the 3GPP specification. RAN4 agreements The latest RAN4 agreement include: ^ Define “availability of valid target satellite information as side condition” o Parameters listed in R2-2201884 are defined as the required target satellite information for measurement and mobility. ^ For measurement ^ Ephemeris ^ Epoch time ^ SMTCs ^ DL polarization information ^ Serving cell stop time and reference location for IDLE mode measurement trigger in NGSO fixed cell, if applicable ^ Under RAN1 discussion: o Feeder link delay (i.e., common TA and K_MAC) of the neighbor cell should also be provided to UE for neighbor cell SMTC adjustment o separate validity timers ^ For mobility ^ Target cell Ephemeris information ^ Epoch time of the ephemeris ^ Common TA ^ Validity timer information for target cell mobility ^ DL and UL Polarization information ^ K_offset ^ Kmac (to determine UE-gNB RTT and perform RACH to target) ^ If the side condition is not met, o Requirements are not applied, i.e. extra delay won’t be explicitly defined o Note: UE is allowed not to perform RRM measurement [and reporting] if the side condition is not met before acquiring new ephemeris information There currently exist certain challenge(s), however. For example, in NTN, satellite assistance information for neighbor cells may be optionally included in SIB19 (in NR NTN) or SIB31 (in IoT NTN). This includes satellite ephemeris and related information (ntn-Config-r17) but also the carrier frequency (carrierFreq-r17) or PCI (physCellId-r17) According to the late RAN4 agreements, which has been captured in 3GPP TR 38.300, the UE is not required to perform neighbor cell measurements if the corresponding satellite assistance information is not present. This applies to both RRC_CONNECTED and RRC_IDLE modes. In order to facilitate mobility from terrestrial networks to NTN networks, the TN network need to provision the satellite information to the UEs. In RAN2 there is an ongoing discussion on whether/how it should be possible to transmit SIB19 from a TN cell. However, this would imply that the TN cell is considered as an NTN cell since it is specified that the presence of SIB19 in cell indicates implicitly that the cell supports NTN. Thus, a new mechanism is required to provide satellite assistance information (provided in SINB19 in an NTN cell) in a TN cell. SUMMARY Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, according to certain embodiments, methods and systems are disclosed for providing the essential parts of SIB19 in NR NTN and SIB31 in IoT NTN to make measurements and enable mobility. According to certain embodiments, a method by a UE for receiving satellite assistance information from a TN includes receiving satellite assistance information from a network node serving the UE in a cell associated with the TN. The satellite assistance information is associated with a satellite that is a candidate for serving the UE in a cell associated with a Non-Terrestrial Network, NTN. The satellite assistance information is received via broadcast. According to certain embodiments, a UE for receiving satellite assistance information from a TN is configured to receive satellite assistance information from a network node serving the UE in a cell associated with the TN. The satellite assistance information is associated with a satellite that is a candidate for serving the UE in a cell associated with a Non-Terrestrial Network, NTN. The satellite assistance information is received via broadcast. According to certain embodiments, a method is provided by a network node associated with a TN for providing satellite assistance information for a satellite of an NTN. The method includes transmitting, to a UE the satellite assistance information associated with a satellite that is a candidate for serving the UE in a cell associated with the NTN. The network node is serving the UE in a cell associated with the TN, and the satellite information is transmitted via broadcast. According to certain embodiments, a network node associated with a TN for providing satellite assistance information for a satellite of a NTN is configured to transmit, to a UE the satellite assistance information associated with a satellite that is a candidate for serving the UE in a cell associated with the NTN. The network node is serving the UE in a cell associated with the TN, and the satellite information is transmitted via broadcast. Certain embodiments may provide one or more of the following technical advantage(s). For example, certain embodiments may provide a technical advantage of enabling a proposed height dependent measurement reporting configuration that provides several candidate measurement reporting configurations for aerial UEs within certain height range and optimize the RRM configuration by adapting to the height of UEs. Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages. BRIEF DESCRIPTION OF THE DRAWINGS For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which: FIGURE 1 illustrates an example architecture of a satellite network with bent pipe transponders; FIGURE 2 illustrate a set of parameters; FIGURE 3 illustrates an example wireless network, according to certain embodiments; FIGURE 4 illustrates an example network node, according to certain embodiments; FIGURE 5 illustrates an example wireless device, according to certain embodiments; FIGURE 6 illustrate an example user equipment, according to certain embodiments; FIGURE 7 illustrates another example wireless network, according to certain embodiments; FIGURE 8 illustrates a method by a UE for receiving satellite assistance information from a TN, according to certain embodiments; FIGURE 9 illustrates another example method by a UE for receiving satellite assistance information from a TN, according to certain embodiments; FIGURE 10 illustrates an example method by a NTN node serving a wireless device in a first cell, according to certain embodiments; and FIGURE 11 illustrates another example method by a network node associated with a TN for providing satellite assistance information for a satellite of a NTN, according to certain embodiments.
DETAILED DESCRIPTION Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description. As used herein, ‘node’ can be a network node or a UE. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), Operations Support System (OSS), Self Organizing Network (SON), positioning node (e.g. E-SMLC), etc. Another example of a node is user equipment (UE), which is a non-limiting term and refers to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, etc. In some embodiments, generic terminology, “radio network node” or simply “network node (NW node)”, is used. It can be any kind of network node which may comprise base station, radio base station, base transceiver station, base station controller, network controller, evolved Node B (eNB), Node B, gNodeB (gNB), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), etc. The term radio access technology (RAT), may refer to any RAT such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), narrow band internet of things (NB- IoT), WiFi, Bluetooth, next generation RAT, NR, 4G, 5G, etc. Any of the equipment denoted by the terms node, network node or radio network node may be capable of supporting a single or multiple RATs. The term signal or radio signal used herein can be any physical signal or physical channel. Examples of DL physical signals are reference signal (RS) such as Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information-Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS) signals in SS/PBCH block (SSB), discovery reference signal (DRS), Cell Specific Reference Signal (CRS), Positioning Reference Signal (PRS), etc. RS may be periodic. For example, RS occasions carrying one or more RSs may occur with certain periodicity such as, for example, 20 ms, 40 ms, etc. The RS may also be aperiodic. Each SSB carries NR-PSS, NR-SSS and NR-PBCH in four successive symbols. One or multiple SSBs are transmit in one SSB burst which is repeated with certain periodicity such as, for example, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms. The UE is configured with information about SSB on cells of certain carrier frequency by one or more SS/PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration comprising parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset with regard to reference time (e.g., serving cell’s SFN), etc. Therefore, SMTC occasion may also occur with certain periodicity such as, for example, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms. Examples of uplink (UL) physical signals are reference signal such as SRS, DMRS etc. The term physical channel refers to any channel carrying higher layer information such as, for example, data, control, etc. Examples of physical channels are Physical Broadcast Channel (PBCH), Narrowband PBCH (NPBCH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), shortened PUCCH (sPUCCH), shortened PDSCH (sPDSCH), shortened PUCCH (sPUCCH), shortened PUSCH (sPUSCH), MTC PDCCH (MPDCCH), narrowband PDCCH (NPDCCH), Narrowband PDSCH (NPDSCH), E-PDCCH, Narrowband PUSCH (NPUSCH), etc. The term time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are: symbol, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, slot, sub-slot, mini-slot, system frame number (SFN) cycle, hyper-SFN (H-SFN) cycle etc. It may be recognized that, in NR, a UE will see cells and not necessarily satellites. While this disclosure talks about serving and neighbor satellites, it may be understood that, as used herein, the term serving satellite is used to refer to a satellite broadcasting the cell that is serving the UE. Likewise, the term neighbor satellite is used to refer to a satellite that is broadcasting the cell that is neighbor cell for the UE. According to certain embodiments, methods and systems are disclosed for providing the essential parts of SIB19 in NR NTN and SIB31 in IoT NTN to make measurements and enable mobility. For example, in various particular embodiments, a proposed height dependent measurement reporting configuration introduces one or more measurement reporting configuration for aerial UEs within certain height range and describes how the configurations are adopted, as well as some candidate parameters which could be included in the configuration sets. Also other approaches are presented on how the measurement and reporting of the UE can be controlled via the RRC configuration. More specifically, according to certain embodiments, the essential information for performing neighbor cell measurements in RRC_INACTIVE and RRC_IDLE state is acquired from SIB19 broadcast in an NR NTN cell. In accordance with certain embodiments, it is broadcast in an NR TN cell in SIB2 and/or SIB3 and/or SIB4 together with a list of Physical Cell Indicators (PCIs) and/or carrier frequencies. In an LTE TN cell, the essential information is, in accordance with the proposed methods, systems, and techniques, broadcast in SIB3 and/or SIB4 and/or SIB5. In NR TN cells, satellite assistance information for an NTN neighbor cell may be transmitted in a new or different (SIB(s). For example, SIB2 may include common information relevant for intra-frequency, inter-frequency, and inter-RAT NTN neighbors. Similarly, SIB3 may be used in case the NTN neighbor operates in the same frequency as the serving cell. There may be overlapping frequency bands between TN and NTN. See, TS 38.304. Finally, SIB4 can be used for inter-frequency NTN neighbors and SIB5 for inter-RAT NTN neighbors (e.g., LTE NTN). The following is an example of how satellite assistance information can be included in SIB4 in NR, (using the SIB4 ASN.1 definition in 3GPP TS 38.331 version 17.3.0 as the baseline and showing changes to the baseline text using bold and underline): -- ASN1START -- TAG-SIB4-START SIB4 ::= SEQUENCE { interFreqCarrierFreqList InterFreqCarrierFreqList, lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ interFreqCarrierFreqList-v1610 InterFreqCarrierFreqList-v1610 OPTIONAL -- Need R ]], [[ interFreqCarrierFreqList-v1700 InterFreqCarrierFreqList-v1700 OPTIONAL -- Need R ]], [[ interFreqCarrierFreqList-v1720 InterFreqCarrierFreqList-v1720 OPTIONAL -- Need R ]], [[ interFreqCarrierFreqList-v1730 InterFreqCarrierFreqList-v1730 OPTIONAL -- Need R ]], [[ NeighCellConfigList-r18 NTN- r17 OPTIONAL, -- Need R NeighCellConfigListExt-r18 NTN- NeighCellConfigList-r17 OPTIONAL -- Need R ]] } InterFreqCarrierFreqList ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo InterFreqCarrierFreqList-v1610 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1610 InterFreqCarrierFreqList-v1700 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1700 InterFreqCarrierFreqList-v1720 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1720 InterFreqCarrierFreqList-v1730 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1730 InterFreqCarrierFreqInfo ::= SEQUENCE { dl-CarrierFreq ARFCN-ValueNR, frequencyBandList MultiFrequencyBandListNR-SIB OPTIONAL, -- Cond Mandatory frequencyBandListSUL MultiFrequencyBandListNR-SIB OPTIONAL, -- Need R nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need S absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need S smtc SSB-MTC OPTIONAL, -- Need S ssbSubcarrierSpacing SubcarrierSpacing, ssb-ToMeasure SSB- ToMeasure OPTIONAL, -- Need S deriveSSB-IndexFromCell BOOLEAN, ss-RSSI-Measurement SS-RSSI- Measurement OPTIONAL, -- Need R q-RxLevMin Q-RxLevMin, q-RxLevMinSUL Q-RxLevMin OPTIONAL, -- Need R q-QualMin Q-QualMin OPTIONAL, -- Need S p-Max P-Max OPTIONAL, -- Need S t-ReselectionNR T-Reselection, t-ReselectionNR-SF SpeedStateScaleFactors OPTIONAL, -- Need S threshX-HighP ReselectionThreshold, threshX-LowP ReselectionThreshold, threshX-Q SEQUENCE { threshX-HighQ ReselectionThresholdQ, threshX-LowQ ReselectionThresholdQ } OPTIONAL, -- Cond RSRQ cellReselectionPriority CellReselectionPriority OPTIONAL, -- Need R cellReselectionSubPriority CellReselectionSubPriority OPTIONAL, -- Need R q-OffsetFreq Q-OffsetRange DEFAULT dB0, interFreqNeighCellList InterFreqNeighCellList OPTIONAL, -- Need R interFreqExcludedCellList InterFreqExcludedCellList OPTIONAL, -- Need R ... } InterFreqCarrierFreqInfo-v1610 ::= SEQUENCE { interFreqNeighCellList-v1610 InterFreqNeighCellList-v1610 OPTIONAL, -- Need R smtc2-LP-r16 SSB-MTC2-LP-r16 OPTIONAL, -- Need R interFreqAllowedCellList-r16 InterFreqAllowedCellList-r16 OPTIONAL, -- Cond SharedSpectrum2 ssb-PositionQCL-Common-r16 SSB-PositionQCL- Relation-r16 OPTIONAL, -- Cond SharedSpectrum interFreqCAG-CellList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF InterFreqCAG-CellListPerPLMN-r16 OPTIONAL -- Need R } InterFreqCarrierFreqInfo-v1700 ::= SEQUENCE { interFreqNeighHSDN-CellList-r17 InterFreqNeighHSDN-CellList-r17 OPTIONAL, -- Need R highSpeedMeasInterFreq-r17 ENUMERATED {true} OPTIONAL, -- Need R redCapAccessAllowed-r17 ENUMERATED {true} OPTIONAL, -- Need R ssb-PositionQCL-Common-r17 SSB-PositionQCL- Relation-r17 OPTIONAL, -- Cond SharedSpectrum interFreqNeighCellList-v1710 InterFreqNeighCellList-v1710 OPTIONAL -- Cond SharedSpectrum2 } InterFreqCarrierFreqInfo-v1720 ::= SEQUENCE { smtc4list-r17 SSB-MTC4List-r17 OPTIONAL -- Need R } InterFreqCarrierFreqInfo-v1730 ::= SEQUENCE { channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL -- Need R } InterFreqNeighHSDN-CellList-r17 ::= SEQUENCE (SIZE (1..maxCellInter)) OF PCI-Range InterFreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo InterFreqNeighCellList-v1610 ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo-v1610 InterFreqNeighCellList-v1710 ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo-v1710 InterFreqNeighCellInfo ::= SEQUENCE { physCellId PhysCellId, q-OffsetCell Q-OffsetRange, q-RxLevMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R q-RxLevMinOffsetCellSUL INTEGER (1..8) OPTIONAL, -- Need R q-QualMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R ... } InterFreqNeighCellInfo-v1610 ::= SEQUENCE { ssb-PositionQCL-r16 SSB-PositionQCL- Relation-r16 OPTIONAL - - Cond SharedSpectrum2 } InterFreqNeighCellInfo-v1710 ::= SEQUENCE { ssb-PositionQCL-r17 SSB-PositionQCL- Relation-r17 OPTIONAL - - Cond SharedSpectrum2 } InterFreqExcludedCellList ::= SEQUENCE (SIZE (1..maxCellExcluded)) OF PCI-Range InterFreqAllowedCellList-r16 ::= SEQUENCE (SIZE (1..maxCellAllowed)) OF PCI-Range InterFreqCAG- ::= SEQUENCE { plmn-IdentityIndex-r16 INTEGER (1..maxPLMN), cag-CellList-r16 SEQUENCE (SIZE (1..maxCAG-Cell-r16)) OF PCI-Range } NTN-NeighCellConfigList-r17 ::= SEQUENCE (SIZE(1..maxCellNTN-r17)) OF NTN-NeighCellConfig-r17 NTN-NeighCellConfig-r17 ::= SEQUENCE { ntn-Config-r17 NTN-Config-r17 OPTIONAL, -- Need R carrierFreq-r17 ARFCN-ValueNR OPTIONAL, -- Need R physCellId-r17 PhysCellId OPTIONAL -- Need R } -- TAG-SIB4-STOP -- ASN1STOP As another example, according to various particular embodiments, SIB19/SIB31 essential parameters are defined by the RAN4 agreements. In particular embodiments, for example, the above NTN-NeighCellConfig-r17 consists, instead of ntn-Config-r17 and may include a list of one or more parameters such as any one or more of (but not limited to): ^ NTN payload ephemeris ^ Epoch time of the ephemeris ^ SMTCs ^ DL and UL polarization information ^ Serving cell stop time ^ Reference location for NGSO fixed and moving cells, if applicable ^ Feeder link delay (i.e., common TA and Kmac) of the neighbor cell should also be provided to UE for neighbor cell SMTC adjustment ^ K_offset ^ Validity time information for ephemeris information, epoch time and Common TA parameters And instead of one PCI, a list of PCIs for which the list of parameters apply. In an alternative example of how satellite assistance information can be included in SIB4 in NR, the ntn-NeighCellConfigList-r17 and ntn- NeighCellConfigListExt-v1720 IEs have been replaced by a single new list denoted as ntn-NeighCellConfigEnhancedList-r18. This alternative example is included below, using the ASN.1 definition of SIB4 in 3GPP TS 38.331 version 17.3.0 as the baseline (and with new/additional text shown with bold and underline): -- ASN1START -- TAG-SIB4-START SIB4 ::= SEQUENCE { interFreqCarrierFreqList InterFreqCarrierFreqList, lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ interFreqCarrierFreqList-v1610 InterFreqCarrierFreqList-v1610 OPTIONAL -- Need R ]], [[ interFreqCarrierFreqList-v1700 InterFreqCarrierFreqList-v1700 OPTIONAL -- Need R ]], [[ interFreqCarrierFreqList-v1720 InterFreqCarrierFreqList-v1720 OPTIONAL -- Need R ]], [[ interFreqCarrierFreqList-v1730 InterFreqCarrierFreqList-v1730 OPTIONAL -- Need R ]], [[ NeighCellConfigEnhancedList-r18 NTN- r18 OPTIONAL, -- Need R ]] } InterFreqCarrierFreqList ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo InterFreqCarrierFreqList-v1610 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1610 InterFreqCarrierFreqList-v1700 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1700 InterFreqCarrierFreqList-v1720 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1720 InterFreqCarrierFreqList-v1730 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1730 InterFreqCarrierFreqInfo ::= SEQUENCE { dl-CarrierFreq ARFCN-ValueNR, frequencyBandList MultiFrequencyBandListNR-SIB OPTIONAL, -- Cond Mandatory frequencyBandListSUL MultiFrequencyBandListNR-SIB OPTIONAL, -- Need R nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need S absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need S smtc SSB-MTC OPTIONAL, -- Need S ssbSubcarrierSpacing SubcarrierSpacing, ssb-ToMeasure SSB-ToMeasure OPTIONAL, -- Need S deriveSSB-IndexFromCell BOOLEAN, ss-RSSI-Measurement SS-RSSI- Measurement OPTIONAL, -- Need R q-RxLevMin Q-RxLevMin, q-RxLevMinSUL Q-RxLevMin OPTIONAL, -- Need R q-QualMin Q-QualMin OPTIONAL, -- Need S p-Max P-Max OPTIONAL, -- Need S t-ReselectionNR T-Reselection, t-ReselectionNR-SF SpeedStateScaleFactors OPTIONAL, -- Need S threshX-HighP ReselectionThreshold, threshX-LowP ReselectionThreshold, threshX-Q SEQUENCE { threshX-HighQ ReselectionThresholdQ, threshX-LowQ ReselectionThresholdQ } OPTIONAL, -- Cond RSRQ cellReselectionPriority CellReselectionPriority OPTIONAL, -- Need R cellReselectionSubPriority CellReselectionSubPriority OPTIONAL, -- Need R q-OffsetFreq Q-OffsetRange DEFAULT dB0, interFreqNeighCellList InterFreqNeighCellList OPTIONAL, -- Need R interFreqExcludedCellList InterFreqExcludedCellList OPTIONAL, -- Need R ... } InterFreqCarrierFreqInfo-v1610 ::= SEQUENCE { interFreqNeighCellList-v1610 InterFreqNeighCellList-v1610 OPTIONAL, -- Need R smtc2-LP-r16 SSB-MTC2-LP-r16 OPTIONAL, -- Need R interFreqAllowedCellList-r16 InterFreqAllowedCellList-r16 OPTIONAL, -- Cond SharedSpectrum2 ssb-PositionQCL-Common-r16 SSB-PositionQCL- Relation-r16 OPTIONAL, -- Cond SharedSpectrum interFreqCAG-CellList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF InterFreqCAG-CellListPerPLMN-r16 OPTIONAL -- Need R } InterFreqCarrierFreqInfo-v1700 ::= SEQUENCE { interFreqNeighHSDN-CellList-r17 InterFreqNeighHSDN-CellList-r17 OPTIONAL, -- Need R highSpeedMeasInterFreq-r17 ENUMERATED {true} OPTIONAL, -- Need R redCapAccessAllowed-r17 ENUMERATED {true} OPTIONAL, -- Need R ssb-PositionQCL-Common-r17 SSB-PositionQCL- Relation-r17 OPTIONAL, -- Cond SharedSpectrum interFreqNeighCellList-v1710 InterFreqNeighCellList-v1710 OPTIONAL -- Cond SharedSpectrum2 } InterFreqCarrierFreqInfo-v1720 ::= SEQUENCE { smtc4list-r17 SSB-MTC4List-r17 OPTIONAL -- Need R } InterFreqCarrierFreqInfo-v1730 ::= SEQUENCE { channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL -- Need R } InterFreqNeighHSDN-CellList-r17 ::= SEQUENCE (SIZE (1..maxCellInter)) OF PCI-Range InterFreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo InterFreqNeighCellList-v1610 ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo-v1610 InterFreqNeighCellList-v1710 ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo-v1710 InterFreqNeighCellInfo ::= SEQUENCE { physCellId PhysCellId, q-OffsetCell Q-OffsetRange, q-RxLevMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R q-RxLevMinOffsetCellSUL INTEGER (1..8) OPTIONAL, -- Need R q-QualMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R ... } InterFreqNeighCellInfo-v1610 ::= SEQUENCE { ssb-PositionQCL-r16 SSB-PositionQCL- Relation-r16 OPTIONAL - - Cond SharedSpectrum2 } InterFreqNeighCellInfo-v1710 ::= SEQUENCE { ssb-PositionQCL-r17 SSB-PositionQCL- Relation-r17 OPTIONAL - - Cond SharedSpectrum2 } InterFreqExcludedCellList ::= SEQUENCE (SIZE (1..maxCellExcluded)) OF PCI-Range InterFreqAllowedCellList-r16 ::= SEQUENCE (SIZE (1..maxCellAllowed)) OF PCI-Range InterFreqCAG- ::= SEQUENCE { plmn-IdentityIndex-r16 INTEGER (1..maxPLMN), cag-CellList-r16 SEQUENCE (SIZE (1..maxCAG-Cell-r16)) OF PCI-Range } NTN-NeighCellConfigEnhancedList-r18 ::= SEQUENCE (SIZE(1..maxCellNTN-r18)) OF NTN-NeighCellConfigEnhanced-r18 NTN-NeighCellConfigEnhanced-r18 ::= SEQUENCE { ntn-Config-r17 NTN-Config-r17 OPTIONAL, -- Need R carrierFreqAndCellsNTN-List-r18 CarrierFreqAndCellsNTN-List-r18 OPTIONAL, -- Need R } CarrierFreqAndCellsNTN-List-r18 ::= SEQUENCE (SIZE(1..maxFreqAndCellsNTN-r18)) OF CarrierFreqAndCellsNTN-r18 CarrierFreqAndCellsNTN-r18 ::= SEQUENCE { carrierFreq-r17 ARFCN-ValueNR OPTIONAL, -- Need R ntn-NeighCells-r18 SEQUENCE (SIZE(1..maxCellNTN-r18)) OF PhysCellId OPTIONAL -- Need R } -- TAG-SIB4-STOP In another embodiment, the above NTN-NeighCellConfigEnhanced-r18 consists, instead of ntn-Config-r17, a list of parameters, one or more of: ^ NTN payload ephemeris ^ Epoch time of the ephemeris ^ SMTCs ^ Downlink (DL) and uplink (UL) polarization information ^ Serving cell stop time ^ Reference location for Non-Geostationary Orbit (NGSO) fixed and moving cells, if applicable ^ Feeder link delay (i.e., common TA and Kmac) of the neighbor cell should also be provided to UE for neighbor cell SMTC adjustment ^ K_offset ^ Validity time information for ephemeris information, epoch time and Common TA parameters In LTE cells, satellite assistance information for an NTN neighbor cell may be transmitted in different SIBs. For example, SIB3 may include common information relevant for intra-frequency, inter-frequency, and inter-RAT NTN neighbors. Similarly, SIB4 may be used in case the NTN neighbor operates in the same frequency as the serving cell. Finally, SIB5 can be used for inter-frequency and/or inter-RAT NTN neighbors (e.g., NR NTN).In an alternative embodiment, the essential or relevant parts of the information contained in SIB19 (in NR) or SIB31 (in LTE) for each neighbor NTN satellite and /or cell are broadcast in a new SIB or in an existing SIB in a TN cell as an extension (wherein the utilized existing SIB is not a SIB whose presence (i.e. availability in a cell) is also used to implicitly or explicitly indicate that the cell is an NTN cell) and are associated with an indication different from PCI or carrier frequency, e.g., satellite identifier (ID). This indication is similarly added to the corresponding entry in InterFreqNeighCellInfo and/or IntraFreqNeighCellInfo, respectively, so that UE can identify the required satellite assistance information for the target NTN cell. Changes of the dynamic satellite assistance information included as an extension in any legacy SIB should be exempt from the typical SI update mechanisms, which involves sending SI update notifications to UEs in the cell by repeated transmissions of a so-called Short Message, which is a Downlink Control Information (DCI) message sent on the PDCCH addressed to the Paging-Radio Network Temporary Identifier (P-RNTI) (i.e., the RNTI otherwise used for paging of UEs). This is motivated by that the content is very dynamic and its validity is governed by timers (indicated as validity durations), which trigger interested (NTN capable) UEs to reacquire the information when needed. This concerns primarily (when included in the concerned embodiment) the fields epochTime-r17, ntn-UlSyncValidityDuration-r17, ta-Common-r17 (in TA-Info-r17), ta-CommonDrift-r17 (in TA-Info-r17), ta- CommonDriftVariant-r17 (in TA-Info-r17), and ephemerisInfo-r17, but it may also concern changes in the set of NTN neighbor cells, i.e. changes of which list items the NTN-NeighCellConfigList-r17 and NeighCellConfigListExt-v1720 IEs or the NeighCellConfigEnhancedList-r18 IE contain, i.e. additions and removals of list items, as well as changes of fields within a list item (such mechanisms are further elaborated in the examples using SIB19 discussed herein and those mechanisms may be reused when the satellite assistance information is included in a legacy TN SIB too). Using NR SIB19 (and/or LTE SIB31) The embodiments herein are described in terms of NR and SIB19, but similar concepts can be applied to LTE and SIB31 too. In some embodiments SIB19 (in NR) and/or SIB31 (in LTE) are used to broadcast the neighbor satellite assistance information also in TN cells. This is true despite the potential problem associated with it. For example, an NTN capable legacy UE may interpret the existence of SIB19 (in NR) or SIB31 (in LTE) as an indication of that the cell is an NR NTN cell or an IoT cell. The usage of SIB19 (in NR) and/or SIB31 (in LTE) in the embodiments described herein is motivated by the reasoning that the advantage of being able to reuse existing specified functionality outweighs the disadvantage. In addition, the legacy UEs implementing NR NTN and/or IoT NTN functionality in accordance with Release 17 of the 3GPP standard can be expected to be very few, and the ones that may be produced can be expected to soon be replaced by superior models implementing later releases of the 3GPP standard and potentially more streamlined hardware (e.g., smaller and more energy efficient hardware). Moreover, the potential problem associated with usage of SIB19 in an NR NTN cell may possibly never occur since the NR stage 2 specification for NR (i.e., 3GPP TS 38.300 version 17.3.0, Section 16.14.3.1) states that “The UE can determine the network type (terrestrial or non-terrestrial) implicitly by the existence of cellBarredNTN in SIB1”. Furthermore, the content of SIB19 (in NR) and SIB31 (in LTE) can be pruned from irrelevant information to streamline them for usage in TN cells, and since their contents are very dynamic and require frequent reacquisition by a UE required to maintain a valid copy of the information. If the relevant satellite assistance information would instead be placed in legacy SIB(s), this would force such a UE to frequently reacquire this(these) legacy SIB(s), which, due to the potentially extensive content of this(these) legacy SIB(s), will cause undesirable overhead (e.g. in terms of processing and energy consumption) in the UE. Usage of SIB19 (in NR) and/or SIB31 (in LTE) may, thus, potentially be advantageous, but to optimize network and UE operations, usage of these SIBs should be different from their usage in NR NTN and IoT NTN. A major difference between a TN cell and an NTN cell is that a TN cell is not served by a satellite. As a consequence, no satellite assistance information is needed for the serving cell. Looking at the ASN.1 definition of SIB19 in NR in 3GPP TS 38.331 version 17.3.0 (which is copied below for convenience), all fields except ntn- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 are associated with the serving cell (disregarding the lateNonCriticalExtension field, whose purpose is to enable future extensions, and for which no content has yet been specified). The ntn- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs are thus the only IEs that are relevant when SIB19 is broadcast in a TN cell, while the other fields (which are all optional) are of no use and should be omitted. (The referenceLocation-r17 and distanceThreshold-r17 fields could in principle be used also in a TN cell, but they were designed for usage in a pseudo-Earth-fixed cell and would be of little or no value in a TN cell.): -- ASN1START -- TAG-SIB19-START SIB19-r17 ::= SEQUENCE { ntn-Config-r17 NTN-Config-r17 OPTIONAL, -- Need R t-Service-r17 INTEGER (0..549755813887) OPTIONAL, -- Need R referenceLocation-r17 ReferenceLocation- r17 OPTIONAL, -- Need R distanceThresh-r17 INTEGER(0..65525) OPTIONAL, -- Need R ntn-NeighCellConfigList-r17 NTN- NeighCellConfigList-r17 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ ntn-NeighCellConfigListExt-v1720 NTN- NeighCellConfigList-r17 OPTIONAL -- Need R ]] } NTN-NeighCellConfigList-r17 ::= SEQUENCE (SIZE(1..maxCellNTN-r17)) OF NTN-NeighCellConfig-r17 NTN-NeighCellConfig-r17 ::= SEQUENCE { ntn-Config-r17 NTN-Config-r17 OPTIONAL, -- Need R carrierFreq-r17 ARFCN-ValueNR OPTIONAL, -- Need R physCellId-r17 PhysCellId OPTIONAL -- Need R } -- TAG-SIB19-STOP -- ASN1STOP To support the above proposed configuration choice for SIB19, the following amendment of the text in section 5.2.2.4.21 in 3GPP TS 38.331 version 17.3.0 (which does not appropriately take broadcast of SIB19 in a TN cell into account) could be made (the text addition is shown with underline and bold): Upon receiving SIB19 in an NTN cell, the UE in RRC_CONNECTED shall: 1> start or restart T430 for serving cell with the timer value set to ntn-UlSyncValidityDuration for the serving cell from the subframe indicated by epochTime for the serving cell; NOTE: UE should attempt to re-acquire SIB19 before the end of the duration indicated by ntn-UlSyncValidityDuration and epochTime by UE implementation. A further beneficial amendment of the 3GPP specifications could be the following amendment to the field description of ntn-Config-r17 in the SIB19 field descriptions in 3GPP TS 38.331 version 17.3.0 (the text addition is shown with underline and bold): ntn-Config Provides parameters needed for the UE to access NR via NTN access such as Ephemeris data, common TA parameters, k_offset, validity duration for UL sync information and epoch. When the serving cell is a TN cell, the field is absent in the information associated with the serving cell. Otherwise the field is optionally present (need R). And in addition, the following sentence could advantageously be added to some of the other SIB19 field descriptions (for the fields t-Service-r17, referenceLocation-r17 and distanceThreshold-r17) in 3GPP TS 38.331 version 17.3.0: “The field is absent when the serving cell is a TN cell.” Alternatively, or in addition to the above amendments, a new conditional presence tag could be introduced and associated with the ntn-Config-r17 field in the serving cell information in SIB19. This new conditional presence tag could be called “NTN-cell”, for example, and would mean that the field is absent if the serving cell is a TN cell, otherwise the field is optionally present (need R). The following is an example where the above-described amendments and the new conditional presence tag all have been implemented in the ASN.1 definition and field descriptions for SIB1, using 3GPP TS 38.331 version 17.3.0 as the baseline (the text addition is shown with underline and bold): -- ASN1START -- TAG-SIB19-START SIB19-r17 ::= SEQUENCE { ntn-Config-r17 NTN-Config-r17 OPTIONAL, -- Cond NTN- cell t-Service-r17 INTEGER (0..549755813887) OPTIONAL, -- Need R referenceLocation-r17 ReferenceLocation-r17 OPTIONAL, -- Need R distanceThresh-r17 INTEGER(0..65525) OPTIONAL, -- Need R ntn-NeighCellConfigList-r17 NTN-NeighCellConfigList-r17 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ ntn-NeighCellConfigListExt-v1720 NTN-NeighCellConfigList-r17 OPTIONAL -- Need R ]] } NeighCellConfigList-r17 ::= SEQUENCE (SIZE(1..maxCellNTN-r17)) OF NeighCellConfig-r17 NTN-NeighCellConfig-r17 ::= SEQUENCE { ntn-Config-r17 NTN-Config-r17 OPTIONAL, -- Need R carrierFreq-r17 ARFCN-ValueNR OPTIONAL, -- Need R physCellId-r17 PhysCellId OPTIONAL -- Need R } -- TAG-SIB19-STOP -- ASN1STOP SIB19 field descriptions a SIB19 field descriptions distanceThresh a Using a new SIB In some embodiments, a new SIB is introduced in NR (herein referred to as SIBxx) specifically for the purpose of providing neighbor NTN cell and satellite assistance information in a TN cell. This new SIB could be tailored for this purpose such as, for example, by reusing the neighbor cell/satellite related fields of SIB19, while omitting the fields related to the serving cell. An example ASN.1 definition of such a new SIB is illustrated below: -- ASN1START -- TAG-SIBxx-START SIBxx-r18 ::= SEQUENCE { ntn-NeighCellConfigList-r17 NTN- NeighCellConfigList-r17 OPTIONAL, -- Need R ntn-NeighCellConfigListExt-v1720 NTN- NeighCellConfigList-r17 OPTIONAL -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ..., } NTN-NeighCellConfigList-r17 ::= SEQUENCE (SIZE(1..maxCellNTN-r17)) OF NTN-NeighCellConfig-r17 NTN-NeighCellConfig-r17 ::= SEQUENCE { ntn-Config-r17 NTN-Config-r17 OPTIONAL, -- Need R carrierFreq-r17 ARFCN-ValueNR OPTIONAL, -- Need R physCellId-r17 PhysCellId OPTIONAL -- Need R } -- TAG-SIBxx-STOP -- ASN1STOP All the previously described options for how updates of the NeighCellConfigList-r17 and NeighCellConfigListExt-v1720 IEs should be treated, such as, in terms of whether they should trigger SI change notifications and valueTag updates, or whether such changes should be indicated in the Short Message DCI conveying SI change notifications, can be reused for the SIBxx example above too. In another example ASN.1 definition, the ntn-NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs have been replaced by a single new list denoted as ntn-NeighCellConfigEnhancedList-r18. -- ASN1START -- TAG-SIBxx-START SIBxx-r18 ::= SEQUENCE { ntn-NeighCellConfigEnhancedList-r18 NTN- NeighCellConfigEnhancedList-r18 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ..., } NTN-NeighCellConfigEnhancedList-r18 ::= SEQUENCE (SIZE(1..maxCellNTN-r18)) OF NTN-NeighCellConfigEnhanced-r18 NTN-NeighCellConfigEnhanced-r18 ::= SEQUENCE { ntn-Config-r17 NTN-Config-r17 OPTIONAL, -- Need R carrierFreqAndCellsNTN-List-r18 CarrierFreqAndCellsNTN-List-r18 OPTIONAL, -- Need R } CarrierFreqAndCellsNTN-List-r18 ::= SEQUENCE (SIZE(1..maxFreqAndCellsNTN-r18)) OF CarrierFreqAndCellsNTN-r18 CarrierFreqAndCellsNTN-r18 ::= SEQUENCE { carrierFreq-r17 ARFCN-ValueNR OPTIONAL, -- Need R ntn-NeighCells-r18 SEQUENCE (SIZE(1..maxCellNTN-r18)) OF PhysCellId OPTIONAL -- Need R } -- TAG-SIBxx-STOP -- ASN1STOP All the previously described options for how updates of the NeighCellConfigList-r17 and NeighCellConfigListExt-v1720 IEs should be treated, e.g., in terms of whether they should trigger SI change notifications and valueTag updates, or whether such changes should be indicated in the Short Message DCI conveying SI change notifications, can be reused for the ntn- NeighCellConfigEnhancedList-r18 IE in the above variant of SIBxx too. Validity of the SI According to certain embodiments (and as opposed to the case for satellite assistance information for the serving cell), a UE is not expected to use the satellite assistance information for a neighbor cell to calculate its UE specific TA, but rather for autonomous adjustments of the SMTC associated with the neighbor cell (and possibly for determination of a receive beam or adjustment of a directional antenna, in case the UE uses such features for NTN monitoring). This usage of the satellite assistance information can be performed with much lower accuracy of the satellite assistance information (i.e., greater errors in the satellite assistance information are tolerable) than UE autonomous TA calculation. As a consequence, a longer validity time can be configured for the satellite assistance information associated with a neighbor cell than for the satellite assistance information associated with the serving cell. When the satellite assistance information for the serving cell is omitted when SIB19 is broadcast in a TN cell (because the serving cell is not served by a satellite), this property could be better utilized if the current maximum configurable value of the validity time (i.e., the ntn-UlSyncValidityDuration-r17 field in the NTN-Config-r17 IE), which is 900 seconds in 3GPP TS 38.331 version 17.3.0, were to be increased (e.g., by adding one or more configurable values greater than 900 seconds such as, for example, to 1800 seconds). Another consequence is the potential use of coarser ephemeris information such as, for example, mean ephemeris information, which inherently holds valid for longer periods of time (in the order of weeks). Mean ephemeris information is presently transmitted in TLE format as part of SIB32 (LTE) assistance information for discontinuous coverage scenarios and could be similarly used for SMTC adjustments. Change of SI content According to 3GPP TS 38.331 version 17.3.0, the most dynamic content in SIB19 is exempt from the regular SI change notification mechanisms. That is, changes thereof trigger neither SI change notifications to be sent, nor modifications of the valueTag associated with SIB19. The concerned fields are all included in the NTN-Config-r17 IE, and they all have the following sentence in their respective field description: “This field is excluded when determining changes in system information, i.e. changes to <field name> should neither result in system information change notifications nor in a modification of valueTag in SIB1.” In the above quoted sentence, “<field name>“ represents the respective one of the concerned field names. The concerned fields are: epochTime-r17 ntn-UlSyncValidityDuration-r17 ta-Common-r17 (in TA-Info-r17) ta-CommonDrift-r17 (in TA-Info-r17) ta-CommonDriftVariant-r17 (in TA-Info-r17) ephemerisInfo-r17 The exemption of these fields serves to avoid frequent SI change notifications, which would consume DL transmission resources as well as processing resources, and would have a negative impact on the UEs’ energy consumption. Such notifications would also be superfluous, as a UE’s reacquisition of SIB19 in an NTN cell anyway is governed by the value of the ntn-UlSyncValidityDuration-r17 field and its internal timer T430. When SIB19 is broadcast in a TN cell, the situation becomes slightly different, because the neighbor NTN cells are served by moving satellites (except in the case of a geostationary satellite, which is not moving in relation to the TN cell), while the TN cell is not. As a result, the neighbor NTN cells will change frequently due to cell switches (triggered by changes in the feeder link or the serving satellite) and moving NTN cells. As a consequence, the list of neighbor NTN cells, as configured in the NTN-NeighCellConfigList-r17 IE and the ntn-NeighCellConfigListExt-v1720 IE will be relatively frequently updated. This motivates introduction of a mechanism serving to avoid changes in the set of NTN neighbor cells triggering SI change notifications to be sent (and updates of the valueTag associated with SIB19). Such changes include primarily changes of which list items the NTN-NeighCellConfigList-r17 and ntn-NeighCellConfigListExt- v1720 IEs contain, i.e. additions and removals of list items, but also changes of any of the carrierFreq-r17 and physCellId-r17 fields within a list item (and the most dynamic fields of the ntn-Config-r17 are already exempt from the regular SI change notification and valueTag update mechanisms as per 3GPP TS 38.331 version 17.3.0). According to certain embodiments, a mechanism serving to avoid that the above-mentioned changes trigger SI change notifications to be sent (and updates of the valueTag associated with SIB19) could be, for example, one of the following: - One alternative could be to exclude changes of the ntn- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs in SIB19 from the SI changes that trigger SI change notifications and SIB19 valueTag update, and introduce an additional field in SIB19, indicating when the next update of the set of neighbor NTN cells included in the ntn-NeighCellConfigList-r17 and ntn- NeighCellConfigListExt-v1720 IEs will occur, e.g. denoted as nextUpdateOfSetOfNeighbourCells-xx. This new field could be an INTEGER indicating a UTC value or a number of seconds. The field may be optional and present only in TN cells. UEs which are interested in the ntn-NeighCellConfigList-r17 and ntn-NeighCellConfigListExt- v1720 IEs in SIB19 would then have the information they need to know when reacquisition of SIB19 is needed. o The relevant changes of the ntn-NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs in SIB19 that should not trigger SI change notifications and SIB19 valueTag update may be changes in the set of of which list items the NTN- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt- v1720 IEs contain, i.e. additions and removals of list items, and changes of the fields within a list item. - Another alternative could be to introduce a new indicator in the Short Message DCI that notifies UEs of SI changes, where the new indication would inform the UE that the SI change concerns an update of the ntn-NeighCellConfigList-r17 IE or the ntn- NeighCellConfigListExt-v1720 IE in SIB19. The execution of the update would not be restricted to a SI modification period border. Upon receiving a SI update notification with this indication, a UE that is interested in the ntn-NeighCellConfigList-r17 and ntn- NeighCellConfigListExt-v1720 IEs in SIB19 would reacquire the updated SIB19, while a UE that is not interested in the ntn- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs in SIB19 would ignore the SI change notification. o More specifically, the indicator in the Short Message DCI could refer specifically to changes in the set of which list items the NTN-NeighCellConfigList-r17 IE and/or ntn- NeighCellConfigListExt-v1720 IE contain (i.e., additions and removals of list items) and changes of the fields within a list item. - Yet another alternative could be to exclude changes of the ntn- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs in SIB19 from the SI changes that trigger SI change notification and SIB19 valueTag update, but not introduce any new parameter in SIB19. It could then be left to UE implementation to ensure that the UE uses valid neighbor NTN cell information, or accept that UEs sometimes will use neighbor NTN cell information which is partly outdated, e.g. a partly outdated set of NTN neighbor cells. o The relevant changes of the ntn-NeighCellConfigList-r17 and ntn-NeighCellConfigListExt-v1720 IEs in SIB19 that should not trigger SI change notifications and SIB19 valueTag update may be changes in the set of of which list items the NTN- NeighCellConfigList-r17 and ntn-NeighCellConfigListExt- v1720 IEs contain, i.e. additions and removals of list items, and changes of the fields within a list item. UE Actions In a particular embodiment (targeting UEs in RRC_CONNECTED state), the essential or relevant parts of SIB19 (in NR) or SIB31 (in LTE) are given to the UE in the measurement object (i.e., the MeasObjectNR IE in NR or the MeasObjectEUTRA IE in LTE) together with a list of PCIs. In an alternative, only an indication, e.g., satellite ID, is added to Measurement Object to assist the UE to identify the required satellite assistance information for the target NTN cell, which the UE obtains by other means such as, for example, reading SI or through dedicated Radio Resource Control (RRC) signaling. In another particular embodiment, the essential or relevant parts of SIB19 (in NR) or SIB31 (in LTE) are provided to UEs in RRC_CONNECTED mode via dedicated RRC signaling. For instance, as part of the RRCReconfiguration message including ReconfigurationWithSync that triggers handover execution and the parameter dedicatedSystemInformationDelivery. In another embodiment, a UE determines one of a plurality of states of the UE with respect to one or more than one of satellite assistance information and adaptively adjusts, updates, or changes one or more operations or aspects related to one or more of the following procedures on TN serving cell or NTN neighbor cell: ^ cell change procedure (e.g., cell reselection, cell selection, RRC connection re-establishment, etc.); ^ measurement procedure (e.g., measurement rate, number, periodicity, duration, total number of carriers/frequencies/cells/satellites to be measured, etc.) and/or ^ channel monitoring or reception procedure (e.g., paging reception, system information reception, etc.). UE may perform one or more of procedures on intra-frequency if no valid NTN assistance information is sent by serving TN cell and received by the UE, but requirements corresponding to the procedures can be relaxed. One example of the embodiment is that UE shall perform one or more of procedures provided valid NTN assistance information sent by serving TN cell is received by the UE only when RSRP/RSRQ received in TN serving cell is higher than a threshold (TH_P1). Another example of the embodiment is that UE shall perform one or more of procedures provided UE doesn’t receive valid NTN assistance information sent by serving TN cell and RSRP/RSRQ received in TN serving cell is lower than a threshold (TH_P2), but requirements corresponding to the procedures can be relaxed. Another example of the embodiment is that UE shall perform one or more of procedures provided the time interval from the time instance when UE receives last NTN assistance information and starts procedures is less than a threshold (T_delta ) and RSRP/RSRQ received in TN serving cell is lower than a threshold (TH_P3), but requirements corresponding to the procedures can be relaxed. In another embodiments, UE operated in serving TN cell does not need to read the SI containing NTN assistance information always. In other words, UE operated in serving TN cell shall read the SI containing NTN assistance information upon fulfilling some conditions such as, for example, a distance between UE position and TN cell boundary is shorter than a threshold (TH_D1) provided TN cell boundary information is known by the UE. FIGURE 3 illustrates a wireless network 100 in accordance with some embodiments. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIGURE 3. For simplicity, the wireless network 100 of FIGURE 3 only depicts network 106, network nodes 160 and 160b, and wireless devices (WDs) 110. In practice, a wireless network 100 may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 160 and WD 110 are depicted with additional detail. The wireless network 100 may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network 100. The wireless network 100 may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network 100 may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network 100 may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards. Network 106 may comprise one or more backhaul networks, core networks, Internet Protocol (IP) networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices. Network node 160 and WD 110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network 100. In different embodiments, the wireless network 100 may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. FIGURE 4 illustrates an example network node 160, according to certain embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network. In FIGURE 4, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Network node 160 may be an NTN network node. Although network node 160 illustrated in the example wireless network of FIGURE 4 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules). Similarly, network node 160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160. Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality. For example, processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC). In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160, but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally. Device readable medium 180 may comprise any form of volatile or non- volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170. Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160. Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 may be considered to be integrated. Interface 190 is used in the wired or wireless communication of signalling and/or data between network node 160, network 106, and/or WDs 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components. In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 may be considered a part of interface 190. In still other embodiments, interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown). Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port. Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment. Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160. For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further example, power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used. Alternative embodiments of network node 160 may include additional components beyond those shown in FIGURE 4 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160. FIGURE 5 illustrates an example WD 110, according to certain embodiments. As used herein, WD refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with UE. Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc.. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to- everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal. As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137. WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 110. Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from WD 110 and be connectable to WD 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface. As illustrated, interface 114 comprises radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116. Radio front end circuitry 114 is connected to antenna 111 and processing circuitry 120, and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 may be coupled to or a part of antenna 111. In some embodiments, WD 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered a part of interface 114. Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components. Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 110 components, such as device readable medium 130, WD 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein. As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 120 of WD 110 may comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 122 may be a part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120. In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of WD 110, but are enjoyed by WD 110 as a whole, and/or by end users and the wireless network generally. Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120. Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120. In some embodiments, processing circuitry 120 and device readable medium 130 may be considered to be integrated. User interface equipment 132 may provide components that allow for a human user to interact with WD 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to WD 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in WD 110. For example, if WD 110 is a smart phone, the interaction may be via a touch screen; if WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into WD 110, and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from WD 110, and to allow processing circuitry 120 to output information from WD 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, WD 110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein. Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario. Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 110 which need power from power source 136 to carry out any functionality described or indicated herein. Power circuitry 137 may in certain embodiments comprise power management circuitry. Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of WD 110 to which power is supplied. IGURE 6 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 200, as illustrated in FIGURE 6, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although FIGURE 6 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa. In FIGURE 6, UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 233, and/or any other component, or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may utilize all of the components shown in FIGURE 6, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. In FIGURE 6, processing circuitry 201 may be configured to process computer instructions and data. Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware- implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general- purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer. In the depicted embodiment, input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 200 may be configured to use an output device via input/output interface 205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor. In FIGURE 6, RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 211 may be configured to provide a communication interface to network 243a. Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243a may comprise a Wi-Fi network. Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately. RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non- volatile memory. Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems. Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium. In FIGURE 6, processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231. Network 243a and network 243b may be the same network or networks or different network or networks. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately. In the illustrated embodiment, the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200. The features, benefits and/or functions described herein may be implemented in one of the components of UE 200 or partitioned across multiple components of UE 200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Further, processing circuitry 201 may be configured to communicate with any of such components over bus 202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware. FIGURE 7 depicts a wireless network 1000 comprising different devices connected, either directly or indirectly, to the wireless network 1000 through one or more access network nodes, such as gNBs 1060a and 1060b. In particular, the wireless network 1000 includes access network nodes such as gNBs 1060a and 1060b, UE 1010a, hub 1010b, remote devices 1015a and 1015b and server 1009. UE 1010a and hub 1010b may be any of a wide variety of devices capable of communicating wirelessly with gNBs 1060’s. Although hub 1010b is referred to as a hub, it may also be considered a UE (with hub functionality) because it is able to communicate wirelessly with gNB 1060b using a standard protocol, for example a wireless standard such as one provided by 3GPP. In fact, each of the devices illustrated in FIGURE 7 represent a wide variety of different devices that can be used in different scenarios as discussed in more detail below. Any of these devices which are able to communicate wirelessly with a gNB, eNB or any other similar 3GPP access node may be considered a wireless device or UE. Looking now at some of the possibilities, UE 1010a may be any of a variety of different devices that are able to wirelessly communicate with gNB 1060a. Some examples, which are listed in FIGURE 7, include a virtual reality (VR) headset, a sensor, an actuator, a monitoring device, a vehicle, or a remote controller. These examples are not exhaustive and include therein a wide variety of more specific devices, including a wide range of Internet of Things (IoT) devices. For example, in embodiments where UE 1010a is a VR headset, UE 1010a may be a cell phone that is used with a head mount or it may be a standalone or dedicated VR headset. In some embodiments UE 1010a may be an augmented reality (AR) headset. As an AR or VR headset UE 1010a may be used for entertainment (e.g., gaming, videos, etc.), education/business (e.g., remote conferences, virtual lectures, etc.), medical (e.g., remote diagnostic, patient consultation, etc.), or any other use in which virtual or augmented content may be provided to a remote user. In any of these cases UE 1010a may be receiving content via wireless connection 1070a with gNB 1060a. As another example, in embodiments where UE 1010a is a sensor or monitoring device, UE 1010a may be a motion, gravitational, moisture, temperature, biometric, speed, door/window open, smoke, fire, volume, flow, or any other type of device that is able to detect or measure one or more conditions. As a sensor UE 1010a may also be able to capture conditions. For example, UE 1010a may capture images if it comprises a camera or sound if it comprises a microphone. Regardless of the type of sensor, UE 1010a may provide an output via wireless connection 1070a to gNB 1060a. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). As another example, in embodiments where UE 1010a is an actuator, UE 1010a may be a motor, switch, or any other device that may change states in response to receiving an input via wireless connection 1070a. For example, UE 1000a may be a vibrator that creates vibration to provide a user with haptic feedback. As another example UE 1000a may be a small motor that adjusts the control surfaces of a drone in flight or to a robotic arm performing a medical procedure. As another example, UE 1000a may be a switch that remotely turns on another device, such as a light. As another example, in embodiments where UE 1010a is a vehicle, UE 1010a may be a drone, car, plane, ship, train, tractor, robot, or any other type of device comprising one or more sensors and/or actuators that may change its locations whether autonomously or at the direction of a user. In such embodiments where UE 1010a is a remotely controlled vehicle, such as a drone, it may receive instructions on movement, actuating, or sensing from a user via wireless connection 1070a and provide location, sensor or video information back to the user via wireless connection 1070a. In such embodiments where UE 1010a is an autonomous vehicle it may receive alerts and other messages from other vehicles and/or infrastructure sensors via wireless connection 1070a as well provide its own telemetry data to others via wireless connection 1070a. As another example, in embodiments where UE 1010a is a remote control, UE 1010a may be a device dedicated to controlling other devices or a general purpose computer with a program or application that provides control of other devices. UE 1010a may send commands to a remote device via wireless connection 1070a. UE 1010a may also receive feedback, telemetry, or other information from the remote device via wireless connection 1070a. UE 1010a may present this received information to a user who may then issue commands for the remote device. For example, UE 1010a may receive via wireless connection 1070a a video signal from a remote surgical room and then issue commands via wireless connection 1070a to a remote surgical machine that can execute the commands. While only a single UE 1010a is illustrated in FIGURE 7, in practice any number of UEs may be used together with respect to a single use case. For example, a first UE 1010a may be a speed sensor used in a drone which provides the drone’s speed information to a second UE 1010a that is a remote control operating the drone. When the user makes changes from the remote control, a third UE 1010a that is an actuator may adjust a throttle on the drone to increase or decrease the speed. Similarly, in the example above, the first (sensor) and third (actuator) UE 1010a’s may be a single UE that handles communication for both the speed sensor and the actuators or UE QQA 110a may comprise one or more of the above. Similarly, in the example above, a hub, such as hub 1010b, may be used to handle communication between the sensors and actuators and the controller. Hub 1010b may be any of a variety of different devices that provides wireless access to gNB 1060b for one or more remote devices 1015a. Some examples of different types of hubs are listed in Figure QAA and include a controller, router, content source and analytics. Hub 1010b may include memory to store data (e.g., video, audio, images, buffer, sensor data, file share) that is collected from, or is to be provided to, remote device 1015a. Hub 1010b hub may include a processor, operating system, and server functionality. Hub 1010b may include components for wireless communication to enable wireless connection 1071 to remote device 1015a and/or components for a fixed connection to remote device 1015b. Hub 1010b may also include routing capabilities, firewall capabilities, a VPN-server or VPN-client. Hub 1010b may also allow for a different communication scheme and/or schedule between hub 1010b and remote devices 1015 and between hub 1010b and network 1006. As one example, hub 1010b may be a broadband router enabling direct or indirect access to network 1006 for remote device 1015a. In certain embodiments, hub 1010b may facilitate communication between remote devices 1015a and 1015b. This may be done with, or without, the communications passing through network 1006. In some embodiments, hub 1010b may simply forward the data from remote device 1015a or 1015b to network 1006. In some embodiments, hub 1010b may first filter, buffer, store, analyze or collate the data from remote device 1015a or 1015b before sending on the data to network 1006 or another remote device. Similarly, the data from network 1006 may pass directly through hub 1010b or it may first be processed by hub 1010b on the way to remote device 1015a or 1015b. As another example, hub 1010b may be a controller that sends commands or instructions to one or more actuators in remote device 1015a. The commands or instructions may be received from a second remote device 1015b, from gNB 1060b or by executable code, script or process instructions in hub 1010b. As another example, hub 1010b may be a collection place for data from one or more remote devices 1015a and/or 1015b. For example, remote devices 1015a and/or 1015b may be a sensor, a camera, measurement equipment, or any other type of device discussed herein that may provide output or receive input. Hub 1010b may act as a temporary storage for data from, for example remote device 1015b and, in some embodiments, may perform analysis, or other processing on the data. Hub 1010b may have a constant/persistent or intermittent connection to gNB 1060b. As another example, hub 1010b may be a content source. For example, when remote device 1015a is a VR headset, display, loudspeaker or other media delivery device, hub 1010b may retrieve VR assets, video, audio, or other media via gNB 1060b which it then provides to remote device 1015a either directly, after some local processing, and/or after adding additional local content. Remote device 1015a may be any of a variety of different devices, for example, remote device 1015a may be a device comprising one or more of sensors, actuators, and/or a screen. Remote device 1015a may alternatively be a VR (or AR) headset, a Machine-2-Machine (M2M) device, an IoT device, an internet of Everything (IoE) device, or any other type of device which is capable of accessing a communication network wirelessly via a hub or a device capable of acting as a hub, which in the present context comprise providing network access to a device which is not able to communicate directly with communication network 1006 via gNB 1060a or 1060b. In some scenarios, remote device 1015a may be able to establish a wireless connection with gNB 1060a or 1060b yet nonetheless still connects via hub QQA 110b. Remote device 1015b may be similar to remote device 1015a in most respects except that it has a wired connection to hub 1010b rather than a wireless connection, such as wireless connection 1071. gNBs 1060a and 1060b may provide various wireless devices such as UE 1010a and hub 1010b with wireless access to network 1006. Network 1006 may connect the various devices illustrated in FIGURE 7 including server 1009 which may host a variety of applications such as live and pre-recorded content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of remote devices 1015a, 1015b or UE 1010a, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function done by a server. For example, factory status information may be collected and analyzed by server 1009. As another example, server 1009 may process audio and video data which may have been retrieved from UE 1010a for use in creating maps. As another example, server 1009 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, server 1009 may store surveillance video uploaded by remote device 1015b via hub 1010b. As another example, server 1009 may store media content such as video, audio, VR, or AR which it can broadcast, multicast or unicast to remote devices such as UE 1010a or remote device 1015a. As other examples, server 1009 may be used for energy pricing, for remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data. FIGURE 8 illustrates a method 1200 by a UE 110 for receiving satellite assistance information from a TN, according to certain embodiments. In the illustrated embodiment, the method includes a receiving step at 1202. For example, at step 1202, the UE 110 may receive satellite assistance information from a network node 112 associated with the TN. The satellite assistance information is associated with a satellite of an NTN. FIGURE 9 illustrates another method 1300 by a UE 110 for receiving satellite assistance information from a TN, according to certain embodiments. As illustrated, the method includes the UE receiving satellite assistance information from a network node 112 serving the UE 110 in a cell associated with the TN, at 1302. The satellite assistance information is associated with a satellite that is a candidate for serving the UE 110 in a cell associated with an NTN. The satellite assistance information is received via broadcast. In a particular embodiment, the satellite assistance information comprises essential system information for NTN. In a particular embodiment, the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the NTN payload ephemeris; at least one Synchronization Signal Block Measurement Timing Configuration, SMTC; downlink and/or uplink polarization information; a stop time associated with the cell associated with the TN; reference location for a fixed and/or moving cell; feeder link delay for SMTC adjustment of the cell associated with the NTN; Kmac; K_offset; and validity time information for the NTN payload ephemeris, the epoch time, and/or at least one Common Timing Advance parameter. In a particular embodiment, the UE 110 uses the satellite assistance information to locate a beam associated with the satellite that is the candidate for serving the UE 110 in the cell associated with the NTN. Additionally or alternatively, the UE 110 uses the satellite assistance information to adjust an SMTC associated with the satellite that is the candidate for serving the UE in the cell associated with the NTN. Additionally or alternatively, the UE 110 uses the satellite assistance information to adjust a directional antenna and/or synchronizes with the satellite that is the candidate for serving the UE in the cell associated with the NTN. In a particular embodiment, the satellite assistance information comprises or is comprised in a measurement reporting configuration configuring the UE 110 to perform at least one measurement. In a further particular embodiment, the measurement reporting configuration applies to the satellite when the satellite is located at a height within a range. In a further particular embodiment, the satellite comprises an aerial UE. In a further particular embodiment, the measurement reporting configuration applies to the UE when at a height within a range. In a particular embodiment, the satellite assistance information is received in a SIB19 message, a SIB31 message, or other SIB. In a particular embodiment, the UE 110 receives at least one PCI or at least one carrier frequency associated with the satellite assistance information. In a particular embodiment, the satellite assistance information is associated with and/or received with a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies. In a particular embodiment, based on the satellite assistance information, the UE 110 adjusts, updates, and/or changes one or more operations or parameters related to one or more of procedures, and the one or more procedures comprises at least one of: a cell change procedure; a measurement procedure; and/or a channel monitoring and/or reception procedure. FIGURE 10 illustrates an example method 1400 by a network node 112 associated with a TN for for providing satellite assistance information for a satellite of a NTN, according to certain embodiments. In the illustrated embodiment, the method includes a transmitting step at 1302. For example, at step 1302, the network node 112 transmit, to a UE 110, the satellite assistance information associated with the NTN. FIGURE 11 illustrates another example method 1500 by a network node associated with a TN for providing satellite assistance information for a satellite of a NTN, according to certain embodiments. In the illustrated example embodiment, the method includes the network node transmitting, to a UE, the satellite assistance information associated with a satellite that is a candidate for serving the UE in a cell associated with the NTN, at step 1502. The network node is serving the UE in a cell associated with the TN. The satellite information is transmitted via broadcast. In a particular embodiment, the satellite assistance information comprises essential system information for NTN. In a particular embodiment, the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the NTN payload ephemeris; at least one Synchronization Signal Block Measurement Timing Configuration; downlink and/or uplink polarization information; a stop time associated with the cell associated with the TN; reference location for a fixed and/or moving cell; feeder link delay for SMTC adjustment of the cell associated with the NTN; Kmac; K_offset; and validity time information for the NTN payload ephemeris information, the epoch time, and/or at least one Common Timing Advance parameter. In a particular embodiment, the satellite assistance information comprises or is comprised in a measurement reporting configuration configuring the UE to perform at least one measurement. In a further particular embodiment, the measurement reporting configuration applies to the satellite when the satellite is located at a height within a range. In a further particular embodiment, the satellite comprises an aerial UE. In a further particular embodiment, the measurement reporting configuration applies to the UE when at a height within a range. In a particular embodiment, the satellite assistance information is transmitted in a SIB19 message, a SIB31 message, or another SIB. In a particular embodiment, the network node 112 transmits at least one PCI or at least one carrier frequency associated with the satellite assistance information. In a particular embodiment, the satellite assistance information is associated with and/or transmitted with a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies. Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure. As used herein, the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein. EXAMPLE EMBODIMENTS Group A Example Embodiments Example Embodiment A1. A method by a user equipment (UE) for receiving satellite assistance information from a Terrestrial Network (TN), the method comprising: any of the user equipment steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. Example Embodiment A2. The method of the previous embodiment, further comprising one or more additional user equipment steps, features or functions described above. Example Embodiment A3. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the network node. Group B Example Embodiments Example Embodiment B1. A method performed by a network node associated with a Terrestrial Network (TN) for providing satellite assistance information for a satellite of a Non-Terrestrial Network (NTN), the method comprising: any of the network node steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. Example Embodiment B2. The method of the previous embodiment, further comprising one or more additional network node steps, features or functions described above. Example Embodiment B3. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. Group C Example Embodiments Example Embodiment C1. A method by a user equipment (UE) for receiving satellite assistance information from a Terrestrial Network (TN), the method comprising: receiving satellite assistance information from a network node associated with the TN, the satellite assistance information being associated with a satellite of a Non-Terrestrial Network (NTN). Example Embodiment C2. The method of Example Embodiment C1, wherein the satellite assistance information comprises essential system information. Example Embodiment C3. The method of any one of Example Embodiments C1 to C2, wherein the satellite assistance information comprises ephemeris data. Example Embodiment C4. The method of any one of Example Embodiments C1 to C3, wherein the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the ephemeris; at least one SMTC; DL and UL polarization information; serving cell stop time; reference location for NGSO fixed and/or moving cell; feeder link delay for neighbor cell SMTC adjustment; TA; Kmac; K_offset; validity time information for ephemeris information, epoch time, and/or Common TA parameters. Example Embodiment C5. The method of any one of Example Embodiments C1 to C4, comprising at least one of: using the satellite assistance information to locate a beam associated with the satellite; using the satellite assistance information to adjust an SMTC associated with the satellite; using the satellite assistance information to adjust a directional antenna; and synchronizing with the satellite. Example Embodiment C6. The method of any one of Example Embodiments C1 to C4, wherein the network node is serving the UE in a cell of the TN, and wherein the satellite is a candidate for serving the UE in a cell of the NTN, and wherein the method comprises: using the satellite assistance information to locate a beam associated with the cell of the NTN; using the satellite assistance information to adjust an SMTC associated with the cell of the NTN; using the satellite assistance information to adjust a directional antenna; and synchronizing with the cell of the NTN. Example Embodiment C7. The method of any one of Example Embodiments C1 to C6, wherein the satellite assistance information comprises or is comprised in a measurement reporting configuration configuring the UE to perform at least one measurement. Example Embodiment C8. The method of Example Embodiment C7, wherein the measurement reporting configuration applies to the satellite when the satellite is located at a height within a range. Example Embodiment C9. The method of Example Embodiment C8, wherein the satellite comprises an aerial UE. Example Embodiment C10. The method of Example Embodiment C7, wherein the measurement reporting configuration applies to the UE when at a height within a range. Example Embodiment C11. The method of any one of Example Embodiment C1 to C10, wherein the satellite assistance information is received in at least one of a SIB2 message, a SIB3 message, a SIB4 message, a SIB5 message, a SIB19 message, and/or a SIB31 message. Example Embodiment C12. The method of any one of Example Embodiments C1 to C11, wherein the satellite assistance information is included in an information element (IE), the IE comprising at least one of: epochTime-r17, ntn- UlSyncValidityDuration-r17, ta-Common-r17 (in TA-Info-r17), ta-CommonDrift-r17 (in TA-Info-r17), ta-CommonDriftVariant-r17 (in TA-Info-r17), ephemerisInfo-r17, NTN-NeighCellConfigList-r17, NeighCellConfigListExt-v1720, and the NeighCellConfigEnhancedList-r18. Example Embodiment C13. The method of any one of Example Embodiments C1 to C12, comprising receiving at least one PCI or at least one carrier frequency to which the satellite assistance information applies. Example Embodiment C14. The method of Example Embodiment C13, wherein the satellite assistance information and the at least one PCI and/or the at least one carrier frequency are received in one message. Example Embodiment C15. The method of any one of Example Embodiments C1 to C14, wherein the satellite assistance information is associated with a validity time duration, and wherein the validity time duration is greater than 900 seconds. Example Embodiment C16. The method of any one of Example Embodiments C1 to C15, wherein the satellite assistance information is associated with and/or received with a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies. Example Embodiment C17. The method of any one of Example Embodiments C1 to C16, wherein the satellite assistance information is received via a dedicated RRC signaling message. Example Embodiment C18. The method of any one of Example Embodiments C1 to C17, comprising determining one of a plurality of states of the UE with respect to the satellite assistance information and adaptively adjusting, updating, and/or changing one or more operations or parameters related to one or more of procedures, and wherein the one or more procedures comprises at least one of: a cell change procedure (such as, for example, cell reselection, cell selection, RRC connection re- establishment etc.); a measurement procedure (such as, for example, measurement rate, number, periodicity, duration, total number of carriers/frequencies/cells/satellites to be measured etc.); and/or a channel monitoring and/or reception procedure (such as, for example, paging reception, system information reception, etc.). Example Embodiment C19. The method of Example Embodiment C18, comprising performing the one or more of procedures based on the satellite assistance information when RSRP and/or RSRQ received in a serving cell of the TN is higher than a threshold (TH_P1). Example Embodiment C20. The method of Example Embodiment C18, comprising performing the one or more of procedures based on the satellite assistance information when RSRP and/or RSRQ received in a serving cell of the TN is lower than a threshold (TH_P2). Example Embodiment C21. The method of Example Embodiment C18, comprising performing one or more of procedures when a time interval from a time instance when the UE receives the satellite assistance information to when the UE starts a procedure is less than a threshold(T_delta ) and/or RSRP and/or RSRQ received in a serving cell of the TN is lower than a threshold (TH_P3). Example Embodiment C22. The method of any one of Example Embodiments C1 to C21, comprising: determining that at least on condition is fulfilled; and reading and/or using the satellite assistance information based on the at least one condition being fulfilled. Example Embodiment C23. The method of Example Embodiment D22, wherein the at least one condition is fulfilled when a distance between a position of the UE and a boundary of a cell of the TN is less than a threshold(TH_D1). Example Embodiment C24. The method of Example Embodiment D23, wherein the at cell is a serving cell in which the UE is served by the network node of the TN. Example Embodiment C25. The method of any one of Example Embodiments C1 to C24, wherein the satellite assistance information is received when the UE is in an inactive or idle state. Example Embodiment C26. The method of any one of Example Embodiments C1 to C25, wherein the UE is an aerial UE. Example Embodiment C27. The method of Example Embodiments C1 to C26, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node. Example Embodiment C28. A user equipment comprising processing circuitry configured to perform any of the methods of Example Embodiments C1 to C27. Example Embodiment C29. A user equipment configured to perform any of the methods of Example Embodiments C1 to C27. Example Embodiment C30. A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments C1 to C27. Example Embodiment C31. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments C1 to C27. Example Embodiment C32. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments C1 to C27. Example Embodiment C33. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments C1 to C27. Group D Example Embodiments Example Embodiment D1. A method by a network node associated with a Terrestrial Network (TN) for providing satellite assistance information for a satellite of a Non-Terrestrial Network (NTN), the method comprising: transmitting, to a user equipment (UE), the satellite assistance information associated with the NTN. Example Embodiment D2. The method of Example Embodiment D1, wherein the satellite assistance information comprises essential system information. Example Embodiment D3. The method of any one of Example Embodiments D1 to D2, wherein the satellite assistance information comprises ephemeris data. Example Embodiment D4. The method of any one of Example Embodiments D1 to D3, wherein the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the ephemeris; at least one SMTC; DL and UL polarization information; serving cell stop time; reference location for NGSO fixed and/or moving cell; feeder link delay for neighbor cell SMTC adjustment; TA; Kmac; K_offset; validity time information for ephemeris information, epoch time, and/or Common TA parameters. Example Embodiment D5. The method of any one of Example Embodiments D1 to D4, comprising configuring the UE to perform at least one of: using the satellite assistance information to locate a beam associated with the satellite; using the satellite assistance information to adjust an SMTC associated with the satellite; using the satellite assistance information to adjust a directional antenna; and synchronizing with the satellite. Example Embodiment D6. The method of any one of Example Embodiments D1 to D4, wherein the network node is serving the UE in a cell of the TN, and wherein the satellite is a candidate target cell for serving the UE in a cell of the NTN, and wherein the method comprises configuring the UE to perform at least one of: using the satellite assistance information to locate a beam associated with the cell of the NTN; using the satellite assistance information to adjust an SMTC associated with the cell of the NTN; using the satellite assistance information to adjust a directional antenna; and synchronizing with the cell of the NTN. Example Embodiment D7. The method of any one of Example Embodiments D1 to D6, wherein the satellite assistance information comprises or is comprised in a measurement reporting configuration configuring the UE to perform at least one measurement. Example Embodiment D8. The method of Example Embodiment D7, wherein the measurement reporting configuration applies to the satellite when the satellite is located at a height within a range. Example Embodiment D9. The method of Example Embodiment D8, wherein the satellite comprises an aerial UE. Example Embodiment D10. The method of Example Embodiment D7, wherein the measurement reporting configuration applies to the UE when at a height within a range. Example Embodiment D11. The method of any one of Example Embodiment D1 to D10, wherein the satellite assistance information is transmitted in at least one of a SIB2 message, a SIB3 message, a SIB4 message, a SIB5 message, a SIB19 message, and/or a SIB31 message. Example Embodiment D12. The method of any one of Example Embodiments D1 to D11, wherein the satellite assistance information is transmitted in at least one information element (IE), the at least one IE comprising at least one of: epochTime- r17, ntn-UlSyncValidityDuration-r17, ta-Common-r17 (in TA-Info-r17), ta- CommonDrift-r17 (in TA-Info-r17), ta-CommonDriftVariant-r17 (in TA-Info-r17), ephemerisInfo-r17, NTN-NeighCellConfigList-r17, NeighCellConfigListExt-v1720, and the NeighCellConfigEnhancedList-r18. Example Embodiment D13. The method of any one of Example Embodiments D1 to D12, comprising transmitting at least one PCI or at least one carrier frequency to which the satellite assistance information applies. Example Embodiment D14. The method of Example Embodiment D13, wherein the satellite assistance information and the at least one PCI and/or the at least one carrier frequency are transmitted in one message. Example Embodiment D15. The method of any one of Example Embodiments D1 to C14, wherein the satellite assistance information is associated with a validity time duration, and wherein the validity time duration is greater than 900 seconds. Example Embodiment D16. The method of any one of Example Embodiments D1 to D15, wherein the satellite assistance information is associated with and/or transmitted with a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies. Example Embodiment D17. The method of any one of Example Embodiments D1 to D16, wherein the satellite assistance information is transmitted via a dedicated RRC signaling message. Example Embodiment D18. The method of any one of Example Embodiments D1 to D17, comprising configuring the UE to determine one of a plurality of states of the UE with respect to the satellite assistance information and adaptively adjust, update, and/or change one or more operations or parameters related to one or more of procedures, and wherein the one or more procedures comprises at least one of: a cell change procedure (such as, for example, cell reselection, cell selection, RRC connection re-establishment etc.); a measurement procedure (such as, for example, measurement rate, number, periodicity, duration, total number of carriers/frequencies/cells/satellites to be measured etc.); and/or a channel monitoring and/or reception procedure (such as, for example, paging reception, system information reception, etc.). Example Embodiment D19. The method of Example Embodiment D18, comprising configuring the UE to perform the one or more of procedures based on the satellite assistance information when a RSRP and/or RSRQ received in a serving cell of the TN is higher than a threshold (TH_P1). Example Embodiment D20. The method of Example Embodiment D18, comprising configuring the UE to perform the one or more of procedures based on the satellite assistance information when a RSRP and/or RSRQ received in a serving cell of the TN is lower than a threshold (TH_P2). Example Embodiment D21. The method of Example Embodiment D18, comprising configuring the UE to perform the one or more of procedures when a time interval from a time instance when the UE receives the satellite assistance information to when the UE starts a procedure is less than a threshold(T_delta ) and/or a RSRP and/or RSRQ received in a serving cell of the TN is lower than a threshold (TH_P3). Example Embodiment D22. The method of any one of Example Embodiments D1 to D21, comprising configuring the UE to: determine that at least on condition is fulfilled; and read and/or use the satellite assistance information based on the at least one condition being fulfilled. Example Embodiment D23. The method of Example Embodiment D22, wherein the at least one condition is fulfilled when a distance between a position of the UE and a boundary of a cell of the TN is less than a threshold(TH_D1). Example Embodiment D24. The method of Example Embodiment D23, wherein the cell is a serving cell in which the UE is served by the network node of the TN. Example Embodiment D25. The method of any one of Example Embodiments D1 to D24, wherein the satellite assistance information is transmitted when the UE is in an inactive or idle state. Example Embodiment D26. The method of any one of Example Embodiments D1 to D25, wherein the UE is an aerial UE. Example Embodiment D27. The method of any of the previous Example Embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. Example Embodiment D28. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments D1 to D27. Example Embodiment D29. A network node configured to perform any of the methods of Example Embodiments D1 to D27. Example Embodiment D30. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments D1 to D27. Example Embodiment D31. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments D1 to D27. Example Embodiment D32. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments D1 to D27.

Claims

CLAIMS 1. A method (1300) by a user equipment, UE (110), for receiving satellite assistance information from a Terrestrial Network, TN, the method comprising: receiving (1302) satellite assistance information from a network node (112) serving the UE in a cell associated with the TN, the satellite assistance information being associated with a satellite that is a candidate for serving the UE in a cell associated with a Non-Terrestrial Network, NTN, wherein the satellite assistance information is received via broadcast.
2. The method of Claim 1, wherein the satellite assistance information comprises essential system information for NTN.
3. The method of any one of Claims 1 to 2, wherein the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the NTN payload ephemeris; at least one Synchronization Signal Block Measurement Timing Configuration, SMTC; downlink and/or uplink polarization information; a stop time associated with the cell associated with the TN; reference location for a fixed and/or moving cell; feeder link delay for SMTC adjustment of the cell associated with the NTN; Kmac; K_offset; and validity time information for the NTN payload ephemeris, the epoch time, and/or at least one Common Timing Advance parameter.
4. The method of any one of Claims 1 to 3, comprising at least one of: using the satellite assistance information to locate a beam associated with the satellite that is the candidate for serving the UE in the cell associated with the NTN; using the satellite assistance information to adjust an SMTC associated with the satellite that is the candidate for serving the UE in the cell associated with the NTN; using the satellite assistance information to adjust a directional antenna; and synchronizing with the satellite that is the candidate for serving the UE in the cell associated with the NTN.
5. The method of any one of Claims 1 to 4, wherein the satellite assistance information comprises or is comprised in a measurement reporting configuration configuring the UE to perform at least one measurement.
6 The method of Claim 5, wherein the measurement reporting configuration applies to the satellite when the satellite is located at a height within a range.
7. The method of Claim 6, wherein the satellite comprises an aerial UE.
8. The method of Claim 5, wherein the measurement reporting configuration applies to the UE when at a height within a range.
9. The method of any one of Claim 1 to 8, wherein the satellite assistance information is received in a SIB19 message, a SIB31 message, or other System Information Block.
10. The method of any one of Claims 1 to 9, comprising receiving at least one Physical Cell Indicator, PCI, or at least one carrier frequency associated with the satellite assistance information.
11. The method of any one of Claims 1 to 10, wherein the satellite assistance information is associated with and/or received with a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies.
12. The method of any one of Claims 1 to 11, comprising: based on the satellite assistance information, adjusting, updating, and/or changing one or more operations or parameters related to one or more of procedures, and wherein the one or more procedures comprises at least one of: a cell change procedure; a measurement procedure; and/or a channel monitoring and/or reception procedure.
13. A method (1500) by a network node (112) associated with a Terrestrial Network, TN, for providing satellite assistance information for a satellite of a Non- Terrestrial Network, NTN, the method comprising: transmitting (1502), to a user equipment, UE (110), the satellite assistance information associated with a satellite that is a candidate for serving the UE in a cell associated with the NTN, wherein the network node is serving the UE in a cell associated with the TN, and wherein the satellite information is transmitted via broadcast.
14. The method of Claim 13, wherein the satellite assistance information comprises essential system information for NTN.
15. The method of any one of Claims 13 to 14, wherein the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the NTN payload ephemeris; at least one Synchronization Signal Block Measurement Timing Configuration; downlink and/or uplink polarization information; a stop time associated with the cell associated with the TN; reference location for a fixed and/or moving cell; feeder link delay for SMTC adjustment of the cell associated with the NTN; Kmac; K_offset; and validity time information for the NTN payload ephemeris information, the epoch time, and/or at least one Common Timing Advance parameter.
16. The method of any one of Claims 13 to 15, wherein the satellite assistance information comprises or is comprised in a measurement reporting configuration configuring the UE to perform at least one measurement.
17. The method of Claim 16, wherein the measurement reporting configuration applies to the satellite when the satellite is located at a height within a range.
18. The method of Claim 17, wherein the satellite comprises an aerial UE.
19. The method of Claim 16, wherein the measurement reporting configuration applies to the UE when at a height within a range.
20. The method of any one of Claim 13 to 19, wherein the satellite assistance information is transmitted in a SIB19 message, a SIB31 message, or another System Information Block.
21. The method of any one of Claims 13 to 20, comprising transmitting at least one Physical Cell Indicator, PCI, or at least one carrier frequency associated with the satellite assistance information.
22. The method of any one of Claims 13 to 21, wherein the satellite assistance information is associated with and/or transmitted with a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies.
23. A user equipment, UE (110), for receiving satellite assistance information from a Terrestrial Network, TN, the UE configured to: receive satellite assistance information from a network node (112) serving the UE in a cell associated with the TN, the satellite assistance information being associated with a satellite that is a candidate for serving the UE in a cell associated with a Non-Terrestrial Network, NTN, wherein the satellite assistance information is received via broadcast.
24. The UE of Claim 23, wherein the satellite assistance information comprises essential system information for NTN.
25. The UE of any one of Claims 23 to 24, wherein the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the NTN payload ephemeris; at least one Synchronization Signal Block Measurement Timing Configuration, SMTC; downlink and/or uplink polarization information; a stop time associated with the cell associated with the TN; reference location for a fixed and/or moving cell; feeder link delay for SMTC adjustment of the cell associated with the NTN; Kmac; K_offset; and validity time information for the NTN payload ephemeris, the epoch time, and/or at least one Common Timing Advance parameter.
26. The UE of any one of Claims 23 to 25, configured to perform at least one of: using the satellite assistance information to locate a beam associated with the satellite that is the candidate for serving the UE in the cell associated with the NTN; using the satellite assistance information to adjust an SMTC associated with the satellite that is the candidate for serving the UE in the cell associated with the NTN; using the satellite assistance information to adjust a directional antenna; and synchronizing with the satellite that is the candidate for serving the UE in the cell associated with the NTN.
27. The UE of any one of Claim 23 to 26, wherein the satellite assistance information is received in at least one System Information Block, SIB.
28. The UE of any one of Claims 23 to 27, configured to receive at least one Physical Cell Indicator, PCI, or at least one carrier frequency associated with the satellite assistance information.
29. The UE of any one of Claims 23 to 28, wherein the satellite assistance information is associated with and/or received with a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies.
30. The UE of any one of Claims 23 to 29, wherein the UE is configured to adjust, update, and/or change one or more operations or parameters related to one or more procedures based on the satellite assistance information, and wherein the one or more procedures comprises at least one of: a cell change procedure; a measurement procedure; and/or a channel monitoring and/or reception procedure.
31. A network node (112) associated with a Terrestrial Network, TN, for providing satellite assistance information for a satellite of a Non-Terrestrial Network, NTN, the network node configured to: transmit, to a user equipment, UE (110), the satellite assistance information associated with a satellite that is a candidate for serving the UE in a cell associated with the NTN, wherein the network node is serving the UE in a cell associated with the TN, and wherein the satellite information is transmitted via broadcast.
32. The network node of Claim 31, wherein the satellite assistance information comprises essential system information for NTN.
33. The network node of any one of Claims 31 to 32, wherein the satellite assistance information comprises at least one of: NTN payload ephemeris; epoch time of the NTN payload ephemeris; at least one Synchronization Signal Block Measurement Timing Configuration,; downlink and/or uplink polarization information; a stop time associated with the cell associated with the TN; reference location for a fixed and/or moving cell; feeder link delay for SMTC adjustment of the cell associated with the NTN; Kmac; K_offset; and validity time information for the NTN payload ephemeris information, the epoch time, and/or at least one Common Timing Advance parameter.
34. The network node of any one of Claims 31 to 33, wherein the satellite assistance information comprises or is comprised in a measurement reporting configuration configuring the UE to perform at least one measurement.
35. The network node of Claim 34, wherein the measurement reporting configuration applies to the satellite when the satellite is located at a height within a range.
36. The network node of Claim 35, wherein the satellite comprises an aerial UE.
37. The method of Claim 35, wherein the measurement reporting configuration applies to the UE when at a height within a range.
38. The network node of any one of Claim 31 to 37, wherein the satellite assistance information is transmitted in at least one System Information Block, SIB.
39. The network node of any one of Claims 31 to 38, configured to transmit at least one Physical Cell Indicator, PCI, or at least one carrier frequency associated with the satellite assistance information.
40. The network node of any one of Claims 31 to 39, wherein the satellite assistance information is associated with and/or transmitted with a satellite identifier that identifies the satellite of the NTN to which the satellite assistance information applies.
EP24706208.6A 2023-02-14 2024-02-13 Satellite assistance information provisioning from a terresterial network Pending EP4666444A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363445605P 2023-02-14 2023-02-14
PCT/IB2024/051327 WO2024171051A1 (en) 2023-02-14 2024-02-13 Satellite assistance information provisioning from a terresterial network

Publications (1)

Publication Number Publication Date
EP4666444A1 true EP4666444A1 (en) 2025-12-24

Family

ID=89983251

Family Applications (1)

Application Number Title Priority Date Filing Date
EP24706208.6A Pending EP4666444A1 (en) 2023-02-14 2024-02-13 Satellite assistance information provisioning from a terresterial network

Country Status (4)

Country Link
EP (1) EP4666444A1 (en)
CN (1) CN120712735A (en)
AU (1) AU2024223468A1 (en)
WO (1) WO2024171051A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4730892A1 (en) * 2023-06-19 2026-04-22 Quectel Wireless Solutions Co., Ltd. Communication method, terminal device, and network device
WO2025064895A1 (en) * 2023-09-22 2025-03-27 Google Llc Non-terrestrial network (ntn) cell measurement
WO2026076428A1 (en) * 2024-10-03 2026-04-09 Google Llc Managing non-terrestrial network access
WO2025171733A1 (en) * 2024-11-08 2025-08-21 Lenovo (Beijing) Limited Sensing service

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12075344B2 (en) * 2019-05-15 2024-08-27 Sony Group Corporation Radio communication device, radio communication method, and radio communication system
KR20220100010A (en) * 2019-11-13 2022-07-14 지티이 코포레이션 Wireless communication method for handling mobility
US11909502B2 (en) * 2021-05-05 2024-02-20 Qualcomm Incorporated Timing configuration management for network entities

Also Published As

Publication number Publication date
AU2024223468A1 (en) 2025-06-12
CN120712735A (en) 2025-09-26
WO2024171051A1 (en) 2024-08-22

Similar Documents

Publication Publication Date Title
US20250097811A1 (en) Systems and methods for reducing system information acquisition during cell reselection in a non-terrestrial network
US20220248286A1 (en) Minimizing signaling load during handover for ntn
US20230284060A1 (en) Synchronization signal block measurement timing configuration window and measurement gap configuration for non-terrestrial networks
EP4233354B1 (en) Methods and systems for rrm measurement relaxation for stationary-mobility devices
WO2024171051A1 (en) Satellite assistance information provisioning from a terresterial network
US20250142505A1 (en) Method and Apparatus for SSB Measurement Time Configuration in Communication Network
US20250106811A1 (en) Location information provisioning
US20260086247A1 (en) Methods and systems for signalling ephemeris data in a non-terrestrial network
JP7733129B2 (en) Detecting Radio Link Failures in IoT NTNs
US20250159654A1 (en) Paging and system information (si) procedures under adjusted synchronization signal block measurement time configuration (smtc) in non-terrestrial networks (ntn)
US20250063524A1 (en) Measurement reporting for propagation delay compensation
US20260046766A1 (en) Group Signaling for Network Energy Savings
EP4427509B1 (en) Measurement time ranges for timing advance (ta) validation for small data transmission (sdt)
WO2024035965A1 (en) Methods for si accumulation in iot ntn with explicit and implicit epoch time indication
EP4612978A1 (en) Discovery signal
WO2022208409A1 (en) Ue-centric location tracking for paging in a wireless communication network
US20260046824A1 (en) Methods for ue-based location integrity reliability determination
WO2025104275A1 (en) Ssb measurement time configuration for cell switching terminal device provided by a movable base station/relay
WO2025202961A1 (en) Time advance configuration in batch for regenerative non-terrestrial network system
WO2025202899A1 (en) Methods, apparatus and computer-readable media related to measurement gaps and/or paging occasions
WO2025210593A1 (en) Indication of store and forward for ntn
WO2025172459A1 (en) Architecture extension for multi-site upf
WO2026074177A1 (en) Service continuity for broadcast services in ntn
WO2025216685A1 (en) Indication of successful handover when some conditions indicate handover failure
WO2025219761A1 (en) Mdt areas scopes for ntn

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20250813

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR