Signaling for ephemeris information

Abstract

The present application relates to apparatuses and components, systems, and methods including devices and means for ephemeris signaling in wireless networks.

Description

BACKGROUND

[0001] As wireless networks have evolved, networks have evolved to serve more areas and more remote areas. One approach has been proposed for wireless networks to serve more areas and more remote areas, namely, utilizing non-terrestrial networks. Specifically, satellites can be utilized within a network to provide radio access network (RAN) services. Using satellites within a network presents many challenges. BRIEF DESCRIPTION OF DRAWINGS

[0002] Figure 1 A network arrangement is shown in accordance with some embodiments.

[0003] Figure 2 A signaling procedure is shown in accordance with some embodiments.

[0004] Figure 3 An operational flow / algorithmic structure is shown in accordance with some embodiments.

[0005] Figure 4 Another operational flow / algorithmic structure is shown in accordance with some embodiments.

[0006] Figure 5 A signaling procedure is shown in accordance with some embodiments.

[0007] Figure 6 Another operational flow / algorithmic structure is shown in accordance with some embodiments.

[0008] Figure 7 User equipment is shown in accordance with some embodiments.

[0009] Figure 8 Network equipment is shown in accordance with some embodiments. DETAILED DESCRIPTION

[0010] The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, and so on in order to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of various embodiments can be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A / B” and “A or B” mean (A), (B), or (A and B).

[0011] The following is a glossary of terms that can be used in the present disclosure.

[0012] The term "circuitry" as used herein refers to, is part of, includes, or encompasses hardware components that are configured as or arranged to provide the described functionality. The hardware components can include electronic circuits, logic circuits, processors (shared, dedicated, or group), or memories (shared, dedicated, or group), application specific integrated circuits (ASICs), field programmable devices (FPDs) (for example, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable systems on chips (SoCs)), or digital signal processors (DSPs). In some embodiments, the circuitry can execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuitry" can also refer to a combination of one or more hardware elements with the program code used to carry out the functionality of the program code, or a combination of one or more hardware elements and the program code used to carry out the functionality of the program code in an electrical or electronic system. In these embodiments, the combination of hardware elements and program code can be referred to as a particular type of circuitry.

[0013] As used herein, the term "processor circuitry" refers to, is part of, or includes circuitry capable of sequentially and automatically processing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuitry" can refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes.

[0014] As used herein, the term "interface circuitry" refers to, is part of, or includes circuitry that enables information exchange between two or more components or devices. The term "interface circuitry" can refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, and a network interface card.

[0015] As used herein, the term "user equipment" or "UE" refers to a device with radio communication capabilities that can allow a user to access network resources in a communication network. The term "user equipment" or "UE" can be considered synonymous to and can be referred to as a client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile equipment. Furthermore, the term "user equipment" or "UE" can include any type of wireless / wired device or any computing device including a wireless communication interface.

[0016] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" can refer to various components of a computer that are communicatively coupled to each other. Further, the term "computer system" or "system" can refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or networking resources.

[0017] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database, and application or unit of work. A "hardware resource" can refer to a computing, storage, or network resource provided by a physical hardware element. A "virtualized resource" can refer to a computing, storage, or network resource provided by a virtualization infrastructure to an application, device, or system. The term "network resource" or "communication resource" can refer to a resource that is accessible by a computer device / system via a communication network. The term "system resource" can refer to any kind of shared entity that provides a service and can include a computing resource or a network resource. A system resource can be viewed as a set of coherent functions, network data objects, or services that are accessible through a server, where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0018] As used herein, the term "channel" refers to any tangible or intangible transmission medium that is used to convey data or data signals. The term "channel" can be synonymous with or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier wave," "radio frequency carrier wave," or any other similar term denoting a pathway or medium through which data is conveyed. Additionally, as used herein, the term "link" refers to a connection between two devices for transmitting and receiving information.

[0019] As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. An "instance" also refers to a concrete occurrence of an object, which can occur, for example, during execution of program code.

[0020] The term "connect" can mean that two or more elements have an established signaling relationship with each other over a communication channel, link, interface, or reference point at a common communication protocol layer.

[0021] As used herein, the term “network element” refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term “network element” can be considered synonymous with or otherwise be referred to as a networked computer, networked hardware, network equipment, network node, or virtualized network function.

[0022] The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual content of an information element, or a data element containing content. An information element can include one or more additional information elements.

[0023] Wireless networks have evolved to include non-terrestrial networks (NTNs) for providing wireless area network (WAN) services to user equipment (UEs). Ephemeris information can describe orbital paths and locations of non-terrestrial components, including, for example, satellites or high-altitude platform systems (HAPS). The ephemeris information can be used: for mobility and measurement operations in cell selection, cell reselection, and conditional handover (CHO); for time and frequency pre-compensation to account for UE-to-base station round trip time and Doppler shift for random access; and to indirectly signal the network and satellite type (e.g., TN, NTN GEO, NTN LEO) or timing information about when a cell will stop serving an area. Embodiments herein describe signaling of ephemeris and related information in New Radio (NR) networks.

[0024] Figure 1 An example network arrangement 100 is shown in accordance with some embodiments. In particular, the network arrangement 100 shows an example NTN in which the methods described herein can be implemented. For clarity and brevity, the NTN shown in the network arrangement 100 is in a simplified form showing a single representation of each element. It will be appreciated that one or more of each of the elements can be present in embodiments of the network arrangement 100.

[0025] The network arrangement 100 can include a base station 102. The base station 102 can provide WAN services to UEs in conjunction with other components within the network arrangement 100. The base station 102 can include a Node B. For example, the base station 102 can include a next generation Node B (gNB), an evolved Node B (eNB), or another type of Node B.

[0026] The network arrangement 100 can also include a core network (CN) 104. For example, the CN 104 can include a 5thGeneration Core Network (5GC). The CN 104 can be coupled to the base stations 102 via fiber or wireless backhaul. The CN 104 can provide functions such as subscriber profile information, subscriber location, service authentication, and / or handover functions for voice and data sessions to UEs that form connections with the base stations 102. The CN 104 can include an Access and Mobility Management Function (AMF) 120 that serves as a control plane function to provide registration management, connection management, reachability management, and mobility management services. The CN 104 can also include a Policy Control Function (PCF) 122 to provide policies associated with mobility management and session management. The functions of the CN 104, including the AMF 120 and the PCF 122, can be included in non-access stratum (NAS) messages of the network arrangement 100, as will be further described.

[0027] The network arrangement 100 can also include a UE 106. The UE 106 can be configured to establish a connection with the WAN and provide services of the WAN to a user of the UE 106. For example, the UE 106 can be configured to establish a wireless connection to a portion of the WAN, such as the base station 102.

[0028] The network arrangement 100 can also include an NTN device 108. For example, the NTN device 108 can include a geo-stationary satellite (such as a geosynchronous earth orbit satellite or a high-altitude platform station (HAPS)), a quasi-geo-stationary satellite (such as a non-geosynchronous earth orbit (NGEO) satellite with steerable beams), or a geo-mobile satellite (such as a NGEO with fixed beams or non-steerable beams). The NTN device 108 can travel along a heading 112 during operation.

[0029] The NTN device 108 can facilitate wireless connections between the base station 102 and the UE 106 by passing signals between the two network devices. The signals can be passed on a first service link between the NTN device 108 and the base station 102 and a second service link between the NTN device 108 and the UE 106. The base station 102 or the UE 106 can benefit from having ephemeris information about the location or heading 112 of the NTN device 108 to establish and maintain these service links. In traditional implementations, there is no agreed upon limit of ephemeris information, and there is no agreed upon method to deliver ephemeris information to the UE 106.

[0030] Network deployment 100 supports fixed Earth satellite service links, quasi-fixed Earth satellite service links, and mobile Earth satellite service links. For fixed Earth satellite service links, continuous coverage of the same geographic area can be provided via beams (e.g., in the case of GEO satellites and HAPS). For quasi-fixed Earth satellite service links, coverage of one geographic area for a limited time period and coverage of a different geographic area during another time period can be provided via beams (e.g., in the case of NGEO satellites generating maneuverable beams). For mobile Earth satellite service links, coverage areas are provided by beams that slide across the Earth's surface (e.g., in the case of NGEO satellites generating fixed or non-maneuverable beams).

[0031] Network deployment 100 may also include an NTN control center 110. The NTN control center 110 may store ephemeris information about the position or heading of one or more NTN devices within a constellation of NTN devices. As an example, the NTN control center 110 may store information about the position or heading of NTN device 108 in the illustrated embodiment.

[0032] According to some implementation schemes, Table 1 includes ephemeris parameters and brief explanations.

[0033]

[0034] Ephemeris, also known as orbital position information, can be divided into slowly changing ephemeris and rapidly changing ephemeris.

[0035] Slowly changing ephemeris, or simply “slow ephemeris,” can include coarse information, also known as almanac information. Generally, slow ephemeris provides information about which satellites from a constellation are currently visible, their orbits, or other information that will not change rapidly. Slow ephemeris can provide information valid for several hours to several days. Slow ephemeris allows the device to determine the coarse Earth coverage area WAN coverage provided by the combination of NTN device 108 and base station 102. In some implementations, slow ephemeris may include the information in Table 1. t oe , , e , M o , ω , i o ,and Ω O In other implementations, the slow ephemeris may include additional / alternative parameters.

[0036] Fast-changing ephemeris or simply“fast ephemeris” can provide more accurate satellite orbital position or coverage information. Fast ephemeris can provide information valid for less than a few hours. In some embodiments, fast ephemeris can include ephemeris corrections or account for antenna beam steering parameters that can be valid for only a few seconds to a few minutes. Fast ephemeris can allow a device to determine accurate earth footprint WAN coverage provided by an NTN device 108 in combination with a base station 102. In some embodiments, fast ephemeris can include the parameters of Table 1 Δn , , , c uc , c us , and c ic , c is . In other embodiments, fast ephemeris can include additional / alternative parameters.

[0037] In general, slow ephemeris can be distinguished from fast ephemeris by a validity period of the associated information. Slow ephemeris can include information in which the validity period exceeds a threshold period, and fast ephemeris can include information in which the validity period is less than the threshold period. In some embodiments, the threshold can be three hours. In some embodiments, multiple thresholds can be used to define more than two types of ephemeris. For example, slow ephemeris can have a validity period of 3 hours or more; first-level fast ephemeris can have a validity period between 120 seconds and 3 hours; and second-level fast ephemeris can have a validity period of less than 120 seconds. It should be understood that any number of ephemeris types can be defined in this manner.

[0038] In some embodiments, a base station 102 can retrieve ephemeris information for a serving cell (e.g., NTN device 108) and one or more neighboring cells from an NTN control center 110. The base station 102 can then provide some or all of the ephemeris information to a UE 106. The UE 106 can utilize the ephemeris information to determine location information for the NTN device 108 or other NTN devices providing neighboring cell coverage. The determined location information can include earth footprint WAN coverage for the NTN device 108 in combination with the base station 102. The UE 106 can use one or more well-known formulas with fields of the ephemeris information to identify a location of the NTN device 108 or its earth footprint WAN coverage 114. The earth footprint WAN coverage 114 can define an area in which the NTN device 108 is to provide radio access coverage for a cell of the base station 102.

[0039] In some embodiments, a base station 102 can broadcast ephemeris information in a system information (SI) message. The SI message can include a master information block (MIB) or one or more system information blocks (SIBs).

[0040] For embodiments using a 15 kHz subcarrier spacing, the SI message can have a periodicity of up to 5.12 seconds. In general, updating ephemeris every few tens of seconds can be sufficient for desired operation including time and frequency pre-compensation. However, in some cases, it can not be sufficient. For example, if the UE 106 responds to a page or initiates a mobile terminated (MT) session (e.g., for a voice call), it can not be able to wait several seconds to acquire ephemeris, perform time and possibly frequency pre-compensation, and then perform random access. Thus, in some cases, it can be desirable to map at least a portion of the ephemeris to an SI message with a much lower periodicity, e.g., 80 milliseconds.

[0041] The UE 106 can store the ephemeris as long as the information is valid and does not expire. The length of validity of the ephemeris can be a function of the type of information broadcast (e.g., fast ephemeris or slow ephemeris) and system implementation.

[0042] Embodiments describe a dynamic system that provides ephemeris in system information while reducing UE energy consumption impact in idle mode by, for example, reducing unnecessary SI acquisition. Various embodiments can be suitable for timely delivery of ephemeris with a wide range of validity period ranges through SI messages. These embodiments can be constrained in a way that UE performance is not penalized. For example, the UE 106 can be able to perform initial access within a desired delay constraint.

[0043] While some embodiments describe transmitting ephemeris in radio resource control (RRC) messages such as SI messages, other embodiments describe utilizing other mechanisms to transmit ephemeris. For example, certain types of ephemeris information can be delivered from the core network 104 through NAS signaling, while other types of ephemeris or related information can be delivered from the base station 102 in RRC messages.

[0044] The NAS-based ephemeris delivery aspects can include enhancements to UE policy delivery. The PCF 122 can use 5G NAS signaling to deliver a variety of UE policies, including, for example, UE Route Selection Policy (URSP), Access Network Discovery and Selection Policy (ANDSP), and Vehicle-to-Everything Policy (V2XP).

[0045] Various features of the UE policy service can also be beneficial for delivering ephemeris information. One of these attractive features includes support for segmentation using a UE Policy Segment Identifier (UPSI) and a UE Policy Segment Code (UPSC). This can allow information to be of arbitrary size. Another attractive feature is native support for modification, deletion, and provision of content. These and other features of the UE policy service can be used to transmit ephemeris.

[0046] Figure 2 is a signaling procedure 200 that illustrates NAS-based ephemeris information delivery in some embodiments. The signaling procedure 200 can include messages transmitted between a UE 106, an AMF 120, and a PCF 122.

[0047] The signaling procedure 200 can include, at 204, the UE transmitting a UL NAS transport message to the AMF 120 to initiate a NAS transport procedure. The NAS transport procedure can be initiated to transport a payload, such as a UE policy container, between the UE 106 and the AMF 120.

[0048] The UL NAS transport message can include a UE status indication message that is used to: deliver a UPSI for a UE policy segment stored in the UE 106; indicate whether the UE supports ANDSP; or deliver one or more operating system (OS) identities for the UE 106. In some embodiments, the UE status indication message can be in a field of the UE policy container.

[0049] In some embodiments, the UE status indication message can be updated to include ephemeris-related information. For example, the UE status indication message can: include an indication of whether the UE 106 supports storage of ephemeris; request ephemeris from a particular type of satellite system (e.g., an orbit type such as low earth orbit (LEO), medium earth orbit (LEO), or GEO); or request ephemeris from a particular satellite system that can be identified by a public land mobile network (PLMN) identifier or some other identifier.

[0050] The signaling procedure 200 can also include, at 208, the AMF 120 forwarding the UE status indication to the PCF 122.

[0051] The signaling procedure 200 can also include, at 212, the PCF 122 transmitting a manage UE policy command message to the UE 106 through the AMF 120. The manage UE policy command message can be sent to the UE 106 to request that the UE 106 manage a UE policy segment. The manage UE policy command message can include an identity field that identifies a UE policy delivery service message type, and can also include a list of UE policy segments that the UE is requested to manage.

[0052] In some embodiments, the manage UE policy command message can provide ephemeris information requested in the UE status indication or other ephemeris information. The ephemeris information can include ephemeris parameters or meta-information related to ephemeris. The meta-information can include, for example: a satellite system identity and type; an ephemeris format (e.g., an orbit format or an earth-centered earth-fixed (ECEF) format); a validity time (after which the information can be considered invalid or out-of-date); or an ephemeris granularity (e.g., fast ephemeris, slow ephemeris, or both fast and slow ephemeris).

[0053] The management UE policy command message can be a field of a UE policy container, which is a payload transmitted from the PCF 122 to the UE 106. The ephemeris information can be part of the UE policy container itself or designated as an additional field in the management UE policy command message.

[0054] The AMF 120 can generate a DL NAS transport message to include the management UE policy command message and then transmit the DL NAS transport message to the UE 106 at 216.

[0055] The UE 106 can generate a UL NAS transport message including a management UE policy completion message to indicate that all received instructions were successfully executed at the UE 106. The management UE policy completion message can include a procedure transaction identity and an identity field identifying the UE policy delivery service message type.

[0056] While Figure 2 The signaling procedures of FIGS. 1-3 are generally shown as UE-initiated NAS transport procedures, but other embodiments can use network-initiated NAS transport procedures to transmit ephemeris information. Generally, NAS-based delivery can be more suitable for slow ephemeris, given that policy information is assumed to be provided relatively infrequently. However, embodiments are not so limited.

[0057] Figure 3 An operational flow / algorithmic structure 300 is shown in accordance with some embodiments. The operational flow / algorithmic structure 300 can be performed or implemented by a UE such as, for example, the UE 106 or the UE 700; or a component thereof such as, for example, the baseband processor 704A.

[0058] The operational flow / algorithmic structure 300 can include generating an uplink NAS transport message to include an indication of UE support for storage of ephemeris or to request ephemeris information at 304. The requested information can include a request for ephemeris from a particular type of satellite system such as, for example, a LEO, GEO, or MEO system. The requested information can additionally or alternatively include a request for ephemeris from a particular satellite system associated with an identifier in the uplink NAS transport message. In some embodiments, the identifier can be a PLMN identifier.

[0059] In some embodiments, the uplink NAS transport message can include a UE policy container or a UE status indication, as described above with respect to the message 204 of FIG. 2. Figure 2

[0060] The operational flow / algorithmic structure 300 can also include transmitting the uplink NAS transport message to an AMF at 308.

[0061] ​The operational flow / algorithmic structure 300 can also include receiving a message with ephemeris or metadata related to ephemeris at 312. The message can include information specifically requested by the uplink NAS transfer message, or can include other types of information. The information can be associated with a satellite system identity or type, and can include an ephemeris format (e.g., orbital or ECEF); a validity time, after which the information can be considered out of date; or a granularity of the ephemeris.

[0062] In some embodiments, ephemeris information can be delivered through system information. This can be in addition to or as an alternative to delivering ephemeris information through NAS signaling as described above.

[0063] In some embodiments, ephemeris information can be incorporated into a broadcast SIB. Ephemeris broadcast every few seconds to minutes can be sufficient to meet time and frequency synchronization / pre-compensation requirements for initial access. However, this can also be associated with increased UE power consumption caused by unnecessary SI modification.

[0064] If the base station 102 changes information in a SIB, the base station can transmit the modified SIB and trigger an SI modification procedure. The SI modification procedure can include the base station 102 transmitting a SIB1 with a changed systemlnfoValueTag value and transmitting a paging message with a systemlnfoModification field set to a value of true.

[0065] If the UE 106 detects that the systemlnfoValueTag has changed within a modification period, or receives a paging message with the systemlnfoModification field set to true, the UE 106 can process the SIB to obtain updated information. In some cases, this can involve transitioning the UE 106 out of a power saving idle mode in discontinuous reception (DRX).

[0066] Using the existing SI modification procedure can be sufficient for slow ephemeris that can change on the order of hours or days. However, fast ephemeris can change more quickly. For example, it can be power intensive for a UE to wake up every few seconds to get new SI whenever a paging occasion occurs during idle mode DRX. Accordingly, embodiments describe separate procedures for handling fast and slow ephemeris in SIB transmissions.

[0067] Figure 4 An operational flow / algorithmic structure 400 is shown in accordance with some embodiments. The operational flow / algorithmic structure 400 can be performed or implemented by a base station such as, for example, the base station 102 or 800; or a component thereof such as, for example, the baseband processor 804A.

[0068] The operational flow / algorithmic structure 400 can include, at 404, generating one or more SI messages with fast ephemeris / slow ephemeris. In some embodiments, the SI messages can include separate SIBs to carry the fast ephemeris and the slow ephemeris. For example, SIBslow can carry the slow ephemeris and SIBfast can carry the fast ephemeris. These SIBs can be transmitted together or separately. In some embodiments, SIBslow and SIBfast can be transmitted in different periodicity transmission patterns. For example, SIBslow can be transmitted with a higher periodicity (e.g., less frequently) and SIBfast can be transmitted with a lower periodicity (e.g., more frequently).

[0069] In some embodiments, a single SIB can be defined to carry both the fast ephemeris and the slow ephemeris. This SIB, which can be referred to as SIBephem, can include a first set of fields for fast ephemeris parameters and a second set of fields for slow ephemeris parameters.

[0070] The slow ephemeris / fast ephemeris can correspond to a serving cell or a neighbor cell. In some embodiments, the serving cell ephemeris and the neighbor cell ephemeris can be broadcast in the same SIB, in separate SIBs, or in a portion of a SIB for cell reselection.

[0071] The operational flow / algorithmic structure 400 can also include, at 408, detecting a change in the slow ephemeris. The change can be a change in SIBslow or a change in the second set of fields of SIBephem. If a change is detected in the slow ephemeris, the operational flow / algorithmic structure 400 can proceed to triggering an SI modification procedure at 416. This SI modification procedure can include the base station transmitting SIB1 with a changed systemlnfoValueTag value and transmitting a paging message with a systemlnfoModification field value set to true. The operational flow / algorithmic structure 400 can then proceed to transmitting one or more SI messages (including the modified SIB) at 416.

[0072] If, at 408, no change in the slow ephemeris is detected, the operational flow / algorithmic structure 400 can proceed to transmitting one or more SI messages at 416. This can be the case regardless of whether the fast ephemeris changed. Thus, in this case, the one or more SI messages can include the unmodified slow ephemeris and the modified or unmodified fast ephemeris.

[0073] In this way, if the base station detects a change in the slow ephemeris carried by the second set of fields of SIBephem or SIBslow, the base station can trigger an SI modification procedure. Given that changes in the slow ephemeris do not occur very frequently, it can be acceptable to use the existing SI modification procedure to notify the UE of the change.

[0074] On the other hand, if the base station detects a change in the fast ephemeris carried by SIBfast or the first set of fields, the base station can refrain from triggering the SI modification procedure. Because the UE is not actively notified of the change in the fast ephemeris, the UE can read the first field of SIBephem or SIBfast only when the UE intends to perform an operation based on the fast ephemeris. For example, when the UE intends to perform initial access or RRM procedures, the UE can read the first field of SIBephem or SIBfast.

[0075] In some embodiments, a change in ephemeris (fast ephemeris or slow ephemeris) does not trigger the SI modification procedure. Instead, the UE 106 is expected to read the current ephemeris based on network indication.

[0076] Figure 5 is a signaling procedure 500 showing periodic acquisition of broadcasted ephemeris information according to some embodiments. The signaling procedure 500 can include messages transmitted between the UE 106 and the base station 102.

[0077] The signaling procedure 500 can include, at 504, the base station 102 transmitting an ephemeris configuration message to the UE 106. The ephemeris configuration message can include validity period values corresponding to different ephemeris parameters. The validity period values can define validity periods for the respective ephemeris parameters.

[0078] The validity period values can correspond to parameters having different levels of granularity. For example, in one embodiment, the validity period values can correspond to each parameter. In another embodiment, the validity period values can correspond to a group of more than one parameter. For example, one validity period value can correspond to fast ephemeris, and one validity period value can correspond to slow ephemeris. It should be understood that more than two groups of parameters can be established and associated with respective validity period values.

[0079] The validity period values can be transmitted with the corresponding ephemeris or separately. The ephemeris configuration message can be a SIB1, SIBephem / SIBfast / SIBslow, or an RRC reconfiguration message. The validity period values can be stored with the corresponding ephemeris in the memory of the UE 106.

[0080] The signaling procedure 500 can also include, at 508, the UE 106 detecting a trigger for an operation and checking whether the stored ephemeris is valid for the operation. The operation can include, for example, cell access, cell reselection, or time / frequency pre-compensation.

[0081] Determining the validity status of the stored ephemeris can depend on the type of validity period value transmitted at 504. For example, if the validity period value is a timer value, the UE 106 can start a timer using the timer value upon receiving the corresponding new ephemeris. When the UE 102 detects the trigger at 508, if the timer has expired, the ephemeris can have an invalid status. If the timer has not expired, the ephemeris can have a valid status.

[0082] In other embodiments, the validity period value can provide an indication of the length of the validity period. Upon receiving a new ephemeris, the UE 106 can store a timestamp. When the UE 106 detects the trigger at 508, it can determine whether the period from the timestamp to the time of the trigger detection exceeds the indicated validity period. If so, the corresponding ephemeris can have an invalid status. If not, the corresponding ephemeris can have a valid status.

[0083] If the stored ephemeris required for the operation is valid, the signaling procedure 500 can include, at 512, the UE 106 performing the operation based on the stored ephemeris.

[0084] If the stored ephemeris required for the operation is invalid, the signaling procedure 500 can include, at 516, the UE 106 acquiring the ephemeris in SIBephem / SIBfast / SIBslow as needed. The acquisition of the ephemeris at 516 can include receiving / processing the appropriate SIB, e.g., SIBephem / SIBfast / SIBslow periodically broadcast by the base station 102. In other embodiments, the UE 106 can request the on-demand SIB by transmitting a request in message 1 or message 3 of a physical random access channel (PRACH) procedure.

[0085] The signaling procedure 500 can then proceed to 512, where the UE 106 performs the operation based on the updated ephemeris.

[0086] In some embodiments, the UE 106 can determine the validity period value in other ways. For example, the value can be pre-defined in 3GPP TS, or can be UE implementation dependent.

[0087] Relying on the SI modification procedure to indicate that the ephemeris has been updated can result in the UE acquiring non-ephemeris related system information in cases where only the ephemeris parameters have been updated. This can be an inefficient use of resources. Thus, in some embodiments, a procedure other than SI modification can be used to provide notification of ephemeris change.

[0088] In some embodiments, a short message transmitted on PDCCH using DCI format 1 0 can be used for ephemeris change notification. This short message can be transmitted using the paging radio network temporary identifier (P-RNTI) with or without a paging message.

[0089] Short messages for the current network are defined in clause 6.5 of 3GPP TS 38.331 v16.5.0 (2021-06). A short message is defined to include bits indicating: a broadcast control channel modification other than SIB6, SIB7, and SIB8; an Earthquake and Tsunami Warning System (ETWS) primary / secondary notification or Commercial Mobile Alert Service (CMAS) notification; and, for dynamic spectrum sharing (DCC) operation, an indication that the UE can stop monitoring PDCCH occasions of a paging occasion. One or more of the reserved bits of the short message can be used as an indication that the ephemeris has changed. In some embodiments, multiple bits can be used to indicate that a particular ephemeris parameter (or type, e.g., fast or slow parameter) has changed.

[0090] Figure 6 An operational flow / algorithmic structure 600 is shown in accordance with some embodiments. Operational flow / algorithmic structure 600 can be performed or implemented by a UE, such as, for example, UE 106 or UE 700; or a component thereof, e.g., baseband processor 704A.

[0091] Operational flow / algorithmic structure 600 can include receiving an ephemeris parameter in a first SI message, at 604. The ephemeris parameter can include a fast / slow ephemeris parameter included in SIBephem / SIBfast / SIBslow.

[0092] Operational flow / algorithmic structure 600 can also include receiving an indication that at least one parameter has changed, at 608. The indication can be a short message indication transmitted on a PDCCH using P-RNTI with DCI format 1_0.

[0093] Operational flow / algorithmic structure 600 can also include acquiring an updated ephemeris parameter from a second SI message, at 612. The second SI message can include SIBephem / SIBfast / SIBslow broadcast periodically or transmitted on demand.

[0094] In this way, a UE can acquire a relevant SI message immediately upon detecting an ephemeris change indication in a short message, without having to wait for the next modification period.

[0095] Figure 7 A UE 700 is shown in accordance with some embodiments. UE 700 can be similar to Figure 1 UE 106 of FIG. 1, and can essentially be interchanged therewith.

[0096] The UE 700 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, or an actuator), a video surveillance / monitoring device (e.g., a camera or a video camera), a wearable device (e.g., a smart watch), or an Internet of Things device.

[0097] The UE 700 can include a processor 704, RF interface circuitry 708, memory / storage 712, user interface 716, sensors 720, drive circuitry 722, power management integrated circuit (PMIC) 724, antenna structure 726, and battery 728. The components of the UE 700 can be implemented as integrated circuits (ICs), portions of ICs, discrete electronic devices, or other modules, logic components, hardware, software, firmware, or a combination thereof. Figure 7 The block diagram of FIG. 7 is intended to show a high-level view of certain ones of the components of the UE 700. However, some of the components shown can be omitted in some implementations, additional components can be present, and different arrangements of the components shown can occur in other implementations.

[0098] The components of the UE 700 can be coupled through one or more interconnects 732, which can represent any type of interface, input / output, bus (local, system, or expansion), transmission line, trace, or optical connection that allows the various circuit components (on common or different chips or chip sets) to interact with each other.

[0099] The processor 704 can include processor circuitry, such as baseband processor circuitry (BB) 704A, central processor unit circuitry (CPU) 704B, and graphics processor unit circuitry (GPU) 704C. The processor 704 can include any type of circuit or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from the memory / storage 712, to cause the UE 700 to perform operations as described herein.

[0100] In some embodiments, the baseband processor circuitry 704A can access the communication protocol stack 736 in the memory / storage 712 to communicate over a 3GPP-compatible network. In general, the baseband processor circuitry 704A can access the communication protocol stack 736 to perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and NAS layer. In some embodiments, PHY layer operations can additionally / alternatively be performed by components of the RF interface circuitry 708.

[0101] The baseband processor circuitry 704A can generate or process baseband signals or waveforms carrying the information in a 3GPP-compatible network. In some embodiments, waveforms for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Spread OFDM (DFT-S-OFDM) in the uplink.

[0102] The memory / storage 712 can include one or more non-transitory computer-readable media storing instructions (e.g., the communication protocol stack 736) executable by one or more of the processors 704 to cause the UE 700 to perform various operations described herein. The memory / storage 712 includes any type of volatile or nonvolatile memory readable and / or writeable by the processors 704. In some embodiments, some of the memory / storage 712 can be located on the processors 704 themselves (e.g., L1 cache and L2 cache), while other memory / storage 712 is located on the processors 704 externally (e.g., L3 cache, RAM, ROM). The memory / storage 712 can include any suitable type of memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, solid-state memory, or any other type of memory.

[0103] The RF interface circuitry 708 can include transceiver circuitry and radio frequency front module (RFEM) that allows the UE 700 to communicate with other devices over a radio access network. The RF interface circuitry 708 can include various elements arranged in transmit or receive paths. These elements can include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

[0104] In the receive path, the RFEM can receive a radiated signal from the air interface via antenna structure 726 and proceed to filter and amplify the signal (with a low-noise amplifier). The signal can be provided to a receiver of the transceiver which down-converts the RF signal into a baseband signal that is provided to the baseband processor of the processor 704.

[0105] In the transmit path, a transmitter of the transceiver up-converts and transmits a baseband signal received from the baseband processor as an RF signal through the RFEM. The RFEM can amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 726.

[0106] In various embodiments, the RF interface circuitry 708 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0107] Antenna 726 can include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. The antenna elements can be arranged into one or more antenna panels. Antenna 726 can have an antenna panel that is omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input multiple-output communication. Antenna 726 can include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, or phased array antennas. Antenna 726 can have one or more panels designed for a particular frequency band, including bands in FR1 or FR2.

[0108] User interface circuitry 716 includes various input / output (I / O) devices that allow a user to interact with UE 700. User interface 716 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for entering or providing input to the UE 700. Input device circuitry

[0109] The sensors 720 can include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information about the detected events (sensor data) to some other devices, modules, or subsystems. Examples of such sensors include: an inertial measurement unit comprising an accelerometer, a gyroscope, or a magnetometer; a microelectromechanical system or nanoelectromechanical system comprising a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravimeter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector or the like); a depth sensor; an ambient light sensor; an ultrasonic transceiver; and a microphone or other similar audio capture device.

[0110] The drive circuits 722 can include software and hardware elements that are tailored to control a particular device embedded in, or attached to, or otherwise interfaced with the UE 700. The drive circuits 722 can include individual drivers to allow other components to interact with or control various input / output (I / O) devices that can be present within, or connected to, the UE 700. For example, the drive circuits 722 can include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, a sensor driver to obtain sensor readings from the sensor circuitry 720 and to control and allow access to the sensor circuitry 720, a driver to obtain actuator positions of electromechanical components or to control and allow access to electromechanical components, a camera driver to control and allow access to an embedded image capture device, or an audio driver to control and allow access to one or more audio devices.

[0111] The PMIC 724 can manage power provided to the various components of the UE 700. In particular, with respect to the processor 704, the PMIC 724 can control a power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.

[0112] In some embodiments, the PMIC 724 can control, or otherwise be part of, various power-saving mechanisms of the UE 700, including DRX, as discussed herein.

[0113] The battery 728 can power the UE 700, but in some examples the UE 700 can be installed in a fixed location, and can have a power supply coupled to an electrical grid. The battery 728 can be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 728 can be a typical lead-acid automotive battery.

[0114] Figure 8 A network device 800 is shown in accordance with some embodiments. The network device 800 can be similar to Figure 1 a base station 102, an AMF 120, or a PCF 122, and can be substantially interchangeable therewith.

[0115] The network device 800 can include a processor 804, RF interface circuitry 808 (if implemented as a base station), core network (CN) interface circuitry 812, memory / storage circuitry 816, and antenna structure 826 (if implemented as a base station).

[0116] The components of the network device 800 can be coupled with various other components through one or more interconnects 828.

[0117] The processor 804, RF interface circuitry 808, memory / storage circuitry 816 (including communication protocol stack 810), antenna structure 826, and interconnects 828 can be similar to similarly named elements described with reference to Figure 7 The communication protocol stack 810 can include an access stratum layer if the device 800 is implemented as a base station. If the network device 800 is implemented as an AMF 120 or a PCF 122, the communication protocol stack 810 can include a NAS layer.

[0118] The CN interface circuitry 812 can provide connectivity for a core network (e.g., a 5thGeneration Core network (5GC) using a network interface protocol compatible with a carrier Ethernet protocol, such as carrier Ethernet over Ethernet, or some other suitable protocol). Network connectivity can be provided to / from the base station 800 via a fiber or wireless backhaul. The CN interface circuitry 812 can include one or more specialized processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 812 can include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0119] In some embodiments, the base station 800 can be coupled with a transmission reception point (TRP) using the antenna structure 826, CN interface circuitry, or other interface circuitry.

[0120] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled in a way to minimize risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[0121] For one or more embodiments, at least one of the components illustrated in one or more of the preceding figures can be configured to perform one or more operations, techniques, processes or methods as described in the following examples section. For example, the baseband circuitry described above in connection with one or more of the preceding figures can be configured to operate in accordance with one or more of the following examples. In another example, circuitry associated with a UE, base station, or network element described above in connection with one or more of the preceding figures can be configured to operate in accordance with one or more of the examples illustrated in the following examples section.

[0122] Example

[0123] In the following sections, further example embodiments are provided.

[0124] Example 1 includes a method of operating a user equipment (UE), the method comprising: generating an uplink non-access stratum (NAS) transport message to include an indication that the UE supports storage of ephemeris information or to request ephemeris information; and transmitting the uplink NAS transport message to an access and mobility management function (AMF).

[0125] Example 2 includes the method of Example 1, wherein the uplink NAS transport message includes a UE state indication to include the indication that the UE supports storage of ephemeris information or to request ephemeris information.

[0126] Example 3 includes the method of Example 1, wherein the method comprises: generating the uplink NAS transport message to include an identifier of a satellite system for which ephemeris information is requested.

[0127] Example 4 includes the method of Example 3, wherein the identifier is to indicate an orbit type of the satellite system for which ephemeris information is requested.

[0128] Example 5 includes the method of Example 3, wherein the identifier is to identify a public land mobile network (PLMN), and the uplink NAS transport message is to request ephemeris information for a satellite system associated with the PLMN.

[0129] Example 6 includes the method of Example 1, further comprising: receiving a message including meta-information related to ephemeris information, the meta-information including an identity or type of a satellite system, an ephemeris format, a validity time, or a granularity.

[0130] Example 7 includes the method of Example 6, wherein the message is a downlink transport message, and the meta-information is part of a UE policy container or is a field in a management UE policy command message.

[0131] Example 8 includes a method comprising: generating one or more system information (SI) messages to include a first ephemeris and a second ephemeris related to a non-terrestrial network (NTN) device, the first ephemeris being associated with a validity period less than a predetermined threshold, and the second ephemeris being associated with a validity period greater than the predetermined threshold; and transmitting the one or more SI messages in the NTN.

[0132] Example 9 includes the method of Example 8, further comprising: detecting a change in the second ephemeris; and triggering a SI modification procedure based on detecting the change in the second ephemeris.

[0133] Example 10 includes the method of Example 8, further comprising: detecting a change in the first ephemeris; and refraining from triggering a SI modification procedure based on detecting the change in the first ephemeris.

[0134] Example 11 includes the method of Example 8, wherein generating the one or more SI messages comprises: generating a first SI block (SIB) to include the first ephemeris; and generating a second SIB to include the second ephemeris.

[0135] Example 12 includes the method of Example 8, wherein generating the one or more SI messages comprises: generating a first SI block (SIB) with one or more fields for the first ephemeris and at least one field for the second ephemeris.

[0136] Example 13 includes the method of Example 8, further comprising: transmitting an indication of a plurality of validity period values for a corresponding plurality of components of the first ephemeris and the second ephemeris in the one or more SI messages or a radio resource control (RRC) reconfiguration message.

[0137] Example 14 includes the method of any of Examples 8-13, wherein the first ephemeris and the second ephemeris are for a serving cell or a neighboring cell.

[0138] Example 15 includes a method comprising: storing ephemeris information received in one or more system information (SI) messages; detecting a trigger for an operation based on the ephemeris information; determining a validity status of the ephemeris information upon detecting the trigger; obtaining updated ephemeris information if the validity status is an invalid status; and performing the operation based on the ephemeris information or the updated ephemeris information.

[0139] Example 16 includes the method of Example 15, further comprising: receiving a validity period value for one or more parameters corresponding to the ephemeris information; and determining the validity status based on the validity period value.

[0140] Example 17 includes the method of Example 16, wherein the validity period value corresponds to a plurality of parameters of the almanac information.

[0141] Example 18 includes the method of Example 15, further comprising: determining that the validity status of a parameter of the almanac information is an invalid status; and acquiring a system information block (SIB) to update the parameter.

[0142] Example 19 includes the method of Example 18, wherein the SIB is a periodically broadcast SIB or an on-demand SIB.

[0143] Example 20 includes a method comprising: receiving a plurality of almanac parameters in a first system information (SI) message; receiving an indication in a physical downlink control channel (PDCCH) transmission that at least one parameter of the plurality of almanac parameters has changed; and acquiring updated almanac parameters from a second SI message based on the indication.

[0144] Example 21 includes the method of Example 20, wherein the second SI message comprises a periodically broadcast system information block (SIB) or an on-demand SIB.

[0145] Example 22 includes the method of Example 20, wherein the PDCCH transmission comprises a downlink control information (DCI) format 1 0.

[0146] Example 23 includes a method of operating a device to implement a policy control function (PCF), the method comprising: receiving a UE status indication from a user equipment (UE), the UE status indication comprising an indication of support for storage of almanac information by the UE or a request for almanac information; and transmitting a management UE policy command, the management UE policy command comprising meta-information related to almanac information, the meta-information comprising an identity or type of a satellite system, an almanac format, a validity time or granularity.

[0147] Example 24 includes the method of Example 23, wherein the meta-information is part of a UE policy container or is a field in a management UE policy command message.

[0148] Example 25 includes the method of Example 23, wherein the UE status indication comprises an identifier of a satellite system for which almanac information is requested or comprises an identifier of an orbit type of a satellite system for which almanac information is requested.

[0149] Example 26 can include an apparatus comprising means for performing one or more elements of a method described in or related to any of Examples 1-25, or any other method or process described herein.

[0150] Example 27 can include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of Examples 1-25, or any other method or process described herein.

[0151] Example 28 can include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of Examples 1-25, or any other method or process described herein.

[0152] Example 29 can include a method, technique, or process as described in or related to any of Examples 1-25, or portions or parts thereof.

[0153] Example 30 can include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions to cause the one or more processors, upon execution of the instructions, to perform a method, technique, or process described in or related to any of Examples 1-25, or portions thereof.

[0154] Example 31 can include a signal as described in or related to any of Examples 1-25, or portions or parts thereof.

[0155] Example 32 can include a datagram, information element, packet, frame, segment, PDU, or message as described in or related to any of Examples 1-25, or portions or parts thereof, or otherwise described in the present disclosure.

[0156] Example 33 can include a signal encoded with data as described in or related to any of Examples 1-25, or portions or parts thereof, or otherwise described in the present disclosure.

[0157] Example 34 can include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described in or related to any of Examples 1-25, or portions or parts thereof, or otherwise described in the present disclosure.

[0158] Example 35 can include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform a method, technique, or process as described in or related to any of Examples 1-25, or portions thereof.

[0159] Example 36 can include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or processes of any of Examples 1-25, or portions thereof.

[0160] Example 37 can include a signal in a wireless network as shown and described herein.

[0161] Example 38 can include a method of communicating in a wireless network as shown and described herein.

[0162] Example 39 can include a system for providing wireless communication as shown and described herein.

[0163] Example 40 can include an apparatus for providing wireless communication as shown and described herein.

[0164] Any of the above examples can be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides functionality and / or technical advantages, but that does not mean that every implementation necessarily makes use of every

[0165] Although the above implementations have been described in considerable detail, variations and modifications are possible to those skilled in the art once they fully understand the above description. The disclosure is not to be construed as limited to the particular forms-disclosed herein, but encompasses all modifications that are within the scope and spirit of the disclosure.

Claims

1. One or more computer-readable media, the one or more computer-readable media having instructions that, when executed, cause a processing element to: Receive a UE status indication from the User Equipment (UE) via Non-Access Stratum (NAS) signaling, the UE status indication including an indication that the UE supports storing or requesting ephemeris information; and A management UE policy command is generated for transmission via NAS signaling. The management UE policy command includes metadata related to ephemeris information, the metadata including ephemeris granularity, the ephemeris granularity indicating that the ephemeris information includes first ephemeris information associated with a first validity period less than a predetermined threshold and second ephemeris information associated with a second validity period greater than the predetermined threshold.

2. The computer-readable medium of claim 1, wherein the metadata is part of a UE policy container or a field in a UE policy command message.

3. The computer-readable medium of claim 1, wherein the UE status indication includes an identifier of the satellite system requesting ephemeris information therefrom, or includes an identifier of the orbital type of the satellite system requesting ephemeris information therefrom.

4. One or more computer-readable media according to any one of claims 1 to 3, wherein the UE status indication comprises: The identifier of the satellite system from which ephemeris information is requested.

5. One or more computer-readable media according to claim 4, wherein the identifier is used to indicate the orbital type of a satellite system requesting ephemeris information therefrom.

6. The computer-readable medium of claim 4, wherein the identifier is used to identify a Public Land Mobile Network (PLMN), and the UE status indication is used to request ephemeris information of a satellite system associated with the PLMN.

7. A method for transmitting ephemeris information, the method comprising: Generate one or more System Information (SI) messages to include a first ephemeris and a second ephemeris associated with a non-terrestrial network (NTN) device, wherein the first ephemeris is associated with a validity period of less than a predetermined threshold and the second ephemeris is associated with a validity period of greater than the predetermined threshold; as well as Output one or more SI messages for transmission in NTN.

8. The method according to claim 7, further comprising: Detect changes in the second ephemeris; as well as The SI modification process is triggered based on the detected change in the second ephemeris.

9. The method according to claim 7, further comprising: Detect changes in the first ephemeris; as well as Based on the detected changes in the first ephemeris, the SI modification process is avoided.

10. The method of claim 7, wherein generating the one or more SI messages comprises: Generate a first system information block (SIB) to include the first ephemeris; as well as Generate a second SIB to include the second ephemeris.

11. The method of claim 7, wherein generating the one or more SI messages comprises: Generate a first System Information Block (SIB) having one or more fields for the first ephemeris and at least one field for the second ephemeris.

12. The method according to claim 7, further comprising: The one or more SI messages or Radio Resource Control (RRC) reconfiguration messages transmit indications of multiple validity period values ​​for corresponding multiple components of the first and second ephemeris.

13. The method according to any one of claims 7 to 12, wherein the first ephemeris and the second ephemeris are used for the serving cell or neighboring cells.

14. A user equipment (UE), the UE comprising: Processing circuit, the processing circuit being used for: Receive a first system information block (SIB), the first SIB including first ephemeris information associated with a first validity period less than a predetermined threshold and second ephemeris information associated with a second validity period greater than the predetermined threshold; Detect the triggering of an operation based on the first ephemeris information or the second ephemeris information; Determine the validity status of the first ephemeris information or the second ephemeris information; as well as Based on the validity status, it is determined whether updated ephemeris information needs to be obtained in the second SIB for the operation.

15. The UE of claim 14, wherein the processing circuit is further configured to: Receive a first timer value associated with the first ephemeris information and a second timer value associated with the second ephemeris information in the first SIB; and The validity status of the first ephemeris information or the second ephemeris information is determined based on a timer started with the corresponding first timer value or second timer value.

16. The UE according to claim 14, wherein the operation is a cell access operation, a cell reselection operation, or a time or frequency pre-compensation operation.

17. The UE according to claim 15, wherein the processing circuit is further configured to: Based on the timer, the updated ephemeris information is obtained from the second SIB.

18. The UE of claim 14, wherein the second SIB is a periodically broadcast SIB or an on-demand SIB.

19. An apparatus for receiving ephemeris parameters, the apparatus comprising: The memory is used to store a plurality of ephemeris parameters received in the first system information (SI) message, the plurality of ephemeris parameters including a first ephemeris parameter associated with a first validity period less than a predetermined threshold and a second ephemeris parameter associated with a second validity period greater than the predetermined threshold; as well as Processing circuitry, coupled to the memory, is used for: Receive an indication that at least one of the plurality of ephemeris parameters has changed during physical downlink control channel (PDCCH) transmission; and Based on the instruction, the updated ephemeris parameters are obtained from the second SI message.

20. The apparatus of claim 19, wherein the second SI message comprises a periodically broadcast System Information Block (SIB) or an on-demand SIB.

21. The apparatus according to any one of claims 19 to 20, wherein the PDCCH transmission includes downlink control information DCI format 1_0.

Images