System information parameter update time in non-terrestrial network

Abstract

To provide: a method for updating one or more system information parameters associated with a non-terrestrial network (NTN); user equipment; a non-transitory computer-readable medium; and an apparatus for wireless communication.SOLUTION: In a wireless network, user equipment (UE) is configured to: determine a reference time for updating one or more system information parameters associated with an NTN or updating a cell status associated with the NTN; determine an update timer length for updating the one or more system information parameters associated with the NTN or the cell status associated with the NTN; and acquire, from a current cell or a new cell, a system information block (SIB) to refresh the one or more system information parameters after an expiration time associated with the one or more system information parameters, where the expiration time is based at least in part on the reference time and the update timer length.SELECTED DRAWING: Figure 5A

Description

Cross-reference to Related Applications

[0001]

[0001] This patent application was filed on April 28, 2021, and claims the priority of U.S. Non-Provisional Patent Application No. 17 / 243,151, entitled "SYSTEM INFORMATION PARAMETER UPDATE TIME IN NON-TERRESTRIAL NETWORK", which is hereby expressly incorporated by reference herein.

Technical Field

[0002]

[0002] Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatus related to system information parameter update time in a non-terrestrial network (NTN).

Background Art

[0003]

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephone communication, video, data, messaging, and broadcast. A typical wireless communication system may use a multiple access technology that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE (registered trademark)). LTE / LTE-Advanced is an extended set of mobile standards for the Universal Mobile Telecommunications System (UMTS) published by the 3rd Generation Partnership Project (3GPP (registered trademark)).

[0004]

[0004] A wireless network may include several base stations (BSs) that can support communication for several user equipments (UEs). The UE can communicate with the BS via a downlink and an uplink. The downlink (i.e., the forward link) refers to the communication link from the BS to the UE, and the uplink (i.e., the reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, the BS may be called a Node B, gNB, access point (AP), radio head, transmission and reception point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0005]

[0005] The above multi-connection technology has been adopted in various telecommunication standards to provide a common protocol that enables different user equipments to communicate on an urban, national, regional, and even global scale. NR, which may also be called 5G, is an extended set to the LTE mobile standard published by 3GPP. NR improves spectral efficiency, reduces costs, improves services, utilizes new spectra, uses orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL), and uses CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL) to better integrate with other open standards, thereby better supporting mobile broadband Internet access and being designed to support beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other wireless access technologies remain useful.

Summary of the Invention

[0006]

[0006] In some aspects, a method of wireless communication performed by a user equipment (UE) includes updating one or more system information parameters associated with a non-terrestrial network (NTN) or determining a reference time for updating a cell status associated with the NTN, determining an update timer length for updating one or more system information parameters associated with the NTN or a cell status associated with the NTN, and obtaining a system information block (SIB) from a current cell or a new cell to refresh the one or more system information parameters after an expiration time associated with the one or more system information parameters, wherein the expiration time is at least partially based on the reference time and the update timer length.

[0007]

[0007] In some aspects, a UE for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors configured to update one or more system information parameters associated with the NTN or determine a reference time for updating a cell status associated with the NTN, determine an update timer length for updating one or more system information parameters associated with the NTN or a cell status associated with the NTN, and obtain an SIB from a current cell or a new cell to refresh the one or more system information parameters after an expiration time associated with the one or more system information parameters, wherein the expiration time is at least partially based on the reference time and the update timer length.

[0008]

[0008] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication, when executed by one or more processors of a UE, causes the UE to update one or more system information parameters associated with NTN or determine a reference time for updating a cell state associated with NTN, determine an update timer length for updating one or more system information parameters associated with NTN or a cell state associated with NTN, and obtain a SIB from a current cell or a new cell to refresh one or more system information parameters after an expiration time associated with the one or more system information parameters, the expiration time being at least partially based on the reference time and the update timer length.

[0009]

[0009] In some aspects, an apparatus for wireless communication includes means for determining a reference time for updating one or more system information parameters associated with NTN or for updating a cell state associated with NTN, means for determining an update timer length for updating one or more system information parameters associated with NTN or a cell state associated with NTN, and means for obtaining a SIB from a current cell or a new cell to refresh one or more system information parameters after an expiration time associated with the one or more system information parameters, the expiration time being at least partially based on the reference time and the update timer length.

[0010]

[0010] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and / or processing system substantially as described herein with reference to the drawings and the specification and as illustrated by the drawings and the specification.

[0011]

[0011] The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes as the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, together with the associated advantages, will be better understood from the following description when considered in connection with the accompanying drawings, both as to their arrangement and manner of operation. Each of the drawings is provided for purposes of illustration and description and is not provided as a definition of the limits of the claims.

[0012]

[0012] While aspects are described in this disclosure by way of illustration to several examples, those skilled in the art will understand that such aspects can be implemented in many different configurations and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects can be implemented via integrated chip embodiments or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, or artificial intelligence-enabled devices). Aspects can be implemented with chip-level components, module components, non-module components, non-chip-level components, device-level components, or system-level components. Devices incorporating the described aspects and features can be patented and can include additional components and features for the implementation and execution of the described aspects. For example, the transmission and reception of wireless signals can include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors (if any), interleavers, adders, or summers). It is intended that the aspects described herein can be implemented in a wide variety of devices, components, systems, distributed arrangements, or end-user devices of various sizes, shapes, and configurations.

[0013]

[0013] So that the features described above of this disclosure can be understood in detail, a more specific description, briefly summarized above, can be made by reference to the aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the accompanying drawings illustrate only certain typical aspects of this disclosure, and thus, the description should not be considered to limit the scope in that it may admit other equally effective aspects. The same reference numbers in different drawings can identify the same or similar elements.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

[0015] FIG. 3 is a diagram illustrating an example of a base station that communicates with a user equipment (UE) in a wireless network according to the present disclosure.

Figure 3

[0016] FIG. 4 is a diagram illustrating an example of a regenerative satellite deployment and an example of a transparent satellite deployment in a non-terrestrial network (NTN) according to the present disclosure.

Figure 4

[0017] FIG. 5 is a diagram illustrating an example of NTN system information parameters that may change over time according to the present disclosure.

Figure 5A

[0018] FIG. 6 is a diagram illustrating one or more examples associated with the system information parameter update time in NTN according to the present disclosure.

Figure 5B

Figure 6

[0019] FIG. 7 is a diagram illustrating an exemplary process associated with the system information parameter update time in NTN according to the present disclosure.

Figure 7

[0020] FIG. 8 is a block diagram of an exemplary apparatus for wireless communication according to the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0015]

[0021] Various aspects of the present disclosure are described in more detail below with reference to the accompanying drawings. This disclosure, however, may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, one skilled in the art should recognize that the scope of the disclosure is intended to cover any other aspect of the disclosure, whether implemented independently of or in combination with any other aspect of the disclosure, as disclosed herein. For example, any number of the aspects described herein may be used to implement an apparatus or to carry out a method. In addition, the scope of the disclosure is intended to cover such apparatus or methods implemented using other structures, functions, or combinations of structures and functions in addition to, or other than, the various aspects of the disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0016]

[0022] Here, some aspects of a telecommunications system are presented with reference to various devices and techniques. These devices and techniques are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or as software depends on the particular application and design constraints imposed on the overall system.

[0017]

[0023] Aspects may be described herein using terminology generally associated with 5G or New Radio (NR) radio access technology (RAT), but it should be noted that aspects of the present disclosure can be applied to other RATs such as 3G RAT, 4G RAT, and / or RATs subsequent to 5G (e.g., 6G).

[0018]

[0024] FIG. 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 can be, or can include, among other examples, elements of a 5G (NR) network and / or an LTE network. The wireless network 100 can include several base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UE) and can also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, transmission and reception point (TRP), etc. Each BS can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the coverage area of a BS and / or the BS subsystem serving this coverage area, depending on the context in which the term is used.

[0019]

[0025] A BS may provide communication coverage to macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographical area (e.g., several kilometers in radius) and may enable unrestricted access by UEs subscribed to the service. A pico cell may cover a relatively small geographical area and may enable unrestricted access by UEs subscribed to the service. A femto cell may cover a relatively small geographical area (e.g., a home) and may enable restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). The BS for a macro cell may be called a macro BS. The BS for a pico cell may be called a pico BS. The BS for a femto cell may be called a femto BS or a home BS. In the example shown in FIG. 1, BS110a may be a macro BS for macro cell 102a, BS110b may be a pico BS for pico cell 102b, and BS110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" may be used interchangeably herein.

[0020]

[0026] In some embodiments, a cell may not necessarily be stationary, and the geographical area of the cell may move according to the location of the mobile BS. In some embodiments, the BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0021]

[0027] Wireless network 100 may also include relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and send transmissions of data to a downstream station (e.g., a UE or a BS). A relay station can also be a UE that can relay transmissions for other UEs. In the example shown in FIG. 1, relay BS 110d can communicate with BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay BS may also be referred to as a relay station, a relay base station, a repeater, etc.

[0022]

[0028] In some aspects, wireless network 100 may include one or more non-terrestrial network (NTN) deployments in which non-terrestrial wireless communication devices may include BSs (alternatively referred to herein as “non-terrestrial BSs” and “non-terrestrial base stations”) and / or relay stations (alternatively referred to herein as “non-terrestrial relay stations”). As used herein, an NTN may refer to a network that is facilitated by NTN nodes such as non-terrestrial BSs and / or non-terrestrial relay stations.

[0023]

[0029] Wireless network 100 may include any number of non-terrestrial wireless communication devices or NTN nodes. The non-terrestrial wireless communication devices (or NTN nodes) may include satellites and / or high-altitude platforms (HAPs). The satellites may include low-earth orbit (LEO) satellites, medium-earth orbit (MEO) satellites, geostationary orbit (GEO) satellites, and / or highly elliptical orbit (HEO) satellites. The HAPs may include balloons, airships, airplanes, helicopters, and / or unmanned aerial vehicles. The non-terrestrial wireless communication devices may be part of a separate NTN from wireless network 100. Alternatively, the NTN may be part of wireless network 100. The satellites may communicate directly and / or indirectly with other entities in wireless network 100 using satellite communication. The other entities may include UEs (e.g., terrestrial UEs and / or non-terrestrial UEs), other satellites in one or more NTN deployments, other types of BSs (e.g., fixed and / or terrestrial-based BSs), relays, and / or one or more components and / or devices included in the core network of wireless network 100.

[0024]

[0030] Wireless network 100 may be a heterogeneous network that includes different types of BSs, such as macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmission power levels, different coverage areas, and different impacts on interference in wireless network 100. For example, a macro BS may have a high transmission power level (e.g., 5 - 40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmission power levels (e.g., 0.1 - 2 watts).

[0025]

[0031] Network controller 130 may be coupled to a set of BSs and may provide coordination and control to these BSs. Network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other directly or indirectly, for example, via a wireless or wireline backhaul.

[0026]

[0032] UE 120 (e.g., 120a, 120b, 120c) can be distributed throughout the wireless network 100, and each UE can be fixed or mobile. The UE can also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, etc. The UE can be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or instrument, a biosensor / device, a wearable device (smartwatch, smart clothing, smart glasses, smart list band, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing device, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0027]

[0033] Some UEs may be considered machine type communication (MTC) or enhanced or extended machine type communication (eMTC) UEs. MTC and eMTC UEs may communicate with, for example, a base station, another device (such as a remote device), or some other entity, including robots, drones, remote devices, sensors, meters, monitors, and / or location tags. A wireless node may provide connectivity for, or to, a network (such as a cellular network or a wide area network like the Internet), for example, via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices and / or may be implemented as narrowband Internet of Things (NB-IoT) devices. Some UEs may be considered customer premises equipment (CPE). UE120 may be included inside a housing that houses components of UE120, such as a processor component and / or a memory component. In some aspects, the processor component and the memory component may be coupled together. For example, the processor component (such as one or more processors) and the memory component (such as a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0028]

[0034] Generally, any number of wireless networks may be deployed in a given geographical area. Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies. The RAT may also be referred to as a wireless technology, an air interface, etc. The frequency may also be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographical area to avoid interference between wireless networks of different RATs. In some cases, a New Radio (NR) or 5G RAT network may be deployed.

[0029]

[0035] In some aspects, two or more UEs 120 (e.g., shown as UEs 120a and 120e) may communicate directly using one or more sidelink channels (e.g., without using the base station 110 as a medium for communicating with each other). For example, the UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or a mesh network. In this case, the UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere in this specification as being performed by the base station 110.

[0030]

[0036] Devices in the wireless network 100 can communicate using the electromagnetic spectrum that can be further divided into various classes, bands, channels, etc. based on frequency or wavelength. For example, devices in the wireless network 100 can communicate using an operating band having a first frequency range (FR1) that can span from 410 MHz to 7.125 GHz, and / or using an operating band having a second frequency range (FR2) that can span from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 may be referred to as mid-band frequencies. A portion of FR1 is greater than 6 GHz, but FR1 is often referred to as the "sub-6 GHz" band. Similarly, although FR2 is different from the millimeter wave (EHF: extremely high frequency) band (30 GHz - 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU), it is often referred to as the "millimeter wave" band. Thus, unless otherwise specified, terms such as "sub-6 GHz" as used in this specification are to be understood to broadly represent frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise specified, terms such as "millimeter wave" as used in this specification are to be understood to broadly represent frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). The frequencies included in FR1 and FR2 can be modified, and the techniques described in this specification are intended to be applicable to those modified frequency ranges.

[0031]

[0037] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere in this specification, the communication manager 140 may update one or more system information parameters associated with NTN or determine a reference time for updating the cell state associated with NTN, may determine an update timer length for updating one or more system information parameters associated with NTN or the cell state associated with NTN, and may obtain a system information block (SIB) from the current cell or a new cell to refresh the one or more system information parameters after the expiration time associated with the one or more system information parameters. In some aspects, the expiration time may be at least partially based on the reference time and the update timer length. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0032]

[0038] As shown above, FIG. 1 is provided as an example. Other examples may be different from those described with respect to FIG. 1.

[0033]

[0039] FIG. 2 is a diagram illustrating an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with T antennas 234a - 234t, and the UE 120 may be equipped with R antennas 252a - 252r, where generally T ≧ 1 and R ≧ 1.

[0034]

[0040] At base station 110, transmission processor 220 receives data for one or more UEs from data source 212, selects one or more modulation and coding schemes (MCSs) for each UE based at least in part on channel quality indicators (CQIs) received from the UEs, processes (e.g., encodes and modulates) the data for each UE based at least in part on the selected MCS(s) for the UE, and may provide data symbols to all UEs. Transmission processor 220 may also process system information and control information (e.g., CQI requests, grants, and / or upper layer signaling, e.g., for semi-static resource partitioning information (SRPI)) and may provide overhead symbols and control symbols. Transmission processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). Transmission (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a - 232t. Each modulator 232 may process its respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process the output sample stream (e.g., convert to analog, amplify, filter, and upconvert) to obtain a downlink signal. The T downlink signals from modulators 232a - 232t may be transmitted respectively via T antennas 234a - 234t.

[0035]

[0041] In UE120, antennas 252a - 252r can receive downlink signals from base station 110 and / or other base stations, and can respectively provide the received signals to demodulators (DEMOD) 254a - 254r. Each demodulator 254 can adjust (e.g., filter, amplify, down - convert, and digitize) the received signal to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM) to obtain the received symbols. The MIMO detector 256 can obtain the symbols received from all R demodulators 254a - 254r, and when applicable, perform MIMO detection on the received symbols and provide the detected symbols. The receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE120 to the data sink 260, and provide the decoded control information and system information to the controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine, among other examples, the reference signal received power (RSRP) parameter, the received signal strength indicator (RSSI) parameter, the reference signal received quality (RSRQ) parameter, and / or the channel quality indicator (CQI) parameter. In some aspects, one or more components of UE120 can be included in the housing 284.

[0036]

[0042] The network controller 130 can include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 can include, for example, one or more devices in the core network. The network controller 130 can communicate with the base station 110 via the communication unit 294.

[0037]

[0043] An antenna (e.g., antennas 234a to 234t and / or antennas 252a to 252r) can include, or be included within, among other examples, one or more antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays. The antenna panel, antenna group, set of antenna elements, and / or antenna array can include one or more antenna elements. The antenna panel, antenna group, set of antenna elements, and / or antenna array can include a set of coplanar antenna elements and / or a set of non-coplanar antenna elements. The antenna panel, antenna group, set of antenna elements, and / or antenna array can include antenna elements within a single housing and / or antenna elements within a plurality of housings. The antenna panel, antenna group, set of antenna elements, and / or antenna array can include one or more antenna elements coupled to one or more transmit and / or receive components, such as one or more components of FIG. 2.

[0038]

[0044] On the uplink, at UE 120, transmission processor 264 may receive and process data from data source 262 and control information (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. Transmission processor 264 may also generate reference symbols for one or more reference signals. Symbols from transmission processor 264 may be precoded by TX MIMO processor 266, when applicable, and further processed by modulators 254a-254r (e.g., for DFT-s-OFDM or CP-OFDM) and transmitted to base station 110. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 254) of UE 120 may be included within the modem of UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modulator and / or demodulator 254, MIMO detector 256, receive processor 258, transmission processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., as described with reference to FIGS. 5A-5B and / or FIG. 6).

[0039]

[0045] At base station 110, uplink signals from UE 120 and other UEs are received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 when applicable, and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 includes communication unit 244 and may communicate with network controller 130 via communication unit 244. Base station 110 may include a scheduler 246 for scheduling UE 120 for downlink and / or uplink communication. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of base station 110 may be included in the modem of base station 110. In some aspects, base station 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, modulator and / or demodulator 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to implement aspects of any of the methods described herein (e.g., as described with reference to FIGS. 5A-5B and / or FIG. 6).

[0040]

[0046] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component(s) in FIG. 2 may perform one or more techniques related to the system information parameter update time in a non-terrestrial network (NTN), as described in more detail elsewhere in this specification. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component(s) in FIG. 2 may execute or instruct the operations of, for example, process 600 of FIG. 6 and / or other processes as described herein. Memories 242 and 282 may respectively store data and program code for the base station 110 and the UE 120. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when the one or more instructions are executed by one or more processors of the base station 110 and / or the UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), the one or more processors, the UE 120, and / or the base station 110 may be caused to execute or instruct the operations of, for example, process 600 of FIG. 6 and / or other processes as described herein. In some aspects, executing the instructions may include, among other examples, executing the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions.

[0041]

[0047] In some aspects, UE120 includes means for determining a reference time for updating one or more system information parameters associated with NTN or for updating a cell state associated with NTN, means for determining an update timer length for updating one or more system information parameters associated with NTN or a cell state associated with NTN, and / or means for obtaining a system information block (SIB) from a current cell or a new cell to refresh one or more system information parameters after an expiration time associated with the one or more system information parameters, wherein the expiration time is at least partially based on the reference time and the update timer length. The means for UE120 to perform the operations described herein may include, for example, one or more of communication manager 140, antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, demodulator 254, controller / processor 280, or memory 282.

[0042]

[0048] Although the blocks in FIG. 2 are illustrated as different components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be executed by or under the control of controller / processor 280.

[0043]

[0049] As shown above, FIG. 2 is provided as an example. Other examples may be different from those described with respect to FIG. 2.

[0044]

[0050] FIG. 3 is a diagram illustrating an example 300 of a regenerative satellite deployment and an example 310 of a transparent satellite deployment in a non-terrestrial network (NTN) according to the present disclosure.

[0045]

[0051] Example 300 shows a regenerative satellite deployment. In Example 300, UE 120 is served by satellite 320 via service link 330. For example, satellite 320 may include BS 110 (e.g., BS 110a) or a gNB. In some aspects, satellite 320 may be referred to as, among other examples, a non-terrestrial base station, a regenerative repeater, and / or an embedded processing repeater. In some aspects, satellite 320 may demodulate an uplink radio frequency signal and may modulate a baseband signal derived from the uplink radio signal to generate a downlink radio frequency transmission. Satellite 320 may transmit a downlink radio frequency signal on service link 330. Satellite 320 may provide a cell that covers UE 120.

[0046]

[0052] Example 310 shows a transparent satellite deployment, which may also be referred to as a bent-pipe satellite deployment. In Example 310, UE 120 is served by satellite 340 via service link 330. Satellite 340 may be a transparent satellite. Satellite 340 may relay a signal received from gateway 350 via feeder link 360. For example, satellite 340 may receive a radio frequency transmission from gateway 350 via feeder link 360 and may relay the radio frequency transmission to UE 120 via service link 330 without demodulating the radio frequency transmission. Additionally or alternatively, satellite 340 may receive a radio frequency transmission from UE 120 via service link 330 and may relay the radio frequency transmission to gateway 350 via feeder link 360 without demodulating the radio frequency transmission. In some aspects, satellite 340 may frequency-convert a radio frequency transmission received on service link 330 to the frequency of a radio frequency transmission on feeder link 360 (or vice versa) and may amplify and / or filter the relayed radio frequency transmission. In some aspects, UE 120 shown in Examples 300 and 310 may be associated with a global navigation satellite system (GNSS) capability or a global positioning system (GPS) capability, but not all UEs have such capabilities. Satellite 340 may provide a cell that covers UE 120.

[0047]

[0053] As shown in FIG. 3, service link 330 may include a link between satellite 340 and UE 120, and may include one or more of an uplink or a downlink. Feeder link 360 may include a link between satellite 340 and gateway 350, and may include one or more of an uplink (e.g., from UE 120 to gateway 350) or a downlink (e.g., from gateway 350 to UE 120). As shown in FIG. 3, the uplink of service link 330 is indicated by reference number 330-U, and the downlink of service link 330 is indicated by reference number 330-D. Similarly, the uplink of feeder link 360 is indicated by reference number 360-U, and the downlink of feeder link 360 is indicated by reference number 360-D.

[0048]

[0054] Feeder link 360 and service link 330 may each experience a Doppler effect due to the movement of satellites 320 and 340, and potentially the movement of UE 120. The Doppler effect may be significantly larger than that of a terrestrial network. The Doppler effect on feeder link 360 may be compensated to some extent, but may still be associated with a certain amount of uncompensated frequency error. Further, gateway 350 may be associated with residual frequency error, and / or satellites 320 / 340 may be associated with built-in frequency error. These sources of frequency error may cause the received downlink frequency at UE 120 to drift from the target downlink frequency. Further, due to the long distance between UE 120 and satellites 320 / 340, communications in the NTN may be associated with a much longer delay (e.g., longer latency and / or longer round-trip time) than the delay associated with a terrestrial network. Any communication between UE 120 and gateway 350 may have a delay that is even greater in a transparent satellite deployment, as each must travel through service link 330 and feeder link 360, each of which may be associated with a longer delay than a terrestrial network.

[0049]

[0055] As shown above, FIG. 3 is provided as an example. Other examples may differ from those described with respect to FIG. 3.

[0050]

[0056] FIG. 4 is a diagram illustrating Example 400 of NTN system information parameters that may change over time according to the present disclosure. As shown in FIG. 4, Example 400 includes a satellite that can communicate with one or more UEs (shown as UE1 and UE2) in NTN. For example, in some embodiments, the satellite may be related to regenerative satellite deployment or transparent satellite deployment as described in more detail above with reference to FIG. 3.

[0051]

[0057] In a wireless network, a base station generally broadcasts a master information block (MIB) that carries information for enabling a UE to access the wireless network and one or more system information blocks (SIBs). For example, the MIB may carry information such as a system frame number (SFN) and information for enabling reception and decoding of SIB1, which carries basic information required for a UE's initial access and information for enabling the UE to obtain any additional SIBs. For example, SIB1 may carry various parameters related to, among other examples, cell selection information, a public land mobile network (PLMN) list, a cell identifier, and / or a tracking area code (TAC). Further, SIB1 may carry scheduling information for one or more other SIBs, which may carry satellite-specific information such as ephemeris data for describing the orbit of a satellite in NTN (e.g., the ephemeris data may include, among other examples, time parameters such as clock reference time, Kepler parameters such as the square root of the orbital semi-major axis, eccentricity, and / or inclination angle, and / or perturbation parameters such as the mean motion difference from calculated values, the rate of change of right ascension and / or inclination, and / or the amplitude of one or more sine or cosine harmonic correction terms).

[0052]

[0058] Therefore, in NTN, due to the need to periodically update system information parameters as the position of the satellite changes relative to the ground, there are some system information parameters that are treated differently from those in the terrestrial network. For example, since ephemeris data is used to describe the orbit of a satellite in space, ephemeris data is generally specific to NTN, and there is no system information parameter such as ephemeris in the terrestrial network. In another example, the TAC indicated in SIB1 is fixed for each cell and does not change in the terrestrial network, whereas the TAC associated with a satellite can change over time as the position of the satellite changes relative to the ground. Furthermore, depending on the position of the satellite, the satellite can be associated with more than one TAC at a particular time. Therefore, in NTN, the network can broadcast more than one TAC for each PLMN in a cell (e.g., in SIB1). For example, as shown by reference numeral 410 in FIG. 4, the satellite can have a coverage area that enters the first geostationary tracking area at time t1, whereby the SIB1 broadcast at time t1 can indicate the TAC associated with the first geostationary tracking area (shown as TAC1). As further shown by reference numeral 412, the position of the satellite relative to the ground changes at time t2 such that the coverage area of the satellite includes a portion of the first geostationary tracking area and a portion of the second geostationary tracking area. Therefore, the TAC associated with the second geostationary tracking area (shown as TAC2) can be added to the SIB1 broadcast at time t2. As further shown by reference numeral 414, the position of the satellite relative to the ground changes again at time t3 such that the coverage area of the satellite enters the second geostationary tracking area and no longer covers any portion of the first geostationary tracking area. Therefore, the TAC associated with the first geostationary tracking area can be removed from the SIB1 broadcast at time t3.

[0053]

[0059] Generally, when one or more system information parameters are updated, the UE is typically notified via a paging message, and the UE is then expected to re-acquire one or more SIBs to refresh the one or more system information parameters. For example, in NTN, the paging message may notify the UE to re-acquire SIB1 when the TAC associated with the satellite changes, so that the UE can verify that it is camped in a cell that supports the tracking area in the configured list associated with the UE. Further, a similar approach may be used to refresh the ephemeris data associated with the satellite. However, sending a paging message to notify the UE when a system information parameter needs to be updated can lead to signaling overhead, which can be particularly problematic in NTN due to the large propagation delay and / or satellite movement that potentially results in frequent changes to the system information parameters. One possible technique to ensure that the UE periodically re-acquires one or more SIBs to refresh the system information parameters without explicitly notifying the UE (e.g., without triggering the system information update procedure via a paging message) could be to provide an expiration time for each system information parameter that is expected to change over time. For example, the expiration time could be provided for each TAC in each PLMN (e.g., depending on the size of each tracking area and / or the satellite orbit), and / or could be provided to limit the time period (e.g., from 30 minutes to 4 hours) for which the ephemeris data is considered valid. However, broadcasting the expiration time for each system information parameter that may become stale or otherwise needs to be updated adds significant signaling overhead.

[0054]

[0060] Some aspects described in this specification relate to techniques and apparatus that enable a UE to implicitly determine an update time at which the UE should obtain (or re-obtain) one or more SIBs to update or refresh one or more system information parameters (e.g., without relying on paging messages or other notifications to explicitly indicate when the UE should update one or more system information parameters). For example, when the UE obtains an SIB indicating one or more system information parameters (e.g., among other examples, the TAC carried in SIB1 and / or the ephemeris data carried in the NTN-specific SIB), the update timer length may be signaled to the UE explicitly or implicitly. Further, the UE may determine a reference time associated with one or more system information parameters that should be refreshed periodically. For example, in some aspects, the reference time may be based on the boundary of a system information modification period, the boundary of a system information period, the boundary of a scheduling window, and / or a particular SFN. Accordingly, the UE may determine an expiration time for one or more system parameters based on the reference time and the update timer length, and the UE may obtain one or more SIBs to refresh one or more system parameters after the expiration time. In this way, the UE may obtain updated or refreshed values for one or more system parameters using reduced signaling overhead (e.g., without notifying the UE to update one or more system parameters or without indicating the expiration time of one or more system parameters).

[0055]

[0061] As shown above, FIG. 4 is provided as an example. Other examples may differ from those described with respect to FIG. 4.

[0056]

[0062] Figures 5A-5B are diagrams illustrating one or more examples 500 associated with the system information parameter update time in NTN according to the present disclosure. As shown in Figures 5A-5B, the example(s) 500 include communication between a satellite and a UE. In some aspects, the satellite and the UE may communicate with each other in NTN. For example, in some aspects, the satellite may be associated with a regenerative satellite deployment or a transparent satellite deployment, and the satellite may communicate with the UE via a wireless service link that may include an uplink and / or a downlink.

[0057]

[0063] As shown by reference numeral 510 in Figure 5A, the satellite may transmit a system information block (SIB) indicating one or more system information parameters associated with NTN, and the UE may receive it. In some aspects, the SIB may include SIB1 indicating various parameters related to accessing a cell associated with the satellite. For example, SIB1 may set one or more PLMN identification information and additional information associated with the one or more PLMN identification information, such as a tracking area code (TAC) indicating the tracking area to which the cell belongs (e.g., to identify a tracking area within the PLMN). Therefore, in some aspects, one or more system information parameters associated with NTN may include one or more TACs indicated in SIB1. In addition or alternatively, the SIB transmitted by the satellite and received by the UE may include an SIB other than SIB1 (e.g., NTN-specific SIB) that carries information specific to the satellite, such as ephemeris data for describing the orbit of the satellite. For example, as described above, the ephemeris data may include time parameters (e.g., clock reference time), Kepler parameters (e.g., square root of the orbital semi-major axis, eccentricity, and / or inclination angle), and / or perturbation parameters (e.g., mean motion difference from the calculated value, rate of change of right ascension and / or inclination, and / or amplitude of one or more sine or cosine harmonic correction terms).

[0058]

[0064] Generally, as described above, one or more TACs indicated in SIB1 and / or ephemeris data indicated in another SIB may change over time (e.g., the TAC may change as the position of the satellite changes relative to the ground, and / or the ephemeris data may change due to variations in the orbit of the satellite in space). In addition or alternatively, the cell state associated with NTN may change over time (e.g., as one or more cells are switched off and / or as additional cells are added to NTN). Therefore, as described herein, the UE may need to periodically re-acquire the SIB(s) indicating the system information parameters (e.g., the TAC and / or ephemeris data associated with the satellite) that are updated over time in NTN. For example, in order to configure the UE to refresh or otherwise update certain system information parameters without relying on explicit signaling (e.g., paging messages) to indicate when the UE should update the system information parameters, the UE may generally need to implicitly determine (e.g., autonomously or with minimal signaling) the expiration time for the TAC, ephemeris data, and / or any other system information parameters that should be periodically refreshed or updated. Therefore, in some aspects, the UE may determine the reference time and the update timer length for updating each system information parameter that should be periodically refreshed or updated and / or for updating the cell state associated with NTN.

[0059]

[0065] For example, as described in this specification, the UE may be configured to implicitly determine a reference time for determining when the next TAC update occurs, a reference time for determining when the next ephemeris update occurs, and / or a reference time for updating the cell state associated with the NTN, based on a periodic structure associated with a SIB (e.g., SIB1 used to indicate the TAC associated with a cell provided by a satellite and / or NTN-specific SIB used to indicate ephemeris data for the satellite) that indicates a value for a corresponding system information parameter, without an explicit indication. Further, as described in more detail below, the update timer length may be signaled explicitly or implicitly by the satellite, or the update timer length may be defined (e.g., in a wireless communication standard) such that the UE can determine the expiration time of the system information parameter based on the reference time and the update timer length (e.g., the update timer for the system information parameter may start moving at the reference time and the system information parameter may expire after the update timer length). In some aspects, the update timer length may also be indicated according to a periodic structure associated with a SIB that indicates a value for a corresponding system information parameter.

[0060]

[0066] For example, FIG. 5B illustrates an example 512 of a periodic SIB structure associated with SIB1 indicating one or more TACs associated with a satellite and / or another SIB (e.g., an NTN-specific SIB) that may indicate ephemeris data associated with the satellite. For example, if the SIB is SIB1, SIB1 can be transmitted on the downlink shared channel (e.g., the physical downlink shared channel (PDSCH)) with a fixed periodicity (shown as SI periodicity) of 160 milliseconds (ms) and a variable transmission repetition periodicity within 160 ms. As further shown, the periodic structure of the SIB may include a system information modification period, which generally refers to a period during which the system information parameters carried in the SIB do not change. In other words, the system information parameters carried in the SIB can be changed only in the first SIB transmission (shaded in gray in FIG. 5A) during the system information modification period, and each subsequent SIB transmission within the system information modification period is a repetition of the first SIB transmission during the current system information modification period.

[0061]

[0067] In general, as shown by Example 512, the boundary of the system information modification period can be defined by a system frame number (SFN) value where SFN mod m = 0, where m is the number of radio frames during the system information modification period. In some aspects, the value of m can be determined based on a set coefficient value (e.g., modificationPeriodCoeff) having a value of 2, 4, 8, or 16, and a default paging cycle (e.g., PagingCycle) having a value of 32, 64, 128, or 256 radio frames. For example, if the set coefficient value is 2 and the default paging cycle is 32 radio frames, the system information modification period can include 64 radio frames. Thus, as described herein, any change in the system information parameters can be updated in the corresponding SIB at the boundary of the system information period, and the UE can generally have the ability to implicitly determine the SFN associated with the most recent system information modification boundary and the SFN associated with the next system information modification boundary (e.g., the start boundary of the current system information modification period). The SFN can generally wrap around after an SFN wrap-around period that can include 1024 frames each having a 10 ms duration, whereby the SFN wraps around every 10.24 seconds so that the system information modification period cannot be longer than 10.24 seconds.

[0062]

[0068] In some aspects, as described above, SIB1 may carry information necessary to enable access to a cell provided by a satellite and is thus transmitted with a fixed periodicity of 160 ms. However, SIB1 may include scheduling information for one or more other SIBs, which may have a similar periodic structure as SIB1, except that the periodic structure of the other SIBs (e.g., SIBs that carry information indicating NTN-specific parameters such as ephemeris data) can be set more flexibly. For example, as further shown by Example 514 in FIG. 5B, SIBs other than SIB1 may be associated with a configurable system information periodicity, which may have a value of 8, 16, 32, 64, 128, 256, or 512 radio frames (e.g., 64 radio frames in Example 514). Further, the SIB may be associated with a scheduling window parameter (e.g., si-WindowLength), which may have a value of 5, 10, 20, 40, 80, 160, 320, 640, or 1280 subframes to define the length of the system information window within which the UE can expect the SIB to be transmitted. Therefore, for SIBs other than SIB1, the system information modification period may include one or more system information periods (e.g., depending on the value of m indicating the number of radio frames during the system information modification period and the value of the si-Periodicity parameter indicating the number of radio frames during the system information period), and each system information period may include one or more system information scheduling windows during which the SIB is transmitted.

[0063]

[0069] As further shown by reference numeral 520 in FIG. 5A, the UE may determine a reference time associated with updating system information parameters and / or updating the cell state, which may be at least partially based on the periodic structure of the SIBs used to indicate the values of the system information parameters. For example, in the case of the TAC having a value shown in SIB1, the UE may implicitly determine (e.g., without an explicit indication) that the reference time for the TAC is the boundary of the system information modification period in which the UE obtained the SIB1 indicating the current TAC associated with the satellite. Similarly, in the case of the ephemeris data shown in SIBs other than SIB1, the UE may implicitly determine that the ephemeris reference time is the boundary of the system information modification period in which the UE obtained the SIB indicating the current ephemeris associated with the satellite. For example, in either case, the boundary of the system information modification period may correspond to the start of the system information modification period in which the UE obtained the SIB indicating the current value of the appropriate system information parameter (e.g., the most recent SFN where SFN mod m = 0). Alternatively, the boundary of the system information modification period may correspond to the end of the system information modification period in which the UE obtained the SIB indicating the current value of the TAC and / or ephemeris data associated with the satellite (e.g., the next SFN where SFN mod m = 0, which also represents the start boundary of the next system information modification period). In such cases, the next update time at which the TAC, ephemeris data, and / or cell state are refreshed may occur at the boundary of each system information modification period.

[0064]

[0070] Alternatively, in some aspects, the UE may implicitly determine that the TAC, ephemeris data, and / or reference time for updating the cell state associated with NTN is the boundary of the system information period within the system information modification period. For example, as described above, the system information modification period may include one or more system information periods, and the reference time may correspond to the boundary at the start or end of any suitable system information period within the system information modification period. In this case, the TAC, ephemeris data, and / or reference time for updating the cell state associated with the satellite may be the boundary of the nth system information period associated with the SIB indicating the TAC, ephemeris data, and / or cell state, and the next update time at which the TAC, ephemeris data, and / or cell state is refreshed may occur at the boundary of each system information period (e.g., more frequently than when the boundary of the system information modification period is used as the reference time).

[0065]

[0071] Alternatively, in some aspects, the UE may implicitly determine that the TAC, ephemeris data, and / or the reference time for updating the cell state is an SFN having a configured value. For example, as described above, the SFN wrap-around period may generally include several radio frames, and the reference time for updating the TAC, ephemeris data, and / or the cell state may be an SFN having a value of x, where x has a value between 0 and z, and z is 1 less than the number of radio frames in the SFN wrap-around period. For example, in a hyper SFN configuration where the SFN wrap-around period includes 1024 radio frames, the radio frames may be indexed from 0 to 1023 such that the reference time for updating the TAC, ephemeris data, and / or the cell state may be an SFN having a value of x, where x has a value between 0 and 1023. In this case, regardless of the system information modification period, the next update time at which the TAC, ephemeris data, and / or the cell state is refreshed may occur at each SFN having a value equal to x, which occurs every 10.24 seconds in the case of an SFN wrap-around period having 1024 radio frames each covering 10 ms. Further, in some aspects, the value of x may correspond to the SFN at which the boundary of the nth system information modification period occurs (e.g., the configured SFN value may be selected to coincide with any suitable system information modification period boundary within the SFN wrap-around period).

[0066]

[0072] In some aspects, when the system information parameter(s) to be refreshed includes ephemeris data and / or other suitable system information parameters indicated in SIBs other than SIB1, the reference time may correspond to the start of the system information scheduling window within the system information period. For example, in FIG. 5B, example 514 illustrates a periodic SIB structure where the system information period includes three system information scheduling windows. Therefore, in some aspects, the UE may determine that the reference time for ephemeris data and / or other system information parameters indicated in SIBs other than SIB1 is the boundary of the nth system information scheduling window within the system information period.

[0067]

[0073] As further shown by reference number 530 in FIG. 5A, the UE may determine an update timer length for system information parameters. For example, as described herein, the reference time and the update timer length for certain system information parameters (e.g., TAC or ephemeris data) and / or cell state (e.g., cells to be switched off and / or added to NTN) may generally indicate the expiration time for the system information parameters and / or cell state. For example, the update timer length may indicate the duration starting from the reference time during which the values of the system information parameters and / or cell state are considered valid. In this way, the reference time and the update timer length may indicate the expiration time for the system information parameters and / or cell state such that the UE may (re)obtain the SIB indicating the most recent value of the system information parameters for one or more cells after the expiration time determined from the reference time and the update timer length. In this way, the satellite may modify the next update time for the system information parameters and / or cell state at any time without the need to notify the UE about the change in the update time in the SIB. For example, after the UE obtains SIB1 indicating one or more TACs associated with the satellite and / or another SIB indicating ephemeris data associated with the satellite, the UE may obtain the appropriate SIB to read the current TAC(s) and / or ephemeris data associated with the satellite again at the next update time.

[0068]

[0074] For example, in some aspects, the satellite may signal the update timer length to the UE in a system information block (SIB) indicating the values of system information parameters that the UE should refresh at the next update time. Generally, the update timer length may be indicated with respect to a reference time that is implicitly determined by the UE such that the UE can determine the expiration time for system information parameters with minimal signaling or no signaling. For example, in some aspects, the update timer length may be signaled as an absolute time value within a range of possible values, as an integer multiple of a system information modification period such that the system information parameters expire after one or more system information modification periods, as an integer multiple of a system information period such that the system information parameters expire after one or more system information periods, as an integer multiple of a system information scheduling window, or as an integer multiple of a paging discontinuous reception (DRX) cycle.

[0069]

[0075] Additionally or alternatively, the update timer length may be based on a correction period having a length based on the number of radio frames during an SFN wrap-around period. For example, in a hyper SFN configuration (e.g., SFN of 1024) where the SFN wraps around every 10.24 seconds, the UE may determine a reference time as described above, and the correction period may be determined according to the signaled value p. For example, for an H-SFN configuration where the SFN wrap-around period is 10.24 seconds, to cover a period of 5 minutes, it may be sufficient for most mobile cells, but a satellite may signal a value of p = 30 H-SFN = 307.2 seconds. After the p-th H-SFN period, the UE may update appropriate system information parameters at the boundary of the q-th system information correction period or system information period, where one H-SFN wrap-around period may generally include more than q system information correction periods. In some aspects, the H-SFN value may be indicated as a 10-bit value in SIB1 or NTN-specific SIB, and the value of p may be indicated as a 5-bit value (although more bits may be used to indicate a larger value for p at the expense of additional signaling overhead). In some aspects, the update timer length may be based on a combination of an integer multiple of the number of radio frames during an SFN wrap-around period and an integer multiple of another time duration such as a system information correction period, system information period, system information scheduling window, or paging DRX cycle.

[0070]

[0076] Alternatively, in some embodiments, the update timer length may be implicitly indicated by the absence of an indication for the update timer length. For example, in some embodiments, a default value may be configured for the update timer length (e.g., 5 minutes), such that the absence of an explicit indication for the update timer length may indicate to the UE that the next update for the corresponding system information parameter does not occur until the default value for the update timer length elapses. In such a case, the UE may be expected to obtain the SIB at least once per time unit (e.g., at least once every 5 minutes if the default value for the update timer length is 5 minutes) to refresh the value of the system information parameter. Further, in some embodiments, the default value for the update timer length may be based on the cell size associated with the satellite (e.g., the amount of time expected for the TAC to change for a moving cell with a size of 500 kilometers, such as 67 seconds). Further, when the update timer length is indicated for a hard TAC update (e.g., when each cell can broadcast only one TAC), the update timer length may be PLMN-specific if only one TAC is broadcast per PLMN, or TAC-specific if a PLMN list is used to signal the update timer length, or cell-specific associated with the satellite if multiple PLMNs share the same earth-fixed tracking area for the same cell (e.g., a common update timer length can be signaled for all PLMNs to indicate when the cell is expected to exit and / or enter a new tracking area). Further, when the update timer length is indicated for a soft TAC update (e.g., when multiple TACs can be broadcast per PLMN), the multiple TACs associated with adjacent tracking areas may have different expiration times. Therefore, in the case of a soft TAC update, the update timer length for each TAC may be signaled per PLMN or per TAC, or a single common time may be indicated to inform the UE of when the moving cell enters or exits the tracking area since the tracking area is earth-fixed.

[0071]

[0077] As further shown by reference number 540 in FIG. 5A, the UE may obtain one or more system information blocks (SIBs) from the current cell or a new cell to refresh one or more system information parameters after the expiration time associated with each respective system information parameter to be refreshed. For example, as described above, the UE may determine a reference time for the tracking area code (TAC) broadcast in SIB1, a reference time for the ephemeris data broadcast in the NTN-specific SIB, and / or a reference time for another suitable parameter that may need to be refreshed periodically. For example, as described above, the reference time for the system information parameter may be the boundary (e.g., start or end) of the system information modification period, the system information period within the system information modification period, the system information scheduling window within the system information period, and / or a system frame number (SFN) having a specific value or index. Further, the update timer length defined with respect to the reference time may be signaled to the UE or (e.g., in the absence of signaling indicating the value of the update timer length) implicitly determined by the UE. Therefore, the reference time and the update timer length may determine the expiration time for the system information parameter, and the UE may obtain an SIB from the current cell or a new cell to refresh the value of the system information parameter after the expiration time. In this way, without relying on a paging message or other explicit notification to indicate when the UE should refresh the system information parameter and / or excessive signaling overhead to explicitly indicate the expiration time for each system information parameter that the UE should refresh periodically, the UE may be provided with updated values for system information parameters that may change over time in the NTN network.

[0072]

[0078] As shown above, FIGS. 5A-5B are provided as one or more examples. Other examples may be different from those described with respect to FIGS. 5A-5B.

[0073]

[0079] FIG. 6 is a diagram illustrating an exemplary process 600 that may be performed, for example, by a UE. The exemplary process 600 is an example of operations that a UE (e.g., UE 120) performs related to a system information parameter update time in NTN.

[0074]

[0080] As shown in FIG. 6, in some aspects, process 600 may include updating one or more system information parameters associated with NTN or determining a reference time for updating a cell state associated with NTN (block 610). For example, the UE may (e.g., using the determination component 708 illustrated in FIG. 7) determine to update one or more system information parameters associated with NTN or determine a reference time for updating a cell state associated with NTN as described above.

[0075]

[0081] As further shown in FIG. 6, in some aspects, process 600 may include determining an update timer length for updating one or more system information parameters associated with NTN or a cell state associated with NTN (block 620). For example, the UE may (e.g., using the determination component 708 illustrated in FIG. 7) determine an update timer length for updating one or more system information parameters associated with NTN or a cell state associated with NTN as described above.

[0076]

[0082] As further shown in FIG. 6, in some embodiments, process 600 may include obtaining SIBs from the current cell or a new cell to refresh one or more system information parameters after an expiration time associated with the one or more system information parameters, where the expiration time is at least partially based on a reference time and an update timer length (block 630). For example, a UE may (e.g., using acquisition component 710 illustrated in FIG. 7) obtain SIBs from the current cell or a new cell to refresh one or more system information parameters after an expiration time associated with the one or more system information parameters, where the expiration time is at least partially based on the reference time and the update timer length as described above.

[0077]

[0083] Process 600 may include additional embodiments, such as any single embodiment or any combination of the embodiments described below, and / or in relation to one or more other processes described elsewhere in this specification.

[0078]

[0084] In a first embodiment, the reference time is the boundary of a system information modification period.

[0079]

[0085] In a second embodiment, alone or in combination with the first embodiment, the reference time is the boundary of system information periodicity within a system information modification period.

[0080]

[0086] In a third embodiment, alone or in combination with one or more of the first and second embodiments, the reference time is a system frame having a set SFN.

[0081]

[0087] In a fourth embodiment, alone or in combination with one or more of the first to third embodiments, the reference time is the boundary of a system information scheduling window within a system information period.

[0082]

[0088] In a fifth aspect, determining the update timer length, alone or in combination with one or more of the first to fourth aspects, includes receiving signaling indicating a value of the update timer length from a range of set values for the update timer length.

[0083]

[0089] In a sixth aspect, determining the update timer length, alone or in combination with one or more of the first to fifth aspects, includes receiving signaling indicating a value of the update timer length as an integer multiple of a duration associated with a system information modification period.

[0084]

[0090] In a seventh aspect, determining the update timer length, alone or in combination with one or more of the first to sixth aspects, includes receiving signaling indicating a value of the update timer length as an integer multiple of a duration associated with a paging DRX cycle or a predefined time duration.

[0085]

[0091] In an eighth aspect, determining the update timer length, alone or in combination with one or more of the first to seventh aspects, includes receiving signaling indicating a value of the update timer length as an integer multiple of a duration associated with a system information periodicity or a system information scheduling window.

[0086]

[0092] In a ninth aspect, determining the update timer length, alone or in combination with one or more of the first to eighth aspects, includes receiving signaling indicating a value of the update timer length as an integer multiple of the number of system frames during an SFN wrap-around period.

[0087]

[0093] In a tenth aspect, determining the update timer length, alone or in combination with one or more of the first to ninth aspects, includes receiving signaling indicating a value of the update timer length as a combination of an integer multiple of a time duration and an integer multiple of the number of system frames during a system frame number wrap-around period.

[0088]

[0094] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the update timer length has a default value in the absence of signaling indicating a value of the update timer length.

[0089]

[0095] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the update timer length is associated with updating one or more system parameters or updating the time when a cell should be switched off or the time to be added to the NTN.

[0090]

[0096] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the update timer length is specific to a cell including a PLMN, a TAC, or a plurality of PLMNs sharing a common TAC update timing.

[0091]

[0097] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, one or more system information parameters include one or more of a TAC or ephemeris data.

[0092]

[0098] FIG. 6 shows an exemplary block of process 600, but in some aspects, process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks compared to that illustrated in FIG. 6. Additionally or alternatively, two or more of the blocks of process 600 may be executed in parallel.

[0093]

[0099] FIG. 7 is a block diagram of an exemplary apparatus 700 for wireless communication. The apparatus 700 can be a UE, or the UE can include the apparatus 700. In some aspects, the apparatus 700 includes a receiving component 702 and a transmitting component 704, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 700 can communicate with another apparatus 706 (such as a UE, a base station, or another wireless communication device) using the receiving component 702 and the transmitting component 704. Further shown, the apparatus 700 can include one or more of a determining component 708 or an obtaining component 710, among other examples.

[0094]

[0100] In some aspects, the apparatus 700 can be configured to perform one or more operations described herein in connection with FIGS. 5A-5B. Additionally or alternatively, the apparatus 700 can be configured to perform one or more processes described herein, such as the process 600 of FIG. 6. In some aspects, the apparatus 700 and / or one or more components shown in FIG. 7 can include one or more components of the UE described above in connection with FIG. 2. Additionally or alternatively, one or more components shown in FIG. 7 can be implemented within one or more components described above in connection with FIG. 2. Additionally or alternatively, one or more of a set of components can be implemented at least partially as software stored in a memory. For example, a component (or a portion of a component) can be stored in a non-transitory computer-readable medium and implemented as instructions or code executable by a controller or processor to perform the functions or operations of the component.

[0095]

[0101] The receiving component 702 may receive communications from the device 706, such as a reference signal, control information, data communication, or a combination thereof. The receiving component 702 may provide the received communication to one or more other components of the device 700. In some aspects, the receiving component 702 may perform signal processing on the received communication (such as, among other examples, filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signal to one or more other components of the device 706. In some aspects, the receiving component 702 may include one or more antennas, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the UE described above with respect to FIG. 2.

[0096]

[0102] The transmitting component 704 may transmit communications, such as a reference signal, control information, data communication, or a combination thereof, to the device 706. In some aspects, one or more other components of the device 706 may generate a communication and may provide the generated communication to the transmitting component 704 for transmission to the device 706. In some aspects, the transmitting component 704 may perform signal processing on the generated communication (such as, among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and may transmit the processed signal to the device 706. In some aspects, the transmitting component 704 may include one or more antennas, modulators, transmit MIMO processors, transmitting processors, controllers / processors, memories, or combinations thereof of the UE described above with respect to FIG. 2. In some aspects, the transmitting component 704 may be collocated with the receiving component 702 in a transceiver.

[0097]

[0103] The determination component 708 may determine to update one or more system information parameters associated with NTN or determine a reference time for updating the cell state associated with NTN. The determination component 708 may determine an update timer length for updating one or more system information parameters associated with NTN or the cell state associated with NTN. The acquisition component 710 may obtain the SIB from the current cell or a new cell to refresh one or more system information parameters after the expiration time associated with the one or more system information parameters, and the expiration time is at least partially based on the reference time and the update timer length.

[0098]

[0104] The receiving component 702 may receive signaling indicating a value of the update timer length from a range of set values for the update timer length.

[0099]

[0105] The receiving component 702 may receive signaling indicating a value of the update timer length as an integer multiple of a duration associated with the system information modification period.

[0100]

[0106] The receiving component 702 may receive signaling indicating a value of the update timer length as an integer multiple of a duration associated with the paging DRX cycle or a predefined time duration.

[0101]

[0107] The receiving component 702 may receive signaling indicating a value of the update timer length as an integer multiple of a duration associated with the system information periodicity or the system information scheduling window.

[0102]

[0108] The receiving component 702 may receive signaling indicating a value of the update timer length as an integer multiple of the number of system frames during the SFN wrap-around period.

[0103]

[0109] The receiving component 702 may receive signaling indicating a value of the update timer length as a combination of an integer multiple of a time duration and an integer multiple of the number of system frames during the SFN wrap-around period.

[0104]

[0110] The number and arrangement of the components shown in FIG. 7 are provided as an example. In practice, there may be additional components, fewer components, different components, or components arranged differently compared to those shown in FIG. 7. Further, two or more components shown in FIG. 7 may be implemented within a single component, or a single component shown in FIG. 7 may be implemented as a plurality of distributed components. Additionally or alternatively, a set of (one or more) components shown in FIG. 7 may perform one or more functions described as being performed by another set of components shown in FIG. 7.

[0105]

[0111] The following provides an overview of some aspects of the present disclosure:

[0106]

[0112] Aspect 1: A method of wireless communication performed by a UE, comprising: determining one or more system information parameters associated with NTN or a reference time for updating a cell state associated with NTN; determining an update timer length for updating one or more system information parameters associated with NTN or a cell state associated with NTN; and obtaining a SIB from a current cell or a new cell to refresh one or more system information parameters after an expiration time associated with the one or more system information parameters, wherein the expiration time is at least partially based on the reference time and the update timer length.

[0107]

[0113] Aspect 2: The method according to Aspect 1, wherein the reference time is a boundary of a system information modification period.

[0108]

[0114] Aspect 3: The method according to Aspect 1, wherein the reference time is a boundary of a system information period within a system information modification period.

[0109]

[0115] Aspect 4: The method according to Aspect 1, wherein the reference time is a system frame having a set SFN.

[0110]

[0116] Aspect 5: The method according to aspect 1, wherein the reference time is the boundary of the system information scheduling window within the system information period.

[0111]

[0117] Aspect 6: The method according to any one of aspects 1 to 5, wherein determining the update timer length includes receiving signaling indicating a value of the update timer length from a set range of values for the update timer length.

[0112]

[0118] Aspect 7: The method according to any one of aspects 1 to 5, wherein determining the update timer length includes receiving signaling indicating a value of the update timer length as an integer multiple of a duration associated with the system information modification period.

[0113]

[0119] Aspect 8: The method according to any one of aspects 1 to 5, wherein determining the update timer length includes receiving signaling indicating a value of the update timer length as an integer multiple of a duration associated with a paging DRX cycle or a predefined time duration.

[0114]

[0120] Aspect 9: The method according to any one of aspects 1 to 5, wherein determining the update timer length includes receiving signaling indicating a value of the update timer length as an integer multiple of a duration associated with system information periodicity or the system information scheduling window.

[0115]

[0121] Aspect 10: The method according to any one of aspects 1 to 5, wherein determining the update timer length includes receiving signaling indicating a value of the update timer length as an integer multiple of the number of system frames during the SFN wrap-around period.

[0116]

[0122] Aspect 11: Determining the update timer length includes receiving signaling indicating a value of the update timer length as a combination of an integer multiple of a time duration and an integer multiple of the number of system frames during the SFN wrap-around period, the method according to any one of Aspects 1 to 5.

[0117]

[0123] Aspect 12: The update timer length has a default value when there is no signaling indicating the value of the update timer length, the method according to any one of Aspects 1 to 5.

[0118]

[0124] Aspect 13: The update timer length is associated with updating one or more system parameters, or updating the time when a cell should be switched off or the time to be added to the NTN, the method according to any one of Aspects 1 to 12.

[0119]

[0125] Aspect 14: The update timer length is specific to a cell including a PLMN, a TAC, or a plurality of PLMNs sharing a common TAC update timing, the method according to any one of Aspects 1 to 13.

[0120]

[0126] Aspect 15: One or more system information parameters include one or more of a TAC or ephemeris data, the method according to any one of Aspects 1 to 14.

[0121]

[0127] Aspect 16: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions storable in the memory and executable by the processor to cause the device to execute the method according to any one of Aspects 1 to 15.

[0122]

[0128] Aspect 17: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to execute the method according to any one of Aspects 1 to 15.

[0123]

[0129] Aspect 18: An apparatus for wireless communication, comprising at least one means for performing the method according to any one of Aspects 1 to 15.

[0124]

[0130] Aspect 19: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to any one of Aspects 1 to 15.

[0125]

[0131] Aspect 20: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to any one of Aspects 1 to 15.

[0126]

[0132] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made based on the above disclosure or obtained from practice of the aspects.

[0127]

[0133] As used herein, the term "component" is intended to be broadly construed as hardware and / or a combination of hardware and software. "Software" should be broadly construed to mean, among other examples, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, whether called software, firmware, middleware, microcode, a hardware description language, or by any other name. As used herein, a processor is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in different forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the aspects. Accordingly, the operation and behavior of the systems and / or methods have been described herein without reference to specific software code, but it is understood that the software and hardware can be designed to implement the systems and / or methods at least in part based on the description herein.

[0128]

[0134] As used herein, meeting a threshold can, depending on the context, refer to a value being greater than the threshold, being greater than or equal to the threshold, being less than the threshold, being less than or equal to the threshold, being equal to the threshold, being not equal to the threshold, and the like.

[0129]

[0135] Certain combinations of features are recited in the claims and / or disclosed herein, but these combinations are not intended to limit the disclosure in various aspects. Indeed, many of these features may be combined in ways not specifically recited in the claims and / or not disclosed herein. Each of the dependent claims listed below may depend directly on only one claim, but the disclosure in various aspects includes each dependent claim in combination with all of the other claims in the claim set. As used herein, the phrase referring to "at least one of" a list of items refers to any combination of those items, including a single member. By way of example, "at least one of a, b, or c" is intended to cover a, b, c, a - b, a - c, b - c, and a - b - c, as well as any combination having multiple of the same elements (e.g., a - a, a - a - a, a - a - b, a - a - c, a - b - b, a - c - c, b - b, b - b - b, b - b - c, c - c, and c - c - c, or any other order of a, b, and c).

[0130]

[0136] Elements, operations, or instructions used in this specification should not be construed as important or essential unless expressly described as such. Also, as used in this specification, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more". Further, as used in this specification, the article "the" is intended to include one or more items referenced in relation to the article "the" and may be used interchangeably with "one or more". Further, as used in this specification, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, or combinations of related and unrelated items) and may be used interchangeably with "one or more". If only one item is intended, the phrase "only one" or similar language is used. Also, as used in this specification, terms such as "has", "have", "having", etc. are intended to be open-ended terms. Further, the phrase "based on" is intended to mean "at least partially based on" unless otherwise specified. Also, as used in this specification, the term "or" is intended to be inclusive when used consecutively and may be used interchangeably with "and / or" unless otherwise specified (e.g., when used in combination with "either" or "only one of").

Claims

1. A method of wireless communication performed by a user equipment (UE), comprising: updating one or more system information parameters associated with a non-terrestrial network (NTN) or determining a reference time for updating a cell state associated with the NTN; determining an update timer length for updating the one or more system information parameters associated with the NTN or the cell state associated with the NTN; obtaining a system information block (SIB) from a current cell or a new cell to refresh the one or more system information parameters after an expiration time associated with the one or more system information parameters; wherein the expiration time is at least partially based on the reference time and the update timer length.

2. The method according to claim 1, wherein the reference time is a boundary of a system information correction period.

3. The method according to claim 1, wherein the reference time is a boundary of system information periodicity within a system information correction period.

4. The method according to claim 1, wherein the reference time is a system frame having a set system frame number.

5. The method according to claim 1, wherein the reference time is a boundary of a system information scheduling window within a system information period.

6. Determining the update timer length comprises: receiving signaling indicating a value of the update timer length from a set range of values for the update timer length.

7. Determining the update timer length comprises: receiving signaling indicating a value of the update timer length as an integer multiple of a duration associated with a system information correction period.

8. Determining the update timer length comprises: receiving signaling indicating a value of the update timer length as an integer multiple of a duration associated with a paging intermittent reception cycle or a predefined time duration.

9. Determining the update timer length comprises: receiving signaling indicating a value of the update timer length as an integer multiple of a duration associated with system information periodicity or a system information scheduling window.

10. Determining the update timer length comprises: The method according to claim 1, comprising receiving signaling indicating the value of the update timer length as an integer multiple of the number of system frames during a system frame number wrap-around period.

11. Determining the update timer length comprises The method according to claim 1, comprising receiving signaling indicating the value of the update timer length as a combination of an integer multiple of a time duration and an integer multiple of the number of system frames during a system frame number wrap-around period.

12. The method according to claim 1, wherein the update timer length has a default value in the absence of signaling indicating the value of the update timer length.

13. The method according to claim 1, wherein the update timer length is associated with updating the one or more system parameters, or updating the time when the cell should be switched off or the time to be added to the NTN.

14. The method according to claim 1, wherein the update timer length is specific to a cell comprising a public land mobile network (PLMN), a tracking area code (TAC), or a plurality of PLMNs sharing a common TAC update timing.

15. The method according to claim 1, wherein the one or more system information parameters comprise one or more of a tracking area code or ephemeris data.

16. A user equipment (UE) for wireless communication, comprising a memory, one or more processors coupled to the memory and the one or more processors are configured to update one or more system information parameters associated with a non-terrestrial network (NTN) or determine a reference time for updating a cell state associated with the NTN; determine an update timer length for updating the one or more system information parameters associated with the NTN or the cell state associated with the NTN; obtain a system information block (SIB) from a current cell or a new cell to refresh the one or more system information parameters after an expiration time associated with the one or more system information parameters and the expiration time is at least partially based on the reference time and the update timer length.

17. The UE according to claim 16, wherein the reference time is a boundary of a system information correction period.

18. The UE according to claim 16, wherein the reference time is a boundary of system information periodicity within a system information correction period.

19. The UE according to claim 16, wherein the reference time is a system frame having a set system frame number.

20. The UE according to claim 16, wherein the reference time is a boundary of a system information scheduling window within a system information period.

21. The one or more processors, in order to determine the update timer length, The UE according to claim 16, configured to receive signaling indicating a value of the update timer length from a range of set values for the update timer length.

22. The one or more processors, in order to determine the update timer length, The UE according to claim 16, configured to receive signaling indicating a value of the update timer length as an integer multiple of a duration associated with a system information correction period.

23. The one or more processors, in order to determine the update timer length, The UE according to claim 16, configured to receive signaling indicating a value of the update timer length as an integer multiple of a duration associated with a system information period or a system information scheduling window.

24. The one or more processors, in order to determine the update timer length, The UE according to claim 16, configured to receive signaling indicating a value of the update timer length as an integer multiple of the number of system frames during a system frame number wrap-around period.

25. The UE according to claim 16, wherein the update timer length has a default value in the absence of signaling indicating a value of the update timer length.

26. The UE according to claim 16, wherein the update timer length is specific to a cell including a public land mobile network (PLMN), a tracking area code (TAC), or a plurality of PLMNs sharing a common TAC update timing.

27. The UE according to claim 16, wherein the one or more system information parameters include one or more of a tracking area code or ephemeris data.

28. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions, When executed by one or more processors of a user equipment (UE), cause the UE to, Updating one or more system information parameters associated with a non-terrestrial network (NTN) or determining a reference time for updating a cell state associated with the NTN; Determining an update timer length for updating the one or more system information parameters associated with the NTN or the cell state associated with the NTN; Obtaining a system information block (SIB) from a current cell or a new cell to refresh the one or more system information parameters after an expiration time associated with the one or more system information parameters; A non-transitory computer-readable medium comprising one or more instructions to cause the above, wherein the expiration time is at least partially based on the reference time and the update timer length.

29. The non-transitory computer-readable medium according to claim 28, wherein the reference time is a boundary of a system information modification period, a boundary of a system information period within a system information modification period, a system frame having a set system frame number, or a boundary of a system information scheduling window within a system information period.

30. An apparatus for wireless communication, comprising: Means for updating one or more system information parameters associated with a non-terrestrial network (NTN) or determining a reference time for updating a cell state associated with the NTN; Means for determining an update timer length for updating the one or more system information parameters associated with the NTN or the cell state associated with the NTN; Means for obtaining a system information block (SIB) from a current cell or a new cell to refresh the one or more system information parameters after an expiration time associated with the one or more system information parameters; The apparatus comprising the above, wherein the expiration time is at least partially based on the reference time and the update timer length.

Images