WO2021066696A1

WO2021066696A1 - Methods for updating ephemeris data in a non-terrestrial network (ntn)

Info

Publication number: WO2021066696A1
Application number: PCT/SE2020/050811
Authority: WO
Inventors: Sebastian EULER; Björn Hofström; Helka-Liina Määttanen; Jonas SEDIN; Olof Liberg
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2019-10-03
Filing date: 2020-08-24
Publication date: 2021-04-08

Abstract

Embodiments include methods, performed by a user equipment,UE, for updating ephemeris data in a non-terrestrial network, NTN, configured to operate as a radio access network, RAN. Such methods include receiving (740), from a network node in the NTN, updated ephemeris data related to one or more satellites in the NTN. Such methods also include selectively storing (760), in a non-volatile memory of the UE, the updated ephemeris data in association with further ephemeris data currently stored in the non-volatile memory. In some embodiments, the updated and further ephemeris data can be associated with different durations of validity, different PLMNs, and/or different satellites or orbital planes. Various selective storing operations can be performed according to various embodiments. Other embodiments include complementary methods performed by a network node, as well as UEs and network nodes configured to perform such methods.

Description

METHODS FOR UPDATING EPHEMERIS DATA IN A NON-TERRESTRIAL

NETWORK (NTN)

TECHNICAL FIELD

The present application relates generally to the field of wireless communication networks, and more specifically to improvements to communications between a satellite and a user equipment (UE) in Long Term Evolution (LTE) or New Radio (NR) radio access network (RAN) adapted to a non-terrestrial network (NTN) scenario.

BACKGROUND

Long Term Evolution (LTE) is an umbrella term for so-called fourth-generation (4G) radio access technologies developed within the Third-Generation Partnership Project (3 GPP) and initially standardized in Releases 8 and 9, also known as Evolved UTRAN (E-UTRAN). LTE is targeted at various licensed frequency bands and is accompanied by improvements to non-radio aspects commonly referred to as System Architecture Evolution (SAE), which includes Evolved Packet Core (EPC) network. LTE continues to evolve through subsequent releases that are developed according to standards-setting processes with 3 GPP and its working groups (WGs), including the Radio Access Network (RAN) WG, and sub-working groups ( e.g ., RANI, RAN2, etc.).

For example, LTE Release 10 (Rel-10) supports bandwidths larger than 20 MHz. One important requirement on Rel-10 is to assure backward compatibility with LTE Release-8. This should also include spectrum compatibility. As such, a wideband LTE Rel-10 carrier (e.g., wider than 20 MHz) should appear as a number of carriers to an LTE Rel-8 (“legacy”) terminal. Each such carrier can be referred to as a Component Carrier (CC). For an efficient use of a wide carrier also for legacy terminals, legacy terminals can be scheduled in all parts of the wideband LTE Rel-10 carrier. One exemplary way to achieve this is by means of Carrier Aggregation (CA), whereby a Rel-10 terminal can receive multiple CCs, each preferably having the same structure as a Rel-8 carrier. Similarly, one of the enhancements in LTE Rel-11 is an enhanced Physical Downlink Control Channel (ePDCCH), which has the goals of increasing capacity and improving spatial reuse of control channel resources, improving inter-cell interference coordination (ICIC), and supporting antenna beamforming and/or transmit diversity for control channel. In Release 13, 3 GPP developed specifications for narrowband Internet of Things (NB- IoT) and LTE Machine-Type Communications (LTE-M or LTE-MTC). These new radio access technologies provide connectivity to services and applications requiring reliable indoor coverage and high capacity in combination with low system complexity and optimized device power consumption. To support reliable coverage in the most extreme situations, both NB-IoT and LTE-M UEs can perform link adaptation on all physical channels using subframe bundling and repetitions. This applies to (N/M)PDCCH and (N)PDSCH in the DL, and to (N)PUSCH, (N)PRACH, and PUCCH (only for LTE-M) in the UL.

An overall exemplary architecture of a network comprising LTE and SAE is shown in Figure 1. E-UTRAN 100 comprises one or more evolved Node B’s (eNB), such as eNBs 105, 110, and 115, and one or more user equipment (UE), such as UE 120. As used within 3 GPP specifications, “user equipment” (or “UE”) can refer to any wireless communication device ( e.g ., smartphone or computing device) that is capable of communicating with 3GPP- standard-compliant network equipment, including E-UTRAN and earlier-generation RANs (e.g., UTRAN/“3G” and/or GERAN/”2G”) as well as later-generation RANs in some cases.

As specified by 3GPP, E-UTRAN 100 is responsible for all radio-related functions in the network, including radio bearer control, radio admission control, radio mobility control, scheduling, and dynamic allocation of resources to UEs in uplink (UL) and downlink (DL), as well as security of the communications with the UE. These functions reside in the eNBs, such as eNBs 105, 110, and 115, which communicate with each other via an XI interface. The eNBs also are responsible for the E-UTRAN interface to EPC 130, specifically the SI interface to the Mobility Management Entity (MME) and the Serving Gateway (SGW), shown collectively as MME/S-GWs 134 and 138 in Figure 1.

In general, the MME/S-GW handles both the overall control of the UE and data flow between UEs (such as UE 120) and the rest of the EPC. More specifically, the MME processes the signaling (e.g., control plane, CP) protocols between UEs and EPC 130, which are known as the Non-Access Stratum (NAS) protocols. The S-GW handles all Internet Protocol (IP) data packets (e.g., user plane, UP) between UEs and EPC 130, and serves as the local mobility anchor for the data bearers when a UE moves between eNBs, such as eNBs 105, 110, and 115.

EPC 130 can also include a Home Subscriber Server (HSS) 131, which manages user- and subscriber-related information. HSS 131 can also provide support functions in mobility management, call and session setup, user authentication and access authorization. The functions of HSS 131 can be related to the functions of legacy Home Location Register (HLR) and Authentication Centre (AuC) functions or operations.

In some embodiments, HSS 131 can communicate with a user data repository (UDR) - labelled EPC-UDR 135 in Figure 1 - via a Ud interface. The EPC-UDR 135 can store user credentials after they have been encrypted by AuC algorithms. These algorithms are not standardized (i.e., vendor-specific), such that encrypted credentials stored in EPC-UDR 135 are inaccessible by any other vendor than the vendor of HSS 131.

Figure 2A shows a high-level block diagram of an exemplary LTE architecture in terms of its constituent entities - UE, E-UTRAN, and EPC - and high-level functional division into the Access Stratum (AS) and the Non-Access Stratum (NAS). Figure 2A also illustrates two particular interface points, namely Uu (UE/E-UTRAN Radio Interface) and SI (E-UTRAN/EPC interface), each using a specific set of protocols, i.e., Radio Protocols and SI Protocols. Each of the two protocols can be further segmented into user plane (UP) and control plane (CP) protocol functionality. Over the Uu interface between UE and E-UTRAN, the UP carries user information ( e.g ., data packets) while the CP carries control information.

Figure 2B illustrates a block diagram of an exemplary CP protocol stack on the Uu interface comprising Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC) layers. The PHY layer is concerned with how and what characteristics are used to transfer data over transport channels on the LTE radio interface. The MAC layer provides data transfer services on logical channels, maps logical channels to PHY transport channels, and reallocates PHY resources to support these services. The RLC layer provides error detection and/or correction, concatenation, segmentation, and reassembly, reordering of data transferred to or from the upper layers. The PHY, MAC, and RLC layers perform identical functions for both the UP and the CP. The PDCP layer provides ciphering/deciphering and integrity protection for UP and CP, as well as other UP functions such as header compression.

In general, the RRC layer (shown in Figure 2B) controls communications between a UE and an eNB at the radio interface, as well as the mobility of a UE crossing cells and/or eNBs. RRC is the highest CP layer in the AS, and also transfers NAS messages from above RRC. Such NAS messages are used to control communications between a UE and the EPC.

Figure 2C shows a block diagram of an exemplary LTE radio interface protocol architecture from the perspective of the PHY. The interfaces between the various layers are provided by Service Access Points (SAPs), indicated by the ovals in Figure 2C. The PHY interfaces with MAC and RRC layers described above. The MAC provides different logical channels to the RLC layer (also described above), characterized by the type of information transferred, whereas the PHY provides a transport channel to the MAC, characterized by how the information is transferred over the radio interface. In providing this transport service, the PHY performs various functions including error detection and correction; rate-matching and mapping of the coded transport channel onto physical channels; power weighting, modulation, and demodulation of physical channels; transmit diversity, beamforming, and multiple input multiple output (MIMO) antenna processing; and sending radio measurements to higher layers (e.g., RRC).

In general, a physical channel corresponds to a set of resource elements (REs) carrying information that originates from higher layers. Downlink (i.e., eNB to UE) physical channels provided by the LTE PHY include Physical Downlink Shared Channel (PDSCH), Physical Multicast Channel (PMCH), Physical Downlink Control Channel (PDCCH), Relay Physical Downlink Control Channel (R-PDCCH), Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), and Physical Hybrid ARQ Indicator Channel (PHICH). In addition, the LTE PHY DL includes various reference signals, synchronization signals, and discovery signals.

PDSCH is the main physical channel used for unicast DL data transmission, as well as for transmission of RAR (random access response), certain system information blocks, and paging information. PBCH carries the basic system information required by the UE to access the network. PDCCH is used for transmitting DL control information (DCI), mainly scheduling decisions, required for reception of PDSCH, and for UL scheduling grants enabling transmission on PUSCH.

Uplink (i.e., UE to eNB) physical channels provided by the LTE PHY include Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Physical Random Access Channel (PRACH). In addition, the LTE PHY UL includes various reference signals including demodulation reference signals (DM-RS), which are transmitted to aid the eNB in the reception of an associated PUCCH or PUSCH; and sounding reference signals (SRS), which are not associated with any UL channel. PUSCH is the UL counterpart to the PDSCH. PUCCH is used by UEs to transmit UL control information, including HARQ acknowledgements, channel state information reports, etc. PRACH is used for random access preamble transmission.

The multiple access scheme for the LTE PHY is based on Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) in the downlink, and on Single- Carrier Frequency Division Multiple Access (SC-FDMA) with a cyclic prefix in the uplink. To support transmission in paired and unpaired spectrum, the LTE PHY supports both Frequency Division Duplexing (FDD) (including both full- and half-duplex operation) and Time Division Duplexing (TDD). Figure 3 shows an exemplary radio frame structure (“type 1”) used for LTE FDD downlink (DL) operation. The DL radio frame has a fixed duration of 10 ms and consists of 20 slots, labeled 0 through 19, each with a fixed duration of 0.5 ms. A 1-ms subframe comprises two consecutive slots where subframe / consists of slots 2/ and 2/ + 1. Each exemplary FDD DL slot consists of N^DL _symb OFDM symbols, each of which is comprised of N_sc OFDM subcarriers. Exemplary values of N^DL _symb can be 7 (with a normal CP) or 6 (with an extended-length CP) for subcarrier bandwidth of 15 kHz. The value of N_sc is configurable based upon the available channel bandwidth. Since persons of ordinary skill in the art are familiar with the principles of OFDM, further details are omitted in this description.

As shown in Figure 3, a combination of a particular subcarrier in a particular symbol is known as a resource element (RE). Each RE is used to transmit a particular number of bits, depending on the type of modulation and/or bit-mapping constellation used for that RE. For example, some REs may carry two bits using QPSK modulation, while other REs may carry four or six bits using 16- or 64-QAM, respectively. The radio resources of the LTE PHY are also defined in terms of physical resource blocks (PRBs). A PRB spans N^RB _SC sub-carriers over the duration of a slot {i.e., N^DL _symb symbols), where Nⁱ _se is typically either 12 (with a 15-kHz sub-carrier bandwidth) or 24 (7.5-kHz bandwidth). A PRB spanning the same N^RB _SC subcarriers during an entire subframe (i.e., 2N^DL _symb symbols) is known as a PRB pair. Accordingly, the resources available in a subframe of the LTE PHY DL comprise N^DLRB PRB pairs, each of which comprises 2N^DL _symb* N^RB _SC REs. For a normal CP and 15-KHz sub carrier bandwidth, a PRB pair comprises 168 REs.

One exemplary characteristic of PRBs is that consecutively numbered PRBs ( e.g ., PRBi and PRBi_+i) comprise consecutive blocks of subcarriers. For example, with a normal CP and 15-KHz sub-carrier bandwidth, PRBo comprises sub-carrier 0 through 11 while PRBi comprises sub-carriers 12 through 23. The LTE PHY resource also can be defined in terms of virtual resource blocks (VRBs), which are the same size as PRBs but may be of either a localized or a distributed type. Localized VRBs can be mapped directly to PRBs such that VRB »_VRB corresponds to PRB o_RRB = o_VRB On the other hand, distributed VRBs may be mapped to non-consecutive PRBs according to various rules, as described in 3GPP Technical Specification (TS) 36.213 or otherwise known to persons of ordinary skill in the art. However, the term “PRB” shall be used in this disclosure to refer to both physical and virtual resource blocks. Moreover, the term “PRB” will be used henceforth to refer to a resource block for the duration of a subframe, i.e., a PRB pair, unless otherwise specified.

An exemplary LTE FDD UL radio frame can be configured in a similar manner as the exemplary FDD DL radio frame shown in Figure 3. Using terminology consistent with the above DL description, each UL slot consists of N^UL _symb OFDM symbols, each of which is comprised of N_sc OFDM subcarriers.

As discussed above, the LTE PHY maps the various DL and UL physical channels to the resources shown in Figures 3A and 3B, respectively. For example, the PHICH carries HARQ feedback (e.g, ACK/NAK) for UL transmissions by the UEs. Similarly, PDCCH carries scheduling assignments, channel quality feedback (e.g, CSI) for the UL channel, and other control information. Likewise, a PUCCH carries uplink control information such as scheduling requests, CSI for the downlink channel, HARQ feedback for eNB DL transmissions, and other control information. Both PDCCH and PUCCH can be transmitted on aggregations of one or several consecutive control channel elements (CCEs), and a CCE is mapped to the physical resource based on resource element groups (REGs), each of which is comprised of a plurality of REs. For example, a CCE can comprise nine (9) REGs, each of which can comprise four (4) REs.

As briefly mentioned above, the LTE RRC layer (shown in Figures 2B-C) controls communications between a UE and an eNB at the radio interface, as well as the mobility of a UE between cells in the E-UTRAN. After the UE is powered ON it will be in the RRC IDLE state until the RRC connection is established, at which time it will transition to RRC CONNECTED state (where data transfer can occur). After a connection is released, the UE returns to RRC IDLE. In RRC IDLE state, the UE’s radio is active on a discontinuous reception (DRX) schedule configured by upper layers. During DRX active periods, an RRC IDLE UE receives system information (SI) broadcast by a serving cell, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel on PDCCH for pages from the EPC via eNB. An RRC IDLE UE is known in the EPC and has an assigned IP address, but is not known to the serving eNB (e.g., there is no stored context). In Rel-13, a mechanism was introduced for the UE to be placed by the network in a suspended state that can be viewed as a “substate” of RRC IDLE.

In 3GPP, a study item on a new radio interface for 5G has been completed and the 5G system (5GS) was first specified in Rel-15. While LTE was primarily designed for user- to-user communications, 5G (also referred to as “NR”) networks are envisioned to support both high single-user data rates ( e.g ., 1 Gb/s) and large-scale, machine-to-machine communication involving short, bursty transmissions from many different devices that share the frequency bandwidth. The 5G radio standards (also referred to as “New Radio” or “NR”) are currently targeting a wide range of data services including eMBB (enhanced Mobile Broad Band), URLLC (Ultra-Reliable Low Latency Communication), and mMTC (massive Machine-Type Communications).

These services can have different requirements and objectives. For example, URLLC is intended to provide a data service with extremely strict error and latency requirements, e.g., error probabilities as low as 10^-5 or lower and 1 ms end-to-end latency or lower. For eMBB, the requirements on latency and error probability can be less stringent whereas the required supported peak rate and/or spectral efficiency can be higher. Additionally, mMTC (which can be seen as an extension of Rel-13 MTC) is intended to provide scalable and efficient connectivity for a massive number of devices sending very short packets.

In addition, NR is targeted to support deployment in lower-frequency spectrum, similar to LTE, and also in very-high-frequency spectrum (referred to as “millimeter wave” or “mmW”). Similar to LTE, NR uses OFDM in the downlink. Each NR radio frame is 10 ms in duration and is composed of 10 subframes having equal durations of 1 ms each. Each subframe consists of one or more slots, and each slot consists of 14 (for normal cyclic prefix) or 12 (for extended cyclic prefix) time-domain symbols. The protocol layers used in NR are very similar to those in LTE, described above, although various enhancements have been introduced to support the new services envisioned for NR/5G.

In Rel-15, 3GPP also started preparing NR for operation in a Non-Terrestrial Network (NTN). The work was performed within the study item “NR to support Non-Terrestrial Networks” and resulted in publication of 3GPP TR 38.811 (vl5.1.0). The work to prepare NR for operation in an NTN network continued in Rel-16 under the study item “Solutions for NR to support Non-Terrestrial Network”. In parallel the interest to adapt LTE for operation in NTN is growing. Consequently, 3GPP is considering introducing support for NTN in both LTE and NR in Rel-17.

Even so, current LTE and NR technologies were developed for terrestrial cellular networks, and adapting them to NTN can create various issues, problems, and/or drawbacks for operation of networks and UEs. SUMMARY

Exemplary embodiments disclosed herein address these problems, issues, and/or drawbacks of existing solutions by providing a flexible but efficient approach for updating user equipment (UEs) with ephemeris information relating to a Non-Terrestrial Network (NTN), thereby facilitating quicker initial acquisition of the NTN upon UE startup as well as other benefits.

Some embodiments include methods for updating ephemeris data in an NTN configured to operate as a radio access network (RAN). These exemplary methods can be implemented, for example, in a TIE (e.g., wireless device).

These exemplary methods can include receiving, from a network node in the NTN, updated ephemeris data related to one or more satellites in the NTN. These exemplary methods can also include selectively storing the updated ephemeris data, in a non-volatile memory of the TIE, in association with further ephemeris data currently stored in the non volatile memory.

In some embodiments, these exemplary methods can also include receiving, in association with the updated ephemeris data, respective lists of cells served by each of the satellites.

In some embodiments, these exemplary methods can also include sending an ephemeris update request to the network node. In such embodiments, the updated ephemeris data can be received in response to the ephemeris update request.

In some embodiments, these exemplary methods can also include determining that a duration of validity of at least a portion of the further ephemeris data has expired. In such embodiments, the ephemeris update request can be sent in response to determining that the duration of validity has expired. For example, the duration of validity can be a parameter (e.g., an explicit parameter) of the further ephemeris data.

In some embodiments, these exemplary methods can also include successfully connecting to the NTN after a predetermined number of failed attempts (e.g., RACH attempts) to connect to the NTN. In such embodiments, the ephemeris update request can be sent in response to the successful connection.

In some embodiments, the further ephemeris data can be related to one or more first satellites or orbital planes and the updated ephemeris data is related to one or more second satellites or orbital planes, that are different from the first satellites or orbital planes. In such embodiments, selectively storing can include storing the updated ephemeris data and retaining the further ephemeris data.

In some embodiments, the further ephemeris data can be associated with a first duration of validity and the updated ephemeris data can be associated with a second duration of validity, subsequent to the first duration of validity. In such embodiments, selectively storing can include one of the following: overwriting the further ephemeris data with the updated ephemeris data; or storing the updated ephemeris data in association with a high priority indicator and storing a low priority indicator in association with the further ephemeris data.

In some embodiments, the further ephemeris data can be related to a first public land mobile network (PLMN) and the updated ephemeris data can be related to a second PLMN different from the first PLMN. In such embodiments, selectively storing can include one of the following: overwriting the further ephemeris data with the updated ephemeris data; or storing the updated ephemeris data and retaining the further ephemeris data.

Other embodiments include methods for providing updated ephemeris data in a non terrestrial network (NTN) configured to operate as a radio access network (RAN). These exemplary methods can be implemented, for example, in a network node (e.g., satellite, gateway, base station, etc.) in the NTN.

These exemplary methods can include sending, to one or more UEs operating in a cell served by the network node, updated ephemeris data related to one or more satellites in the NTN. In some embodiments, these exemplary methods can also include sending, in association with the updated ephemeris data, respective lists of cells served by each of the satellites.

In some embodiments, these exemplary methods can also include determining the updated ephemeris in association with a change in at least one satellite or orbital plane of the NTN. In such embodiments, the updated ephemeris data can be sent subsequent to this determination.

In some embodiments, these exemplary methods can also include receiving an ephemeris update request from a particular one of the UEs. In such embodiments, the updated ephemeris data can be sent to the particular UE in response to the ephemeris update request. In some of these embodiments, the ephemeris update request includes a timestamp or duration of validity associated with the further ephemeris data. In such embodiments, these exemplary methods can also include determining the updated ephemeris data based on the timestamp or duration of validity included in the ephemeris update request. In various embodiments, the updated ephemeris data can be related to one or more of the following: one or more satellites or orbital planes, a duration of validity, and a public land mobile network (PLMN).

Other exemplary embodiments include NTN nodes (e.g., satellites, gateways, base stations, or components thereof) and user equipment (UEs, e.g., wireless devices) configured to perform operations corresponding to any of the exemplary methods described herein. Other exemplary embodiments include non-transitory, computer-readable media storing program instructions that, when executed by processing circuitry, configure such NTN nodes or UEs to perform operations corresponding to any of the exemplary methods described herein.

These and other objects, features and advantages of the present disclosure will become apparent upon reading the following Detailed Description in view of the Drawings briefly described below.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a high-level block diagram of an exemplary architecture of the Long-Term Evolution (LTE) Evolved UTRAN (E-UTRAN) and Evolved Packet Core (EPC) network, as standardized by 3 GPP.

Figure 2A is a high-level block diagram of an exemplary E-UTRAN architecture in terms of its constituent components, protocols, and interfaces.

Figure 2B is a block diagram of exemplary protocol layers of the control-plane portion of the radio (Uu) interface between a user equipment (UE) and the E-UTRAN.

Figure 2C is a block diagram of an exemplary LTE radio interface protocol architecture from the perspective of the PHY layer.

Figure 3 is a block diagram of an exemplary downlink (DL) LTE radio frame structures used for frequency division duplexing (FDD) operation.

Figures 4A-4B illustrate an exemplary configuration of a satellite radio access network (RAN), also referred to as a non-terrestrial network (NTN).

Figures 5-6 shows sequence and/or flow diagrams that illustrate, respectively, UE- and network-initiated ephemeris update procedures, according to various exemplary embodiments of the present disclosure.

Figure 7 is a flow diagram illustrating an exemplary method performed by a user equipment (UE), according to various exemplary embodiments of the present disclosure. Figure 8 is a flow diagram illustrating an exemplary method performed by a network node according to various exemplary embodiments of the present disclosure.

Figure 9 is a block diagram of an exemplary wireless network configurable according to various exemplary embodiments of the present disclosure.

Figure 10 is a block diagram of an exemplary user equipment (UE) configurable according to various exemplary embodiments of the present disclosure.

Figure 11 is a block diagram of illustrating a virtualization environment that can facilitate virtualization of various functions implemented according to various exemplary embodiments of the present disclosure.

Figures 12-13 are block diagrams of exemplary communication systems configurable according to various exemplary embodiments of the present disclosure.

Figure 14-17 are flow diagrams illustrating various exemplary methods implemented in a communication system, according to various exemplary embodiments of the present disclosure.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

The steps of any methods and/or procedures disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein can be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments can apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

Furthermore, the following terms are used throughout the description given below:

• Radio Node: As used herein, a “radio node” can be either a “radio access node” or a

“wireless device.” • Radio Access Node: As used herein, a “radio access node” (or “radio network node”) can be any node in a radio access network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station ( e.g ., a New Radio (NR) base station (gNB) in a 3 GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3 GPP LTE network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), an integrated access backhaul (LAB) node, a relay node, and a non-terrestrial access node (e.g., satellite or gateway).

• Core Network Node: As used herein, a “core network node” is any type of node in a core network. Some examples of a core network node include, e.g, a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), or the like.

• Wireless Device: As used herein, a “wireless device” (or “WD” for short) is any type of device that has access to (i.e., is served by) a cellular communications network by communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term “wireless device” is used interchangeably herein with “user equipment” (or “UE” for short). Some examples of a wireless device include, but are not limited to, a UE in a 3GPP network and a Machine Type Communication (MTC) device. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.

• Network Node: As used herein, a “network node” is any node that is either part of the radio access network or the core network of a cellular communications network. Functionally, a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g, administration) in the cellular communications network.

Note that the description given herein focuses on a 3 GPP cellular communications system and, as such, 3 GPP terminology or terminology similar to 3 GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from the concepts, principles, and/or embodiments described herein.

In addition, functions and/or operations described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. Furthermore, although the term “cell” is used herein, it should be understood that (particularly with respect to 5G NR) beams may be used instead of cells and, as such, concepts described herein apply equally to both cells and beams. In addition, although the embodiments of the present disclosure are described in terms of 3GPP non terrestrial networks (NTNs) that utilize LTE and/or NR technologies, such embodiments are equally applicable to any wireless network dominated by line of sight conditions, including terrestrial networks.

As briefly mentioned above, current LTE and NR technologies were developed for terrestrial cellular networks and adapting them to NTNs can create various issues, problems, and/or drawbacks for operation of networks and UEs. These issues are discussed in more detail below.

Figure 4A shows a high-level view of an exemplary satellite radio access network (RAN), which is also referred to as a non-terrestrial network (NTN) 400. The exemplary satellite RAN shown in Figure 4 A includes a space-borne platform, such as a satellite 430, and an earth gateway 450 that connects the satellite to a base station 460. The radio link between the gateway and the satellite is referred to as a “feeder link” (440), while the radio link between the satellite and a particular device (e.g., UE 410) is referred to as an “access link” (420).

Depending on the orbit altitude, a satellite may be categorized as low earth orbit (LEO), medium earth orbit (MEO), or geostationary earth orbit (GEO). LEO satellites typically have orbital heights between 250 - 1,500 km and orbital periods between 90 - 120 minutes. MEO satellites typically have orbital heights between 5,000 - 25,000 km and orbital periods between 3 - 15 hours. GEO satellites have a height of approximately 35,786 km and an orbital period of 24 hours. In general, the orbital period is proportional to the orbital height.

Due to these significant orbit heights, satellite systems generally have path losses that are significantly higher than experienced in terrestrial networks. To overcome the high pathloss, the access and feeder links may need to be operated in line of sight (LOS) conditions. As such, the NTN radio channels for the access and feeder links may therefore be dominated by a LOS component with few reflective (or non-LOS) components. One consequence is that signal received on the earth will have generally the same polarization as the signal transmitted by the satellite, which is typically circularly polarized. As such, it is possible to achieve orthogonality between two signals transmitted by a satellite by choosing orthogonal polarizations, e.g., right hand circular polarization (RHCP) and left-hand circular polarization (LHCP). This is generally not possible in terrestrial networks, where non-LOS components having different polarizations (e.g., due to various reflections) dominate the received signal.

A communication satellite typically generates several beams over a given area. The footprint of a beam (also referred to as “spotbeam”) is usually an elliptic shape, which has been traditionally considered as a cell. A spotbeam may move over the earth surface with the satellite movement or may be earth-fixed with some beam pointing mechanism used by the satellite to compensate for its motion. The size of a spotbeam depends on the system design and may range from tens of kilometers to a few thousands of kilometers.

Relative to beams observed in a terrestrial network, the NTN beams (e.g., spotbeams 1-4 in Figure 4A) can be very wide and extend beyond the area defined by a served cell. As such, beams covering adjacent cells can overlap, causing significant levels of intercell interference. To overcome this interference, different cells (e.g., different spotbeams) can be configured with different carrier frequencies and polarization modes. Figure 4B shows an exemplary polarization arrangement for the spotbeams shown in Figure 4A.

In LTE and NR, the UE reference point for the transmission of physical signals and channels is referred to as an “antenna port.” This is an abstract concept specified by 3GPP, partly intended to relate a radio channel over which a first signal is transmitted to a radio channel over which a second signal is transmitted. The 3GPP specifications do not disclose how signals defined at a certain antenna port is mapped to a physical antenna connector, which is the input to the radiating antenna elements.

In LTE and NR, when a UE is powered on, it performs an initial search over its supported frequency bands for a PLMN and a cell in the PLMN to camp on, e.g., in RRC IDLE mode. In terrestrial cellular networks, this “initial acquisition” procedure is relatively well-bounded in time due to the fixed locations and relatively small sizes of cells.

On the other hand, during initial acquisition in an NTN, a UE may need to search for a satellite over the entire sky from horizon to horizon. Moreover, satellites at lower orbital heights (e.g., LEOs and MEOs) are moving relative to the earth’s surface, causing various Doppler shifts to the respective signals as received by UEs on earth. Furthermore, satellite signals experience significant path loss before reaching UEs on earth. As such, UEs may need to use highly directive antenna beams (e.g., with maximum gain in a very narrow beamwidth, i.e., the “main lobe”) for initial acquisition of satellite signals.

Because such beamwidths correspond to only a fraction of the overall sky (e.g., azimuth and elevation ranges), the UE will usually need to perform sequential searches for a satellite, with each search covering a range of azimuth and elevation corresponding to the UE’s beamwidth. The rapid movement of LEO and MEO satellite can also complicate this initial search for a satellite. Consequently, the time required for the initial search to find an NTN and a cell in the NTN to camp on can be very long and can consume a significant portion of the UE’s stored energy (e.g., in a battery), which can be unacceptable for users.

The time required for the initial search can be reduced significantly by pre programming the UE with ephemeris data, which describes the locations of the respective satellites relative to an earth-centered earth-fixed (ECEF) reference frame. The combination of accurate ephemeris data with the UE’s approximate current location and approximate current time can provide the UE with a much narrower range of azimuth and elevation over which to conduct the initial search. This can reduce the initial search time for a given level of satellite signal.

In general, ephemeris data includes at least five (5) parameters describing the shape and position of the satellite orbit. The position of a satellite can be predicted based on these parameters and well-known equations that model satellite orbits (so-called “orbital equations”), which are also a function of time. Typically, ephemeris data is associated with a timestamp indicating when the parameters were obtained and/or derived, and/or a duration of their validity. The accuracy of the predicted satellite position (i.e., based on the parameters) will generally be quite good at or near the timestamp, or within the duration of validity, but will degrade as time progress in the future. The validity duration of a set of parameters can depend on the type and altitude of the orbit, but it can also depend on the degree of accuracy needed for the predicted position. In general, duration of validity (or validity duration) can range from few hours (e.g., for high accuracy) to a few years (e.g., for moderate accuracy).

An NTN UE that is pre-programmed with ephemeris data (e.g., in a uSIM or other non-volatile memory) might determine at some point that the ephemeris data is beyond its duration of validity, such that the UE can no longer predict the satellite positions with the required accuracy (e.g., for initial search). A mechanism is needed to update the data stored in the UE.

Accordingly, exemplary embodiments of the present disclosure provide techniques for updating ephemeris data stored in an NTN UE. The ephemeris data to be updated might be pre-programmed in the uSIM (e.g., provisioned by a network operation) or obtained in another way and stored in the UE’s non-volatile memory. The updated ephemeris data can be obtained via NAS signaling (e.g., initiated by UE or the network), or via system information broadcast by the network. Such embodiments provide various benefits and/or advantages, including reducing UE energy consumption (or, equivalently, increasing UE operational time on one battery charge) and improving user access to 3 GPP services provided by an NTN.

In some embodiments, the updating procedure can be initiated by the UE. For example, the UE has acquired ephemeris data that includes a timestamp or duration of validity. Alternately, the UE can acquire ephemeris data that does not include a timestamp or duration of validity, but the UE initiates a timer upon ephemeris acquisition, and expiration of the timer indicates that the acquired ephemeris is no longer valid. The initiation of the timer can also be based on a difference between a timestamp indicating when the ephemeris was derived, and an expected duration of validity of the ephemeris (which may be pre configured or estimated). In any event, at the expiration of the timer or of the duration of validity, the UE initiates acquisition of updated ephemeris data.

Figure 5 shows a sequence and/or flow diagram that illustrates UE-initiated ephemeris updates, according to various exemplary embodiments of the present disclosure. As shown in Figure 5, the UE (510) triggers an update when the timer expires, or when the time stamp is old enough. The UE then requests new ephemeris data from an MME (e.g., in an EPC network) or from an AMF (e.g., in a 5GC network) via the intermediate RAN (e.g., E- UTRAN or NG-RAN). These are collectively labelled MME/AMF 520 in Figure 5. The UE can request updates to all earlier ephemeris data stored at the UE, or only a portion of such data (e.g., for certain satellites or certain orbital planes). When the UE receives the update, it can monitor the duration of validity of the updated ephemeris, e.g., based on an explicit duration of validity. Alternately, the UE can re-initiate the timer (e.g., based on a derivation timestamp and pre-configured/estimated duration of validity) and wait for timer expiration, as explained above.

In some embodiments, if the UE has difficulty connecting to the RAN (e.g., X number of RACH failures toward a cell), the UE may send the Ephemeris Update Request shown in Figure 5 after it finally managed to connect, to ensure it has up-to-date ephemeris data in case of future connection difficulties. Various connection-related conditions can be used to trigger the ephemeris update, according to UE implementations.

In some embodiments, the Ephemeris Update Request sent to the network includes information about the UE’s current status, e.g., whether the UE already has ephemeris data and if so, a time stamp, validity duration, and/or timer value associated with the existing data. The request may also indicate if the UE is requesting a full update (e.g., information about all individual satellites) or a partial update (e.g., only information about certain orbital planes or certain satellites). Given this information in the request from the UE, the network (e.g., MME/AMF) can determine whether the UE needs an ephemeris update and, if so, the particular information to send the UE in response to the Ephemeris Update Request.

In other embodiments, the updating procedure can be initiated by the network. For example, the network can initiate ephemeris updates to UEs when one or more satellite orbits have changed significantly (e.g., due to correctional maneuvers), making any existing stored ephemeris data invalid. As another example, the network could initiate updates if new satellites are launched and put in new orbits, and/or when old satellites are removed from their orbits and/or replaced. Figure 6 shows a sequence and/or flow diagram that illustrates network-initiated ephemeris updates, according to various exemplary embodiments of the present disclosure. In this exemplary sequence, MME/AMF 620 detects changes in orbits and/or satellites and sends new (i.e., updated) ephemeris data to UE 610 in accordance with the detected changes.

In other embodiments, when the network receives updated ephemeris information (e.g., for one or more satellites), it will indicate this by a flag in system information block (SIB) broadcast in one or more cells. Upon reading this flag from the broadcast SIB, the UE can trigger the ephemeris update procedure shown in Figure 5 (e.g., rather than a timer-based trigger). The network can also broadcast a sequence or version number associated with the updated ephemeris, which UEs can compare with a corresponding sequence or version number associated with their stored ephemeris to determine whether an ephemeris update procedure should be triggered. Alternately, the network can broadcast a timestamp associated with the updated ephemeris, which the UE can use in a similar manner to determine if an update is required. As another alternative, the network can broadcast the updated ephemeris, or a portion thereof.

In some embodiments, the UE can trigger an on-demand broadcast of the ephemeris data in system information based on the Ephemeris Update Request.

In any case, whether the UE receives updated ephemeris information via a UE- initiated or network-initiated procedure, the UE updates its stored previous ephemeris data with the newly received data. The stored data may be updated fully or partially, depending on the type and/or amount of data received in the update. In some embodiments, both the previous ephemeris data and the newly updated ephemeris data are maintained in the UE’s non-volatile memory, with the latter being given a higher priority over the former. In some embodiments, the previous and newly updated ephemeris data can apply to different satellites and/or orbital planes such that they may be stored as a single ephemeris data, albeit with different timestamps or durations of validity.

In some embodiments, the stored ephemeris data and the updates can be specific to a particular network (e.g., public land mobile network, PLMN). For example, the UE may store multiple ephemeris data sets, each associated with a particular PLMN. In such case, any received updates should be applied only to stored ephemeris data associated with the same PLMN. For example, the UE may have a stored first ephemeris data set associated with its home PLMN, but receives an updated ephemeris associated with a visited PLMN that it is currently camping on or connected to (or an equivalent PLMN). In various embodiments, the UE could either store the updated ephemeris as a second ephemeris data set (e.g., together with the first ephemeris data set), or may discard the update since it does not pertain to the same PLMN as the first ephemeris data set.

In some embodiments, the UE’s stored ephemeris data set can be a minimal set of satellite orbits required to support initial access to a network. In such embodiments, the updates from the network can supplement and/or complement this minimal set, e.g., with ephemeris data for additional orbits and/or additional satellites.

In some embodiments, if the stored set of satellite orbits is minimal (e.g., does not cover all satellites in the NTN), the ephemeris data for a handover (HO) target satellite can be included in a HO command from the network to the UE (e.g., an RRCReconfiguration message) during inter-satellite HO. For example, this can be beneficial if the HO is network- triggered based on UE position.

In some embodiments, the network can provide updated ephemeris data for one or more satellites and a list of cells served by each of the satellites. Based on this information, the UE can determine which cells share common ephemeris data, which can be beneficial during initial search and acquisition.

These embodiments described above can be further illustrated with reference to Figures 7-8, which depict exemplary methods performed by a network node and a UE, respectively. In other words, various features of the operations described below, with reference to Figures 7-8, correspond to various embodiments described above.

More specifically, Figure 7 is a flow diagram illustrating an exemplary method for updating ephemeris data in a non-terrestrial network (NTN) configured to operate as a radio access network (RAN), according to various exemplary embodiments of the present disclosure. The exemplary method shown in Figure 7 can be implemented, for example, in a UE (e.g., wireless device) such as described in relation to other figures herein. The exemplary method shown in Figure 7 can also be used cooperatively with other exemplary methods described herein (e.g., Figure 8) to provide various benefits, advantages, and/or solutions described herein. Although Figure 7 shows specific blocks in a particular order, the operations of the exemplary method can be performed in a different order than shown and can be combined and/or divided into blocks having different functionality than shown. Optional operations are indicated by dashed lines.

The exemplary method illustrated in Figure 7 can include the operations of block 740, in which the UE can receive, from a network node in the NTN, updated ephemeris data related to one or more satellites in the NTN. The exemplary method can also include the operations of block 760, in which the UE can selectively store, in a non-volatile memory of the UE, the updated ephemeris data in association with further ephemeris data currently stored in the non-volatile memory.

In some embodiments, the exemplary method can also include the operations of block 750, where the UE can receive, in association with the updated ephemeris data, respective lists of cells served by each of the satellites.

In some embodiments, the updated ephemeris data can be received in a handover command from the network node. In other embodiments, the updated ephemeris data can be received via broadcast in a cell served by the network node.

In other embodiments, the exemplary method can also include the operations of block 730, in which the UE can send an ephemeris update request to the network node. In such embodiments, the updated ephemeris data can be received (e.g., in block 740) in response to the ephemeris update request.

In some of these embodiments, the exemplary method can also include the operations of block 710, in which the UE can determine that a duration of validity of at least a portion of the further ephemeris data has expired. In such embodiments, the, ephemeris update request can be sent in response to determining that the duration of validity has expired. For example, the duration of validity can be a parameter (e.g., an explicit parameter) of the further ephemeris data. As another example, determining that the duration of validity has expired can include initiating a validity timer (e.g., based on a timestamp indicating when the further ephemeris data was derived and/or obtained), and determining that the validity timer has expired. In others of these embodiments, the exemplary method can also include the operations of block 720, in which the UE can successfully connect to the NTN after a predetermined number of failed attempts (e.g., RACH attempts) to connect to the NTN. In such embodiments, the ephemeris update request can be sent in response to the successful connection.

In some embodiments, the further ephemeris data is related to one or more first satellites or orbital planes and the updated ephemeris data is related to one or more second satellites or orbital planes, that are different from the first satellites or orbital planes. In such embodiments, the operations of block 760 can include storing the updated ephemeris data and retaining the further ephemeris data (sub-block 761).

In other embodiments, the further ephemeris data can be associated with a first duration of validity and the updated ephemeris data can be associated with a second duration of validity, subsequent to the first duration of validity. In such embodiments, the operations of block 760 can include one of the following: overwriting the further ephemeris data with the updated ephemeris data (sub-block 762), or storing the updated ephemeris data in association with a high priority indicator and storing a low priority indicator in association with the further ephemeris data (sub-block 763).

In other embodiments, the further ephemeris data can be related to a first public land mobile network (PLMN) and the updated ephemeris data is related to a second PLMN different from the first PLMN. In such embodiments, the operations of block 760 can include one of the following: overwriting the further ephemeris data with the updated ephemeris data (sub-block 762), or storing the updated ephemeris data and retaining the further ephemeris data (sub-block 761).

In addition, Figure 8 is a flow diagram illustrating an exemplary method for providing updated ephemeris data in a non-terrestrial network (NTN) configured to operate as a radio access network (RAN), according to various exemplary embodiments of the present disclosure. The exemplary method shown in Figure 8 can be implemented, for example, in a network node (e.g., satellite, gateway, base station, etc.) described in relation to other figures herein. The exemplary method shown in Figure 8 can also be used cooperatively with other exemplary methods described herein (e.g., Figure 7) to provide various benefits, advantages, and/or solutions described herein. Although Figure 8 shows specific blocks in a particular order, the operations of the exemplary method can be performed in a different order than shown and can be combined and/or divided into blocks having different functionality than shown. Optional blocks or operations are indicated by dashed lines. The exemplary method illustrated in Figure 8 can include the operations of block 840, in which the network node can send, to one or more UEs operating in a cell served by the network node, updated ephemeris data related to one or more satellites in the NTN. In some embodiments, the exemplary method can also include the operations of block 850, where the network node can send, in association with the updated ephemeris data, respective lists of cells served by each of the satellites.

In some embodiments, the updated ephemeris data can be sent in a handover command to a particular one of the UEs. In other embodiments, the updated ephemeris data can be sent via broadcast in a cell served by the network node.

In some embodiments, the exemplary method can also include the operations of block 810, in which the network node can determine the updated ephemeris in association with a change in at least one satellite or orbital plane of the NTN. In such embodiments, the updated ephemeris data can be sent subsequent to this determination.

In other embodiments, the exemplary method can also include the operations of block 820, in which the network node can receive an ephemeris update request from a particular one of the UEs. In such embodiments, the updated ephemeris data can be sent to the particular UE in response to the ephemeris update request. In some of these embodiments, the ephemeris update request includes a timestamp or duration of validity associated with the further ephemeris data. In such embodiments, the exemplary method can also include the operations of block 830, in which the network node can determine the updated ephemeris data based on the timestamp or duration of validity included in the ephemeris update request.

In various embodiments, the updated ephemeris data is related to one or more of the following: one or more satellites or orbital planes, a duration of validity, and a public land mobile network (PLMN).

Although the subject matter described herein can be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 9. For simplicity, the wireless network of Figure 9 only depicts network 906, network nodes 960 and 960b, and WDs 910, 910b, and 910c. In practice, a wireless network can further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 960 and wireless device (WD) 910 are depicted with additional detail. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

The wireless network can comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network can be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network can implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 906 can comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 960 and WD 910 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network can comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that can facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

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, NBs, eNBs, gNBs, or components thereof). Base stations can be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node controlling a relay. A network node can 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 can also be referred to as nodes in a distributed antenna system (DAS).

Further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes ( e.g ., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node can be a virtual network node as described in more detail below.

In Figure 9, network node 960 includes processing circuitry 970, device readable medium 980, interface 990, auxiliary equipment 984, power source 986, power circuitry 987, and antenna 962. Although network node 960 illustrated in the example wireless network of Figure 9 can represent a device that includes the illustrated combination of hardware components, other embodiments can comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 960 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node can comprise multiple different physical components that make up a single illustrated component (e.g, device readable medium 980 can comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 960 can be composed of multiple physically separate components (e.g, a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which can each have their own respective components. In certain scenarios in which network node 960 comprises multiple separate components (e.g, BTS and BSC components), one or more of the separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, can in some instances be considered a single separate network node. In some embodiments, network node 960 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g, separate device readable medium 980 for the different RATs) and some components can be reused (e.g, the same antenna 962 can be shared by the RATs). Network node 960 can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 960, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or different chip or set of chips and other components within network node 960.

Processing circuitry 970 can be configured to perform any determining, calculating, or similar operations ( e.g ., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 970 can include processing information obtained by processing circuitry 970 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 970 can 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 various functionality of network node 960, either alone or in conjunction with other network node 960 components (e.g., device readable medium 980). Such functionality can include any of the various wireless features, functions, or benefits discussed herein.

For example, processing circuitry 970 can execute instructions stored in device readable medium 980 or in memory within processing circuitry 970. In some embodiments, processing circuitry 970 can include a system on a chip (SOC). As a more specific example, instructions (also referred to as a computer program product) stored in medium 980 can include instructions that, when executed by processing circuitry 970, can configure network node 960 to perform operations corresponding to various exemplary methods (e.g, procedures) described herein.

In some embodiments, processing circuitry 970 can include one or more of radio frequency (RF) transceiver circuitry 972 and baseband processing circuitry 974. In some embodiments, radio frequency (RF) transceiver circuitry 972 and baseband processing circuitry 974 can 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 972 and baseband processing circuitry 974 can be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device can be performed by processing circuitry 970 executing instructions stored on device readable medium 980 or memory within processing circuitry 970. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 970 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 970 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 970 alone or to other components of network node 960 but are enjoyed by network node 960 as a whole, and/or by end users and the wireless network generally.

Device readable medium 980 can 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 can be used by processing circuitry 970. Device readable medium 980 can store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 970 and, utilized by network node 960. Device readable medium 980 can be used to store any calculations made by processing circuitry 970 and/or any data received via interface 990. In some embodiments, processing circuitry 970 and device readable medium 980 can be considered to be integrated.

Interface 990 is used in the wired or wireless communication of signaling and/or data between network node 960, network 906, and/or WDs 910. As illustrated, interface 990 comprises port(s)/terminal(s) 994 to communicate (send and receive) data, for example, to and from network 906 over a wired connection. Interface 990 also includes radio front end circuitry 992 that can be coupled to, or in certain embodiments a part of, antenna 962. Radio front end circuitry 992 comprises filters 998 and amplifiers 996. Radio front end circuitry 992 can be connected to antenna 962 and processing circuitry 970. Radio front end circuitry can be configured to condition signals communicated between antenna 962 and processing circuitry 970. Radio front end circuitry 992 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 992 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 998 and/or amplifiers 996. The radio signal can then be transmitted via antenna 962. Similarly, when receiving data, antenna 962 can collect radio signals which are then converted into digital data by radio front end circuitry 992. The digital data can be passed to processing circuitry 970. In other embodiments, the interface can comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 960 may not include separate radio front end circuitry 992, instead, processing circuitry 970 can comprise radio front end circuitry and can be connected to antenna 962 without separate radio front end circuitry 992. Similarly, in some embodiments, all or some of RF transceiver circuitry 972 can be considered a part of interface 990. In still other embodiments, interface 990 can include one or more ports or terminals 994, radio front end circuitry 992, and RF transceiver circuitry 972, as part of a radio unit (not shown), and interface 990 can communicate with baseband processing circuitry 974, which is part of a digital unit (not shown).

Antenna 962 can include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 962 can be coupled to radio front end circuitry 990 and can be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 962 can comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna can be used to transmit/receive radio signals in any direction, a sector antenna can be used to transmit/receive radio signals from devices within a particular area, and a panel antenna can be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna can be referred to as MIMO. In certain embodiments, antenna 962 can be separate from network node 960 and can be connectable to network node 960 through an interface or port.

Antenna 962, interface 990, and/or processing circuitry 970 can be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals can be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 962, interface 990, and/or processing circuitry 970 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals can be transmitted to a wireless device, another network node and/or any other network equipment. Power circuitry 987 can comprise, or be coupled to, power management circuitry and can be configured to supply the components of network node 960 with power for performing the functionality described herein. Power circuitry 987 can receive power from power source 986. Power source 986 and/or power circuitry 987 can be configured to provide power to the various components of network node 960 in a form suitable for the respective components ( e.g ., at a voltage and current level needed for each respective component). Power source 986 can either be included in, or external to, power circuitry 987 and/or network node 960. For example, network node 960 can be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 987. As a further example, power source 986 can comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 987. The battery can provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, can also be used.

Alternative embodiments of network node 960 can include additional components beyond those shown in Figure 9 that can be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 960 can include user interface equipment to allow and/or facilitate input of information into network node 960 and to allow and/or facilitate output of information from network node 960. This can allow and/or facilitate a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 960.

In some embodiments, a wireless device (WD, e.g, WD 910) can be configured to transmit and/or receive information without direct human interaction. For instance, a WD can be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premise equipment (CPE), mobile-type communication (MTC) devices, Internet- of-Things (IoT) devices, vehicle-mounted wireless terminal devices, etc. A WD can support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and can in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD can represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be referred to as an MTC device. As one particular example, the WD can be a UE implementing the 3 GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances ( e.g ., refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD can represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, a WD as described above can be mobile, in which case it can also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 910 includes antenna 911, interface 914, processing circuitry 920, device readable medium 930, user interface equipment 932, auxiliary equipment 934, power source 936 and power circuitry 937. WD 910 can include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 910, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies can be integrated into the same or different chips or set of chips as other components within WD 910.

Antenna 911 can include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 914. In certain alternative embodiments, antenna 911 can be separate from WD 910 and be connectable to WD 910 through an interface or port. Antenna 911, interface 914, and/or processing circuitry 920 can be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals can be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 911 can be considered an interface.

As illustrated, interface 914 comprises radio front end circuitry 912 and antenna 911. Radio front end circuitry 912 comprise one or more filters 918 and amplifiers 916. Radio front end circuitry 914 is connected to antenna 911 and processing circuitry 920 and can be configured to condition signals communicated between antenna 911 and processing circuitry 920. Radio front end circuitry 912 can be coupled to or a part of antenna 911. In some embodiments, WD 910 may not include separate radio front end circuitry 912; rather, processing circuitry 920 can comprise radio front end circuitry and can be connected to antenna 911. Similarly, in some embodiments, some or all of RF transceiver circuitry 922 can be considered a part of interface 914. Radio front end circuitry 912 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 912 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 918 and/or amplifiers 916. The radio signal can then be transmitted via antenna 911. Similarly, when receiving data, antenna 911 can collect radio signals which are then converted into digital data by radio front end circuitry 912. The digital data can be passed to processing circuitry 920. In other embodiments, the interface can comprise different components and/or different combinations of components.

Processing circuitry 920 can 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 WD 910 functionality either alone or in combination with other WD 910 components, such as device readable medium 930. Such functionality can include any of the various wireless features or benefits discussed herein.

For example, processing circuitry 920 can execute instructions stored in device readable medium 930 or in memory within processing circuitry 920 to provide the functionality disclosed herein. More specifically, instructions (also referred to as a computer program product) stored in medium 930 can include instructions that, when executed by processor 920, can configure wireless device 910 to perform operations corresponding to various exemplary methods ( e.g ., procedures) described herein.

As illustrated, processing circuitry 920 includes one or more of RF transceiver circuitry 922, baseband processing circuitry 924, and application processing circuitry 926. In other embodiments, the processing circuitry can comprise different components and/or different combinations of components. In certain embodiments processing circuitry 920 of WD 910 can comprise a SOC. In some embodiments, RF transceiver circuitry 922, baseband processing circuitry 924, and application processing circuitry 926 can be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 924 and application processing circuitry 926 can be combined into one chip or set of chips, and RF transceiver circuitry 922 can be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 922 and baseband processing circuitry 924 can be on the same chip or set of chips, and application processing circuitry 926 can be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 922, baseband processing circuitry 924, and application processing circuitry 926 can be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 922 can be a part of interface 914. RF transceiver circuitry 922 can condition RF signals for processing circuitry 920.

In certain embodiments, some or all of the functionality described herein as being performed by a WD can be provided by processing circuitry 920 executing instructions stored on device readable medium 930, which in certain embodiments can be a computer-readable storage medium. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 920 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 920 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 920 alone or to other components of WD 910, but are enjoyed by WD 910 as a whole, and/or by end users and the wireless network generally.

Processing circuitry 920 can be configured to perform any determining, calculating, or similar operations ( e.g ., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 920, can include processing information obtained by processing circuitry 920 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 910, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 930 can be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 920. Device readable medium 930 can include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g, a hard disk), removable storage media (e.g, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that can be used by processing circuitry 920. In some embodiments, processing circuitry 920 and device readable medium 930 can be considered to be integrated.

User interface equipment 932 can include components that allow and/or facilitate a human user to interact with WD 910. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment 932 can be operable to produce output to the user and to allow and/or facilitate the user to provide input to WD 910. The type of interaction can vary depending on the type of user interface equipment 932 installed in WD 910. For example, if WD 910 is a smart phone, the interaction can be via a touch screen; if WD 910 is a smart meter, the interaction can be through a screen that provides usage ( e.g ., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 932 can include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 932 can be configured to allow and/or facilitate input of information into WD 910 and is connected to processing circuitry 920 to allow and/or facilitate processing circuitry 920 to process the input information. User interface equipment 932 can include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 932 is also configured to allow and/or facilitate output of information from WD 910, and to allow and/or facilitate processing circuitry 920 to output information from WD 910. User interface equipment 932 can include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 932, WD 910 can communicate with end users and/or the wireless network and allow and/or facilitate them to benefit from the functionality described herein.

Auxiliary equipment 934 is operable to provide more specific functionality which may not be generally performed by WDs. This can comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 934 can vary depending on the embodiment and/or scenario.

Power source 936 can, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g, an electricity outlet), photovoltaic devices or power cells, can also be used. WD 910 can further comprise power circuitry 937 for delivering power from power source 936 to the various parts of WD 910 which need power from power source 936 to carry out any functionality described or indicated herein. Power circuitry 937 can in certain embodiments comprise power management circuitry. Power circuitry 937 can additionally or alternatively be operable to receive power from an external power source; in which case WD 910 can be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 937 can also in certain embodiments be operable to deliver power from an external power source to power source 936. This can be, for example, for the charging of power source 936. Power circuitry 937 can perform any converting or other modification to the power from power source 936 to make it suitable for supply to the respective components of WD 910.

Figure 10 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE can 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 can represent a device that is not intended for sale to, or operation by, an end user but which can be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 10200 can be any UE identified by the 3^rd Generation Partnership Project (3 GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 1000, as illustrated in Figure 10, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE can be used interchangeable. Accordingly, although Figure 10 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In Figure 10, UE 1000 includes processing circuitry 1001 that is operatively coupled to input/output interface 1005, radio frequency (RF) interface 1009, network connection interface 1011, memory 1015 including random access memory (RAM) 1017, read-only memory (ROM) 1019, and storage medium 1021 or the like, communication subsystem 1031, power source 1033, and/or any other component, or any combination thereof. Storage medium 1021 includes operating system 1023, application program 1025, and data 1027. In other embodiments, storage medium 1021 can include other similar types of information. Certain UEs can utilize all of the components shown in Figure 10, or only a subset of the components. The level of integration between the components can vary from one UE to another UE. Further, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In Figure 10, processing circuitry 1001 can be configured to process computer instructions and data. Processing circuitry 1001 can be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware-implemented state machines ( e.g ., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1001 can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 1005 can be configured to provide a communication interface to an input device, output device, or input and output device. UE 1000 can be configured to use an output device via input/output interface 1005. An output device can use the same type of interface port as an input device. For example, a USB port can be used to provide input to and output from UE 1000. The output device can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 1000 can be configured to use an input device via input/output interface 1005 to allow and/or facilitate a user to capture information into UE 1000. The input device can 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 can include a capacitive or resistive touch sensor to sense input from a user. A sensor can be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In Figure 10, RF interface 1009 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 1011 can be configured to provide a communication interface to network 1043a. Network 1043a can encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1043a can comprise a Wi-Fi network. Network connection interface 1011 can be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 1011 can implement receiver and transmitter functionality appropriate to the communication network links ( e.g ., optical, electrical, and the like). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.

RAM 1017 can be configured to interface via bus 1002 to processing circuitry 1001 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 1019 can be configured to provide computer instructions or data to processing circuitry 1001. For example, ROM 1019 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (EO), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 1021 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.

In one example, storage medium 1021 can be configured to include operating system 1023; application program 1025 such as a web browser application, a widget or gadget engine or another application; and data file 1027. Storage medium 1021 can store, for use by UE 1000, any of a variety of various operating systems or combinations of operating systems. For example, application program 1025 can include executable program instructions (also referred to as a computer program product) that, when executed by processor 1001, can configure UE 1000 to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.

Storage medium 1021 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 1021 can allow and/or facilitate UE 1000 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system can be tangibly embodied in storage medium 1021, which can comprise a device readable medium.

In Figure 10, processing circuitry 1001 can be configured to communicate with network 1043b using communication subsystem 1031. Network 1043a and network 1043b can be the same network or networks or different network or networks. Communication subsystem 1031 can be configured to include one or more transceivers used to communicate with network 1043b. For example, communication subsystem 1031 can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.10, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver can include transmitter 1033 and/or receiver 1035 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links ( e.g ., frequency allocations and the like). Further, transmitter 1033 and receiver 1035 of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 1031 can include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 1031 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 1043b can encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1043b can be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 1013 can be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1000.

The features, benefits and/or functions described herein can be implemented in one of the components of UE 1000 or partitioned across multiple components of UE 1000. Further, the features, benefits, and/or functions described herein can be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 1031 can be configured to include any of the components described herein. Further, processing circuitry 1001 can be configured to communicate with any of such components over bus 1002. In another example, any of such components can be represented by program instructions stored in memory that when executed by processing circuitry 1001 perform the corresponding functions described herein. In another example, the functionality of any of such components can be partitioned between processing circuitry 1001 and communication subsystem 1031. In another example, the non-computationally intensive functions of any of such components can be implemented in software or firmware and the computationally intensive functions can be implemented in hardware.

Figure 11 is a schematic block diagram illustrating a virtualization environment 1100 in which functions implemented by some embodiments can be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which can include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node ( e.g ., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) 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 (e.g, via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1100 hosted by one or more of hardware nodes 1130. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g, a core network node), then the network node can be entirely virtualized.

The functions can be implemented by one or more applications 1120 (which can alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 1120 are run in virtualization environment 1100 which provides hardware 1130 comprising processing circuitry 1160 and memory 1190. Memory 1190 contains instructions 1195 executable by processing circuitry 1160 whereby application 1120 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 1100 can include general-purpose or special-purpose network hardware devices (or nodes) 1130 comprising a set of one or more processors or processing circuitry 1160, which can be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device can comprise memory 1190-1 which can be non-persistent memory for temporarily storing instructions 1195 or software executed by processing circuitry 1160. For example, instructions 1195 can include program instructions (also referred to as a computer program product) that, when executed by processing circuitry 1160, can configure hardware node 1120 to perform operations corresponding to various exemplary methods ( e.g ., procedures) described herein. Such operations can also be attributed to virtual node(s) 1120 that is/are hosted by hardware node 1130.

Each hardware device can comprise one or more network interface controllers (NICs) 1170, also known as network interface cards, which include physical network interface 1180. Each hardware device can also include non-transitory, persistent, machine-readable storage media 1190-2 having stored therein software 1195 and/or instructions executable by processing circuitry 1160. Software 1195 can include any type of software including software for instantiating one or more virtualization layers 1150 (also referred to as hypervisors), software to execute virtual machines 1140 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 1140, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer 1150 or hypervisor. Different embodiments of the instance of virtual appliance 1120 can be implemented on one or more of virtual machines 1140, and the implementations can be made in different ways.

During operation, processing circuitry 1160 executes software 1195 to instantiate the hypervisor or virtualization layer 1150, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1150 can present a virtual operating platform that appears like networking hardware to virtual machine 1140.

As shown in Figure 11, hardware 1130 can be a standalone network node with generic or specific components. Hardware 1130 can comprise antenna 11225 and can implement some functions via virtualization. Alternatively, hardware 1130 can be part of a larger cluster of hardware ( e.g such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 11100, which, among others, oversees lifecycle management of applications 1120.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV can 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.

In the context of NFV, virtual machine 1140 can be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 1140, and that part of hardware 1130 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 1140, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 1140 on top of hardware networking infrastructure 1130 and corresponds to application 1120 in Figure 11.

In some embodiments, one or more radio units 11200 that each include one or more transmitters 11220 and one or more receivers 11210 can be coupled to one or more antennas 11225. Radio units 11200 can communicate directly with hardware nodes 1130 via one or more appropriate network interfaces and can 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. Nodes arranged in this manner can also communicate with one or more UEs, such as described elsewhere herein.

In some embodiments, some signaling can be performed via control system 11230, which can alternatively be used for communication between the hardware nodes 1130 and radio units 11200.

With reference to Figure 12, in accordance with an embodiment, a communication system includes telecommunication network 1210, such as a 3 GPP -type cellular network, which comprises access network 1211, such as a radio access network, and core network 1214. Access network 1211 comprises a plurality of base stations 1212a, 1212b, 1212c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1213a, 1213b, 1213c. Each base station 1212a, 1212b, 1212c is connectable to core network 1214 over a wired or wireless connection 1215. A first UE 1291 located in coverage area 1213c can be configured to wirelessly connect to, or be paged by, the corresponding base station 1212c. A second UE 1292 in coverage area 1213a is wirelessly connectable to the corresponding base station 1212a. While a plurality of UEs 1291, 1292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1212

Telecommunication network 1210 is itself connected to host computer 1230, which can be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 1230 can be under the ownership or control of a service provider or can be operated by the service provider or on behalf of the service provider. Connections 1221 and 1222 between telecommunication network 1210 and host computer 1230 can extend directly from core network 1214 to host computer 1230 or can go via an optional intermediate network 1220. Intermediate network 1220 can be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1220, if any, can be a backbone network or the Internet; in particular, intermediate network 1220 can comprise two or more sub-networks (not shown).

The communication system of Figure 12 as a whole enables connectivity between the connected UEs 1291, 1292 and host computer 1230. The connectivity can be described as an over-the-top (OTT) connection 1250. Host computer 1230 and the connected UEs 1291, 1292 are configured to communicate data and/or signaling via OTT connection 1250, using access network 1211, core network 1214, any intermediate network 1220 and possible further infrastructure (not shown) as intermediaries. OTT connection 1250 can be transparent in the sense that the participating communication devices through which OTT connection 1250 passes are unaware of routing of uplink and downlink communications. For example, base station 1212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1230 to be forwarded ( e.g ., handed over) to a connected UE 1291. Similarly, base station 1212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1291 towards the host computer 1230.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 13. In communication system 1300, host computer 1310 comprises hardware 1315 including communication interface 1316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1300. Host computer 1310 further comprises processing circuitry 1318, which can have storage and/or processing capabilities. In particular, processing circuitry 1318 can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 1310 further comprises software 1311, which is stored in or accessible by host computer 1310 and executable by processing circuitry 1318. Software 1311 includes host application 1312. Host application 1312 can be operable to provide a service to a remote user, such as UE 1330 connecting via OTT connection 1350 terminating at UE 1330 and host computer 1310. In providing the service to the remote user, host application 1312 can provide user data which is transmitted using OTT connection 1350.

Communication system 1300 can also include base station 1320 provided in a telecommunication system and comprising hardware 1325 enabling it to communicate with host computer 1310 and with UE 1330. Hardware 1325 can include communication interface

1326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1300, as well as radio interface

1327 for setting up and maintaining at least wireless connection 1370 with UE 1330 located in a coverage area (not shown in Figure 13) served by base station 1320. Communication interface 1326 can be configured to facilitate connection 1360 to host computer 1310. Connection 1360 can be direct, or it can pass through a core network (not shown in Figure 13) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1325 of base station 1320 can also include processing circuitry 1328, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.

Base station 1320 also includes software 1321 stored internally or accessible via an external connection. For example, software 1321 can include program instructions (also referred to as a computer program product) that, when executed by processing circuitry 1328, can configure base station 1320 to perform operations corresponding to various exemplary methods ( e.g ., procedures) described herein.

Communication system 1300 can also include UE 1330 already referred to, whose hardware 1335 can include radio interface 1337 configured to set up and maintain wireless connection 1370 with a base station serving a coverage area in which UE 1330 is currently located. Hardware 1335 of UE 1330 can also include processing circuitry 1338, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.

UE 1330 also includes software 1331, which is stored in or accessible by UE 1330 and executable by processing circuitry 1338. Software 1331 includes client application 1332. Client application 1332 can be operable to provide a service to a human or non-human user via EE 1330, with the support of host computer 1310. In host computer 1310, an executing host application 1312 can communicate with the executing client application 1332 via OTT connection 1350 terminating at UE 1330 and host computer 1310. In providing the service to the user, client application 1332 can receive request data from host application 1312 and provide user data in response to the request data. OTT connection 1350 can transfer both the request data and the user data. Client application 1332 can interact with the user to generate the user data that it provides. Software 1331 can also include program instructions (also referred to as a computer program product) that, when executed by processing circuitry 1338, can configure UE 1330 to perform operations corresponding to various exemplary methods (e-g·, procedures) described herein.

As an example, host computer 1310, base station 1320 and UE 1330 illustrated in Figure 13 can be similar or identical to host computer 1230, one of base stations 1212a-c, and one of UEs 1291-1292 of Figure 12, respectively. In other words, the inner workings of these entities can be as shown in Figure 13 and the surrounding network topology can be that of Figure 12.

In Figure 13, OTT connection 1350 has been drawn abstractly to illustrate the communication between host computer 1310 and UE 1330 via base station 1320, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure can determine the routing, which it can be configured to hide from UE 1330 or from the service provider operating host computer 1310, or both. While OTT connection 1350 is active, the network infrastructure can further take decisions by which it dynamically changes the routing ( e.g. , on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 1370 between UE 1330 and base station 1320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 1330 using OTT connection 1350, in which wireless connection 1370 forms the last segment. More precisely, the exemplary embodiments disclosed herein can improve flexibility for the network to monitor end-to-end quality-of-service (QoS) of data flows, including their corresponding radio bearers, associated with data sessions between a user equipment (UE) and another entity, such as an OTT data application or service external to the 5G network. These and other advantages can facilitate more timely design, implementation, and deployment of 5G/NR solutions. Furthermore, such embodiments can facilitate flexible and timely control of data session QoS, which can lead to improvements in capacity, throughput, latency, etc. that are envisioned by 5G/NR and important for the growth of OTT services.

A measurement procedure can be provided for the purpose of monitoring data rate, latency and other network operational aspects on which the one or more embodiments improve. There can further be an optional network functionality for reconfiguring OTT connection 1350 between host computer 1310 and UE 1330, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 1350 can be implemented in software 1311 and hardware 1315 of host computer 1310 or in software 1331 and hardware 1335 of UE 1330, or both. In embodiments, sensors (not shown) can be deployed in or in association with communication devices through which OTT connection 1350 passes; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 1311, 1331 can compute or estimate the monitored quantities. The reconfiguring of OTT connection 1350 can include message format, retransmission settings, preferred routing etc .; the reconfiguring need not affect base station 1320, and it can be unknown or imperceptible to base station 1320. Such procedures and functionalities can be known and practiced in the art. In certain embodiments, measurements can involve proprietary UE signaling facilitating host computer 1310’s measurements of throughput, propagation times, latency and the like. The measurements can be implemented in that software 1311 and 1331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1350 while it monitors propagation times, errors, etc.

Figure 14 is a flowchart illustrating an exemplary method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE such as those described herein with reference to other figures. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section. In step 1410, the host computer provides user data. In substep 1411 (which can be optional) of step 1410, the host computer provides the user data by executing a host application. In step 1420, the host computer initiates a transmission carrying the user data to the UE. In step 1430 (which can be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1440 (which can also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 15 is a flowchart illustrating an exemplary method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE such as those described herein with reference to other figures. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section. In step 1510 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 1520, the host computer initiates a transmission carrying the user data to the UE. The transmission can pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1530 (which can be optional), the UE receives the user data carried in the transmission.

Figure 16 is a flowchart illustrating an exemplary method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE such as those described herein with reference to other figures. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section. In step 1610 (which can be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1620, the UE provides user data. In substep 1621 (which can be optional) of step 1620, the UE provides the user data by executing a client application. In substep 1611 (which can be optional) of step 1610, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application can further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 1630 (which can be optional), transmission of the user data to the host computer. In step 1640 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Figure 17 is a flowchart illustrating an exemplary method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE such as those described herein with reference to other figures. For simplicity of the present disclosure, only drawing references to Figure 17 will be included in this section. In step 1710 (which can be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1720 (which can be optional), the base station initiates transmission of the received user data to the host computer. In step 1730 (which can be optional), the host computer receives the user data carried in the transmission initiated by the base station.

The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the spirit and scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.

The term unit, as used herein, can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure. As described herein, device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor. Furthermore, functionality of a device or apparatus can be implemented by any combination of hardware and software. A device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other. Moreover, devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

In addition, certain terms used in the present disclosure, including the specification, drawings and exemplary embodiments thereof, can be used synonymously in certain instances, including, but not limited to, e.g ., data and information. It should be understood that, while these words and/or other words that can be synonymous to one another, can be used synonymously herein, that there can be instances when such words can be intended to not be used synonymously. Further, to the extent that the prior art knowledge has not been explicitly incorporated by reference herein above, it is explicitly incorporated herein in its entirety. All publications referenced are incorporated herein by reference in their entireties.

Example embodiments of the methods, apparatus, and computer-readable media described herein include, but are not limited to, the following enumerated examples:

El . A method, performed by a user equipment (UE), for updating ephemeris data in a non-terrestrial network (NTN) configured to operate as a radio access network (RAN), the method comprising: receiving, from a network node in the NTN, updated ephemeris data related to one or more satellites in the NTN; selectively storing the updated ephemeris data, in a non-volatile memory of the UE, in association with further ephemeris data currently stored in the non-volatile memory.

E2. The method of embodiment El, further comprising receiving, in associated with the updated ephemeris data, respective lists of cells served by each of the satellites.

E3. The method of any of embodiments E1-E2, wherein the updated ephemeris data is received in a handover command from the network node.

E4. The method of any of embodiments E1-E2, wherein the updated ephemeris data is received via broadcast in a cell served by the network node.

E5. The method of any of embodiments E1-E2, further comprising sending an ephemeris update request to the network node, wherein the updated ephemeris data is received in response to the ephemeris update request.

E6. The method of embodiment E5, wherein the ephemeris update request includes a timestamp or duration of validity associated with the further ephemeris data.

E7. The method of any of embodiments E5-E6, further comprising successfully connecting to the NTN after a predetermined number of failed attempts to connect to the NTN, wherein the ephemeris update request is sent in response to the successful connection.

E8. The method of any of embodiments E5-E6, further comprising determining that a duration of validity of at least a portion of the further ephemeris data has expired, wherein the ephemeris update request is sent in response to determining that the duration of validity has expired.

E9. The method of embodiment E8, wherein the duration of validity is a parameter of the further ephemeris data.

E10. The method of embodiment E8, wherein determining that the duration of validity has expired further comprises: initiating a validity timer; and determining that the validity timer has expired.

El 1. The method of any of embodiments E1-E10, wherein: the further ephemeris data is related to one or more first satellites or orbital planes; the updated ephemeris data is related to one or more second satellites or orbital planes, that are different from the first satellites or orbital planes; selectively storing comprises storing the updated ephemeris data and retaining the further ephemeris data.

E12. The method of any of embodiments E1-E10, wherein: the further ephemeris data is associated with a first duration of validity; the updated ephemeris data is associated with a second duration of validity, subsequent to the first duration of validity; and selectively storing comprises one of the following: overwriting the further ephemeris data with the updated ephemeris data; or storing the updated ephemeris data in association with a high priority indicator and storing a low priority indicator in association with the further ephemeris data.

E13. The method of any of embodiments E1-E10, wherein: the further ephemeris data is related to a first public land mobile network (PLMN); the updated ephemeris data is related to a second PLMN different from the first PLMN; and selectively storing comprises one of the following: overwriting the further ephemeris data with the updated ephemeris data; or storing the updated ephemeris data and retaining the further ephemeris data.

E14. A method, performed by a network node, for providing updated ephemeris data in a non-terrestrial network (NTN) configured to operate as a radio access network (RAN), the method comprising: sending, to one or more EIEs operating in a cell served by the network node, updated ephemeris data related to one or more satellites in the NTN. E15. The method of embodiment E14, further comprising sending, in association with the updated ephemeris data, respective lists of cells served by each of the satellites.

E16. The method of any of embodiments E14-E15, further comprising determining the updated ephemeris in association with a change in at least one satellite or orbital plane of the NTN.

E17. The method of any of embodiments E14-E16, wherein the updated ephemeris data is sent in a handover command to a particular one of the EIEs.

E18. The method of any of embodiments E14-E16, further comprising receiving an ephemeris update request from a particular one of the EIEs, wherein the updated ephemeris data is sent to the particular TIE in response to the ephemeris update request.

E19. The method of embodiment E18, wherein the ephemeris update request includes a timestamp or duration of validity associated with the further ephemeris data.

E20. The method of embodiment E19, further comprising determining the updated ephemeris based data on the timestamp or duration of validity included in the ephemeris update request.

E21. The method of any of embodiments E14-E16, wherein the updated ephemeris data is sent via broadcast in a cell served by the network node.

E22. The method of any of embodiments E14-E21, wherein the updated ephemeris data is related to one or more of the following: one or more satellites or orbital planes; a duration of validity; and a public land mobile network (PLMN).

E23. A user equipment (TIE) configured to operate in a non-terrestrial network (NTN), the TIE comprising: radio interface circuitry configured to communicate with a network node via at least one cell; and processing circuitry operably coupled to the radio interface circuitry, whereby the processing circuitry and the radio interface circuitry are configured to perform operations corresponding to any of the methods of embodiments El- E13.

E24. A user equipment (UE) configured to operate in a non-terrestrial network (NTN), the UE being further arranged to perform operations corresponding to any of the methods of embodiments El -El 3.

E25. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a user equipment (UE), configure the UE to perform operations corresponding to any of the methods of embodiments El -El 3.

E26. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE), configure the UE to perform operations corresponding to any of the methods of embodiments El -El 3.

E27. A network node in a non-terrestrial network (NTN) configured to operate as a radio access network (RAN), the network node comprising: radio interface circuitry configured to communicate with user equipment (UEs) via the at least one cell; and processing circuitry operably coupled to the radio interface circuitry, whereby the processing circuitry and the radio interface circuitry are configured to perform operations corresponding to any of the methods of embodiments E14-E22.

E28. A network node in a non-terrestrial network (NTN) configured to operate as a radio access network (RAN), the network node being further arranged to perform operations corresponding to any of the methods of embodiments E14-E22.

E29. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a network node in a non- terrestrial network (NTN), configure the network node to perform operations corresponding to any of the methods of embodiments E14-E22.

E30. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a network node in a non-terrestrial network (NTN), configure the network node to perform operations corresponding to any of the methods of embodiments E14-E22.

Glossary of some abbreviations used above:

3GPP 3rd Generation Partnership Project

5GS 5G system

AMF Access and Mobility Management Function

BS Base Station

CU Control Unit or Centralized Unit

DU Distributed Unit eMBB enhanced mobile broadband EPC Evolved Packet Core EPS Evolved Packet System GEO Geostationary Orbit GW Gateway HO Handover LEO Low Earth Orbit LTE Long Term Evolution LTE-M LTE for Machine-Type Communications MAC Medium Access Control MBB Mobile broadband MEO Medium Earth Orbit mMTC massive machine type communications MME Mobility Management Entity NAS Non-Access Stratum NB-IoT Narrowband Internet of Things NGSO Non-Geostationary Orbit NR New Radio

NTN Non-T erre stri al N etwork NW Network

PLMN Public Land Mobile Network RACH Random Access Channel RRC Radio Resource Control SI System Information SIB System Information Block UE User Equipment

URLLC ultra-reliable and low latency communication uSIM Universal Subscriber Identity Module

Claims

1. A method, performed by a user equipment, UE, for updating ephemeris data in a non-terrestrial network, NTN, configured to operate as a radio access network, RAN, the method comprising: receiving (740), from a network node in the NTN, updated ephemeris data related to one or more satellites in the NTN; and selectively storing (760), in a non-volatile memory of the UE, the updated ephemeris data in association with further ephemeris data currently stored in the non volatile memory.

2. The method of claim 1, further comprising receiving (750), in association with the updated ephemeris data, respective lists of cells served by each of the satellites.

3. The method of any of claims 1-2, further comprising sending (730) an ephemeris update request to the network node, wherein the updated ephemeris data is received in response to the ephemeris update request.

4. The method of claim 3, wherein the ephemeris update request includes a timestamp or duration of validity associated with the further ephemeris data.

5. The method of any of claims 3-4, further comprising successfully connecting (720) to the NTN after a predetermined number of failed attempts to connect to the NTN, wherein the ephemeris update request is sent in response to the successful connection.

6. The method of any of claims 3-4, further comprising determining (710) that a duration of validity of at least a portion of the further ephemeris data has expired, wherein the ephemeris update request is sent in response to determining that the duration of validity has expired.

7. The method of any of claims 1-6, wherein: the further ephemeris data is related to one or more first satellites or orbital planes; the updated ephemeris data is related to one or more second satellites or orbital planes that are different from the first satellites or orbital planes; and selectively storing (760) the updated ephemeris data in association with the further ephemeris data comprises storing (761) the updated ephemeris data and retaining the further ephemeris data.

8. The method of any of claims 1-6, wherein: the further ephemeris data is associated with a first duration of validity; the updated ephemeris data is associated with a second duration of validity that is subsequent to the first duration of validity; and selectively storing (760) the updated ephemeris data in association with the further ephemeris data comprises one of the following: overwriting (762) the further ephemeris data with the updated ephemeris data; or storing (763) the updated ephemeris data in association with a high priority indicator and storing a low priority indicator in association with the further ephemeris data.

9. The method of any of claims 1-6, wherein: the further ephemeris data is related to a first public land mobile network, PLMN; the updated ephemeris data is related to a second PLMN that is different from the first PLMN; and selectively storing (760) the updated ephemeris data in association with the further ephemeris data comprises one of the following: overwriting (762) the further ephemeris data with the updated ephemeris data; or storing (761) the updated ephemeris data and retaining the further ephemeris data.

10. A method, performed by a network node, to provide updated ephemeris data in a non-terrestrial network, NTN, configured to operate as a radio access network, RAN, the method comprising: sending (840), to one or more user equipment, UEs, operating in a cell served by the network node, updated ephemeris data related to one or more satellites in the NTN.

11. The method of claim 10, further comprising sending (850) to the one or more UEs, in association with the updated ephemeris data, respective lists of cells served by each of the satellites.

12. The method of any of claims 10-11, further comprising determining (810) the updated ephemeris in association with a change in at least one satellite or orbital plane of the NTN.

13. The method of any of claims 10-12, further comprising receiving (820) an ephemeris update request from a particular one of the UEs, wherein the updated ephemeris data is sent to the particular UE in response to the ephemeris update request.

14. The method of claim 13, wherein the ephemeris update request includes a timestamp or duration of validity associated with the further ephemeris data.

15. The method of claim 14, further comprising determining (830) the updated ephemeris data based on the timestamp or duration of validity included in the ephemeris update request.

16. The method of any of claims 10-15, wherein the updated ephemeris data is related to one or more of the following: one or more satellites or orbital planes; a duration of validity; and a public land mobile network, PLMN.

17. A user equipment, UE (120, 410, 510, 610, 910, 1000, 1330), comprising: radio interface circuitry (914, 1009, 1031, 1337) configured to communicate with one or more satellites (430) in a non-terrestrial network, NTN (400), configured to operate as a radio access network, RAN; and processing circuitry (920, 1001, 1338) operably coupled to the radio interface circuitry, whereby the processing circuitry and the radio interface circuitry are configured to: receive, from a network node in the NTN, updated ephemeris data related to one or more satellites in the NTN; and selectively store, in a non-volatile memory of the UE, the updated ephemeris data in association with further ephemeris data currently stored in the non-volatile memory.

18. The UE of claim 17, wherein the processing circuitry and the radio interface circuitry are further configured to receive, in association with the updated ephemeris data, respective lists of cells served by each of the satellites.

19. The UE of any of claims 17-18, wherein: the processing circuitry and the radio interface circuitry are further configured to send an ephemeris update request to the network node; and the updated ephemeris data is received in response to the ephemeris update request.

20. The UE of claim 19, wherein the ephemeris update request includes a timestamp or duration of validity associated with the further ephemeris data.

21. The UE of any of claims 19-20, wherein: the processing circuitry and the radio interface circuitry are further configured to successfully connect to the NTN after a predetermined number of failed attempts to connect to the NTN; and the ephemeris update request is sent in response to the successful connection.

22. The UE of any of claims 19-20, wherein the processing circuitry and the radio interface circuitry are further configured to: determine that a duration of validity of at least a portion of the further ephemeris data has expired; and send the ephemeris update request in response to determining that the duration of validity has expired.

23. The UE of any of claims 17-22, wherein: the further ephemeris data is related to one or more first satellites or orbital planes; the updated ephemeris data is related to one or more second satellites or orbital planes that are different from the first satellites or orbital planes; and the processing circuity is configured to selectively store the updated ephemeris data in association with the further ephemeris data by storing the updated ephemeris data and retaining the further ephemeris data.

24. The UE of any of claims 17-22, wherein: the further ephemeris data is associated with a first duration of validity; the updated ephemeris data is associated with a second duration of validity that is subsequent to the first duration of validity; and the processing circuity is configured to selectively store the updated ephemeris data in association with the further ephemeris data by one of the following: overwriting the further ephemeris data with the updated ephemeris data; or storing the updated ephemeris data in association with a high priority indicator and storing a low priority indicator in association with the further ephemeris data.

25. The UE of any of claims 17-22, wherein: the further ephemeris data is related to a first public land mobile network, PLMN; the updated ephemeris data is related to a second PLMN that is different from the first PLMN; and the processing circuity is configured to selectively store the updated ephemeris data in association with the further ephemeris data by one of the following: overwriting the further ephemeris data with the updated ephemeris data; or storing the updated ephemeris data and retaining the further ephemeris data.

26. A user equipment, UE (120, 410, 510, 610, 910, 1000, 1330), configured to operate in a non-terrestrial network, NTN (400), the UE being arranged to perform operations corresponding to any of the methods of claims 1-9.

27. A non-transitory, computer-readable medium (930, 1021) storing computer- executable instructions that, when executed by processing circuitry (920, 1001, 1338) of a user equipment, UE (120, 410, 510, 610, 910, 1000, 1330), configure the UE to perform operations corresponding to any of the methods of claims 1-9.

28. A computer program product (1025, 1331) comprising computer-executable instructions that, when executed by processing circuitry of a user equipment, UE (120, 410, 510, 610, 910, 1000, 1292, 1330), configure the UE to perform operations corresponding to any of the methods of claims 1-9.

29. A network node (134, 138, 430, 450, 460, 520, 620, 960, 1130, 1320) in a non terrestrial network, NTN (400), configured to operate as a radio access network, RAN, the network node comprising: communication interface circuitry (990, 1170, 1326) configured to communicate with user equipment, UEs (120, 410, 510, 610, 910, 1000, 1292, 1330), via one or more satellites (430) of the NTN; and processing circuitry (970, 1160, 1328) operably coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to: send, to one or more user equipment, UEs, operating in a cell served by the network node, updated ephemeris data related to one or more satellites in the NTN.

30. The network node of claim 29, wherein the processing circuitry and the communication interface circuitry are further configured to send to the one or more UEs, in association with the updated ephemeris data, respective lists of cells served by each of the satellites.

31. The network node of any of claims 29-30, wherein the processing circuitry is further configured to determine the updated ephemeris in association with a change in at least one satellite or orbital plane of the NTN.

32. The network node of any of claims 29-31, wherein the processing circuitry and the communication interface circuitry are further configured to receive an ephemeris update request from a particular one of the UEs, wherein the updated ephemeris data is sent to the particular UE in response to the ephemeris update request.

33. The network node of claim 32, wherein the ephemeris update request includes a timestamp or duration of validity associated with the further ephemeris data.

34. The network node of claim 33, wherein the processing circuitry is further configured to determine the updated ephemeris data based on the timestamp or duration of validity included in the ephemeris update request.

35. The network node of any of claims 29-34, wherein the updated ephemeris data is related to one or more of the following: one or more satellites or orbital planes; a duration of validity; and a public land mobile network, PLMN.

36. A network node (134, 138, 430, 450, 460, 520, 620, 960, 1130, 1320) in a non terrestrial network, NTN (400), the network node being arranged to perform operations corresponding to any of the methods of claims 10-16.

37. A non-transitory, computer-readable medium (980, 1190) storing computer- executable instructions that, when executed by processing circuitry (970, 1160, 1328) of a network node (134, 138, 430, 450, 460, 520, 620, 960, 1130, 1320) in a non-terrestrial network, NTN (400) configured to operate as a radio access network, RAN, configure the network node to perform operations corresponding to any of the methods of claims 10-16.

38. A computer program product (1195, 1321) comprising computer-executable instructions that, when executed by processing circuitry (970, 1160, 1328) of a network node (134, 138, 430, 450, 460, 520, 620, 960, 1130, 1320) in a non-terrestrial network,

NTN (400) configured to operate as a radio access network, RAN, configure the network node to perform operations corresponding to any of the methods of claims 10-16.