[go: up one dir, main page]

WO2025210593A1 - Indication of store and forward for ntn - Google Patents

Indication of store and forward for ntn

Info

Publication number
WO2025210593A1
WO2025210593A1 PCT/IB2025/053601 IB2025053601W WO2025210593A1 WO 2025210593 A1 WO2025210593 A1 WO 2025210593A1 IB 2025053601 W IB2025053601 W IB 2025053601W WO 2025210593 A1 WO2025210593 A1 WO 2025210593A1
Authority
WO
WIPO (PCT)
Prior art keywords
store
indication
network node
ntn
network
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
PCT/IB2025/053601
Other languages
French (fr)
Inventor
Ignacio Javier PASCUAL PELAYO
Emre YAVUZ
Johan Rune
Talha KHAN
Zhang Zhang
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 WO2025210593A1 publication Critical patent/WO2025210593A1/en
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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
    • H04B7/18519—Operations control, administration or maintenance
    • 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/1853—Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
    • H04B7/18532—Arrangements for managing transmission, i.e. for transporting data or a signalling message
    • H04B7/18534—Arrangements for managing transmission, i.e. for transporting data or a signalling message for enhancing link reliablility, e.g. satellites diversity
    • 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/1853—Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
    • H04B7/18539—Arrangements for managing radio, resources, i.e. for establishing or releasing a connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks

Definitions

  • Embodiments of the present disclosure are directed to wireless communications and, more particularly to signaling an indication of store-and-forward operation for a non-terrestrial network (NTN).
  • NTN non-terrestrial network
  • BACKGROUND [0002] Third Generation Partnership Project (3GPP) fifth generation system (5GS) is a new generation radio access technology intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), narrowband Internet of things (NB-IOT) and massive machine type communication (mMTC).5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low latency communication
  • NB-IOT narrowband Internet of things
  • mMTC massive machine type communication
  • 5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC).
  • the NR physical and higher layers are reusing parts of the Long Term Evolution (LTE) specification, and to that add needed components when motivated by new use cases.
  • LTE Long Term Evolution
  • 3GPP has discussed in the last few years how to specify technologies to cover/address use cases for machine-to- machine (M2M) and/or IoT.
  • Release 13 specified enhancements to support machine-type communications (MTC) and introduced new user equipment (UE) categories M1 (Cat-M1) and NB1 (Cat-NB1) to support reduced maximum bandwidth of up to six physical resource blocks (PRBs) in eMTC work item and narrowband carrier in NB-IoT work item specifying a new radio interface, respectively.
  • MTC machine-type communications
  • UE new user equipment
  • Cat-M1 new user equipment
  • NB1 NB1
  • IoT 3GPP technologies There are multiple differences between “legacy” LTE and the procedures and channels defined for eMTC or NB-IoT. Some important differences include a new physical downlink control channel, i.e., machine physical downlink control channel (MPDCCH) used in eMTC and narrowband physical downlink control channel (NPDCCH) used in NB-IoT.
  • MPDCCH machine physical downlink control channel
  • NPDCCH narrowband physical downlink control channel
  • eMTC 3GPP Release 12 initiated the work on eMTC, also often referred to as LTE-M, and specified the first low-complexity UE category 0 (Cat-0). Cat-0 supports a reduced peak data rate of 1 Mbps, single antenna and half duplex frequency division duplex (HD FDD) operation.
  • LTE-M first low-complexity UE category 0
  • Cat-0 supports a reduced peak data rate of 1 Mbps, single antenna and half duplex frequency division duplex (HD FDD) operation.
  • the P111188WO01 PCT APPLICATION 3 of 68 repetitions may be seen as a third level of retransmissions added at the physical layer as a complement to those at medium access control (MAC) hybrid automatic repeat request (HARQ) and Radio Link Control (RLC) automatic repeat request (ARQ).
  • MAC medium access control
  • HARQ hybrid automatic repeat request
  • RLC Radio Link Control
  • a NB-IoT downlink carrier is defined by twelve orthogonal frequency division multiplexing (OFDM) sub-carriers, each of 15 kHz, giving a total baseband bandwidth of 180 kHz. When multiple carriers are configured, several 180 kHz carriers can be used, e.g., for increasing the system capacity, inter- cell interference coordination, load balancing, etc.
  • OFDM orthogonal frequency division multiplexing
  • NB-IoT supports the following three different deployment scenarios or mode of operations: 1 .
  • ‘Stand-alone operation’ using, for example, the spectrum currently being used by global system for mobile communications (GSM) edge radio access network (GERAN) systems as a replacement of one or more GSM carriers. In principle, it operates on any carrier frequency that is neither within the carrier of another system nor within the guard band of another system’s operating carrier.
  • the other system can be another NB-IoT operation or any other radio access technology (RAT), e.g. LTE. 2 .
  • ‘Guard band operation’ uses the unused resource blocks within an LTE carrier’s guard- band.
  • guard band may also interchangeably be referred to as guard bandwidth.
  • the guard band operation of NB-IoT can place anywhere outside the central 18 MHz but within 20 MHz LTE bandwidth. 3 .
  • ‘In-band operation’ uses resource blocks within a normal LTE carrier.
  • the in-band operation may also interchangeably be referred to as in-bandwidth operation. More generally, the operation of one RAT within the bandwidth of another RAT is also referred to as in-band operation.
  • NTN Non-terrestrial Networks
  • a satellite network or satellite based mobile network may also be referred to as a non- terrestrial network.
  • mobile network with base stations on the ground may be referred to as terrestrial network (TN) or non-NTN network.
  • TN terrestrial network
  • NTN node NTN satellite or simply a satellite.
  • a satellite may be categorized as low earth orbit (LEO), medium earth orbit (MEO), or geostationary earth orbit (GEO) satellite.
  • LEO low earth orbit
  • 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 terrestrial networks.
  • the access and feeder links are often operated in line-of-sight conditions, and the UE is equipped with an antenna offering high beam directivity.
  • P111188WO01 PCT APPLICATION 5 of 68 Architecture Two basic architectures can be distinguished for satellite communication networks, depending on the functionality of the satellites in the system: ⁇ Transparent payload (also referred to as bent pipe architecture). The satellite forwards the received signal between the terminal and the network equipment on the ground with only amplification and a shift from uplink frequency to downlink frequency.
  • the transparent payload architecture means that the gNB is located on the ground and the satellite forwards signals/data between the gNB and the UE.
  • ⁇ Regenerative payload When applied to general 3GPP architecture and terminology, the transparent payload architecture means that the gNB is located on the ground and the satellite forwards signals/data between the gNB and the UE.
  • the satellite includes on-board processing to demodulate and decode the received signal and regenerate the signal before sending it back to the earth.
  • the regenerative payload architecture means that the gNB is located in the satellite.
  • FIGURE 1 shows an example architecture of a satellite network with bent pipe transponders (i.e., the transparent payload architecture).
  • FIGURE 1 illustrates an example architecture of a satellite network with bent pipe transponders.
  • the gNB may be integrated in the gateway or connected to the gateway via a terrestrial connection (wire, optic fiber, wireless link).
  • 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 a 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 2 shows an example architecture of a satellite network with bent pipe transponders. [0024]
  • FIGURE 2 illustrates an example architecture of a satellite network with bent pipe transponders.
  • Discontinuous coverage refers to the situation where the visibility of a satellite or group of satellites, commonly low Earth orbit (LEO), from a certain ground point is limited in time leading to periods without satellite network coverage.
  • LEO low Earth orbit
  • NGSO Non- Geostationary Orbit
  • the rapid movement of NGSO (Non- Geostationary Orbit) satellites around Earth is the cause of this time limitation and its length depends on the characteristics of the satellite constellation (e.g., structure, total number of satellites, number of orbital planes, or satellites per plane) and UE (e.g., minimum elevation angle, or local radio conditions).
  • NGSO Non- Geostationary Orbit
  • the indication that the serving NTN network node is operating or will operate in store and forward mode is associated with a location for store and forward operation. P111188WO01 PCT APPLICATION 13 of 68
  • receiving the system information message comprises receiving a broadcasted system information message comprising the indication or receiving a dedicated system information message comprising the indication.
  • the indication indicates that the serving NTN network node is operating in store and forward mode for all wireless devices that support operation with network nodes operating in store and forward mode.
  • the indication indicates that the serving NTN network node is operating in store and forward mode only for wireless devices in connected mode.
  • the indication or implicit statement makes the UE aware of when the satellite or NTN payload serving the current cell operates with the store and forward mode and thus does not have connectivity towards the NTN ground station or another satellite via ISL.
  • the network and UE may leverage the indication in broadcast or dedicated signaling for the serving or neighbor cells to optimally perform a plurality of procedures ranging from data transactions, power saving operations, mobility procedures, and cell measurements.
  • FIGURE 1 illustrates an example architecture of a satellite network with bent pipe transponders
  • FIGURE 2 illustrates an example architecture of a satellite network with bent pipe transponders
  • FIGURE 3 illustrates an example of the diurnal Doppler shift of the forward service link observed for a GEO satellite operating from an inclined orbit
  • FIGURE 4 illustrates orbital elements
  • FIGURE 5 illustrates store and forward operation for an NTN payload
  • FIGURE 6 illustrates an example communication system, according to certain embodiments
  • FIGURE 7 illustrates an example user equipment (UE), according to certain embodiments
  • FIGURE 8 illustrates an example network node, according to certain embodiments
  • FIGURE 9 illustrates a block diagram of a host, according to certain embodiments
  • FIGURE 10 illustrates a virtualization environment in which functions
  • NTN non-terrestrial network
  • Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges.
  • particular embodiments include an indication, i.e., a field, parameter, or an implicit statement in broadcast or dedicated signaling of the presence of store and forward operation for the serving and/or neighbor frequency, cells, or satellites.
  • NTN may, depending on the context, refer to either or both of New Radio (NR) NTN and Internet-of-things (IoT) NTN, and sometimes the term is used to refer to only IoT NTN.
  • NR New Radio
  • IoT Internet-of-things
  • LTE Long Term Evolution
  • network is used herein to refer to a network node, which typically will be a gNB (e.g., in a NR based NTN) or an eNB (e.g., in an LTE based NTN, such as an IoT NTN), but which may also be a base station or an access point in another type of network based on communication via satellites or high-altitude platforms (HAPS), or any other network node (in a network involving satellites or HAPS) with the ability to directly or indirectly communicate with a user equipment (UE). Refinements with finer granularity are also conceivable.
  • UE user equipment
  • a gNB may be an en-gNB, and if a split gNB architecture is applied (dividing the gNB into multiple separate entities or notes), the term “network” or “network node” or “node” may refer to a part of the gNB, such as a gNB-CU (often referred to as just central unit (CU)), a gNB-DU (often referred to as just distributed unit (DU)), a gNB-CU- control plane (CP) or a gNB-CU-user plane (UP).
  • a gNB-CU often referred to as just central unit (CU)
  • a gNB-DU often referred to as just distributed unit (DU)
  • CP gNB-CU- control plane
  • UP gNB-CU-user plane
  • an eNB may be an ng-eNB, and if a split eNB architecture is applied (dividing the gNB into multiple separate entities or nodes), the term “network” (and the network node it implies) may refer to a part of the eNB, such as an eNB-CU, an eNB-DU, an eNB-CU-CP or an eNB-CU-UP. Furthermore, the term “network” (and the network node it implies) may also refer to an integrated access and backhaul (IAB)- donor, IAB-donor-CU, IAB-donor-DU, IAB-donor-CU-CP, or an IAB-donor-CU-UP.
  • IAB integrated access and backhaul
  • source node target node
  • target node candidate target node
  • the “node” in these terms should be understood as typically being a radio access network (RAN) node in an NTN based on NR technology, LTE technology or any other radio access technology (RAT) in which conditional handover or another conditional mobility concept is defined.
  • RAN radio access network
  • RAT radio access technology
  • an NR based NTN such a RAN node may be assumed to be a gNB.
  • LTE based NTN including an IoT NTN
  • a RAN node may be assumed to be an eNB.
  • Alternatives to, or refinements of, these interpretations are however also conceivable.
  • Parameters/IEs/fields following this naming convention are typically referred to both with and without the suffix, where the name including the suffix is used in the ASN.1 code (and thus defines the formal name from the ASN.1 compiler’s perspective), while the name without the suffix is used in running text, e.g. in field descriptions and procedural text.
  • Relevant examples in the context of this document include the parameters/IEs/fields t1-Threshold-r17/t1-Threshold and t-Service- r17/t-Service. As used herein, both name variants may occur for various parameters/IEs/fields.
  • NTN There are two main deployment principles for NTN: quasi-Earth-fixed cells and Earth- moving cells.
  • the quasi- Earth-fixed cells deployment principle is also referred to as quasi-Earth-fixed beams.
  • the Earth-moving cells deployment principle is also referred to as Earth-moving beams, or shorter, moving cells or and moving beams.
  • a satellite or NTN payload operating in store and forward mode is associated herein with the lack of end-to-end connectivity.
  • a limitation with this association is that it only indicates the current satellite's mode of operation in the NTN radio access network (RAN), while makes no guarantees that the other end of a communication is available without store and forward at that end.
  • store and forward may still be applied to the communication in another part of the network on the path to the remote endpoint, e.g. in another satellite payload or in a network node with intermittent connectivity to a satellite payload.
  • the network provides UEs with an implicit or explicit indication of the present or future existence of a store and forward NTN connectivity.
  • a satellite or NTN payload does not have access to end-to-end connectivity in the feeder link neither via a ground station nor via another satellite (inter-satellite link (ISL)).
  • ISL inter-satellite link
  • a UE is not expected to have end-to- end connectivity with the network, although the RAN and parts of the 4G/5G core network may be available on the NTN payload (i.e., on the satellite) to complete the service link part of the communication.
  • An indication of such a type may be associated with the cell or the satellite and may take several forms.
  • a single bit is used to indicate whether the store and forward operation is used at the moment of transmission.
  • the bit simply indicates the NTN payload (serving or neighbor) supports store and forward without any implications on the current operation mode.
  • a time span either absolute (e.g., coordinated universal time (UTC)) or relative (e.g., seconds, system frame number (SFN), hyper-SFN (H-SFN)) is used to indicate when the store and forward operation is used.
  • the time span indicates when end-to-end connectivity, i.e., feeder link connection through ground station or ISL is available.
  • the time indication may refer to the remaining time with or without end-to-end connectivity, i.e., feeder link connection through ground station or ISL is available.
  • the time span may refer to the current time, i.e. when the indication is sent, or a time span in the near future.
  • the concerned time span may be represented in various ways: ⁇ Only a start time. ⁇ A start time and an end time, where the end time may be signaled through the cell operation service time, i.e., t-Service field parameter. ⁇ A start time and a duration. ⁇ An end time and a duration. ⁇ Only an end time.
  • the time span may use a variety of starting and ending point references, which may be compatible with existing specified field parameters in different system information blocks (SIBs) or included in a new SIB: ⁇ Epoch time ⁇ The start (e.g., starting SFN) of the previous SIB31 transmission (or SIB32 transmission) ⁇ The end of previous SIB31 (or SIB32) transmission as the reference. ⁇ The start of the future SIB31 (or SIB32) transmission. ⁇ The end of the future SIB31 (or SIB32) transmission. ⁇ The start of the current SIB31 (or SIB32) transmission carrying the store and forward parameters as the reference.
  • SIBs system information blocks
  • ⁇ The end of the current SIB31 (or SIB32) transmission carrying the store and forward parameters as the reference ⁇
  • the start of the uplink synchronization validity duration (assuming the NTN-SIB was used to indicate store and forward related parameters) as the reference.
  • a time schedule which is composed of several time spans, is used to indicate when the store and forward operation is used (or when non-store and forward is used).
  • an additional bit is included together with the time schedule to indicate if during that certain period of time the satellite is operating in store and forward mode.
  • a finite number e.g., integer
  • this number may indicate the currently available buffer space in bytes.
  • the indication implicitly signals that the current mode of operation of the NTN payload is the store and forward mode.
  • similar information as described above may also be indicated (provided from the network to a UE) for other satellites than the satellite serving the cell where the indication/information is provided/signaled, e.g., neighbor satellites, or may indicate for other cells than the cell where the indication/information is provided, e.g., neighbor cells.
  • indications/information related to store and forward operation may be indicated for one or more satellite(s) that will P111188WO01 PCT APPLICATION 20 of 68 later cover the same area (i.e., serve cell(s) in the same area) as the satellite presently providing the indication.
  • the indication of store and forward is tied to a tracking area (TA). For example, depending on the geographical locations of the ground stations, the satellite operator or the network can estimate beforehand if an NTN payload will need to resort to store and forward operation when serving a certain tracking area.
  • TA tracking area
  • the network may use dedicated or broadcast signaling to indicate if store and forward operation is required on a per tracking area basis (e.g., a 1-bit indicator to indicate if store and forward operation is required, is tied to the TA code and is applicable to the entire TA).
  • a list of up to N, where N is an integer number greater than zero tracking areas that a satellite will be serving and the corresponding 1-bit indicators for each TA may be indicated.
  • a list of up to N, where N is an integer number greater than zero TAs that will require store and forward operation may be indicated using dedicated and/or broadcast signaling, and the TAs not included in that list are assumed not to require store and forward operation.
  • a broadcast indication may be included in SIB31 in IoT NTN (using SIB31 ASN.1 definition in 3GPP TS 36.331 version 18.0.0 as the baseline).
  • SIB31 ASN.1 definition in 3GPP TS 36.331 version 18.0.0 as the baseline.
  • this example relates only to the indication using a single bit (this is an example, and the other representations may also be used).
  • NeighSatelliteInfoList-r18 SEQUENCE (SIZE(1..maxSat-r18)) OF NeighSatelliteInfo-r18 P111188WO01 PCT APPLICATION 22 of 68
  • NeighSatelliteInfo-r18 SEQUENCE ⁇ satelliteId-r18 SatelliteId-r18, ephemerisInfo-r18 CHOICE ⁇ stateVectors EphemerisStateVectors-r17, o rbitalParameters EphemerisOrbitalParameters-r17 ⁇ , nta-CommonParameters-r18 SEQUENCE ⁇ nta-Common-r18 INTEGER (0..8316827) OPTIONAL, -- Need OP nta-CommonDrift-r18 INTEGER (-261935..261935) OPTIONAL, -- Need OP nta-CommonDriftVariation-r18 INTEGER (0.
  • a UE receiving an indication of operation in store and forward mode and that the next satellite serving the same area will also operate in store and forward mode (and optionally also the same indications for subsequent satellites) may conclude that in its current location, the UE will only receive store and forward mode service and may take consequent actions.
  • the indication may be provided in SIB32 in IoT NTN, together with other information related to discontinuous coverage.
  • This additional information may, e.g., be included in a new complementing satelliteInfoList IE, e.g. denoted as SatelliteInfoList- vXXXX.
  • SatelliteInfoList- vXXXX The following is an extended ASN.1 example based on the ASN.1 code for SIB32 in 3GPP TS 36.331 version 18.0.0 and in this extended example, each time indication is provided in the form of a UTC indication instead of as a combination of HSFN and SFN as in the example above.
  • the added ASN.1 code is indicated with underlined text.
  • a UE may not support store and forward operation from a UE radio access capability standpoint.
  • a UE may operate an application with traffic patterns not suitable for the store and forward operation.
  • the network may need to release a group of UEs in connected mode due to capacity limitations when operating in store and forward, e.g., running out of memory due to not being able to buffer data further.
  • RRCConnectionRelease :: SEQUENCE ⁇ r rc-TransactionIdentifier RRC-TransactionIdentifier, -- -- P111188WO01 PCT APPLICATION 29 of 68
  • RRCConnectionRelease-v890-IEs :: SEQUENCE ⁇ lateNonCriticalExtension OCTET STRING (CONTAINING RRCConnectionRelease- v9e0-IEs) OPTIONAL, nonCriticalExtension
  • RRCConnectionRelease-v9e0-IEs :: SEQUENCE ⁇ redirectedCarrierInfo-v9e0 -- Cond NoRedirect-r8 idleModeMobilityControlInfo-v9e0 -- Cond IdleInfoEUTRA nonCriticalExtension ⁇ -- Regular non critical extensions
  • RRCConnectionRelease-v920-IEs :: cellInfoList-r9
  • the UE cannot transmit uplink traffic not allowed (or not suitable) to be transmitted when the UE is served by satellite(s) operating in non-store and forward mode, i.e., different traffic may be transmitted when served by satellites operating in P111188WO01 PCT APPLICATION 34 of 68 different modes, in which case the proposed prioritization is needed. To enable this the UE may report its capability regarding supporting store and forward operation to the network. [0114] Similarly, the satellite(s) operating in store and forward mode may indicate that only uplink traffic from certain logical channel(s) can be transmitted, where the logical channel(s) may (only) serve uplink traffic that is allowed (or suitable) to be transmitted when the UE is served by satellite(s) operating in store and forward mode.
  • Some embodiments include handling of traffic in transmission buffer during handover. If the UE is configured to handover from an NTN payload operating in non-store and forward mode to an NTN payload operating in store and forward mode, the source gNB does not forward the packet data convergence protocol (PDCP) protocol data units (PDUs) carrying downlink traffic that are not allowed (or not suitable) to be transmitted by NTN payload operating in store and forward mode to the target NTN payload, rather it discards those PDCP PDUs.
  • PDCP packet data convergence protocol
  • PDUs protocol data units
  • the UE discards the buffered PDCP PDUs carrying uplink traffic that are not allowed (or not suitable) to be transmitted to NTN payload operating in store and forward mode.
  • Some embodiments include validity of store and forward operation mode information.
  • the UE may assume the store and forward related information acquired via NTN SIB31 to be valid even if the uplink synchronization validity duration has expired.
  • the UE may assume the store and forward related information acquired via NTN SIB31 to be valid if the one or more time spans indicated for store and forward have not expired even if the uplink synchronization validity duration has expired.
  • the UE may assume the store and forward related information acquired via NTN SIB31 to be valid if the one or more time spans indicated for store and forward have not expired even if the uplink synchronization validity duration has expired. However, if the network provides the UE with updated store and forward parameters, then the UE discards the previous value of the updated store and forward parameters regardless of its uplink synchronization validity duration. [0119] For example, if the UE has determined (based on the store and forward related parameters acquired via NTN-SIB) that the store and forward operation is expected to last for another four seconds at the time of expiration of its validity duration, the UE may consider its P111188WO01 PCT APPLICATION 35 of 68 estimate to be valid.
  • Some embodiments include UE actions upon detection of store and forward operation. As previously stated, the presence of store and forward operations has an impact on delay, QoS, network congestion, and mobility management. Upon detection of the network indication for store and forward operation, the UE may perform one or more of the following actions. [0121] The UE may have a choice of service/application or type of communication to activate, e.g., when the satellite/network indicates store and forward operation, refraining from initiating communication of a type that would not work, or would suffer severely from being subject to store and forward.
  • This choice may also take into account the time until the store and forward operation will end, e.g., such that if this time is short enough, the UE may initiate communication of a certain type, but will refrain from initiating communication of that type if the time until the store and forward operation ends is too long, e.g., longer than a certain threshold time.
  • the UE may choose a network.
  • the UE may conclude that in its present location, it can only receive store and forward service from the NTN, and may, consequently, e.g., choose to perform any of the following actions: o Connect to another type of network access without a store and forward operation such as terrestrial network (if available). o Modify the criterion used for cell reselection algorithms, described in TS 36.304 V18.0.0 (e.g., S-criterion or R-criterion) by the application of a relative and temporary offset to the evaluation conditions to prioritize the (re)-selection to neighbor cells without a store and forward operation.
  • S-criterion or R-criterion e.g., S-criterion or R-criterion
  • the offset may be configured by the network via broadcast or dedicated signaling. o Initiate search for another network from which the UE can receive service, or choose to put its communication parts, e.g., hardware for cellular communication, or hardware for NTN communication, in an energy saving state. [0123]
  • the UE may inform the network. There are cases when a service or application running on the UE may not be well-suited for store and forward operation. Among the possible reasons are the necessity of real-time communication, the request to send a large amount of data that P111188WO01 PCT APPLICATION 36 of 68 may compromise the buffering mechanism of the NTN payload, or the incompatibility with the long delays associated with store and forward operation.
  • the UE may notify the network via a RRC message such as UEAssistanceInformation with a new field parameter or the extension of the interpretation of an existing one such as TrafficPatternInfo-r14.
  • the UE may optimize measurements. A UE may consider the store and forward operation with the configured RRC_CONNECTED mode and RRC_IDLE/RRC_INACTIVE mode measurements. Depending on the traffic profiles, the UE may skip or refrain from performing neighbor cell measurements for those cells or satellites with present or future store and forward operation.
  • Some embodiments use satellite position indications instead of time indications/timestamps. In any of the previously described embodiments where a time indication, e.g. a timestamp, e.g.
  • FIGURE 6 illustrates an example of a communication system 100 in accordance with some embodiments.
  • the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108.
  • the access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • the network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, P111188WO01 PCT APPLICATION 37 of 68 cables, or other material conductors.
  • the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 110 and other communication devices.
  • the network nodes 110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 112 and/or with other network nodes or equipment in the telecommunication network 102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 102.
  • the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 6G wireless local area network
  • WiFi wireless local area network
  • WiMax Worldwide Interoperability for Micro
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change.
  • the network node 300 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs).
  • the network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.
  • RFID Radio Frequency Identification
  • the processing circuitry 302 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 300 components, such as the memory 304, to provide network node 300 functionality.
  • the processing circuitry 302 includes a system on a chip (SOC).
  • the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314.
  • RF radio frequency
  • the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 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 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.
  • the memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300.
  • the memory 304 may be used to store any calculations made by the processing circuitry 302 and/or any data received via the communication interface 306.
  • the processing circuitry 302 and memory 304 is integrated.
  • the communication interface 306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 306 comprises port(s)/terminal(s) 316 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments P111188WO01 PCT APPLICATION 47 of 68 a part of, the antenna 310.
  • Radio front-end circuitry 318 comprises filters 320 and amplifiers 322.
  • the radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302.
  • the radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and/or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0159] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310.
  • the RF transceiver circuitry 312 is part of the communication interface 306.
  • the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).
  • the antenna 310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.
  • the antenna 310, communication interface 306, and/or the processing circuitry 302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment.
  • the antenna 310, the communication interface 306, and/or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being P111188WO01 PCT APPLICATION 48 of 68 performed by the network node.
  • the power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein.
  • the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308.
  • FIGURE 10 is a block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • P111188WO01 PCT APPLICATION 50 of 68 [0169]
  • Hardware 504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508.
  • the VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506.
  • a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV).
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • a VM 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 508, and that part of hardware 504 that executes that VM forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502.
  • Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g.
  • hardware 504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more P111188WO01 PCT APPLICATION 51 of 68 appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.
  • the host 602 also includes software, which is stored in or accessible by the host 602 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 650.
  • the network node 604 includes hardware enabling it to communicate with the host 602 and UE 606.
  • the connection 660 may be direct or pass through a core network (like core network 106 of FIGURE 6) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • the OTT connection 650 may transfer both the request P111188WO01 PCT APPLICATION 52 of 68 data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 650.
  • the OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606.
  • the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602.
  • the host 602 receives the user data carried in the transmission initiated by the UE 606.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the delay to directly activate an SCell by RRC and power consumption of user equipment and thereby provide benefits such as reduced user waiting time and extended battery lifetime.
  • factory status information may be collected and analyzed by the host 602.
  • the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 602 may store surveillance video uploaded by a UE.
  • the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 602 and/or UE 606.
  • sensors may be deployed in or in association with other devices through which the OTT connection 650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and P111188WO01 PCT APPLICATION 54 of 68 practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 602.
  • FIGURE 12 is a flowchart illustrating an example method 1200 in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 12 may be performed by UE 200 described with respect to FIGURE 7.
  • the wireless device is capable of being served by a non-terrestrial network.
  • the method begins at step 1212, where the wireless device (e.g., UE 200) receives via a system information message an indication from a network node indicating that a serving NTN network node is operating or will operate in store and forward mode.
  • receiving the system information message comprises receiving a broadcasted system information message (e.g., SIB) comprising the indication or receiving a dedicated system information message comprising the indication.
  • SIB system information message
  • the indication indicates that the serving NTN network node is operating in store and forward mode for all wireless devices that support operation with network nodes operating in store and forward mode.
  • the indication indicates that the serving NTN network node is operating in store and forward mode only for wireless devices in connected mode.
  • the wireless device performs an operation with respect to the serving NTN network node based on the indication.
  • performing the operation comprises activating or deactivating services or applications based on the received indication. For example, when the received indication indicates store and forward operation, the wireless device may refrain from initiating communication of a type that would not work or would suffer severely from being subject to store and forward operation. The determination may account for a time until the store and forward operation will end, e.g., such that if this time is short enough, the UE may initiate communication of a certain type, but will refrain from initiating communication of that type if the time until the store and forward operation ends is too long, e.g., longer than a certain threshold time.
  • performing the operation comprises performing cell selection or reselection based on the received indication.
  • the wireless device may reselect to another network without store and forward operation, such as a terrestrial network.
  • performing the operation comprises modifying a measurement configuration based on the received notification. For example, depending on traffic profiles, the wireless device may skip or refrain from performing neighbor cell measurements for cells or satellites with present or future store and forward operation.
  • performing the operation comprises informing the network that the wireless device is performing a service or application that is not well-suited for store and forward operation. P111188WO01 PCT APPLICATION 56 of 68 [0195] Additional operations are described with respect to the embodiments and examples described herein.
  • FIGURE 13 is a flowchart illustrating an example method 1300 in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 13 may be performed by network node 300 described with respect to FIGURE 8. The network node is capable of operating within a non-terrestrial network.
  • the method begins at step 1312, where the network node (e.g., network node 300) transmits via a system information message an indication to a wireless device indicating that a serving NTN network node is operating or will operate in store and forward mode.
  • transmitting the system information message comprises broadcasting the system information message (e.g., SIB) comprising the indication or transmitting a dedicated system information message comprising the indication.
  • SIB system information message
  • the network node performs an operation with respect to the wireless device based on the indication.
  • performing the operation comprises transmitting a connection release message to the wireless device, wherein a release cause in the connection release message is related to store and forward operation; and/or prioritizing uplink traffic based on the indication. Additional operations are described with respect to the embodiments and examples described herein. [0200] Modifications, additions, or omissions may be made to method 1300 of FIGURE 13. Additionally, one or more steps in the method of FIGURE 13 may be performed in parallel or in any suitable order. [0201] Modifications, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the invention. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.
  • P111188WO01 PCT APPLICATION 58 of 68 5 The method of any one of the previous embodiments, the operation comprises any of the operations described in the embodiments and examples listed herein. 6 .
  • a method performed by a wireless device the method comprising: ⁇ any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. 7 .
  • the method of the previous embodiment further comprising one or more additional wireless device steps, features or functions described above.
  • 8 The method of any of the previous two embodiments, further comprising: ⁇ providing user data; and ⁇ forwarding the user data to a host computer via the transmission to the base station.
  • Group B Embodiments 9 the method of any of the previous two embodiments, further comprising: ⁇ providing user data; and ⁇ forwarding the user data to a host computer via the transmission to the base station.
  • a communication system including a host computer comprising: ⁇ processing circuitry configured to provide user data; and ⁇ a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), ⁇ wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. 17.
  • the communication system of the pervious embodiment further including the base P111188WO01 PCT APPLICATION 60 of 68 station. 18.
  • the communication system of the previous embodiment further including the base station. 40.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: ⁇ at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. 43. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE. 44. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Landscapes

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

Abstract

According to some embodiments, a method is performed by a wireless device. The method comprises receiving via system information message an indication from a network node indicating that a serving non-terrestrial network (NTN) network node is operating or will operate in store and forward mode and performing an operation with respect to the serving NTN network node based on the indication.

Description

INDICATION OF STORE AND FORWARD FOR NTN TECHNICAL FIELD [0001] Embodiments of the present disclosure are directed to wireless communications and, more particularly to signaling an indication of store-and-forward operation for a non-terrestrial network (NTN). BACKGROUND [0002] Third Generation Partnership Project (3GPP) fifth generation system (5GS) is a new generation radio access technology intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), narrowband Internet of things (NB-IOT) and massive machine type communication (mMTC).5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC). The NR physical and higher layers are reusing parts of the Long Term Evolution (LTE) specification, and to that add needed components when motivated by new use cases.3GPP has discussed in the last few years how to specify technologies to cover/address use cases for machine-to- machine (M2M) and/or IoT. Release 13 specified enhancements to support machine-type communications (MTC) and introduced new user equipment (UE) categories M1 (Cat-M1) and NB1 (Cat-NB1) to support reduced maximum bandwidth of up to six physical resource blocks (PRBs) in eMTC work item and narrowband carrier in NB-IoT work item specifying a new radio interface, respectively. IoT 3GPP technologies [0003] There are multiple differences between “legacy” LTE and the procedures and channels defined for eMTC or NB-IoT. Some important differences include a new physical downlink control channel, i.e., machine physical downlink control channel (MPDCCH) used in eMTC and narrowband physical downlink control channel (NPDCCH) used in NB-IoT. eMTC [0004] 3GPP Release 12 initiated the work on eMTC, also often referred to as LTE-M, and specified the first low-complexity UE category 0 (Cat-0). Cat-0 supports a reduced peak data rate of 1 Mbps, single antenna and half duplex frequency division duplex (HD FDD) operation. [0005] In Release 13 the work accelerated with the introduction of the Cat-M1 UE category. It supports a further reduced complexity, and coverage enhanced (CE) operation. The additional P111188WO01 PCT APPLICATION 2 of 68 cost reduction came from a reduced transmission and reception bandwidth of 1.08 MHz, equivalent to six 180 kHz physical resource blocks (PRBs). The introduction of a lower UE power class of 20 dBm, in addition to the 23 dBm power class, further facilitates a lower UE complexity. [0006] Because of the reduction in bandwidth, a new narrowband physical downlink control channel, the MTC physical downlink control channel (MPDCCH), was introduced as a substitute for the wideband legacy physical downlink control channel (PDCCH) and the enhanced PDCCH (EPDCCH). The Cat-M1 UEs monitor MPDCCH in a narrowband (NB), which is defined by six adjacent PRBs. [0007] eMTC supports a maximum coupling loss (MCL) that is 20 dB larger than the normal MCL of LTE. This is achieved mainly through time repetition and a relaxed acquisition time of the physical channels and signals. The primary and secondary synchronization signals (PSS and SSS) are fully reused from LTE and extended coverage is achieved by means of increased acquisition time. [0008] For the physical broadcast channel (PBCH), the MPDCCH, the physical uplink control channel (PUCCH) and the data channels, that is, the physical uplink shared channel (PUSCH) and physical downlink shared channel (PDSCH), the desired coverage enhancement is achieved through time repetition of a transmission block. [0009] LTE Releases 14 and 15 further enhanced eMTC to support a more diversified set of applications and services. For example, by specifying a new UE category Cat-M2. The performance of eMTC Release 15 meets the IMT-20205G requirements for the massive IoT use case. [0010] The work in 3GPP on eMTC was continued in Release 16 and is further evolved also in Release 17 and Release 18. NB-IoT [0011] An objective of a new Release 13 work item named Narrowband IoT (NB-IoT) is to specify a radio access for cellular internet of things (IoT) that addresses improved indoor coverage, support for massive number of low throughput devices, not sensitive to delay, ultra- low device cost, low device power consumption and (optimized) network architecture. [0012] NB-IoT can be described as a narrowband version of LTE. Similar to eMTC, NB-IoT uses increased acquisition times and time repetitions to extend the system coverage. The P111188WO01 PCT APPLICATION 3 of 68 repetitions may be seen as a third level of retransmissions added at the physical layer as a complement to those at medium access control (MAC) hybrid automatic repeat request (HARQ) and Radio Link Control (RLC) automatic repeat request (ARQ). A NB-IoT downlink carrier is defined by twelve orthogonal frequency division multiplexing (OFDM) sub-carriers, each of 15 kHz, giving a total baseband bandwidth of 180 kHz. When multiple carriers are configured, several 180 kHz carriers can be used, e.g., for increasing the system capacity, inter- cell interference coordination, load balancing, etc. This design gives NB-IoT a high deployment flexibility: [0013] NB-IoT supports the following three different deployment scenarios or mode of operations: 1. ‘Stand-alone operation’ using, for example, the spectrum currently being used by global system for mobile communications (GSM) edge radio access network (GERAN) systems as a replacement of one or more GSM carriers. In principle, it operates on any carrier frequency that is neither within the carrier of another system nor within the guard band of another system’s operating carrier. The other system can be another NB-IoT operation or any other radio access technology (RAT), e.g. LTE. 2. ‘Guard band operation’ uses the unused resource blocks within an LTE carrier’s guard- band. The term guard band may also interchangeably be referred to as guard bandwidth. As an example, for LTE bandwidth of 20 MHz (i.e., Bw1= 20 MHz or 100 RBs), the guard band operation of NB-IoT can place anywhere outside the central 18 MHz but within 20 MHz LTE bandwidth. 3. ‘In-band operation’ uses resource blocks within a normal LTE carrier. The in-band operation may also interchangeably be referred to as in-bandwidth operation. More generally, the operation of one RAT within the bandwidth of another RAT is also referred to as in-band operation. As an example, in an LTE bandwidth of 50 RBs (i.e., Bw1= 10 MHz or 50 RBs), NB-IoT operation over one resource block (RB) within the 50 RBs is referred to as in-band operation. Non-terrestrial Networks (NTN) [0014] To benefit from the strong mobile ecosystem and economy of scale, the satellite network based on the terrestrial wireless access technologies including LTE and NR for satellite networks is being specified in the 3GPP standard. P111188WO01 PCT APPLICATION 4 of 68 [0015] In Release 15 3GPP started the work to prepare NR for operation in a non-terrestrial network. The work was performed within the study item “NR to support Non-Terrestrial Networks” and resulted in TR 38.811. In Release 16 the work to prepare NR for operation in an NTN network continues with the study item “Solutions for NR to support Non-Terrestrial Network”. In parallel the interest to adapt LTE for operation in NTN is growing. As a consequence, 3GPP introduced support for NTN in both LTE and NR in Release 17. After the basic functionality was established, NTN enhancements continued in Release 18 for both LTE and NR. Satellite Communications [0016] A satellite radio access network usually includes the following components: ^ 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. ^ Feeder link that refers to the link between a gateway and a satellite ^ Access link that refers to the link between a satellite and a UE. [0017] A satellite network or satellite based mobile network may also be referred to as a non- terrestrial network. On the other hand, mobile network with base stations on the ground may be referred to as terrestrial network (TN) or non-NTN network. A satellite within NTN may be referred to as NTN node, NTN satellite or simply a satellite. [0018] 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. ^ 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. [0019] The significant orbit height means that satellite systems are characterized by a path loss that is significantly higher than what is expected in terrestrial networks. To overcome the pathloss, the access and feeder links are often operated in line-of-sight conditions, and the UE is equipped with an antenna offering high beam directivity. P111188WO01 PCT APPLICATION 5 of 68 Architecture [0020] Two basic architectures can be distinguished for satellite communication networks, depending on the functionality of the satellites in the system: ^ Transparent payload (also referred to as bent pipe architecture). The satellite forwards the received signal between the terminal and the network equipment on the ground with only amplification and a shift from uplink frequency to downlink frequency. When applied to general 3GPP architecture and terminology, the transparent payload architecture means that the gNB is located on the ground and the satellite forwards signals/data between the gNB and the UE. ^ Regenerative payload. The satellite includes on-board processing to demodulate and decode the received signal and regenerate the signal before sending it back to the earth. When applied to general 3GPP architecture and terminology, the regenerative payload architecture means that the gNB is located in the satellite. [0021] The work item for NR NTN and IoT NTN in 3GPP Release 17 and Release 18 only considers the transparent payload architecture. FIGURE 1 shows an example architecture of a satellite network with bent pipe transponders (i.e., the transparent payload architecture). [0022] FIGURE 1 illustrates an example architecture of a satellite network with bent pipe transponders. The gNB may be integrated in the gateway or connected to the gateway via a terrestrial connection (wire, optic fiber, wireless link). Beam patterns in satellite communications [0023] 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 a 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 2 shows an example architecture of a satellite network with bent pipe transponders. [0024] FIGURE 2 illustrates an example architecture of a satellite network with bent pipe transponders. P111188WO01 PCT APPLICATION 6 of 68 [0025] The NTN beam may, in comparison to the beams observed in a terrestrial network, be wide and cover an area outside of the area defined by the served cell. Beam covering adjacent cells will overlap and cause significant levels of intercell interference. To overcome the large levels of interference, a typical approach is an NTN is to configure different cells with different carrier frequencies and polarization modes. NTN specific challenges Propagation delay [0026] Propagation delay is an important aspect of satellite communications that is different from the delay expected in a terrestrial mobile system. For a bent pipe satellite network, the round-trip delay may, depending on the orbit height, range from tens of ms for LEO satellites to several hundreds of ms for GEO satellites. As a comparison, the round-trip delays in terrestrial cellular networks are typically below 1 ms. [0027] The distance between the UE and a satellite can vary significantly, depending on the position of the satellite and thus the elevation angle ε seen by the UE. Assuming circular orbits, the minimum distance is realized when the satellite is directly above the UE (ε = 90°), and the maximum distance when the satellite is at the smallest possible elevation angle. Table 1 shows the distances between satellite and UE for different orbital heights and elevation angles together with the one-way propagation delay and the maximum propagation delay difference (the difference from the propagation delay at ε = 90°). Note that Table 1 assumes regenerative payload architecture. For the transparent payload case, the propagation delay between gateway and satellite needs to be considered as well, unless the base station corrects for that. Table 1 Propagation delay for different orbital heights and elevation angles. Orbital Elevation Distance One-way Propagation delay height angle UE <-> satellite propagation delay difference 600 km 90° 600 km 2.0 ms --- 30° 1075 km 3.6 ms 1.6 ms 10° 1932 km 6.4 ms 4.4 ms 1200 km 90° 1200 km 4.0 ms --- 30° 1999 km 6.7 ms 2.7 ms 10° 3131 km 10.4 ms 6.4 ms 35786 km 90° 35786 km 119.4 ms --- 30° 38609 km 128.8 ms 9.4 ms 10° 40581 km 135.4 ms 16.0 ms P111188WO01 PCT APPLICATION 7 of 68 [0028] The propagation delay may also be highly variable due to the high velocity of the LEO and MEO satellites and change in the order of 10 – 100 µs every second, depending on the orbit altitude and satellite velocity. Doppler shift [0029] In a LEO NTN, the satellites are moving with a very high velocity. This leads to a Doppler shift of the carrier frequency on the service link of up to 24 ppm for a LEO satellite at 600 km altitude. The Doppler shift is also time variant due to the satellite motion over the sky. The Doppler shift may vary with up to 0.27 ppm/s for a LEO 600 km satellite. The Doppler shift will impact, i.e., increase or decrease, the frequency received on the service link compared to the transmitted frequency. [0030] For GEO NTN, the satellites may move in an orbit inclined relative to the plane of the equator. The inclination introduces a periodic movement of the satellite relative earth which introduces a predictable, and daily periodically repeating Doppler shift of the carrier frequency as exemplified in FIGURE 3. The terms beam and cell may herein be used interchangeably, unless explicitly noted otherwise. Particular embodiments and examples described herein may be focused on NTN in the context of IoT, but the embodiments and examples apply similarly to NR and any wireless network dominated by line-of-sight conditions. [0031] FIGURE 3 illustrates an example of the diurnal Doppler shift of the forward service link observed for a GEO satellite operating from an inclined orbit. Discontinuous coverage [0032] Discontinuous coverage refers to the situation where the visibility of a satellite or group of satellites, commonly low Earth orbit (LEO), from a certain ground point is limited in time leading to periods without satellite network coverage. The rapid movement of NGSO (Non- Geostationary Orbit) satellites around Earth is the cause of this time limitation and its length depends on the characteristics of the satellite constellation (e.g., structure, total number of satellites, number of orbital planes, or satellites per plane) and UE (e.g., minimum elevation angle, or local radio conditions). Thus, the use of partial, sparse, or incomplete constellations where the number of satellites is not enough to provide continuous coverage in a region will result in satellite network coverage gaps. This might be a usual case in early IoT NTN deployments due to the relaxed delay requirements and traffic profiles typical of IoT applications. P111188WO01 PCT APPLICATION 8 of 68 [0033] During Release 17, a UE centric solution to evaluate coverage gaps was standardized in 3GPP for IoT NTN. The assistance information sent to the UE includes satellite mean ephemeris in two-line element (TLE) format, satellite ID and coverage information. Additionally, in quasi-Earth fixed cell deployments, the network may provide the absolute start serving time (T-service-start) instead of the satellite’s ephemeris. The UE uses this information to estimate when the same or next satellite will be visible from its current location so that the UE can enter a deep sleep state in between the satellite passes when there is no available coverage. Ephemeris data [0034] TR 38.821 specifies that ephemeris data should be provided to the UE, for example, to assist with pointing a directional antenna (or an antenna beam) towards the satellite. A UE that knows its own position, e.g., based on global navigation satellite system (GNSS) support, may also use the ephemeris data to calculate correct timing advance (TA) and Doppler shift. The contents of the ephemeris data and the procedures on how to provide and update such data have not yet been studied in detail. [0035] A satellite orbit can be fully described using six parameters. Which set of parameters is used can be decided by the user; 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 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 satellite moves through periapsis). The set of these parameters is illustrated in FIGURE 4. [0036] FIGURE 4 illustrates orbital elements. [0037] A two-line element set is a data format encoding a list of orbital elements of an Earth- orbiting object for a given point in time, the epoch. As an example of a different parametrization, TLEs use mean motion n and mean anomaly M instead of a and t. [0038] A different set of parameters is the position and velocity vector (x, y, z, vx, vy, vz) of a satellite. These are sometimes referred to as orbital state vectors. They can be derived from the orbital elements and vice versa because the information they contain is equivalent. All these formulations (and many others) are possible choices for the format of ephemeris data to be used in NTN. P111188WO01 PCT APPLICATION 9 of 68 [0039] It is important that a UE can determine the position of a satellite with accuracy of at least a few meters. However, several studies have shown that this might be hard to achieve when using the de-facto standard of TLEs. On the other hand, LEO satellites often have GNSS receivers and can determine their position with meter-level accuracy. [0040] Another aspect discussed during the study item and captured in 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 that are exposed to strong atmospheric drag and need to perform correctional maneuvers often. While it seems possible to provide the satellite position with the required accuracy, care needs to be taken to meet these requirements, e.g., when choosing the ephemeris data format, or the orbital model to be used for the orbital propagation. [0041] Ephemeris data consists of at least five parameters describing the shape and position in space of the satellite orbit. It also comes with a timestamp, which is the time when the other parameters describing the orbit ellipse were obtained. The position of the satellite at any given time in the near future can be predicted from this data using orbital mechanics. The accuracy of the prediction will, however, degrade for projections further and further into the future. The validity time of a certain set of parameters depends on many factors like the type and altitude of the orbit, but also the desired accuracy, and ranges from the scale of a few days to a few years. Deployment considerations [0042] In a LEO or MEO communication system, a large number of satellites deployed over a range of orbits is required to provide continuous coverage across the full globe. Launching a mega satellite constellation is both an expensive and time-consuming procedure. It is therefore expected that LEO and MEO satellite constellations for some time will only provide partial earth-coverage. For constellations dedicated to massive IoT services with relaxed latency requirements, full earth-coverage may not even be necessary. It may be sufficient to provide occasional or periodic coverage according to the orbital period of the constellation. P111188WO01 PCT APPLICATION 10 of 68 Release 19 NTN enhancements [0043] The standardization of NTN technologies continues in 3GPP with another two work items for NR and LTE, respectively. The justification for these enhancements is the necessities of the commercial deployments that are currently ongoing. Based on real deployment or deployment plans, further evolution of NR and IoT NTN is required. [0044] Among the objectives included in the IoT NTN Release 19 WID is support for store and forward (S&F) satellite operation with full eNB as regenerative payload, which includes: defining the necessary enhancements into E-UTRAN (network and UE) to support S&F operation for delay-tolerant services; at least specify necessary enhancements, e.g., related to S1 protocol, especially to address the feeder link switch over as needed; and minimize UE impact. [0045] Coordination is needed on the detail requirements (e.g., traffic type, or quality of service (QoS) parameters for S&F), network architecture (e.g., whether consider (partial) core network on satellite) etc. Store and forward architecture [0046] The store and forward architecture for NTN involves the use of network nodes as satellites or high-altitude platforms (HAPS) to relay communication signals between terrestrial user equipment (UE) and the core network. This architecture is designed to extend the coverage and capacity of traditional terrestrial networks, particularly in remote or underserved areas. [0047] The store and forward mechanism enables the NTN to temporarily store incoming data before transmitting it to the next hop in the network, which could be another relay node (e.g., thanks to inter-satellite links) or the core network itself. This enables the NTN to overcome the inherent latency and intermittent connectivity associated with non-terrestrial communication links. [0048] The store and forward architecture is particularly useful in scenarios where the NTN is used to provide connectivity in areas with limited terrestrial infrastructure, such as remote rural or maritime environments. Using store and forward, the NTN can efficiently manage the transmission of data between UEs and the core network, even in challenging communication conditions, i.e., areas where satellites cannot be connected to ground stations. From a business perspective, this architecture improves ground segment affordability by enabling operation with fewer ground-stations and a more robust operation of the satellite under intermittent feeder P111188WO01 PCT APPLICATION 11 of 68 link operation. This is specifically well-suited for delay tolerant IoT applications that do not require continuous connectivity. [0049] FIGURE 5 illustrates store and forward operation for an NTN payload. [0050] There currently exist certain challenges. For example, LEO satellite constellations with limited number of ground stations or satellites lead to discontinuity. This refers to gaps in service when no satellite is within range to maintain a direct line of sight with a given ground terminal. In small, low density LEO constellations with tens or few hundreds of satellites, revisit times may be in the magnitude of hours and visibility windows in the magnitude of minutes. [0051] The discontinuity challenge was first addressed in Release 17 and 18 with the discontinuous coverage enhancements. However, these assumed concurrent connectivity between the satellite payload and the ground station. In Release 19, early constellation deployments assumed further intermittent connectivity and increased transfer delays. Ensuring consistent coverage with a limited number of satellites requires strategic planning of orbits and may necessitate additional ground infrastructure, such as relay stations, to fill coverage gaps. [0052] The introduction of store and forward architecture brings several challenges in the communication between the network node (e.g., eNB/gNB) and the UE within the radio access network. Some of the challenges include: ^ Latency and buffering capability: Data must be temporarily stored before being forwarded. In an NTN scenario, this is compounded by the long propagation delays associated with satellite communication, which can impact the performance of applications and services. ^ Resource management and configuration. ^ Quality of Service (QoS): The variability in transmission times makes the prioritization of different types of traffic complex when connections are considered end-to-end. ^ Mobility management: In a mobile environment such as LEO constellations, handovers between terrestrial and non-terrestrial networks can be challenging due to differences in network characteristics. ^ Network congestion: Given the relatively limited opportunities for simultaneous connectivity, store and forward nodes become bottlenecks. P111188WO01 PCT APPLICATION 12 of 68 ^ Backwards compatibility with previous releases of the specification and compatibility with terrestrial networks is essential. SUMMARY [0053] As described above, certain challenges currently exist with store-and-forward operation for a non-terrestrial network (NTN). Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments provide an indication from the network to a user equipment (UE) to signal the present or future presence of store and forward operation for the serving and/or neighbor frequency, cell(s), or satellite(s). The indication may take the form of a bit, a time span, a time schedule, among others, which may be provided via broadcast or dedicated signaling. The store and forward operation refers to the case when there is no connectivity towards an NTN ground station or another satellite via inter-satellite link (ISL). A new release cause may also be included for the network to release the Radio Resource Control (RRC) connections for UEs not supporting the store and forward operation mode (e.g., Release 17 or Release 18 UEs) or for traffic patterns are not suitable for store and forward operation mode. Similarly, the UE may adjust a set of procedures accordingly depending on the operation mode (e.g., store and forward) and its own application necessities. [0054] In general, particular embodiments include an indication, i.e., a field, parameter, or an implicit statement in broadcast or dedicated signaling of the presence of store and forward operation for the serving and/or neighbor frequency, cells, or satellites. [0055] According to some embodiments, a method is performed by a wireless device. The method comprises receiving via a system information message an indication from a network node indicating that a serving NTN network node is operating or will operate in store and forward mode and performing an operation with respect to the serving NTN network node based on the indication. [0056] In particular embodiments, the indication that the serving NTN network node is operating or will operate in store and forward mode is associated with a time for store and forward operation. In particular embodiments, the indication that the serving NTN network node is operating or will operate in store and forward mode is associated with a location for store and forward operation. P111188WO01 PCT APPLICATION 13 of 68 [0057] In particular embodiments, receiving the system information message comprises receiving a broadcasted system information message comprising the indication or receiving a dedicated system information message comprising the indication. [0058] In particular embodiments, the indication indicates that the serving NTN network node is operating in store and forward mode for all wireless devices that support operation with network nodes operating in store and forward mode. In particular embodiments, the indication indicates that the serving NTN network node is operating in store and forward mode only for wireless devices in connected mode. [0059] In particular embodiments, performing the operation comprises activating or deactivating services or applications based on the received indication; refraining from transmitting traffic that is unsuitable for store and forward operation based on the received indication; performing cell selection or reselection based on the received indication; modifying a measurement configuration based on the received notification; and/or informing the network that the wireless device is performing a service or application that is not well-suited for store and forward operation. [0060] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the methods of the wireless receiver described above. [0061] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above. [0062] According to some embodiments, a method is performed by a network node. The method comprises transmitting via a system information message an indication to a wireless device indicating that a serving NTN network node is operating or will operate in store and forward mode and performing an operation with respect to the wireless device based on the indication. [0063] In particular embodiments, transmitting the system information message comprises broadcasting the system information message comprising the indication or transmitting a dedicated system information message comprising the indication. [0064] In particular embodiments, performing the operation comprises transmitting a connection release message to the wireless device, wherein a release cause in the connection P111188WO01 PCT APPLICATION 14 of 68 release message is related to store and forward operation; and/or prioritizing uplink traffic based on the indication. [0065] According to some embodiments, a network node comprises processing circuitry operable to perform any of the methods of the network node described above. [0066] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above. [0067] Certain embodiments may provide one or more of the following technical advantages. For example, in particular embodiments the indication or implicit statement makes the UE aware of when the satellite or NTN payload serving the current cell operates with the store and forward mode and thus does not have connectivity towards the NTN ground station or another satellite via ISL. [0068] The network and UE may leverage the indication in broadcast or dedicated signaling for the serving or neighbor cells to optimally perform a plurality of procedures ranging from data transactions, power saving operations, mobility procedures, and cell measurements. BRIEF DESCRIPTION OF THE DRAWINGS [0069] 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 illustrates an example architecture of a satellite network with bent pipe transponders; FIGURE 3 illustrates an example of the diurnal Doppler shift of the forward service link observed for a GEO satellite operating from an inclined orbit; FIGURE 4 illustrates orbital elements; FIGURE 5 illustrates store and forward operation for an NTN payload; FIGURE 6 illustrates an example communication system, according to certain embodiments; P111188WO01 PCT APPLICATION 15 of 68 FIGURE 7 illustrates an example user equipment (UE), according to certain embodiments; FIGURE 8 illustrates an example network node, according to certain embodiments; FIGURE 9 illustrates a block diagram of a host, according to certain embodiments; FIGURE 10 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments; FIGURE 11 illustrates a host communicating via a network node with a UE over a partially wireless connection, according to certain embodiments; FIGURE 12 illustrates a method performed by a wireless device, according to certain embodiments; and FIGURE 13 illustrates a method performed by a network node, according to certain embodiments. DETAILED DESCRIPTION [0070] As described above, certain challenges currently exist with store-and-forward operation for a non-terrestrial network (NTN). Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments include an indication, i.e., a field, parameter, or an implicit statement in broadcast or dedicated signaling of the presence of store and forward operation for the serving and/or neighbor frequency, cells, or satellites. [0071] Particular embodiments are 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. [0072] As used herein, the term NTN may, depending on the context, refer to either or both of New Radio (NR) NTN and Internet-of-things (IoT) NTN, and sometimes the term is used to refer to only IoT NTN. [0073] The embodiments outlined below are described mainly in terms of Long Term Evolution (LTE) based NTNs, but they are equally applicable in an NTN based on NR technology. P111188WO01 PCT APPLICATION 16 of 68 [0074] The term “network” is used herein to refer to a network node, which typically will be a gNB (e.g., in a NR based NTN) or an eNB (e.g., in an LTE based NTN, such as an IoT NTN), but which may also be a base station or an access point in another type of network based on communication via satellites or high-altitude platforms (HAPS), or any other network node (in a network involving satellites or HAPS) with the ability to directly or indirectly communicate with a user equipment (UE). Refinements with finer granularity are also conceivable. [0075] For example, a gNB may be an en-gNB, and if a split gNB architecture is applied (dividing the gNB into multiple separate entities or notes), the term “network” or “network node” or “node” may refer to a part of the gNB, such as a gNB-CU (often referred to as just central unit (CU)), a gNB-DU (often referred to as just distributed unit (DU)), a gNB-CU- control plane (CP) or a gNB-CU-user plane (UP). Similarly, an eNB may be an ng-eNB, and if a split eNB architecture is applied (dividing the gNB into multiple separate entities or nodes), the term “network” (and the network node it implies) may refer to a part of the eNB, such as an eNB-CU, an eNB-DU, an eNB-CU-CP or an eNB-CU-UP. Furthermore, the term “network” (and the network node it implies) may also refer to an integrated access and backhaul (IAB)- donor, IAB-donor-CU, IAB-donor-DU, IAB-donor-CU-CP, or an IAB-donor-CU-UP. [0076] The terms “source node”, “target node” and “candidate target node” may be used herein. The “node” in these terms should be understood as typically being a radio access network (RAN) node in an NTN based on NR technology, LTE technology or any other radio access technology (RAT) in which conditional handover or another conditional mobility concept is defined. In an NR based NTN, such a RAN node may be assumed to be a gNB. In an LTE based NTN (including an IoT NTN), such a RAN node may be assumed to be an eNB. [0077] Alternatives to, or refinements of, these interpretations are however also conceivable. For example, a gNB may be an en-gNB, and if a split gNB architecture is applied (dividing the gNB into multiple separate entities or nodes), the term “node” may refer to a part of the gNB, such as a gNB-CU (often referred to as just CU), a gNB-DU (often referred to as just DU), a gNB-CU-CP or a gNB-CU-UP. Similarly, an eNB may be an ng-eNB, and if a split eNB architecture is applied (dividing the gNB into multiple separate entities or notes), the term “node” may refer to a part of the eNB, such as an eNB-CU, an eNB-DU, an eNB-CU-CP or an eNB-CU-UP. Furthermore, the “node” in the terms may also refer to an IAB-donor, IAB- donor-CU, IAB-donor-DU, IAB-donor-CU-CP, or an IAB-donor-CU-UP. P111188WO01 PCT APPLICATION 17 of 68 [0078] The terms information element (IE), parameter, field parameter, and field may be used interchangeably herein. [0079] Parameters/IEs/fields used in ASN.1 code as well as in procedural text in the Third Generation Partnership Project (3GPP) RRC specification for 5G/NR, i.e., 3GPP TS 38.331 version 18.0.0, are often named with a suffix indicating the number of the release of the 3GPP standard the parameter/IE/field was introduced in (e.g., the suffix “-r17” for a parameter/IE/field introduced in release 17 of the 3GPP standard). Parameters/IEs/fields following this naming convention are typically referred to both with and without the suffix, where the name including the suffix is used in the ASN.1 code (and thus defines the formal name from the ASN.1 compiler’s perspective), while the name without the suffix is used in running text, e.g. in field descriptions and procedural text. Relevant examples in the context of this document include the parameters/IEs/fields t1-Threshold-r17/t1-Threshold and t-Service- r17/t-Service. As used herein, both name variants may occur for various parameters/IEs/fields. [0080] There are two main deployment principles for NTN: quasi-Earth-fixed cells and Earth- moving cells. These deployment principles are also referred to by other names. The quasi- Earth-fixed cells deployment principle is also referred to as quasi-Earth-fixed beams. The Earth-moving cells deployment principle is also referred to as Earth-moving beams, or shorter, moving cells or and moving beams. [0081] That a satellite operates in store and forward mode (or non-store and forward mode) strictly speaking means that the satellite payload (i.e., in this context the communications related equipment placed in the satellite) operates in store and forward mode (or non-store and forward mode). That a satellite operates in store and forward mode (or non-store and forward mode), and that a satellite payload operates in store and forward mode (or non-store and forward mode) are considered to be equivalent concepts. [0082] A satellite or NTN payload operating in store and forward mode is associated herein with the lack of end-to-end connectivity. A limitation with this association is that it only indicates the current satellite's mode of operation in the NTN radio access network (RAN), while makes no guarantees that the other end of a communication is available without store and forward at that end. Depending on the scenario, store and forward may still be applied to the communication in another part of the network on the path to the remote endpoint, e.g. in another satellite payload or in a network node with intermittent connectivity to a satellite payload. P111188WO01 PCT APPLICATION 18 of 68 [0083] According to particular embodiments, the network provides UEs with an implicit or explicit indication of the present or future existence of a store and forward NTN connectivity. During a store and forward NTN connectivity, mode, or operation, a satellite or NTN payload does not have access to end-to-end connectivity in the feeder link neither via a ground station nor via another satellite (inter-satellite link (ISL)). Thus, a UE is not expected to have end-to- end connectivity with the network, although the RAN and parts of the 4G/5G core network may be available on the NTN payload (i.e., on the satellite) to complete the service link part of the communication. [0084] An indication of such a type may be associated with the cell or the satellite and may take several forms. [0085] In one embodiment, a single bit is used to indicate whether the store and forward operation is used at the moment of transmission. In an alternative, the bit simply indicates the NTN payload (serving or neighbor) supports store and forward without any implications on the current operation mode. [0086] In another embodiment, a time span, either absolute (e.g., coordinated universal time (UTC)) or relative (e.g., seconds, system frame number (SFN), hyper-SFN (H-SFN)) is used to indicate when the store and forward operation is used. In an alternative, the time span indicates when end-to-end connectivity, i.e., feeder link connection through ground station or ISL is available. In another alternative, the time indication may refer to the remaining time with or without end-to-end connectivity, i.e., feeder link connection through ground station or ISL is available. The time span may refer to the current time, i.e. when the indication is sent, or a time span in the near future. [0087] The concerned time span may be represented in various ways: ^ Only a start time. ^ A start time and an end time, where the end time may be signaled through the cell operation service time, i.e., t-Service field parameter. ^ A start time and a duration. ^ An end time and a duration. ^ Only an end time. P111188WO01 PCT APPLICATION 19 of 68 [0088] The time span may use a variety of starting and ending point references, which may be compatible with existing specified field parameters in different system information blocks (SIBs) or included in a new SIB: ^ Epoch time ^ The start (e.g., starting SFN) of the previous SIB31 transmission (or SIB32 transmission) ^ The end of previous SIB31 (or SIB32) transmission as the reference. ^ The start of the future SIB31 (or SIB32) transmission. ^ The end of the future SIB31 (or SIB32) transmission. ^ The start of the current SIB31 (or SIB32) transmission carrying the store and forward parameters as the reference. ^ The end of the current SIB31 (or SIB32) transmission carrying the store and forward parameters as the reference ^ The start of the uplink synchronization validity duration (assuming the NTN-SIB was used to indicate store and forward related parameters) as the reference. [0089] In another embodiment, a time schedule, which is composed of several time spans, is used to indicate when the store and forward operation is used (or when non-store and forward is used). In an alternative, an additional bit is included together with the time schedule to indicate if during that certain period of time the satellite is operating in store and forward mode. [0090] In another embodiment, a finite number (e.g., integer) is used to indicate the existing or remaining buffering capability of the NTN payload. For example, if the buffering capability is limited by the available memory in the satellite, this number may indicate the currently available buffer space in bytes. The indication implicitly signals that the current mode of operation of the NTN payload is the store and forward mode. [0091] In some embodiments, similar information as described above may also be indicated (provided from the network to a UE) for other satellites than the satellite serving the cell where the indication/information is provided/signaled, e.g., neighbor satellites, or may indicate for other cells than the cell where the indication/information is provided, e.g., neighbor cells. [0092] In some embodiments, indications/information related to store and forward operation (and/or non-store and forward operation) may be indicated for one or more satellite(s) that will P111188WO01 PCT APPLICATION 20 of 68 later cover the same area (i.e., serve cell(s) in the same area) as the satellite presently providing the indication. [0093] In one embodiment, the indication of store and forward is tied to a tracking area (TA). For example, depending on the geographical locations of the ground stations, the satellite operator or the network can estimate beforehand if an NTN payload will need to resort to store and forward operation when serving a certain tracking area. The network may use dedicated or broadcast signaling to indicate if store and forward operation is required on a per tracking area basis (e.g., a 1-bit indicator to indicate if store and forward operation is required, is tied to the TA code and is applicable to the entire TA). [0094] Alternatively, a list of up to N, where N is an integer number greater than zero, tracking areas that a satellite will be serving and the corresponding 1-bit indicators for each TA may be indicated. In yet another alternative, a list of up to N, where N is an integer number greater than zero, TAs that will require store and forward operation may be indicated using dedicated and/or broadcast signaling, and the TAs not included in that list are assumed not to require store and forward operation. As a result, a timing indication for the store and forward operation is not needed because store and forward operation is tied to an Earth-fixed geographical region. In another embodiment, a 1-bit flag is signaled using dedicated or broadcast signaling to indicate whether one or more of the store and forward related information is applicable to all the cells within the tracking area. [0095] In one embodiment, the indication of store and forward architecture is provided to the UE in broadcast signaling. For example, the network may broadcast the indication via system information. In this case, a change of the connectivity status, i.e., whether the satellite has gained or lost connectivity to the network, may be notified to the UE according to the existing system information update mechanisms specified in 3GPP TS 36.331 version 18.0.0 section 5.2.1.3. [0096] The following is an example of how a broadcast indication may be included in SIB31 in IoT NTN (using SIB31 ASN.1 definition in 3GPP TS 36.331 version 18.0.0 as the baseline). For illustrative purposes, this example relates only to the indication using a single bit (this is an example, and the other representations may also be used). -- ASN1START SystemInformationBlockType31-r17 ::= SEQUENCE { servingSatelliteInfo-r17 ServingSatelliteInfo-r17, P111188WO01 PCT APPLICATION 21 of 68 } ServingSatelliteInfo-r17 ::= SEQUENCE { ephemerisInfo-r17 CHOICE { stateVectors EphemerisStateVectors-r17, orbitalParameters EphemerisOrbitalParameters-r17 }, nta-CommonParameters-r17 SEQUENCE { nta-Common-r17 INTEGER (0..8316827) OPTIONAL, -- Need OP nta-CommonDrift-r17 INTEGER (-261935..261935) OPTIONAL, -- Need OP nta-CommonDriftVariation-r17 INTEGER (0..29479) OPTIONAL -- Need OP }, ul-SyncValidityDuration-r17 ENUMERATED {s5, s10, s15, s20, s25, s30, s35, s40, s45, s50, s55, s60, s120, s180, s240, s900}, epochTime-r17 SEQUENCE { startSFN-r17 INTEGER (0..1023), startSubFrame-r17 INTEGER (0..9) } OPTIONAL, -- Need OP k-Offset-r17 INTEGER (0..1023), k-Mac-r17 INTEGER (1..512) OPTIONAL, -- Need OP ..., [[ satelliteId-r18 SatelliteId-r18 OPTIONAL, -- Need OR referenceLocation-r18 CHOICE { fixedCell-r18 ReferenceLocation-r18, movingCell-r18 ReferenceLocation-r18 } OPTIONAL, -- Need OR distanceThresh-r18 INTEGER(0..65535) OPTIONAL -- Need OR ]], [[ storeForward-rXY BIT STRING (SIZE (1)) OPTIONAL -- Need OR ]] } -- ASN1STOP [0097] In yet another alternative, the indication may be provided in a new (not presently specified) SIB in IoT NTN, e.g., a SIB dedicated for (or used primarily for) providing information related to the store and forward mode of operation or to the network’s/satellite’s mode of operation in general. [0098] Furthermore, similar indication(s) may be provided for the neighbor NTN cells or the neighbor satellites. The following is an example of how a broadcast indication may be included in SIB33 in IoT NTN for neighbor satellites (using SIB33 ASN.1 definition in 3GPP TS 36.331 version 18.0.0 as the baseline). For illustrative purposes, this example relates only to the indication using a single bit (this is an example, and other representations may also be used). -- ASN1START SystemInformationBlockType33-r18 ::= SEQUENCE { neighSatelliteInfoList-r18 NeighSatelliteInfoList-r18 OPTIONAL, -- Need OR neighValidityDuration-r18 ENUMERATED {s5, s10, s15, s20, s25, s30, s35, s40, s45, s50, s55, s60, s120, s180, s240, s900} OPTIONAL, -- Need OP lateNonCriticalExtension OCTET STRING OPTIONAL, ... } NeighSatelliteInfoList-r18 ::= SEQUENCE (SIZE(1..maxSat-r18)) OF NeighSatelliteInfo-r18 P111188WO01 PCT APPLICATION 22 of 68 NeighSatelliteInfo-r18 ::= SEQUENCE { satelliteId-r18 SatelliteId-r18, ephemerisInfo-r18 CHOICE { stateVectors EphemerisStateVectors-r17, orbitalParameters EphemerisOrbitalParameters-r17 }, nta-CommonParameters-r18 SEQUENCE { nta-Common-r18 INTEGER (0..8316827) OPTIONAL, -- Need OP nta-CommonDrift-r18 INTEGER (-261935..261935) OPTIONAL, -- Need OP nta-CommonDriftVariation-r18 INTEGER (0..29479) OPTIONAL -- Need OP }, epochTime-r18 SEQUENCE { startSFN-r18 INTEGER (0..1023), startSubFrame-r18 INTEGER (0..9) } OPTIONAL, -- Need OP k-Mac-r18 INTEGER (1..512) OPTIONAL, -- Need OP t-ServiceStartNeigh-r18 TimeOffsetUTC-r17 OPTIONAL, -- Need OR ..., [[ storeForward-rXY BIT STRING (SIZE (1)) OPTIONAL -- Need OR ]] } -- ASN1STOP [0099] The following is an example of how a broadcast indication may be included in SIB4 in IoT NTN for neighbor cells (using SIB4 ASN.1 definition in 3GPP TS 36.331 version 18.0.0 as the baseline). For illustrative purposes, this example relates to the indication using a single bit (this is an example, and the other representations may also be used). -- ASN1START SystemInformationBlockType4 ::= SEQUENCE { intraFreqNeighCellList IntraFreqNeighCellList OPTIONAL, -- Need OR intraFreqExcludedCellList IntraFreqExcludedCellList OPTIONAL, -- Need OR csg-PhysCellIdRange PhysCellIdRange OPTIONAL, -- Cond CSG ..., lateNonCriticalExtension OCTET STRING OPTIONAL, [[ intraFreqNeighHSDN-CellList-r15 IntraFreqNeighHSDN-CellList-r15 OPTIONAL -- Need OR ]], [[ rss-ConfigCarrierInfo-r16 RSS-ConfigCarrierInfo-r16 OPTIONAL, -- Cond RSS intraFreqNeighCellList-v1610 IntraFreqNeighCellList-v1610 OPTIONAL -- Cond RSS ]] } IntraFreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo IntraFreqNeighCellList-v1610 ::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo-v1610 IntraFreqNeighCellList-vXY ::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo- vXY IntraFreqNeighHSDN-CellList-r15 ::= SEQUENCE (SIZE (1..maxCellIntra)) OF PhysCellIdRange IntraFreqNeighCellInfo ::= SEQUENCE { physCellId PhysCellId, q-OffsetCell Q-OffsetRange, ... } IntraFreqNeighCellInfo-v1610 ::= SEQUENCE { rss-MeasPowerBias-r16 RSS-MeasPowerBias-r16 P111188WO01 PCT APPLICATION 23 of 68 } IntraFreqNeighCellInfo-vXY ::= SEQUENCE { storeForward-rXY BIT STRING (SIZE (1)) } IntraFreqExcludedCellList ::= SEQUENCE (SIZE (1..maxExcludedCell)) OF PhysCellIdRange -- ASN1STOP [0100] In another embodiment, the indication of store and forward architecture is provided to the UE in RRC_CONNECTED mode via dedicated signaling. For example, the network may send the indication in a RRC Connection Reconfiguration message. [0101] The following is an example of how a dedicated indication may be included in the RRCConnectionReconfiguration message as part of the measurement configuration in IoT NTN (using MeasObjectEUTRA ASN.1 definition in 3GPP TS 36.331 version 18.0.0 as the baseline). For illustrative purposes, this example relates to the indication using a time span (this is an example, and the other representations may also be used). -- ASN1START MeasObjectEUTRA ::= SEQUENCE { carrierFreq ARFCN-ValueEUTRA, allowedMeasBandwidth AllowedMeasBandwidth, -- -- reducedMeasPerformance-r12 BOOLEAN OPTIONAL, -- Need ON measDS-Config-r12 MeasDS-Config-r12 OPTIONAL -- Need ON ]], [[ allowedCellsToRemoveList-r13 CellIndexList OPTIONAL, -- Need ON allowedCellsToAddModList-r13 AllowedCellsToAddModList-r13 OPTIONAL, -- Need ON rmtc-Config-r13 RMTC-Config-r13 OPTIONAL, -- Need ON carrierFreq-r13 ARFCN-ValueEUTRA-v9e0 OPTIONAL -- Need ON ]], P111188WO01 PCT APPLICATION 24 of 68 [[ tx-ResourcePoolToRemoveList-r14 Tx-ResourcePoolMeasList-r14 OPTIONAL, -- Need ON tx-ResourcePoolToAddList-r14 Tx-ResourcePoolMeasList-r14 OPTIONAL, -- Need ON fembms-MixedCarrier-r14 BOOLEAN OPTIONAL -- Need ON ]], [[ measSensing-Config-r15 MeasSensing-Config-r15 OPTIONAL -- Need ON ]], [[ measRSS-DedicatedConfig-r16 SetupRelease {MeasRSS-DedicatedConfig-r16} OPTIONAL -- Need ON ]] } MeasObjectEUTRA-v9e0 ::= SEQUENCE { carrierFreq-v9e0 ARFCN-ValueEUTRA-v9e0 } MeasRSS-DedicatedConfig-r16 ::= SEQUENCE { rss-ConfigCarrierInfo-r16 RSS-ConfigCarrierInfo-r16 OPTIONAL, -- Need OP cellsToAddModList-v1610 CellsToAddModList-v1610 OPTIONAL -- Need ON } CellsToAddModList ::= SEQUENCE (SIZE (1..maxCellMeas)) OF CellsToAddMod CellsToAddModList-v1610 ::= SEQUENCE (SIZE (1..maxCellMeas)) OF CellsToAddMod-v1610 CellsToAddMod ::= SEQUENCE { cellIndex INTEGER (1..maxCellMeas), physCellId PhysCellId, cellIndividualOffset Q-OffsetRange } CellsToAddMod-v1610 ::= SEQUENCE { rss-MeasPowerBias-r16 RSS-MeasPowerBias-r16 } CellsToAddMod-vXY ::= SEQUENCE { storeForward-rXY StoreForward-rXY } ExcludedCellsToAddModList ::= SEQUENCE (SIZE (1..maxCellMeas)) OF ExcludedCellsToAddMod ExcludedCellsToAddMod ::= SEQUENCE { cellIndex INTEGER (1..maxCellMeas), physCellIdRange PhysCellIdRange } MeasCycleSCell-r10 ::= ENUMERATED {sf160, sf256, sf320, sf512, sf640, sf1024, sf1280, spare1} MeasSubframePatternConfigNeigh-r10 ::= CHOICE { release NULL, setup SEQUENCE { measSubframePatternNeigh-r10 MeasSubframePattern-r10, measSubframeCellList-r10 MeasSubframeCellList-r10 OPTIONAL -- Cond always } } MeasSubframeCellList-r10 ::= SEQUENCE (SIZE (1..maxCellMeas)) OF PhysCellIdRange AltTTT-CellsToAddModList-r12 ::= SEQUENCE (SIZE (1..maxCellMeas)) OF AltTTT-CellsToAddMod- r12 AltTTT-CellsToAddMod-r12 ::= SEQUENCE { cellIndex-r12 INTEGER (1..maxCellMeas), physCellIdRange-r12 PhysCellIdRange } P111188WO01 PCT APPLICATION 25 of 68 AllowedCellsToAddModList-r13 ::= SEQUENCE (SIZE (1..maxCellMeas)) OF AllowedCellsToAddMod-r13 AllowedCellsToAddMod-r13 ::= SEQUENCE { cellIndex-r13 INTEGER (1..maxCellMeas), physCellIdRange-r13 PhysCellIdRange } RMTC-Config-r13 ::= CHOICE { release NULL, setup SEQUENCE { rmtc-Period-r13 ENUMERATED {ms40, ms80, ms160, ms320, ms640}, rmtc-SubframeOffset-r13 INTEGER(0..639) OPTIONAL, -- Need ON measDuration-r13 ENUMERATED {sym1, sym14, sym28, sym42, sym70}, ... } } StoreForward-rXY ::= SEQUENCE { t-ServiceStart-rXY TimeOffsetUTC-r17 OPTIONAL, -- Need OR t-ServiceStop-rXY TimeOffsetUTC-r17 OPTIONAL, -- Need OR t-ServiceDuration-rXY ENUMERATED {s5, s10, s15, s20, s25, s30, s35, s40, s45, s50, s55, s60, s120, s180, s240, s900} OPTIONAL -- Need OR } Tx-ResourcePoolMeasList-r14 ::= SEQUENCE (SIZE (1..maxSL-PoolToMeasure-r14)) OF SL-V2X- TxPoolReportIdentity-r14 -- ASN1STOP [0102] Discontinuous coverage information is provided in system information (e.g., SIB32) and assists the UE in estimating when the same or next satellite will be visible from its current location. The purpose is that the UE can move to RRC_IDLE/RRC_INACTIVE and enter a deep sleep state for the NTN connectivity in between the satellite passes when there is no available NTN coverage. [0103] During discontinuous coverage, in the time windows when the NTN payload is serving the area, it is assumed that there exists end-to-end connectivity. Thus, as a complement, both concepts, i.e., discontinuous coverage and store and forward operation, may be combined. In this scenario, the network provides an indication of whether the next satellite(s) that will cover the same area (in the discontinuous coverage deployment) operates or not in store and forward mode, and optionally if the next satellite(s) will follow a similar/same schedule as the present satellite, i.e., equally long periods of store and forward operation periods as the present satellite and equally long non-store and forward operation periods as the present satellite. The information/indications about a satellite that will later cover the same area as the satellite presently providing the indication/information may be further elaborated with a time schedule for switches between store and forward operation and non-store and forward operation for each satellite. P111188WO01 PCT APPLICATION 26 of 68 [0104] A UE receiving an indication of operation in store and forward mode and that the next satellite serving the same area will also operate in store and forward mode (and optionally also the same indications for subsequent satellites) may conclude that in its current location, the UE will only receive store and forward mode service and may take consequent actions. [0105] Further related to combination with discontinuous coverage, in another example where the indication is provided through broadcast signaling, the indication may be provided in SIB32 in IoT NTN, together with other information related to discontinuous coverage. The following is an ASN.1 example of this, based on the ASN.1 code for SIB32 in 3GPP TS 36.331 version 18.0.0. The added ASN.1 code is indicated with underlined text. In this example, the time when the store and forward operation will end is indicated (and absence of the indication implies that non-store and forward operation is used). SystemInformationBlockType32 information element -- ASN1START SystemInformationBlockType32-r17 ::= SEQUENCE { satelliteInfoList-r17 SatelliteInfoList-r17 OPTIONAL, -- Need OR lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ satelliteInfoList-v1800 SatelliteInfoList-v1800 OPTIONAL -- Need OR ]], [[ timeOfStopStoreAndForwardMode-rXY OPTIONAL ]] } SatelliteInfoList-r17 ::= SEQUENCE (SIZE (1..maxSat-r17)) OF SatelliteInfo-r17 SatelliteInfoList-v1800 ::= SEQUENCE (SIZE (1..maxSat-r17)) OF CarrierFreqList-v1800 SatelliteInfo-r17 ::= SEQUENCE { satelliteId-r17 INTEGER (0..255), serviceInfo-r17 SEQUENCE { tle-EphemerisParameters-r17 TLE-EphemerisParameters-r17 OPTIONAL, -- Need OR t-ServiceStart-r17 TimeOffsetUTC-r17 OPTIONAL -- Need OR }, footprintInfo-r17 SEQUENCE { referencePoint-r17 SEQUENCE { longitude-r17 INTEGER (-131072..131071), latitude-r17 INTEGER (-131072..131071) } OPTIONAL, -- Need OR elevationAngles-r17 SEQUENCE { elevationAngleRight-r17 INTEGER (-14..14), elevationAngleLeft-r17 INTEGER (-14..14) OPTIONAL -- Need OP } OPTIONAL, -- Need OR radius-r17 INTEGER (1..256) OPTIONAL -- Need OR } } CarrierFreqList-v1800 ::= SEQUENCE (SIZE (1..maxSat-r17)) OF ARFCN-ValueEUTRA timeOfStopStoreAndForwardMode-rXY ::= SEQUENCE { hsfn INTEGER (0..1023) OPTIONAL, sfn INTEGER (0..1023) } -- ASN1STOP P111188WO01 PCT APPLICATION 27 of 68 [0106] The above example may be complemented by information/indications related to store and forward operation and/or non-store and forward operation for other satellite(s) that will later cover the same area (i.e., serve cell(s) at the same area) as the satellite (payload) presently providing/signaling/broadcasting the indication. This additional information may, e.g., be included in a new complementing satelliteInfoList IE, e.g. denoted as SatelliteInfoList- vXXXX. The following is an extended ASN.1 example based on the ASN.1 code for SIB32 in 3GPP TS 36.331 version 18.0.0 and in this extended example, each time indication is provided in the form of a UTC indication instead of as a combination of HSFN and SFN as in the example above. The added ASN.1 code is indicated with underlined text. SystemInformationBlockType32 information element -- ASN1START SystemInformationBlockType32-r17 ::= SEQUENCE { satelliteInfoList-r17 SatelliteInfoList-r17 OPTIONAL, -- Need OR lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ satelliteInfoList-v1800 SatelliteInfoList-v1800 OPTIONAL -- Need OR ]], [[ timeOfStopStoreAndForwardMode-rXY TimeOffsetUTC-r17 OPTIONAL satelliteInfoList-vXXXX SatelliteInfoList—Vxxxx OPTIONAL ]] } SatelliteInfoList-r17 ::= SEQUENCE (SIZE (1..maxSat-r17)) OF SatelliteInfo-r17 SatelliteInfoList-v1800 ::= SEQUENCE (SIZE (1..maxSat-r17)) OF CarrierFreqList-v1800 SatelliteInfoList—Vxxxx ::= SEQUENCE (SIZE (1..maxSat-r17)) OF SatelliteInfo-vXXXX SatelliteInfo-r17 ::= SEQUENCE { satelliteId-r17 INTEGER (0..255), serviceInfo-r17 SEQUENCE { tle-EphemerisParameters-r17 TLE-EphemerisParameters-r17 OPTIONAL, -- Need OR t-ServiceStart-r17 TimeOffsetUTC-r17 OPTIONAL -- Need OR }, footprintInfo-r17 SEQUENCE { referencePoint-r17 SEQUENCE { longitude-r17 INTEGER (-131072..131071), latitude-r17 INTEGER (-131072..131071) } OPTIONAL, -- Need OR elevationAngles-r17 SEQUENCE { elevationAngleRight-r17 INTEGER (-14..14), elevationAngleLeft-r17 INTEGER (-14..14) OPTIONAL -- Need OP } OPTIONAL, -- Need OR radius-r17 INTEGER (1..256) OPTIONAL -- Need OR } } CarrierFreqList-v1800 ::= SEQUENCE (SIZE (1..maxSat-r17)) OF ARFCN-ValueEUTRA timeOfStopStoreAndForwardMode-rXY :;= SEQUENCE { hsfn INTEGER (0..1023) OPTIONAL, P111188WO01 PCT APPLICATION 28 of 68 timesOfSwitchFromStoreAndForwardToNonStoreAndForward SEQUENCE (SIZE (1..maxSwitchTimes- vXXXX) OF TimeOffsetUTC-r17, timesOfSwitchFromNonStoreAndForwardToStoreAndForward SEQUENCE (SIZE (1..maxSwitchTimes- vXXXX) OF TimeOffsetUTC-r17 upon operation. [0108] One example is to release RRC connections through a new RRC release cause. A UE may not support store and forward operation from a UE radio access capability standpoint. In addition, a UE may operate an application with traffic patterns not suitable for the store and forward operation. Yet in another case, the network may need to release a group of UEs in connected mode due to capacity limitations when operating in store and forward, e.g., running out of memory due to not being able to buffer data further. These are some examples for cases where network may need to release the RRC connection with a specific UE due to the start of a store and forward period. [0109] Upon reception of the RRC release message with the new release cause related to store and forward, a UE will refrain to re-establish the RRC connection with the cell at least until the time when the store and forward operation finishes, i.e., the satellite payload re-gains connectivity with the NTN ground station or another satellite through ISL. [0110] The following is an example of a new RRC connection release cause included in the RRCConnectionRelease message in IoT NTN (using RRCConnectionRelease ASN.1 definition in 3GPP TS 36.331 version 18.0.0 as the baseline). For illustrative purposes, this example relates to the indication using a single bit. -- ASN1START RRCConnectionRelease ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, -- -- P111188WO01 PCT APPLICATION 29 of 68 RRCConnectionRelease-v890-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING (CONTAINING RRCConnectionRelease- v9e0-IEs) OPTIONAL, nonCriticalExtension RRCConnectionRelease-v920-IEs OPTIONAL } -- Late non critical extensions RRCConnectionRelease-v9e0-IEs ::= SEQUENCE { redirectedCarrierInfo-v9e0 -- Cond NoRedirect-r8 idleModeMobilityControlInfo-v9e0 -- Cond IdleInfoEUTRA nonCriticalExtension } -- Regular non critical extensions RRCConnectionRelease-v920-IEs ::= cellInfoList-r9 geran-r9 utra-FDD-r9 utra-TDD-r9 ..., utra-TDD-r10 } Redirection nonCriticalExtension } RRCConnectionRelease-v1020-IEs ::= extendedWaitTime-r10 nonCriticalExtension OPTIONAL } RRCConnectionRelease-v1320-IEs::= resumeIdentity-r13 Need OR nonCriticalExtension } RRCConnectionRelease-v1530-IEs ::= drb-ContinueROHC-r15 UP-EDTorPUR nextHopChainingCount-r15 EarlySec measIdleConfig-r15 rrc-InactiveConfig-r15 cn-Type-r15 nonCriticalExtension } RRCConnectionRelease-v1540-IEs ::= waitTime nonCriticalExtension } RRCConnectionRelease-v15b0-IEs ::= noLastCellUpdate-r15 nonCriticalExtension } RRCConnectionRelease-v1610-IEs ::= fullI-RNTI-r16 shortI-RNTI-r16 ShortI- pur-Config-r16 ON rrc-InactiveConfig-v1610 BLCE-IDLEeDRX releaseIdleMeasConfig-r16 altFreqPriorities-r16 ON t323-r16 P111188WO01 PCT APPLICATION 30 of 68 min720} OPTIONAL, -- Need OR nonCriticalExtension RRCConnectionRelease-v1650-IEs OPTIONAL } Redirection2 nonCriticalExtension SEQUENCE {} OPTIONAL } ReleaseCause ::= ENUMERATED {loadBalancingTAUrequired, other, cs-FallbackHighPriority-v1020, rrc- Suspend-v1320, storeAndForward-vXY} RedirectedCarrierInfo ::= eutra geran CarrierFreqsGERAN, utra-FDD ARFCN-ValueUTRA, utra-TDD ARFCN-ValueUTRA, cdma2000-HRPD CarrierFreqCDMA2000, cdma2000-1xRTT CarrierFreqCDMA2000, ..., utra-TDD-r10 CarrierFreqListUTRA-TDD-r10, nr-r15 CarrierInfoNR-r15, nr-r17 CarrierInfoNR-r17 } RedirectedCarrierInfo-v9e0 ::= SEQUENCE { eutra-v9e0 ARFCN-ValueEUTRA-v9e0 } RRC-InactiveConfig-r15::= SEQUENCE { fullI-RNTI-r15 I-RNTI-r15, shortI-RNTI-r15 ShortI-RNTI-r15, ran-PagingCycle-r15 ENUMERATED { rf32, rf64, rf128, rf256} OPTIONAL, -- Need OR ran-NotificationAreaInfo-r15 RAN-NotificationAreaInfo-r15 OPTIONAL, --Need ON periodic-RNAU-timer-r15 ENUMERATED {min5, min10, min20, min30, min60, min120, min360, min720} OPTIONAL, --Need OR nextHopChainingCount-r15 NextHopChainingCount OPTIONAL, --Cond INACTIVE dummy SEQUENCE{} OPTIONAL } RRC-InactiveConfig-v1610::= SEQUENCE { ran-PagingCycle-v1610 ENUMERATED {rf512, rf1024} } RAN-NotificationAreaInfo-r15 ::= CHOICE { cellList PLMN-RAN-AreaCellList-r15, ran-AreaConfigList PLMN-RAN-AreaConfigList-r15 } PLMN-RAN-AreaCellList-r15 ::= SEQUENCE (SIZE (1..maxPLMN-r15)) OF PLMN-RAN-AreaCell-r15 PLMN-RAN-AreaCell-r15 ::= SEQUENCE { plmn-Identity-r15 PLMN-Identity OPTIONAL, ran-AreaCells-r15 SEQUENCE (SIZE (1..32)) OF CellIdentity } PLMN-RAN-AreaConfigList-r15 ::= SEQUENCE (SIZE (1..maxPLMN-r15)) OF PLMN-RAN-AreaConfig-r15 PLMN-RAN-AreaConfig-r15 ::= SEQUENCE { plmn-Identity-r15 PLMN-Identity OPTIONAL, ran-Area-r15 SEQUENCE (SIZE (1..16)) OF RAN-AreaConfig-r15 } RAN-AreaConfig-r15 ::= SEQUENCE { trackingAreaCode-5GC-r15 TrackingAreaCode-5GC-r15, ran-AreaCodeList-r15 SEQUENCE (SIZE (1..32)) OF RAN-AreaCode-r15 OPTIONAL --Need OR } P111188WO01 PCT APPLICATION 31 of 68 CarrierFreqListUTRA-TDD-r10 ::= SEQUENCE (SIZE (1..maxFreqUTRA-TDD-r10)) OF ARFCN- ValueUTRA IdleModeMobilityControlInfo ::= SEQUENCE { freqPriorityListEUTRA FreqPriorityListEUTRA OPTIONAL, -- Need ON freqPriorityListGERAN FreqsPriorityListGERAN OPTIONAL, -- Need ON freqPriorityListUTRA-FDD FreqPriorityListUTRA-FDD OPTIONAL, -- Need ON freqPriorityListUTRA-TDD FreqPriorityListUTRA-TDD OPTIONAL, -- Need ON bandClassPriorityListHRPD BandClassPriorityListHRPD OPTIONAL, -- Need ON bandClassPriorityList1XRTT BandClassPriorityList1XRTT OPTIONAL, -- Need ON t320 ENUMERATED { min5, min10, min20, min30, min60, min120, min180, spare1} OPTIONAL, -- Need OR ..., [[ freqPriorityListExtEUTRA-r12 FreqPriorityListExtEUTRA-r12 OPTIONAL -- Need ON ]], [[ freqPriorityListEUTRA-v1310 FreqPriorityListEUTRA-v1310 OPTIONAL, -- Need ON freqPriorityListExtEUTRA-v1310 FreqPriorityListExtEUTRA-v1310 OPTIONAL -- Need ON ]], [[ freqPriorityListNR-r15 FreqPriorityListNR-r15 OPTIONAL -- Need ON ]] } IdleModeMobilityControlInfo-v9e0 ::= SEQUENCE { freqPriorityListEUTRA-v9e0 SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityEUTRA- v9e0 cellReselectionSubPriority-r13 CellReselectionSubPriority-r13 OPTIONAL -- Need ON } P111188WO01 PCT APPLICATION 32 of 68 FreqPriorityListNR-r15 ::= SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityNR-r15 FreqPriorityNR-r15 ::= SEQUENCE { carrierFreq-r15 ARFCN-ValueNR-r15, cellReselectionPriority-r15 CellReselectionPriority, cellReselectionSubPriority-r15 CellReselectionSubPriority-r13 OPTIONAL -- Need OR } FreqsPriorityListGERAN ::= SEQUENCE (SIZE (1..maxGNFG)) OF FreqsPriorityGERAN FreqsPriorityGERAN ::= SEQUENCE { carrierFreqs CarrierFreqsGERAN, cellReselectionPriority CellReselectionPriority } FreqPriorityListUTRA-FDD ::= SEQUENCE (SIZE (1..maxUTRA-FDD-Carrier)) OF FreqPriorityUTRA-FDD FreqPriorityUTRA-FDD ::= SEQUENCE { carrierFreq ARFCN-ValueUTRA, cellReselectionPriority CellReselectionPriority } FreqPriorityListUTRA-TDD ::= SEQUENCE (SIZE (1..maxUTRA-TDD-Carrier)) OF FreqPriorityUTRA-TDD FreqPriorityUTRA-TDD ::= SEQUENCE { carrierFreq ARFCN-ValueUTRA, cellReselectionPriority CellReselectionPriority } BandClassPriorityListHRPD ::= SEQUENCE (SIZE (1..maxCDMA-BandClass)) OF BandClassPriorityHRPD BandClassPriorityHRPD ::= SEQUENCE { bandClass BandclassCDMA2000, cellReselectionPriority CellReselectionPriority } BandClassPriorityList1XRTT ::= SEQUENCE (SIZE (1..maxCDMA-BandClass)) OF BandClassPriority1XRTT BandClassPriority1XRTT ::= SEQUENCE { bandClass BandclassCDMA2000, cellReselectionPriority CellReselectionPriority } CellInfoListGERAN-r9 ::= SEQUENCE (SIZE (1..maxCellInfoGERAN-r9)) OF CellInfoGERAN-r9 CellInfoGERAN-r9 ::= SEQUENCE { physCellId-r9 PhysCellIdGERAN, carrierFreq-r9 CarrierFreqGERAN, systemInformation-r9 SystemInfoListGERAN } CarrierInfoNR-r15 ::= SEQUENCE { carrierFreq-r15 ARFCN-ValueNR-r15, subcarrierSpacingSSB-r15 ENUMERATED {kHz15, kHz30, kHz120, kHz240}, smtc-r15 MTC-SSB-NR-r15 OPTIONAL -- Need OP } CarrierInfoNR-r17 ::= SEQUENCE { carrierFreq-r17 ARFCN-ValueNR-r15, subcarrierSpacingSSB-r17 ENUMERATED {kHz15, kHz30, kHz120, kHz240, kHz480, spare1}, smtc-r17 MTC-SSB-NR-r15 OPTIONAL -- Need OP } CellInfoListUTRA-FDD-r9 ::= SEQUENCE (SIZE (1..maxCellInfoUTRA-r9)) OF CellInfoUTRA- P111188WO01 PCT APPLICATION 33 of 68 FDD-r9 CellInfoUTRA-FDD-r9 ::= SEQUENCE { physCellId-r9 PhysCellIdUTRA-FDD, utra-BCCH-Container-r9 OCTET STRING } CellInfoListUTRA-TDD-r9 ::= SEQUENCE (SIZE (1..maxCellInfoUTRA-r9)) OF CellInfoUTRA- TDD-r9 CellInfoUTRA-TDD-r9 ::= SEQUENCE { physCellId-r9 PhysCellIdUTRA-TDD, utra-BCCH-Container-r9 OCTET STRING } CellInfoListUTRA-TDD-r10 ::= SEQUENCE (SIZE (1..maxCellInfoUTRA-r9)) OF CellInfoUTRA- TDD-r10 CellInfoUTRA-TDD-r10 ::= SEQUENCE { physCellId-r10 PhysCellIdUTRA-TDD, carrierFreq-r10 ARFCN-ValueUTRA, utra-BCCH-Container-r10 OCTET STRING } -- ASN1STOP [0111] Some embodiments include prioritization between different uplink traffic. When an area is served by NTN payload(s) operating in store and forward mode and satellite(s) operating in non-store and forward mode, the satellite(s) operating in non-store and forward mode may prioritize scheduling of uplink traffic from a UE where the uplink traffic is only allowed (or only suitable) to be transmitted when the UE is served by satellite(s) operating in non-store and forward mode. [0112] The satellite(s) operating in non-store and forward mode may indicate that only uplink traffic from certain logical channel(s) may be transmitted, where the logical channel(s) may (only) serve uplink traffic that is allowed (or suitable) to be transmitted when the UE is served by satellite(s) operating in non-store and forward mode. Alternatively, it may indicate that the logical channel(s) shall be prioritized (e.g., the traffic from those logical channel(s) shall be transmitted first). Such indication may be transmitted in system information, dedicated RRC signaling and/or downlink control information (DCI) scheduling dynamic grant. [0113] Such prioritization may be performed with UEs capable of store and forward operation. These UEs can transmit when served either by satellite(s) supporting store and forward or by satellite(s) not supporting store and forward. When a UE is served by a satellite(s) operating in store and forward mode, the UE can only transmit uplink traffic that is allowed (or suitable) for the store and forward mode. Thus, the UE cannot transmit uplink traffic not allowed (or not suitable) to be transmitted when the UE is served by satellite(s) operating in non-store and forward mode, i.e., different traffic may be transmitted when served by satellites operating in P111188WO01 PCT APPLICATION 34 of 68 different modes, in which case the proposed prioritization is needed. To enable this the UE may report its capability regarding supporting store and forward operation to the network. [0114] Similarly, the satellite(s) operating in store and forward mode may indicate that only uplink traffic from certain logical channel(s) can be transmitted, where the logical channel(s) may (only) serve uplink traffic that is allowed (or suitable) to be transmitted when the UE is served by satellite(s) operating in store and forward mode. Such indication may be transmitted in system information, dedicated RRC signaling and/or DCI scheduling dynamic grant. [0115] Some embodiments include handling of traffic in transmission buffer during handover. If the UE is configured to handover from an NTN payload operating in non-store and forward mode to an NTN payload operating in store and forward mode, the source gNB does not forward the packet data convergence protocol (PDCP) protocol data units (PDUs) carrying downlink traffic that are not allowed (or not suitable) to be transmitted by NTN payload operating in store and forward mode to the target NTN payload, rather it discards those PDCP PDUs. Similarly, the UE discards the buffered PDCP PDUs carrying uplink traffic that are not allowed (or not suitable) to be transmitted to NTN payload operating in store and forward mode. [0116] Some embodiments include validity of store and forward operation mode information. In one embodiment, the UE may assume the store and forward related information acquired via NTN SIB31 to be valid even if the uplink synchronization validity duration has expired. [0117] In another embodiment, the UE may assume the store and forward related information acquired via NTN SIB31 to be valid if the one or more time spans indicated for store and forward have not expired even if the uplink synchronization validity duration has expired. [0118] In another embodiment, the UE may assume the store and forward related information acquired via NTN SIB31 to be valid if the one or more time spans indicated for store and forward have not expired even if the uplink synchronization validity duration has expired. However, if the network provides the UE with updated store and forward parameters, then the UE discards the previous value of the updated store and forward parameters regardless of its uplink synchronization validity duration. [0119] For example, if the UE has determined (based on the store and forward related parameters acquired via NTN-SIB) that the store and forward operation is expected to last for another four seconds at the time of expiration of its validity duration, the UE may consider its P111188WO01 PCT APPLICATION 35 of 68 estimate to be valid. After the lapse of four seconds, the UE will need to reacquire store and forward related parameters. [0120] Some embodiments include UE actions upon detection of store and forward operation. As previously stated, the presence of store and forward operations has an impact on delay, QoS, network congestion, and mobility management. Upon detection of the network indication for store and forward operation, the UE may perform one or more of the following actions. [0121] The UE may have a choice of service/application or type of communication to activate, e.g., when the satellite/network indicates store and forward operation, refraining from initiating communication of a type that would not work, or would suffer severely from being subject to store and forward. This choice may also take into account the time until the store and forward operation will end, e.g., such that if this time is short enough, the UE may initiate communication of a certain type, but will refrain from initiating communication of that type if the time until the store and forward operation ends is too long, e.g., longer than a certain threshold time. [0122] The UE may choose a network. If the indication tells a UE that the serving cell or the next satellite covering the area will also operate in store and forward mode, the UE may conclude that in its present location, it can only receive store and forward service from the NTN, and may, consequently, e.g., choose to perform any of the following actions: o Connect to another type of network access without a store and forward operation such as terrestrial network (if available). o Modify the criterion used for cell reselection algorithms, described in TS 36.304 V18.0.0 (e.g., S-criterion or R-criterion) by the application of a relative and temporary offset to the evaluation conditions to prioritize the (re)-selection to neighbor cells without a store and forward operation. In an alternative, the offset may be configured by the network via broadcast or dedicated signaling. o Initiate search for another network from which the UE can receive service, or choose to put its communication parts, e.g., hardware for cellular communication, or hardware for NTN communication, in an energy saving state. [0123] The UE may inform the network. There are cases when a service or application running on the UE may not be well-suited for store and forward operation. Among the possible reasons are the necessity of real-time communication, the request to send a large amount of data that P111188WO01 PCT APPLICATION 36 of 68 may compromise the buffering mechanism of the NTN payload, or the incompatibility with the long delays associated with store and forward operation. In this scenario, the UE may notify the network via a RRC message such as UEAssistanceInformation with a new field parameter or the extension of the interpretation of an existing one such as TrafficPatternInfo-r14. [0124] The UE may optimize measurements. A UE may consider the store and forward operation with the configured RRC_CONNECTED mode and RRC_IDLE/RRC_INACTIVE mode measurements. Depending on the traffic profiles, the UE may skip or refrain from performing neighbor cell measurements for those cells or satellites with present or future store and forward operation. [0125] Some embodiments use satellite position indications instead of time indications/timestamps. In any of the previously described embodiments where a time indication, e.g. a timestamp, e.g. a UTC or a combination of HSFN and SFN, is used to indicate the end or start of a period of store and forward operation, or the end or start of a period of non- store and forward operation, or the time of switching between store and forward operation and non-store and forward operation (or vice versa) for a satellite (payload), the time indication may in alternative embodiments be replaced by an indication of a satellite position, and the UE may, if desired, translate this position indication into a time indication by using the ephemeris data associated with the concerned satellite (payload) (i.e., the indicated time is the time at which the concerned satellite will be located at the indicated position). [0126] FIGURE 6 illustrates an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections. [0127] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, P111188WO01 PCT APPLICATION 37 of 68 cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0128] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 112 and/or with other network nodes or equipment in the telecommunication network 102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 102. [0129] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). [0130] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and/or the telecommunication network 102 and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics P111188WO01 PCT APPLICATION 38 of 68 functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. [0131] As a whole, the communication system 100 of FIGURE 6 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. [0132] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs. [0133] In some examples, the UEs 112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC). [0134] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and/or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, P111188WO01 PCT APPLICATION 39 of 68 content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices. [0135] The hub 114 may have a constant/persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and/or schedule between the hub 114 and UEs (e.g., UE 112c and/or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and/or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 110b. In other embodiments, the hub 114 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [0136] FIGURE 7 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, P111188WO01 PCT APPLICATION 40 of 68 desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. [0137] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). [0138] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input/output interface 206, a power source 208, a memory 210, a communication interface 212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 7. 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. [0139] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor P111188WO01 PCT APPLICATION 41 of 68 (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs). [0140] In the example, the input/output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. [0141] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and/or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied. [0142] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, P111188WO01 PCT APPLICATION 42 of 68 or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems. [0143] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium. [0144] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and/or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately. [0145] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based P111188WO01 PCT APPLICATION 43 of 68 communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. [0146] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). [0147] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. [0148] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented P111188WO01 PCT APPLICATION 44 of 68 Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 200 shown in FIGURE 7. [0149] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. [0150] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. [0151] FIGURE 8 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). [0152] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or P111188WO01 PCT APPLICATION 45 of 68 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). [0153] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). [0154] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300. P111188WO01 PCT APPLICATION 46 of 68 [0155] The processing circuitry 302 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 300 components, such as the memory 304, to provide network node 300 functionality. [0156] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 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 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units. [0157] The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and/or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated. [0158] The communication interface 306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 306 comprises port(s)/terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments P111188WO01 PCT APPLICATION 47 of 68 a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and/or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0159] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown). [0160] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port. [0161] The antenna 310, communication interface 306, and/or the processing circuitry 302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 310, the communication interface 306, and/or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being P111188WO01 PCT APPLICATION 48 of 68 performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment. [0162] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. [0163] Embodiments of the network node 300 may include additional components beyond those shown in FIGURE 8 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300. [0164] FIGURE 9 is a block diagram of a host 400, which may be an embodiment of the host 116 of FIGURE 6, in accordance with various aspects described herein. As used herein, the host 400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 400 may provide one or more services to one or more UEs. [0165] The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a network interface 408, a power source 410, and a memory 412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 3 and 4, such that the descriptions thereof are generally applicable to the corresponding components of host 400. P111188WO01 PCT APPLICATION 49 of 68 [0166] The memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE. Embodiments of the host 400 may utilize only a subset or all of the components shown. The host application programs 414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 400 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. [0167] FIGURE 10 is a block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. [0168] Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. P111188WO01 PCT APPLICATION 50 of 68 [0169] Hardware 504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508. [0170] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. [0171] In the context of NFV, a VM 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502. [0172] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more P111188WO01 PCT APPLICATION 51 of 68 appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units. [0173] FIGURE 11 shows a communication diagram of a host 602 communicating via a network node 604 with a UE 606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 112a of FIGURE 6 and/or UE 200 of FIGURE 7), network node (such as network node 110a of FIGURE 6 and/or network node 300 of FIGURE 8), and host (such as host 116 of FIGURE 6 and/or host 400 of FIGURE 9) discussed in the preceding paragraphs will now be described with reference to FIGURE 11. [0174] Like host 400, embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory. The host 602 also includes software, which is stored in or accessible by the host 602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 650. [0175] The network node 604 includes hardware enabling it to communicate with the host 602 and UE 606. The connection 660 may be direct or pass through a core network (like core network 106 of FIGURE 6) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. [0176] The UE 606 includes hardware and software, which is stored in or accessible by UE 606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 606 with the support of the host 602. In the host 602, an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 650 may transfer both the request P111188WO01 PCT APPLICATION 52 of 68 data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 650. [0177] The OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606. The connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawn abstractly to illustrate the communication between the host 602 and the UE 606 via the network node 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices. [0178] As an example of transmitting data via the OTT connection 650, in step 608, the host 602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 606. In other embodiments, the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction. In step 610, the host 602 initiates a transmission carrying the user data towards the UE 606. The host 602 may initiate the transmission responsive to a request transmitted by the UE 606. The request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606. The transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 614, the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602. [0179] In some examples, the UE 606 executes a client application which provides user data to the host 602. The user data may be provided in reaction or response to the data received from the host 602. Accordingly, in step 616, the UE 606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604. In step 620, in accordance with the teachings of the embodiments described throughout P111188WO01 PCT APPLICATION 53 of 68 this disclosure, the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602. In step 622, the host 602 receives the user data carried in the transmission initiated by the UE 606. [0180] One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the delay to directly activate an SCell by RRC and power consumption of user equipment and thereby provide benefits such as reduced user waiting time and extended battery lifetime. [0181] In an example scenario, factory status information may be collected and analyzed by the host 602. As another example, the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 602 may store surveillance video uploaded by a UE. As another example, the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 602 may be used for energy pricing, 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. [0182] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 650 between the host 602 and UE 606, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 602 and/or UE 606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and P111188WO01 PCT APPLICATION 54 of 68 practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc. [0183] FIGURE 12 is a flowchart illustrating an example method 1200 in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 12 may be performed by UE 200 described with respect to FIGURE 7. The wireless device is capable of being served by a non-terrestrial network. [0184] The method begins at step 1212, where the wireless device (e.g., UE 200) receives via a system information message an indication from a network node indicating that a serving NTN network node is operating or will operate in store and forward mode. For example, particular embodiments include an indication, i.e., a field, parameter, or an implicit statement in broadcast or dedicated signaling of the presence of store and forward operation for serving and/or neighbor frequency, cells, or satellites. [0185] In particular embodiments, the indication that the serving NTN network node is operating or will operate in store and forward mode is associated with a time for store and forward operation. For example, a time span, either absolute (e.g., UTC) or relative (e.g., seconds, SFN, H-SFN) is used to indicate when the store and forward operation is used. The time span may indicate when end-to-end connectivity, i.e., feeder link connection through ground station or ISL is available. The time indication may refer to the remaining time with or without end-to-end connectivity, i.e., feeder link connection through ground station or ISL is available. The time span may refer to the current time, i.e. when the indication is sent, or a time span in the near future. Additional examples of time intervals are described with respect to the embodiments and examples described herein. [0186] In particular embodiments, the indication that the serving NTN network node is operating or will operate in store and forward mode is associated with a location for store and forward operation. For example, the wireless device can estimate whether a network node is operating or will operate in store and forward mode based on geographical location of the satellite, the wireless device, or any combination. Ephemeris data may be used as part of the estimate. P111188WO01 PCT APPLICATION 55 of 68 [0187] In particular embodiments, receiving the system information message comprises receiving a broadcasted system information message (e.g., SIB) comprising the indication or receiving a dedicated system information message comprising the indication. [0188] In particular embodiments, the indication indicates that the serving NTN network node is operating in store and forward mode for all wireless devices that support operation with network nodes operating in store and forward mode. In particular embodiments, the indication indicates that the serving NTN network node is operating in store and forward mode only for wireless devices in connected mode. [0189] Additional information regarding the indication is described with respect to the embodiments and examples described herein. [0190] At step 1214, the wireless device performs an operation with respect to the serving NTN network node based on the indication. [0191] In particular embodiments, performing the operation comprises activating or deactivating services or applications based on the received indication. For example, when the received indication indicates store and forward operation, the wireless device may refrain from initiating communication of a type that would not work or would suffer severely from being subject to store and forward operation. The determination may account for a time until the store and forward operation will end, e.g., such that if this time is short enough, the UE may initiate communication of a certain type, but will refrain from initiating communication of that type if the time until the store and forward operation ends is too long, e.g., longer than a certain threshold time. [0192] In particular embodiments, performing the operation comprises performing cell selection or reselection based on the received indication. For example, the wireless device may reselect to another network without store and forward operation, such as a terrestrial network. [0193] In particular embodiments, performing the operation comprises modifying a measurement configuration based on the received notification. For example, depending on traffic profiles, the wireless device may skip or refrain from performing neighbor cell measurements for cells or satellites with present or future store and forward operation. [0194] In particular embodiments, performing the operation comprises informing the network that the wireless device is performing a service or application that is not well-suited for store and forward operation. P111188WO01 PCT APPLICATION 56 of 68 [0195] Additional operations are described with respect to the embodiments and examples described herein. [0196] Modifications, additions, or omissions may be made to method 1200 of FIGURE 12. Additionally, one or more steps in the method of FIGURE 12 may be performed in parallel or in any suitable order. [0197] FIGURE 13 is a flowchart illustrating an example method 1300 in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 13 may be performed by network node 300 described with respect to FIGURE 8. The network node is capable of operating within a non-terrestrial network. [0198] The method begins at step 1312, where the network node (e.g., network node 300) transmits via a system information message an indication to a wireless device indicating that a serving NTN network node is operating or will operate in store and forward mode. In particular embodiments, transmitting the system information message comprises broadcasting the system information message (e.g., SIB) comprising the indication or transmitting a dedicated system information message comprising the indication. The indication is described in more detail with respect to Figure 12 and with respect to the embodiments and examples described herein. [0199] At step 1314, the network node and performs an operation with respect to the wireless device based on the indication. In particular embodiments, performing the operation comprises transmitting a connection release message to the wireless device, wherein a release cause in the connection release message is related to store and forward operation; and/or prioritizing uplink traffic based on the indication. Additional operations are described with respect to the embodiments and examples described herein. [0200] Modifications, additions, or omissions may be made to method 1300 of FIGURE 13. Additionally, one or more steps in the method of FIGURE 13 may be performed in parallel or in any suitable order. [0201] Modifications, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the invention. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order. [0202] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the P111188WO01 PCT APPLICATION 57 of 68 included descriptions, will be able to implement appropriate functionality without undue experimentation. [0203] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described. [0204] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below. [0205] Some example embodiments follow. Group A Embodiments 1. A method performed by a wireless device, the method comprising: − receiving an indication from a network node indicating that one or more network nodes will operate in store and forward mode; and − performing an operation with respect to one of the one or more network nodes based on the indication. 2. The method of the previous embodiment, wherein the indication that the one or more network nodes will operate in store and forward mode is associated with time interval for store and forward operation. 3. The method of any one of the previous embodiments, wherein the indication that the one or more network nodes will operate in store and forward mode is associated with a location for store and forward operation. 4. The method of any one of the previous embodiments, wherein the indication comprises any of the indications described in the embodiments and examples listed herein. P111188WO01 PCT APPLICATION 58 of 68 5. The method of any one of the previous embodiments, the operation comprises any of the operations described in the embodiments and examples listed herein. 6. A method performed by a wireless device, the method comprising: − any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. 7. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above. 8. The method of any of the previous two embodiments, further comprising: − providing user data; and − forwarding the user data to a host computer via the transmission to the base station. Group B Embodiments 9. A method performed by a base station, the method comprising: − transmitting an indication to a wireless device indicating that one or more network nodes will operate in store and forward mode. 10. A method performed by a base station, the method comprising: − any of the steps, features, or functions described above with respect to base stations, either alone or in combination with other steps, features, or functions described above. 11. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above. 12. The method of any of the previous embodiments, further comprising: − obtaining user data; and − forwarding the user data to a host computer or a wireless device. Group C Embodiments 13. A mobile terminal comprising: P111188WO01 PCT APPLICATION 59 of 68 − processing circuitry configured to perform any of the steps of any of the Group A embodiments; and − power supply circuitry configured to supply power to the wireless device. 14. A base station comprising: − processing circuitry configured to perform any of the steps of any of the Group B embodiments; − power supply circuitry configured to supply power to the wireless device. 15. A user equipment (UE) comprising: − an antenna configured to send and receive wireless signals; − radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; − the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; − an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; − an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and − a battery connected to the processing circuitry and configured to supply power to the UE. 16. A communication system including a host computer comprising: − processing circuitry configured to provide user data; and − a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), − wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. 17. The communication system of the pervious embodiment further including the base P111188WO01 PCT APPLICATION 60 of 68 station. 18. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. 19. The communication system of the previous 3 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and − the UE comprises processing circuitry configured to execute a client application associated with the host application. 20. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: − at the host computer, providing user data; and − at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments. 21. The method of the previous embodiment, further comprising, at the base station, transmitting the user data. 22. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application. 23. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments. 24. A communication system including a host computer comprising: − processing circuitry configured to provide user data; and − a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), − wherein the UE comprises a radio interface and processing circuitry, the UE’s P111188WO01 PCT APPLICATION 61 of 68 components configured to perform any of the steps of any of the Group A embodiments. 25. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE. 26. The communication system of the previous 2 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and − the UE’s processing circuitry is configured to execute a client application associated with the host application. 27. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: − at the host computer, providing user data; and − at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments. 28. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station. 29. A communication system including a host computer comprising: − communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, − wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments. 30. The communication system of the previous embodiment, further including the UE. 31. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer P111188WO01 PCT APPLICATION 62 of 68 the user data carried by a transmission from the UE to the base station. 32. The communication system of the previous 3 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application; and − the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. 33. The communication system of the previous 4 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and − the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. 34. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: − at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. 35. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station. 36. The method of the previous 2 embodiments, further comprising: − at the UE, executing a client application, thereby providing the user data to be transmitted; and − at the host computer, executing a host application associated with the client application. 37. The method of the previous 3 embodiments, further comprising: − at the UE, executing a client application; and − at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with P111188WO01 PCT APPLICATION 63 of 68 the client application, − wherein the user data to be transmitted is provided by the client application in response to the input data. 38. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. 39. The communication system of the previous embodiment further including the base station. 40. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. 41. The communication system of the previous 3 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application; − the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer. 42. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: − at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. 43. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE. 44. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Claims

P111188WO01 PCT APPLICATION 64 of 68 CLAIMS: 1. A method performed by a wireless device, the method comprising: receiving (1212) via a system information message an indication from a network node indicating that a serving non-terrestrial network (NTN) network node is operating or will operate in store and forward mode; and performing (1214) an operation with respect to the serving NTN network node based on the indication. 2. The method of claim 1, wherein the indication that the serving NTN network node is operating or will operate in store and forward mode is associated with a time for store and forward operation. 3. The method of any one of claims 1-2, wherein the indication that the serving NTN network node is operating or will operate in store and forward mode is associated with a location for store and forward operation. 4. The method of any one of claims 1-3, wherein receiving the system information message comprises receiving a broadcasted system information message. 5. The method of any one of claims 1-3, wherein receiving the system information message comprises receiving a dedicated system information message. 6. The method of any one of claims 1-5, wherein the indication indicates that the serving NTN network node is operating in store and forward mode for all wireless devices that support operation with network nodes operating in store and forward mode. 7. The method of any one of claims 1-5, wherein the indication indicates that the serving NTN network node is operating in store and forward mode only for wireless devices in connected mode. 8. The method of any one of claims 1-7, wherein performing the operation P111188WO01 PCT APPLICATION 65 of 68 comprises activating or deactivating services or applications based on the received indication. 9. The method of any one of claims 1-7, wherein performing the operation comprises refraining from transmitting traffic that is unsuitable for store and forward operation based on the received indication. 10. The method of any one of claims 1-7, wherein performing the operation comprises performing cell selection or reselection based on the received indication. 11. The method of any one of claims 1-7, wherein performing the operation comprises modifying a measurement configuration based on the received notification. 12. The method of any one of claims 1-11, wherein performing the operation comprises informing the network that the wireless device is performing a service or application that is not well-suited for store and forward operation 13. A computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the steps of any one of claims 1-12. 14. A wireless device (200) comprising processing circuitry (202) operable to: receive via a system information message an indication from a network node (300) indicating that a serving non-terrestrial network (NTN) network node is operating or will operate in store and forward mode; and perform an operation with respect to the NTN network node based on the indication. 15. The wireless device of claim 14, the processing circuitry further operable to perform the steps of any one of claims 2-12. P111188WO01 PCT APPLICATION 66 of 68 16. A method performed by a network node, the method comprising: transmitting (1312) via a system information message an indication to a wireless device indicating that a serving non-terrestrial network (NTN) network node is operating or will operate in store and forward mode; and performing (1314) an operation with respect to the wireless device based on the indication. 17. The method of claim 16, wherein the indication that the serving NTN network node is operating or will operate in store and forward mode is associated with a time for store and forward operation. 18. The method of any one of claims 16-17, wherein the indication that the serving NTN network node is operating or will operate in store and forward mode is associated with a location for store and forward operation. 19. The method of any one of claims 16-18, wherein transmitting the system information message comprises broadcasting the system information message. 20. The method of any one of claims 16-18, wherein transmitting the system information message comprises transmitting a dedicated system information message. 21. The method of any one of claims 16-20, wherein the indication indicates that the serving NTN network node is operating in store and forward mode for all wireless devices that support operation with network nodes operating in store and forward mode. 22. The method of any one of claims 16-20, wherein the indication indicates that the serving NTN network node is operating in store and forward mode only for wireless devices in connected mode. 23. The method of any one of claims 16-22, wherein performing the operation comprises transmitting (1316) a connection release message to the wireless device, wherein a release cause in the connection release message is related to store and forward operation. P111188WO01 PCT APPLICATION 67 of 68 24. The method of any one of claims 16-22, wherein performing the operation comprises prioritizing uplink traffic based on the indication. 25. A computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the steps of any one of claims 16-24. 26. A network node (300) comprising processing circuitry (302) operable to: transmit via a system information message an indication to a wireless device (200) indicating that a serving non-terrestrial network (NTN) network node is operating or will operate in store and forward mode; and perform an operation with respect to the wireless device based on the indication. 27. The network node of claim 26, the processing circuitry further operable to perform the steps of any one of claims 17-24.
PCT/IB2025/053601 2024-04-05 2025-04-04 Indication of store and forward for ntn Pending WO2025210593A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463575383P 2024-04-05 2024-04-05
US63/575,383 2024-04-05

Publications (1)

Publication Number Publication Date
WO2025210593A1 true WO2025210593A1 (en) 2025-10-09

Family

ID=95474655

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2025/053601 Pending WO2025210593A1 (en) 2024-04-05 2025-04-04 Indication of store and forward for ntn

Country Status (1)

Country Link
WO (1) WO2025210593A1 (en)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
XINGYA SHEN ET AL: "Discussion on support of Store&Forward", vol. RAN WG2, no. Changsha, Hunan Province, CN; 20240415 - 20240419, 3 April 2024 (2024-04-03), XP052584423, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_125bis/Docs/R2-2402454.zip R2-2402454.docx> [retrieved on 20240403] *

Similar Documents

Publication Publication Date Title
US20250097811A1 (en) Systems and methods for reducing system information acquisition during cell reselection in a non-terrestrial network
EP4381829A1 (en) Global navigation satellite system data validity in non-terrestrial networks
US20250142505A1 (en) Method and Apparatus for SSB Measurement Time Configuration in Communication Network
US20250106811A1 (en) Location information provisioning
US20250159654A1 (en) Paging and system information (si) procedures under adjusted synchronization signal block measurement time configuration (smtc) in non-terrestrial networks (ntn)
US20250287461A1 (en) Ephemeris data for conditional handover
US20250227521A1 (en) Minimization of Drive Testing Configuration
WO2024035316A1 (en) Methods, apparatus and computer-readable media for determining a timing advance in a non-terrestrial network
US20240406760A1 (en) Minimization of Drive Testing for Non-Terrestrial Networks
WO2024035301A1 (en) Location information for mobility in ntn
US20250175242A1 (en) Configuration of periodic behavior of spatial filter in repeater-assisted networks
WO2024171139A1 (en) Activation of measurement gaps for ntn
US20250212036A1 (en) Joint-repeater-ue beam report in repeater-assisted networks
WO2025210593A1 (en) Indication of store and forward for ntn
US20250261092A1 (en) Systems and methods for system information accumulation in internet of things non-terrestrial networks
US20250185000A1 (en) Latency saving design and trigger for mac ce for measurement gap
EP4666644A1 (en) Activation of measurement gaps for ntn
WO2025177172A1 (en) Timing advance modification for non-terrestrial networks
WO2024035965A1 (en) Methods for si accumulation in iot ntn with explicit and implicit epoch time indication
WO2025104275A1 (en) Ssb measurement time configuration for cell switching terminal device provided by a movable base station/relay
WO2025219761A1 (en) Mdt areas scopes for ntn
EP4566194A1 (en) Selection of spatial filters in repeater-assisted networks
WO2024176171A1 (en) Cho chain methods in ntn
WO2024248705A1 (en) Method to provide service to high-speed user equipments
WO2025104082A1 (en) Method and apparatus of reducing interruption to positioning in ntn

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25720145

Country of ref document: EP

Kind code of ref document: A1