Broadcasting of non-terrestrial network system information blocks

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive from an entity of a non-terrestrial network (NTN) a SIB indicating information related to one or more NTN system information blocks (SIBs) that may include at least one of ephemeris information or feeder link timing advance information. The UE may receive from the entity of the NTN one or more NTN SIBs based at least in part on the information. Numerous other aspects are described.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 203,961, entitled "BROADCASTING OF A NON-TERRESTRIAL NETWORK SYSTEM INFORMATION BLOCK," filed on August 5, 2021, and U.S. Nonprovisional Patent Application No. 17 / 661,996, entitled "BROADCASTING OF A NON-TERRESTRIAL NETWORK SYSTEM INFORMATION BLOCK," filed on May 4, 2022, which are hereby expressly incorporated by reference in this specification.

[0002] Aspects of the present disclosure relate generally to wireless communication, and to techniques and apparatus for broadcasting non-terrestrial network (NTN) system information blocks (SIBs). [Background technology]

[0003]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may use multiple access technologies capable of supporting 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). LTE / LTE-Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP).

[0004] A wireless network may include one or more base stations that support communication for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink and uplink communications. "Downlink" (or "DL") refers to the communication link from a base station to a UE, and "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0005]

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that allows different UEs to communicate on a city, national, regional, and / or global scale. New Radio (NR), sometimes referred to as 5G, is a set of extensions to the LTE mobile standard promulgated by 3GPP. NR is designed to improve spectral efficiency, lower costs, improve services, take advantage of new spectrum, and better support mobile broadband Internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies will remain useful. Summary of the Invention

[0006]

[0006] Certain aspects described herein relate to a method of wireless communication in a user equipment (UE). The method may include receiving, from a non-terrestrial network (NTN) entity, a SIB indicating information related to one or more NTN system information blocks (SIBs), the SIBs including at least one of ephemeris information or feeder link timing advance information. The method may include receiving, from the NTN entity, one or more NTN SIBs based at least in part on the information.

[0007]

[0007] Certain aspects described herein relate to a method of wireless communication in an NTN entity. The method may include transmitting, to a UE, a SIB indicating information related to one or more NTN SIBs, the information including at least one of ephemeris information or feeder link timing advance information. The method may include transmitting, to the UE, the one or more NTN SIBs based at least in part on the information.

[0008]

[0008] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a memory comprising instructions and one or more processors configured to execute the instructions. The one or more processors may be configured to execute the instructions and cause the apparatus to obtain, from an entity of the NTN, a SIB indicating information related to one or more NTN SIBs, the information including at least one of ephemeris information or feeder link timing advance information. The one or more processors may be configured to execute the instructions and cause the apparatus to obtain, from an entity of the NTN, one or more NTN SIBs based at least in part on the information.

[0009]

[0009] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a memory comprising instructions and one or more processors configured to execute the instructions. The one or more processors may be configured to execute the instructions and cause the apparatus to output, for transmission to the UE, a SIB indicating information related to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information. The one or more processors may be configured to execute the instructions and cause the apparatus to output, for transmission to the UE, one or more NTN SIBs based at least in part on the information.

[0010]

[0010] Some aspects described herein relate to a non-transitory computer-readable medium comprising instructions. The instructions, when executed by one or more processors of the device, may cause the device to obtain, from an NTN entity, a SIB indicating information related to one or more NTN SIBs, the information including at least one of ephemeris information or feeder link timing advance information. The instructions, when executed by the device's one or more processors, may cause the device to obtain, from the NTN entity, one or more NTN SIBs based at least in part on the information.

[0011]

[0011] Some aspects described herein relate to a non-transitory computer-readable medium comprising instructions. The instructions, when executed by one or more processors of the device, may cause the device to output, for transmission to a UE, a SIB indicating information related to one or more NTN SIBs, the SIBs including at least one of ephemeris information or feeder link timing advance information. The instructions, when executed by one or more processors of the device, may cause the device to output, for transmission to the UE, one or more NTN SIBs based at least in part on the information.

[0012]

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for obtaining, from an NTN entity, a SIB indicating information related to one or more NTN SIBs, the information including at least one of ephemeris information or feeder link timing advance information. The apparatus may include means for obtaining, from the NTN entity, the one or more NTN SIBs based at least in part on the information.

[0013]

[0013] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for outputting, for transmission to a UE, a SIB indicating information related to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information. The apparatus may include means for outputting, for transmission to the UE, one or more NTN SIBs based at least in part on the information.

[0014]

[0014] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems substantially as described in this specification with reference to and as illustrated by the drawings and specification.

[0015]

[0015] The above outlines rather broadly the features and technical advantages of the examples according to the present disclosure so that the following detailed description may be better understood. Additional features and advantages are described below. The concepts and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their organization and the method of operation, together with associated advantages, will be better understood from the following description when considered in conjunction with the accompanying figures. Each of the figures is provided for the purpose of illustration and description, and not as a definition of the limits of the claims.

[0016]

[0016] Although aspects are described in this disclosure by way of illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different configurations and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects may be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices, etc.). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or adders). Aspects described herein may be practiced in a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and configurations.

[0017]

[0017] In order that the above-listed features of the present disclosure may be understood in detail, a more detailed description briefly summarized above may be obtained by referring to the embodiments, some of which are shown in the attached drawings. However, it should be noted that the attached drawings only show some typical embodiments of the present disclosure, and therefore should not be considered as limiting its scope, since the description may admit of other equally effective embodiments. The same reference numbers in different drawings may identify the same or similar elements. [Brief description of the drawings]

[0018] [Figure 1]

[0018] FIG. 1 illustrates an example of a wireless network according to the present disclosure. [Diagram 2]

[0019] 1 illustrates an example of a base station in communication with a user equipment (UE) in a wireless network in accordance with the present disclosure. [Diagram 3]

[0020] FIG. 1 illustrates an example of regenerative satellite deployment and an example of transparent satellite deployment in a non-terrestrial based network (NTN) according to the present disclosure. [Figure 4]

[0021] FIG. 1 illustrates an example of system information scheduling in accordance with the present disclosure. [Diagram 5]

[0022] FIG. 1 illustrates an example of NTN-specific system information block (SIB) transmission in accordance with the present disclosure. [Figure 6]

[0023] FIG. 2 illustrates an example relating to broadcasting of an NTN SIB in accordance with the present disclosure. [Figure 7]

[0024] FIG. 2 illustrates an example process associated with broadcasting an NTN SIB in accordance with the present disclosure. [Figure 8] FIG. 2 illustrates an example process associated with broadcasting an NTN SIB in accordance with the present disclosure. [Figure 9]

[0025] 1 is a diagram of an example apparatus for wireless communication according to the present disclosure. [Figure 10] 1 is a diagram of an example apparatus for wireless communication according to the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019]

[0026] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present 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. Those skilled in the art should appreciate that the scope of the present disclosure encompasses any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects described herein. In addition, the scope of the present disclosure is intended to cover such an apparatus or method practiced using other structures, functions, or structures and functions in addition to or other than the various aspects of the present disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0020]

[0027] Several aspects of a telecommunications system are now presented with reference to various apparatus and techniques that are described in the following detailed description and 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 software depends on the particular application and design constraints imposed on the overall system.

[0021]

[0028] Although aspects may be described herein using terminology commonly associated with 5G or New Radio (NR) radio access technologies (RATs), aspects of the disclosure may apply to other RATs, such as 3G RATs, 4G RATs, and / or RATs subsequent to 5G (e.g., 6G).

[0022]

[0029] FIG. 1 illustrates an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base stations 110 are entities that communicate with the UEs 120. The base stations 110 (which may be referred to as BSs) may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., for 4G), gNBs (e.g., for 5G), access points, and / or transmit / receive points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving that coverage area, depending on the context in which the term is used.

[0023]

[0030] A base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having an association with a femto cell (e.g., a UE 120 in a Closed Subscriber Group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or an in-home base station. 1, BS 110a may be a macro base station for a macro cell 102a, BS 110b may be a pico base station for a pico cell 102b, and BS 110c may be a femto base station for a femto cell 102c. A base station may support one or more (e.g., three) cells.

[0024]

[0031] In some examples, the cells may not necessarily be fixed and the geographic area of ​​the cells may move according to the location of the base station 110 that is mobile (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or with one or more other base stations 110 or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0025]

[0032] In some aspects, as shown in Figure 1, the cells may be provided by base stations 110 of a non-terrestrial based network. As used herein, a "non-terrestrial based network" (NTN) may refer to a network to which access is provided by a non-terrestrial based base station, such as a base station carried by an NTN entity (e.g., a satellite, a balloon, an airship, an airplane, an unmanned aerial vehicle, a high altitude platform station). A base station of an NTN may be a base station carried by an NTN entity (regenerative deployment) or a terrestrial base station communicating through an NTN entity (bent pipe or transparent deployment).

[0026]

[0033] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station 110 or a UE 120) and send a transmission of the data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that can relay a transmission for another UE 120. In the example shown in FIG. 1, a BS 110d (e.g., a relay base station) may communicate with a BS 110a (e.g., a macro base station) and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A base station 110 that relays communication may be referred to as a relay station, a relay base station, a relay, etc.

[0027]

[0034] The wireless network 100 may be a heterogeneous network including different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different susceptibility to interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5-40 Watts), while the pico, femto, and relay base stations may have lower transmit power levels (e.g., 0.1-2 Watts).

[0028]

[0035] The network controller 130 may couple to or communicate with a set of base stations 110 and may provide coordination and control for these base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may communicate with each other directly or indirectly via wireless or wireline backhaul communication links.

[0029]

[0036] The UEs 120 may be distributed throughout the wireless network 100, and each UE 120 may be fixed or mobile. The UEs 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. The UEs 120 may 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, a biometric device, a wearable device (e.g., a smart watch, a smart clothing, a smart glasses, a smart wristband, a smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate over a wireless medium.

[0030]

[0037] Some UEs 120 may be considered as machine type communication (MTC) or evolved or extended machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and / or a location tag that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. The UE 120 may be included in a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0031]

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

[0032]

[0039] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using a base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, vehicle-to-everything (V2X) protocols (which may include, e.g., vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, the UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0033]

[0040] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, etc. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers, although portions of FR1 are greater than 6 GHz. A similar naming issue sometimes arises with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is distinct from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

[0034]

[0041] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified these mid-band frequency bands of operation as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit the characteristics of FR1 and / or the characteristics of FR2, thus effectively extending the characteristics of FR1 and / or FR2 to the mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0035]

[0042] With the above examples in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz," as used herein, may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specified, it should be understood that terms such as "millimeter wave," as used herein, may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be changed, and the techniques described herein are applicable to those changed frequency ranges.

[0036]

[0043] In some aspects, the UE 120 may include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 may obtain, from an NTN entity, an NTN system information block (SIB) indicating information related to one or more SIBs that will include at least one of ephemeris information or feeder link timing advance information, and obtain, from the NTN entity, one or more NTN SIBs based at least in part on the information. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0037]

[0044] In some aspects, the base station 110, or another NTN entity, may include a communications manager 150. As described in more detail elsewhere herein, the communications manager 150 may output a SIB indicating information related to one or more NTN SIBs, which may include at least one of ephemeris information or feeder link timing advance information, for transmission to the UE, and output one or more NTN SIBs based at least in part on the information, for transmission to the UE. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0038]

[0045] As noted above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.

[0039]

[0046] 2 illustrates an example base station 200 in communication with a UE 120 in a wireless network 100 in accordance with the present disclosure. The base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas, where T≧1. The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas, where R≧1.

[0040]

[0047] At the base station 110, a transmit processor 220 may receive data destined for a UE 120 (or set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for a UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The base station 110 may process (e.g., encode and modulate) data for the UE 120 based at least in part on the MCS selected for the UE 120 and provide data symbols to the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or higher layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for a reference signal (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and a synchronization signal (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). The transmit (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 a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) depicted as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (depicted as MOD) of modem 232. Each modem 232 may process a respective output symbol stream (e.g., for OFDM) using a respective modulator component to obtain an output sample stream. Each modem 232 may further process (eg, convert to analog, amplify, filter, and / or upconvert) the output sample stream using a respective modulator component to obtain a downlink signal.Modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) depicted as antennas 234a through 234t.

[0041]

[0048] At the UE 120, a set of antennas 252 (depicted as antennas 252a through 252r) may receive downlink signals from the base station 110 and / or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) depicted as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (depicted as DEMOD) of the modem 254. Each modem 254 may condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal using a respective demodulator component to obtain input samples. Each modem 254 may further process the input samples (e.g., for OFDM) using the demodulator component to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modems 254, perform MIMO detection on the received symbols if applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other examples. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0042]

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

[0043]

[0050] One or more antennas (e.g., antennas 234a-t and / or antennas 252a-r) may include or be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmitting and / or receiving components, such as one or more components of FIG.

[0044]

[0051] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antennas 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and / or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to implement any aspect of the methods described herein (e.g., with reference to Figures 6-10).

[0045]

[0052] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by an antenna 234, processed by a modem 232 (e.g., a demodulator component of the modem 232, denoted as DEMOD), detected by a MIMO detector 236, if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. The base station 110 may include a communication unit 244 and may communicate to the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communication. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antennas 234, modem 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 any aspects of the methods described herein (e.g., with reference to FIGS. 6-10).

[0046]

[0053] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other components of FIG. 2 may perform one or more techniques related to broadcasting the NTN SIB, as described in more detail elsewhere herein. In some aspects, the NTN entity described herein is, is included in, or includes one or more components of the base station 110 shown in FIG. 2. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other components of FIG. 2 may perform or direct operations of, for example, process 700 of FIG. 7, process 800 of FIG. 8, and / or other processes described herein. The memory 242 and the memory 282 may store data and program codes for the base station 110 and the UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly or after compiling, converting, and / or interpreting), may cause the one or more processors, UE 120, and / or base station 110 to perform or direct operations of, for example, process 700 of FIG. 7, process 800 of FIG. 8, and / or other processes described herein. In some examples, executing instructions may include invoking instructions, converting instructions, compiling instructions, and / or interpreting instructions, among other examples.

[0047]

[0054] In some aspects, the UE 120 includes means for obtaining, from an entity of the NTN, a SIB indicative of information related to one or more NTN SIBs, which will include at least one of ephemeris information or feeder link timing advance information, and / or means for obtaining, from an entity of the NTN, one or more NTN SIBs based at least in part on the information. The means for the UE 120 to perform operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0048]

[0055] In some aspects, the base station 110, or another NTN entity, includes means for outputting a SIB indicating information related to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information for transmission to the UE, and / or means for outputting one or more NTN SIBs based at least in part on the information for transmission to the UE. The means for the base station 110, or another NTN entity, to perform the operations described herein may include, for example, one or more of the communications manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antennas 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0049]

[0056] 2 are shown as separate components, the functionality described above with respect to the blocks may be implemented in a single hardware, software, or combination component, or in various combinations of components. For example, functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0050]

[0057] As noted above, Figure 2 is provided as an example. Other examples may differ from those described with respect to Figure 2.

[0051]

[0058] FIG. 3 illustrates an example of a regenerative satellite deployment 300 and an example of a transparent satellite deployment 310 in an NTN, in accordance with the present disclosure.

[0052]

[0059] The example 300 illustrates a regenerative satellite deployment. In the example 300, the UE 120 is served by a satellite 320 via a service link 330. For example, the satellite 320 may include a base station 110 (e.g., base station 110a) or a gNB. In some aspects, the satellite 320 may be referred to as a non-terrestrial base station, a regenerative repeater, or an on-board processing repeater. In some aspects, the satellite 320 may demodulate an uplink radio frequency signal and modulate a baseband signal derived from the uplink radio signal to generate a downlink radio frequency transmission. The satellite 320 may transmit the downlink radio frequency signal on the service link 330. The satellite 320 may provide a cell covering the UE 120.

[0053]

[0060] Example 310 illustrates a transparent satellite deployment, sometimes 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 signals received from gateway 350 via feeder link 360. For example, the satellite may receive an uplink radio frequency transmission and transmit a downlink radio frequency transmission without demodulating the uplink radio frequency transmission. In some aspects, the satellite may frequency convert an uplink radio frequency transmission received on service link 330 to the frequency of an uplink radio frequency transmission on feeder link 360 and may amplify and / or filter the uplink radio frequency transmission. In some aspects, UE 120 illustrated in examples 300 and 310 may be associated with Global Navigation Satellite System (GNSS) or Global Positioning System (GPS) capabilities, although not all UEs have such capabilities. The satellite 340 may provide a cell that covers the UE 120 .

[0054]

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

[0055]

[0062] The feeder link 360 and the service link 330 may each experience Doppler effects due to the movement of the satellites 320 and 340 and potentially the movement of the UE 120. These Doppler effects may be significantly greater than in terrestrial networks. The Doppler effects on the feeder link 360 may be compensated to some extent, but may still be associated with some amount of uncompensated frequency error. Additionally, the gateway 350 may be associated with residual frequency error and / or the satellites 320 / 340 may be associated with on-board frequency error. These sources of frequency error may cause the received downlink frequency at the UE 120 to drift from the target downlink frequency.

[0056]

[0063] As noted above, Figure 3 is provided as an example. Other examples may differ from those described with respect to Figure 3.

[0057]

[0064] FIG. 4 is a diagram illustrating an example 400 of system information scheduling in accordance with the present disclosure.

[0058]

[0065] A base station may provide system information (SI) to UEs covered by the base station. The SI may include physical layer information (e.g., in a master information block), access information (e.g., in SIB type 1 (SIB1)), and / or other information (e.g., in one or more other types of SIBs) for communication between the UE and the base station. One or more SIBs may be carried in an SI message. For example, SIB1 may be carried alone in an SI message, and one or more other SIBs may be carried in another SI message.

[0059]

[0066] The SI message carrying SIB1 may be transmitted at a fixed time location, which may facilitate identification of SIB1. In some examples, SIB1 carries scheduling information for other SI messages, and these other SI messages are transmitted during non-overlapping scheduling windows (e.g., scheduling windows that do not overlap with each other or with the window of SIB1). Thus, when a UE receives downlink control information (DCI) in a physical downlink control channel (PDCCH) that identifies an SI message, the UE may know which SI message is scheduled based at least in part on the scheduling window indicated by the scheduling information of SIB1.

[0060]

[0067] The scheduling information in SIB1 may indicate an SI window length (e.g., si-WindowLength), which is a common parameter of SI messages. That is, the SI window length is the same for all scheduled SI messages. The SI window length may define the length of the SI window in which the UE can expect SIB messages (e.g., which may carry one or more SIBs) to be transmitted. The UE may use a specific formula to determine the time location of the start of the SI window. During the SI window, the UE may search for the PDCCH to receive SI messages (e.g., may perform decoding of control communications using the SI Radio Network Temporary Identifier (SI-RNTI)). The scheduling information in SIB1 may also indicate, for each SI message, an SI periodicity (e.g., si-Periodicity) that identifies the time gap between consecutive SI windows (e.g., each SI message may have a separately configured SI periodicity).

[0061]

[0068] Changes to the information in the SI message may occur only after the upcoming boundary of the SI correction period (unless the SI message is for an Earthquake and Tsunami Warning System (ETWS), Commercial Mobile Alert System (CMAS), positioning assistance data, SIB type 9 (SIB9), etc.). Multiple SI windows may occur between SI correction boundaries due to repeat or retransmission of an SI message (e.g., without changes to the information in the SI message).

[0062]

[0069] As shown in FIG. 4, the boundaries of the SI modification period may be defined by a system frame number (SFN) value, SFN mod m=0, where m is the number of radio frames during the SI modification period. In some aspects, the value of m may be determined based on a configured factor value (e.g., modificationPeriodCoeff), which may have a value of 2, 4, 8, or 16, and a default paging cycle (e.g., PagingCycle), which may have a value of 32, 64, 128, or 256 radio frames. For example, as shown, if the configured factor value is 2 and the default paging cycle is 64 radio frames, the SI modification period may include 128 radio frames (e.g., corresponding to 1.28 seconds). Continuing with this example, a new SIB1 may be acquired at SFN mod 128=0 (e.g., after the SI modification period boundary). If the UE receives an SI update notification before the SI modification period boundary, the UE may acquire a new SIB1 after the SI modification period boundary. If the UE receives an SI update notification, the UE may receive SIB1 to check for changes to SI scheduling information and / or value tag (e.g., valueTag) parameters after an SI modification period. If the SIB1 stored by the UE is valid (i.e., no SIB1 change notification is received), all other SIBs (e.g., for scheduling and / or content) may also be considered valid (e.g., unchanged).

[0063]

[0070] As shown in Figure 4, if three SI messages are scheduled, the SI period may include three non-overlapping SI windows. SI may also be transmitted at the request of the UE, in which case an SI window may exist but no SI messages are broadcast. Within an SI window, an SI message may be transmitted one or more times. However, an SIB may only be included in a single SI message, and an SIB may be included in an SI message at most once.

[0064]

[0071] As noted above, Figure 4 is provided as an example. Other examples may differ from those described with respect to Figure 4.

[0065]

[0072] 5 is a diagram illustrating an example 500 of transmission of an NTN-specific SIB according to the present disclosure. An NTN-specific SIB (sometimes referred to herein as an NTN SIB) is a SIB that carries information of communication in an NTN. For example, the NTN SIB may carry ephemeris information and / or feeder link timing advance information. The feeder link timing advance information may indicate a round trip delay of all or part of a feeder link common to multiple UEs. The NTN SIB may be a new SIB type that may be indicated by a SIB type information parameter (e.g., SIB-TypeInfo) of SIB1.

[0066]

[0073] As shown in FIG. 5, the SI window may have a length (w) of 160 slots, and the NTN SIB may be the first of multiple scheduled SIBs (i.e., n=1 for the NTN SIB). The SI periodicity (T) may be configured as a value from 80 milliseconds (ms) to 5.12 seconds. As shown in FIG. 5, the periodicity of the SI message including the NTN SIB may be 640 ms (e.g., T=64 radio frames). In other words, the NTN SIB may have updated ephemeris information and / or updated feeder link timing advance information every 640 ms. Thus, as shown, the UE may acquire updated ephemeris information and / or feeder link timing advance information (e.g., an updated NTN SIB) at SFN=0, SFN=64, or SFN=128, etc. (e.g., where the slot number (a) for acquiring the updated NTN SIB is represented as slot a=(n-1)w mod 10).

[0067]

[0074] However, if the SI modification period is greater than 640 ms (e.g., m=128 radio frames, or 1.28 seconds, as shown), updating the NTN SIB every 640 ms is not possible in current wireless networks. Therefore, the network should be able to update the NTN SIB without notifying the UE (e.g., via an SI update notification paging message). In other words, the NTN SIB can change without changes to the scheduling parameters of the SI or changes to the version of SIB1 (e.g., systemInfoValueTag).

[0068]

[0075] As noted above, Figure 5 is provided as an example. Other examples may differ from those described with respect to Figure 5.

[0069]

[0076] The ephemeris information may describe the orbits of the satellites in the NTN (e.g., the ephemeris information may include parameters such as a reference time, or so-called “epoch time”, that specifies the time at which the orbital parameters are taken, Keplerian orbital parameters such as the square root of the semi-major axis, the eccentricity, and / or the inclination angle, and / or perturbation parameters such as the mean motion difference from a calculated value, the rate of change of right ascension and / or inclination, and / or the amplitude of one or more sine or cosine harmonic correction terms, among other examples). For example, the ephemeris information may indicate a formula that may be used by the UE to predict the position of the satellite over time. The maximum correction periodicity of the ephemeris information may be 10 to 60 seconds, and the transmission periodicity of the ephemeris information may be less than 1 second (e.g., may be determined at least in part based on an initial access delay). The UE may determine when to read the ephemeris information based at least in part on the UE's uplink timing error budget and / or an ephemeris prediction error associated with the UE.

[0070]

[0077] The feeder link timing advance information may indicate a timing advance to be used by the UE due to delays associated with the feeder link between the gateway and the satellite of the NTN. The feeder link timing advance information may indicate a feeder link timing advance without timing drift (e.g., a timing advance value that does not account for timing drift over time) or a feeder link timing advance with timing drift (e.g., a timing advance formula that accounts for timing drift over time).

[0071]

[0078] The correction periodicity of the feeder link timing advance without timing drift may be greater than 20 seconds (e.g., assuming 0.5 ms granularity), and the transmission periodicity of the feeder link timing advance without timing drift may be less than 1 second (e.g., may be determined based at least in part on the initial access delay). The UE may read the feeder link timing advance information of the timing advance without timing drift before the validity time of the information (e.g., which may be delayed relative to the signaling time of the information). In some examples, the feeder link timing advance information of the timing advance without timing drift may indicate a formula that the UE can use to determine the timing advance, thereby reducing reading of the feeder link timing advance information by the UE (e.g., the formula may indicate an increase of one slot from a common offset every 30 seconds).

[0072]

[0079] The maximum correction periodicity of the feeder link timing advance with timing drift may be 10 to 20 seconds in FR1 or 2 to 5 seconds in FR2, and the transmission periodicity of the feeder link timing advance with timing drift may be less than 1 second (e.g., may be determined based at least in part on the initial access delay). If a common timing advance offset (e.g., without timing drift) is used, the UE may read the feeder link timing advance information immediately upon updating the information. If timing drift is used instead, the UE may delay reading the information for a period of time after the information is updated (although the UE's prediction error may deteriorate rapidly beyond this period of time).

[0073]

[0080] As described above, the NTN SIB carrying ephemeris information (e.g., with timing drift) and / or timing advance information should be updated periodically. The update periodicity of the NTN SIB may be constrained by the need for reference time (e.g., epoch time) updates, which may also result in updates to the content of the NTN SIB. For example, the reference time used by the UE should be the latest time relative to the reception of the message to reduce prediction errors (network-performed ephemeris prediction may be more accurate than UE-performed ephemeris prediction due to the network's use of sophisticated prediction models). In some examples, the reference time (e.g., epoch time) may be implicitly indicated to the UE to reduce signaling overhead. For example, the reference time may be based at least in part on the boundaries of the downlink signal (e.g., of the NTN SIB).

[0074]

[0081] If the ephemeris information is updated every SI period via the NTN SIB, a repetition of the NTN SIB may be transmitted within the SI period, where the repetition of the NTN SIB within the SI period may be associated with the same reference time. That is, a single reference time may be used per SI period. The network may predict the position and / or velocity of the NTN satellite at the reference time (e.g., the time at the end of the slot of the first transmission within the period off the satellite) based at least in part on the latest GNSS readings.

[0075]

[0082] Thus, in NTNs, there are some SI parameters that are treated differently than in terrestrial networks due to the need to periodically update the SI parameters as the satellites' positions change relative to the earth. For example, ephemeris information is generally unique to NTNs, since it is used to describe the orbits of the satellites in the sky, and there are no SI parameters such as ephemeris in terrestrial networks. In another example, the feeder link timing advance may also be based at least in part on the positions of the satellites, but the timing advance used in terrestrial networks does not need to account for the movement of the satellites.

[0076]

[0083] In general, when one or more SI parameters are updated, the UE is usually notified via a paging message, and the UE is then expected to reacquire one or more SIBs to refresh the one or more SI parameters. However, sending a paging message to inform the UE when an SI parameter needs to be updated can lead to signaling overhead, which may be particularly problematic in NTNs due to large propagation delays and / or satellite motion potentially resulting in frequent changes to SI parameters. Moreover, SI parameters for NTNs, such as ephemeris information and feeder link timing advance information, may need to be updated more frequently than the SI correction period allows. If such SI parameters are not updated as frequently as required, the UE may become out of sync with the base station or satellite, communication to or from the UE may fail, etc.

[0077]

[0084] In some techniques and apparatus described herein, scheduling information for the NTN SIB may be provided in a SIB (e.g., SIB1). In some aspects, an update period for the NTN SIB, as well as a transmission window for the NTN SIB within the SI period, may be indicated in SIB1. In some aspects, SIB1 may include an indication of the validity duration and / or accuracy of the NTN SIB. In some aspects, SIB1 may include a resource allocation and / or MCS for the NTN SIB to avoid the need to schedule the NTN SIB over a PDCCH.

[0078]

[0085] The techniques described herein enable updating of ephemeris information and / or feeder link timing advance information without triggering an SI update procedure via a paging message. For example, the UE may obtain updated ephemeris information and / or feeder link timing advance information according to the scheduling information in SIB1 without notification to the UE via paging. In this manner, signaling overhead is reduced. Moreover, as described above, the UE may receive resource allocation for the NTN SIB in SIB1 rather than via the PDCCH, thereby further reducing signaling overhead.

[0079]

[0086] 6 is a diagram illustrating an example 600 relating to broadcasting an NTN SIB in accordance with the present disclosure. As shown in FIG. 6, the example 600 includes communication between an NTN entity 605 and a UE 120. In some aspects, the NTN entity 605 and the UE 120 may be included in a wireless network, such as wireless network 100 (e.g., an NTN). In some aspects, the NTN entity 605 may be an NTN base station 110, an NTN gateway 350, an NTN satellite 320, an NTN satellite 340, or the like.

[0080]

[0087] As indicated by reference numeral 610, the NTN entity 605 may transmit, and the UE 120 may receive, a SIB indicating information related to one or more NTN SIBs. As described herein, the NTN SIB may include at least one of ephemeris information or feeder link timing advance information (e.g., timing advance with timing drift or timing advance without timing drift). In some aspects, the SIB indicating the information may also carry access information. For example, the SIB indicating the information may be SIB1.

[0081]

[0088] In some aspects, the information related to one or more NTN SIBs may indicate an update periodicity of one or more NTN SIBs (e.g., of an SI message including one or more NTN SIBs) and / or may indicate one or more transmission windows (also referred to herein as scheduling windows or SI windows) within an update period of one or more NTN SIBs (e.g., of an SI message including one or more NTN SIBs). The update periodicity may be a SI period during which ephemeris information and / or feeder link timing advance information are updated, as described herein. The update period may be a SI period defined by the update periodicity and including one or more transmission windows for repetition or retransmission of one or more NTN SIBs (e.g., of an SI message including one or more NTN SIBs), as described herein. The SIB may indicate information related to one or more NTN SIBs (e.g., update periodicity and / or transmission window) separately (e.g., using a different parameter type than) information related to one or more non-NTN SIBs indicated in the SIB (e.g., update periodicity and / or transmission window).

[0082]

[0089] In aspects where a PDCCH is used to schedule physical downlink shared channel (PDSCH) communications of the NTN SIB, the transmission window may be for the NTN entity 605 to transmit and the UE 120 to receive a PDCCH communication that schedules the PDSCH communication (e.g., the transmission window is for PDCCH decoding). In aspects where a PDCCH is not used, the transmission window may be for the NTN entity 605 to transmit and the UE 120 to receive a PDSCH communication of the NTN SIB (e.g., a PDSCH communication of ephemeris information and / or feeder link timing advance information).

[0083]

[0090] In some aspects, a default update periodicity (e.g., used when update periodicity is not indicated) of one or more NTN SIBs may be the same as the periodicity (e.g., default periodicity or indicated periodicity in SIB1) of one or more non-NTN SIBs (e.g., SIB type 2 (SIB2), SIB type 3 (SIB3), etc.). In some aspects, one or more repetitions of an NTN SIB within an update period may be associated with the same reference time (e.g., epoch time, etc.). For example, SI messages of ephemeris information transmitted during a single update period may use the same reference time. However, different SIBs or information elements transmitted within an update period may be associated with different reference times.

[0084]

[0091] In some aspects, the reference time of the NTN SIB (e.g., for one or more repetitions of the NTN SIB associated with the same reference time) may be based at least in part on a particular downlink transmit timepoint (e.g., with respect to a satellite) within an update period. For example, the reference time of the SI message of the ephemeris information may be a particular downlink timepoint within an update period at a satellite of the NTN. The downlink transmit timepoint used for the reference time may be configured, specified, or otherwise provisioned for the UE 120, as described herein, thereby enabling an implicit indication of the reference time to the UE 120. The downlink transmit timepoint may be, for example, the end of the last downlink slot of the PDSCH carrying the NTN SIB (e.g., carrying ephemeris information and / or feeder link timing advance information) of the first transmit window of the update period at the satellite if a transmit window is specified. The downlink transmit timepoint may be, for example, the end of the first downlink slot of the update period at the satellite if a transmit window is not specified.

[0085]

[0092] In some aspects, the information related to one or more NTN SIBs may indicate a resource allocation and / or MCS for reception of the NTN SIBs at the UE 120. In this manner, the UE 120 can receive PDSCH communication of the NTN SIBs based at least in part on the resource allocation and / or MCS indicated in the information, and the PDCCH does not need to be used to schedule the PDSCH communication. The time domain resource allocation of the resource allocation may be with respect to (e.g., may be relative to) a start of a transmission window for the one or more NTN SIBs. In some aspects, the information related to one or more NTN SIBs may indicate a message size of the one or more NTN SIBs. For example, if the NTN SIBs may use a variable message size, the information may include an indication of the message size.

[0086]

[0093] In some aspects, the information related to one or more NTN SIBs may indicate a validity duration and / or accuracy (e.g., relative to a particular accuracy per subcarrier spacing) of one or more NTN SIBs. The validity duration and / or accuracy may be indicated in units of an update period (e.g., as a multiplier of the update period). In some aspects, the information may indicate a first validity duration and / or a first accuracy of ephemeris information and a second validity duration and / or a second accuracy of feeder link timing advance information.

[0087]

[0094] In some aspects, a mechanism for indicating scheduling information of one or more non-NTN SIBs (e.g., SIB2, SIB3, etc.) described herein (e.g., si-Periodicity parameter in SIB1) may also be used to indicate scheduling information of one or more NTN SIBs. For example, information related to one or more NTN SIBs may indicate update periodicity of one or more NTN SIBs using a parameter type (e.g., si-Periodicity parameter type) of a SIB that is also used to indicate the periodicity of one or more non-NTN SIBs. In other words, an update period of an NTN SIB may be defined similarly (e.g., in SIB1) to an SI period of another SIB. The update period may have a size small enough to accommodate a random access channel (RACH) delay. In some aspects, one or more SI windows (e.g., a first SI window and a third SI window of an SI period) may be designated or defined for transmission of the NTN SIB.

[0088]

[0095] In some aspects, the information related to one or more NTN SIBs may indicate an identifier of an entry in a table stored by UE 120. The table (e.g., a look-up table) may identify various combinations of an update periodicity of the NTN SIB, a transmission window within an update period of the NTN SIB (e.g., PDCCH or PDSCH of the NTN SIB), a time domain resource allocation for the NTN SIB, a frequency domain resource allocation for the NTN SIB, an MCS for the NTN SIB, and / or a message size of the NTN SIB. Thus, the identifier may indicate a particular combination of an update periodicity of the NTN SIB, a transmission window within an update period of the NTN SIB, a time domain resource allocation for the NTN SIB, a frequency domain resource allocation for the NTN SIB, an MCS for the NTN SIB, and / or a message size of the NTN SIB according to the table.

[0089]

[0096] In some aspects, the one or more NTN SIBs may include a single NTN SIB including ephemeris information and feeder link timing advance information (e.g., ephemeris information and feeder link timing advance information may be sent together in one NTN SIB). In some aspects, the one or more NTN SIBs may include multiple NTN SIBs each including ephemeris information and feeder link timing advance information (e.g., ephemeris information may be sent in a first NTN SIB and feeder link timing advance information may be sent in a second NTN SIB).

[0090]

[0097] In some aspects, if the feeder link timing advance information indicates a feeder link timing advance with timing drift, the information related to one or more NTN SIBs may provide an indication of a validity duration and / or accuracy of each of the ephemeris information and the feeder link timing advance information (e.g., when the ephemeris information and the feeder link timing advance information are sent together in one NTN SIB). For example, the information may indicate a first validity duration and / or a first accuracy of the ephemeris information and a second validity duration and / or a second accuracy of the feeder link timing advance information, as described above. In some aspects, if the feeder link timing advance information indicates a feeder link timing advance without timing drift, the update periodicity of the feeder link timing advance information may be based at least in part on the update periodicity of the ephemeris information (e.g., when the ephemeris information and the feeder link timing advance information are sent together in one NTN SIB). For example, the update periodicity of the feeder link timing advance information may be indicated in units of the update periodicity of the ephemeris information.

[0091]

[0098] In some aspects, if the feeder link timing advance information indicates a feeder link timing advance without timing drift, the information related to one or more NTN SIBs may indicate the feeder link timing advance information (e.g., the feeder link timing advance information is not indicated in the NTN SIB, but SIB1 indicates such information). Here, updates to the feeder link timing advance information may use a system information update procedure, as described herein. In some aspects, if the feeder link timing advance information indicates a feeder link timing advance without timing drift, the information related to one or more NTN SIBs may indicate an update periodicity of the feeder link timing advance information and / or an update period of the feeder link timing advance information (but may not indicate, e.g., a validity duration and / or accuracy of the feeder link timing advance information).

[0092]

[0099] In some aspects, if the feeder link timing advance information indicates a feeder link timing advance without timing drift, the application time of the feeder link timing advance information (e.g., by UE 120) may be determined based on a last slot number (m) of a first PDSCH communication of one or more NTN SIBs during an update period, or a last slot number (m) of a first transmission window of one or more transmission windows during an update period, plus a system scheduling offset value (K offset For example, the application time of the feeder link timing advance (e.g., common offset) may be based at least in part on uplink slot number m+K offset +x, where x is a constant value such as 1 or 2.

[0093]

[0100] As described herein, the update periodicity of the NTN SIB may indicate the periodicity at which ephemeris information and / or feeder link timing advance information are updated. Thus, an update to one or more NTN SIBs may include (updated) ephemeris information and / or feeder link timing advance information without triggering (e.g., without relying on) a system information update procedure. That is, the update does not trigger a SIB modification and associated paging, as described herein.

[0094]

[0101] Based at least in part on information related to one or more NTN SIBs in the SIB (e.g., in SIB1), the NTN entity 605 may transmit, and the UE 120 may receive, one or more NTN SIBs, as indicated by reference numeral 615. For example, the UE 120 may receive the one or more NTN SIBs according to an indicated update periodicity (e.g., within an update period according to the update periodicity), according to one or more indicated transmission windows, according to an indicated resource allocation and / or MCS, etc. As described herein, during each update period (e.g., without SI update notification paging), the UE 120 may receive one or more updated NTN SIBs including updated ephemeris information and / or updated feeder link timing advance information.

[0095]

[0102] As indicated by reference numeral 620, the UE 120 and the NTN entity 605 may communicate based at least in part on one or more NTN SIBs. That is, the UE 120 and the NTN entity 605 may communicate based at least in part on ephemeris information and / or feeder link timing advance information. For example, the UE 120 may communicate with the NTN entity 605 using the ephemeris information and / or feeder link timing advance information (e.g., in accordance with a reference time, validity duration, and / or accuracy as described herein).

[0096]

[0103] As noted above, Figure 6 is provided as an example. Other examples may differ from those described with respect to Figure 6.

[0097]

[0104] 7 illustrates an example process 700, for example, performed by a UE, in accordance with the present disclosure. The example process 700 is an example in which a UE (for example, UE 120) performs operations related to broadcasting an NTN SIB.

[0098]

[0105] 7, in some aspects, process 700 may include receiving, from an entity of the NTN, a SIB indicating information related to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information (block 710). For example, the UE may receive (e.g., using the communications manager 140 and / or the receiving component 902, shown in FIG. 9), from an entity of the NTN, a SIB indicating information related to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information, as described above.

[0099]

[0106] 7, in some aspects, process 700 may include receiving, from an entity of the NTN, one or more NTN SIBs based at least in part on the information (block 720). For example, the UE may receive (e.g., using the communications manager 140 and / or the receiving component 902, shown in FIG. 9), one or more NTN SIBs based at least in part on the information from an entity of the NTN, as described above.

[0100]

[0107] Process 700 may include additional aspects, such as any single aspect or any combination of aspects, with respect to one or more other processes described below and / or elsewhere herein.

[0101]

[0108] In a first aspect, the information indicates at least one of an update periodicity of one or more NTN SIBs or one or more transmission windows within an update period of one or more NTN SIBs.

[0102]

[0109] In a second aspect, alone or in combination with the first aspect, the one or more transmission windows are for reception of PDCCH communications that schedule one or more NTN SIBs.

[0103]

[0110] In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more transmission windows are for reception of PDSCH communications of one or more NTN SIBs.

[0104]

[0111] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the default update periodicity of one or more NTN SIBs is the same as the periodicity of one or more non-NTN SIBs.

[0105]

[0112] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, one or more repetitions of an NTN SIB of one or more NTN SIBs within an update period are associated with the same reference time.

[0106]

[0113] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, a reference time for one or more NTN SIBs is based at least in part on a particular downlink transmission time point within an update period.

[0107]

[0114] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the information indicates at least one of a resource allocation or an MCS for reception of one or more NTN SIBs.

[0108]

[0115] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the time domain resource allocation of the resource allocation is with respect to a start of a transmission window for one or more NTN SIBs.

[0109]

[0116] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the information further indicates a message size of one or more NTN SIBs.

[0110]

[0117] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the information indicates at least one of a duration of effectiveness or accuracy of one or more NTN SIBs.

[0111]

[0118] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the information indicates an update periodicity of one or more NTN SIBs using a parameter type of a SIB that is also used to indicate the periodicity of one or more non-NTN SIBs.

[0112]

[0119] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, updates to one or more NTN SIBs include at least one of ephemeris information or feeder link timing advance information without triggering a system information update procedure.

[0113]

[0120] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the information indicates an identifier indicating one or more of an update periodicity of one or more NTN SIBs, one or more transmission windows within an update period of one or more NTN SIBs, a time domain resource allocation for one or more NTN SIBs, a frequency domain resource allocation for one or more NTN SIBs, an MCS, or a message size of one or more NTN SIBs according to a table.

[0114]

[0121] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the one or more NTN SIBs include a single NTN SIB that includes ephemeris information and feeder link timing advance information.

[0115]

[0122] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the feeder link timing advance information indicates a feeder link timing advance with timing drift, and the information indicates at least one of a first validity duration or a first accuracy of the ephemeris information and at least one of a second validity duration or a second accuracy of the feeder link timing advance information.

[0116]

[0123] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the feeder link timing advance information indicates a feeder link timing advance without timing drift, and an update periodicity of the feeder link timing advance information is based at least in part on an update periodicity of the ephemeris information.

[0117]

[0124] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the one or more NTN SIBs include a plurality of NTN SIBs each including ephemeris information and feeder link timing advance information.

[0118]

[0125] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the information indicates feeder link timing advance information, the feeder link timing advance information indicating a feeder link timing advance without timing drift.

[0119]

[0126] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the feeder link timing advance information indicates a feeder link timing advance without timing drift, and the information indicates at least one of an update periodicity of the feeder link timing advance information or an update period of the feeder link timing advance information.

[0120]

[0127] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, the feeder link timing advance information indicates a feeder link timing advance without timing drift, and an application time of the feeder link timing advance information is based at least in part on a last slot number of a first PDSCH communication of one or more NTN SIBs or a last slot number of a first transmission window during an update period and a system scheduling offset value.

[0121]

[0128] Although Figure 7 illustrates example blocks of process 700, in some aspects process 700 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those illustrated in Figure 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0122]

[0129] 8 illustrates an example process 800, performed, for example, by an NTN entity, in accordance with the present disclosure. The example process 800 is an example of an NTN entity (e.g., base station 110, satellite 320, satellite 340, gateway 350, etc.) performing operations related to broadcasting an NTN SIB.

[0123]

[0130] 8, in some aspects, process 800 may include transmitting to the UE a SIB indicating information related to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information (block 810). For example, the NTN entity (e.g., using the communications manager 150 and / or the transmitting component 1004 shown in FIG. 10) may transmit to the UE a SIB indicating information related to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information, as described above.

[0124]

[0131] 8, in some aspects, process 800 may include transmitting, to the UE, one or more NTN SIBs based at least in part on the information (block 820). For example, the NTN entity (e.g., using the communications manager 150 and / or the transmitting component 1004, shown in FIG. 10), may transmit, to the UE, one or more NTN SIBs based at least in part on the information, as described above.

[0125]

[0132] Process 800 may include additional aspects, such as any single aspect or any combination of aspects with respect to one or more other processes described below and / or elsewhere herein.

[0126]

[0133] In a first aspect, the information indicates at least one of an update periodicity of one or more NTN SIBs or one or more transmission windows within an update period of one or more NTN SIBs.

[0127]

[0134] In a second aspect, alone or in combination with the first aspect, the one or more transmission windows are for transmission of PDCCH communications that schedule one or more NTN SIBs.

[0128]

[0135] In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more transmission windows are for transmission of PDSCH communications of one or more NTN SIBs.

[0129]

[0136] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the default update periodicity of one or more NTN SIBs is the same as the periodicity of one or more non-NTN SIBs.

[0130]

[0137] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, one or more repetitions of an NTN SIB of one or more NTN SIBs within an update period are associated with the same reference time.

[0131]

[0138] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, a reference time for one or more NTN SIBs is based at least in part on a particular downlink transmission time point within an update period.

[0132]

[0139] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the information indicates at least one of a resource allocation or an MCS for reception of one or more NTN SIBs.

[0133]

[0140] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the time domain resource allocation of the resource allocation is with respect to a start of a transmission window for one or more NTN SIBs.

[0134]

[0141] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the information further indicates a message size of one or more NTN SIBs.

[0135]

[0142] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the information indicates at least one of a duration of effectiveness or accuracy of one or more NTN SIBs.

[0136]

[0143] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the information indicates an update periodicity of one or more NTN SIBs using a parameter type of a SIB that is also used to indicate the periodicity of one or more non-NTN SIBs.

[0137]

[0144] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, updates to one or more NTN SIBs include at least one of ephemeris information or feeder link timing advance information without triggering a system information update procedure.

[0138]

[0145] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the information indicates an identifier indicating one or more of an update periodicity of one or more NTN SIBs, one or more transmission windows within an update period of one or more NTN SIBs, a time domain resource allocation for one or more NTN SIBs, a frequency domain resource allocation for one or more NTN SIBs, an MCS, or a message size of one or more NTN SIBs according to a table.

[0139]

[0146] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the one or more NTN SIBs include a single NTN SIB that includes ephemeris information and feeder link timing advance information.

[0140]

[0147] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the feeder link timing advance information indicates a feeder link timing advance with timing drift, and the information indicates at least one of a first validity duration or a first accuracy of the ephemeris information and at least one of a second validity duration or a second accuracy of the feeder link timing advance information.

[0141]

[0148] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the feeder link timing advance information indicates a feeder link timing advance without timing drift, and an update periodicity of the feeder link timing advance information is based at least in part on an update periodicity of the ephemeris information.

[0142]

[0149] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the one or more NTN SIBs include a plurality of NTN SIBs each including ephemeris information and feeder link timing advance information.

[0143]

[0150] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the information indicates feeder link timing advance information, the feeder link timing advance information indicating a feeder link timing advance without timing drift.

[0144]

[0151] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the feeder link timing advance information indicates a feeder link timing advance without timing drift, and the information indicates at least one of an update periodicity of the feeder link timing advance information or an update period of the feeder link timing advance information.

[0145]

[0152] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, the feeder link timing advance information indicates a feeder link timing advance without timing drift, and an application time of the feeder link timing advance information is based at least in part on a last slot number of a first PDSCH communication of one or more NTN SIBs or a last slot number of a first transmission window during an update period and a system scheduling offset value.

[0146]

[0153] 8 illustrates example blocks of process 800, in some aspects process 800 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those illustrated in FIG 8. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0147]

[0154] 9 is a diagram of an example apparatus 900 for wireless communication. The apparatus 900 may be a UE, or the UE may include the apparatus 900. In some aspects, the apparatus 900 includes a receiving component 902 and a transmitting component 904 that may be in communication with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using the receiving component 902 and the transmitting component 904. As further shown, the apparatus 900 may include a communications manager 140. The communications manager 140 may include an SI component 908, among other examples.

[0148]

[0155] In some aspects, the apparatus 900 may be configured to perform one or more operations described herein with respect to FIG. 6. Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as the process 700 of FIG. 7, or a combination thereof. In some aspects, the apparatus 900 and / or one or more components illustrated in FIG. 9 may include one or more components of a UE described with respect to FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 9 may be implemented within one or more components described with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented, at least in part, as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0149]

[0156] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 906. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of a UE as described with respect to FIG.

[0150]

[0157] The transmitting component 904 may transmit a communication, such as a reference signal, control information, a data communication, or a combination thereof, to the device 906. In some aspects, one or more other components of the device 900 may generate a communication and provide the generated communication to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and transmit the processed signal to the device 906. In some aspects, the transmitting component 904 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of a UE as described with respect to FIG. 2. In some aspects, the transmitting component 904 may be co-located with the receiving component 902 in a transceiver.

[0151]

[0158] The receiving component 902 may receive, from an NTN entity (e.g., device 906), a SIB indicating information related to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information. The receiving component 902 may receive one or more NTN SIBs from the NTN entity based at least in part on the information. The receiving component 902 and / or the transmitting component 904 may communicate with the NTN entity based at least in part on the one or more NTN SIBs. The SI component 908 may process, store, apply, etc., SI in the one or more NTN SIBs (e.g., ephemeris information and / or feeder link timing advance information).

[0152]

[0159] In some examples, the means for transmitting, outputting, or sending (or the means for outputting for transmission) may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, or combinations thereof, of the UE, as described above with respect to FIG.

[0153]

[0160] In some examples, the means for receiving (or the means for obtaining) may include one or more antennas, a demodulator, a MIMO detector, a receive processor, or a combination thereof, of the UE, as described above with respect to FIG.

[0154]

[0161] In some cases, for example, rather than actually transmitting signals and / or data, a device may have an interface (means for outputting) to output signals and / or data for transmission. For example, a processor may output signals and / or data to an RF front end for transmission via a bus interface. Similarly, rather than actually receiving signals and / or data, a device may have an interface (means for acquiring) to acquire signals and / or data received from another device. For example, a processor may acquire (or receive) signals and / or data from an RF front end for reception via a bus interface. In various aspects, the RF front end may include various components, including transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc., such as those shown in the example of FIG. 2.

[0155]

[0162] In some examples, the means for determining, obtaining, or sending may include various processing system components of the UE, such as a receiving processor, a transmitting processor, a controller / processor, a memory, or combinations thereof, as described above with respect to FIG. 2.

[0156]

[0163] The number and configuration of components shown in Figure 9 are provided as an example. In practice, there may be additional components, fewer components, different components, or components configured differently than those shown in Figure 9. Furthermore, two or more components shown in Figure 9 may be implemented within a single component, or a single component shown in Figure 9 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (or components) shown in Figure 9 may perform one or more functions described as being performed by another set of components shown in Figure 9.

[0157]

[0164] FIG. 10 is a diagram of an example apparatus 1000 for wireless communication. The apparatus 1000 may be a base station or another NTN entity, or the base station or another NTN entity may include the apparatus 1000. In some aspects, the apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may be in communication with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using the receiving component 1002 and the transmitting component 1004. As further shown, the apparatus 1000 may include a communications manager 150. The communications manager 150 may include an SI component 1008, among other examples.

[0158]

[0165] In some aspects, the apparatus 1000 may be configured to perform one or more operations described herein with respect to FIG. 6. Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as the process 800 of FIG. 8, or a combination thereof. In some aspects, the apparatus 1000 and / or one or more components illustrated in FIG. 10 may include one or more components of a base station described with respect to FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 10 may be implemented within one or more components described with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented, at least in part, as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0159]

[0166] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the base station described with respect to FIG.

[0160]

[0167] The transmitting component 1004 may transmit a communication, such as a reference signal, control information, a data communication, or a combination thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate a communication and provide the generated communication to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and transmit the processed signal to the device 1006. In some aspects, the transmitting component 1004 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the base station described with respect to FIG. 2. In some aspects, the transmitting component 1004 may be co-located with the receiving component 1002 in a transceiver.

[0161]

[0168] The transmitting component 1004 may transmit to the UE (e.g., the apparatus 1006) a SIB indicating information related to one or more NTN SIBs, which will include at least one of ephemeris information or feeder link timing advance information. The transmitting component 1004 may transmit to the UE one or more NTN SIBs based at least in part on the information. The receiving component 1002 and / or the transmitting component 1004 may communicate with the UE based at least in part on the one or more NTN SIBs. The SI component 1008 may generate, process, store, etc., SI (e.g., ephemeris information and / or feeder link timing advance information) for one or more NTN SIBs.

[0162]

[0169] In some examples, the means for transmitting, outputting, or sending (or the means for outputting for transmission) may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, or combinations thereof, of a base station or another NTN entity described above with respect to FIG. 2.

[0163]

[0170] In some examples, the means for receiving (or the means for obtaining) may include one or more antennas, a demodulator, a MIMO detector, a receive processor, or a combination thereof, of a base station or another NTN entity described above with respect to FIG.

[0164]

[0171] In some cases, for example, rather than actually transmitting signals and / or data, a device may have an interface (means for outputting) to output signals and / or data for transmission. For example, a processor may output signals and / or data to an RF front end for transmission via a bus interface. Similarly, rather than actually receiving signals and / or data, a device may have an interface (means for acquiring) to acquire signals and / or data received from another device. For example, a processor may acquire (or receive) signals and / or data from an RF front end for reception via a bus interface. In various aspects, the RF front end may include various components, including transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc., such as those shown in the example of FIG. 2.

[0165]

[0172] In some examples, the means for determining, obtaining, or sending may include various processing system components, such as a receiving processor, a transmitting processor, a controller / processor, a memory, or combinations thereof, of a base station or another NTN entity described above with respect to FIG. 2.

[0166]

[0173] The number and configuration of components shown in Figure 10 are provided as an example. In practice, there may be additional components, fewer components, different components, or components configured differently than those shown in Figure 10. Furthermore, two or more components shown in Figure 10 may be implemented within a single component, or a single component shown in Figure 10 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (or components) shown in Figure 10 may perform one or more functions described as being performed by another set of components shown in Figure 10.

[0167]

[0174] The following provides a summary of several aspects of the disclosure.

[0168]

[0175] Aspect 1: A method of wireless communication in a user equipment (UE), comprising: obtaining, from an entity of a non-terrestrial network (NTN), a SIB indicating information relating to one or more NTN system information blocks (SIBs) that include at least one of ephemeris information or feeder link timing advance information; and obtaining, from the entity of the NTN, one or more NTN SIBs based at least in part on the information.

[0169]

[0176] Aspect 2: The method of aspect 1, wherein the information indicates at least one of an update periodicity of one or more NTN SIBs or one or more transmission windows within an update period of one or more NTN SIBs.

[0170]

[0177] Aspect 3: The method of aspect 2, wherein the one or more transmission windows are for reception of physical downlink control channel communication that schedules one or more NTN SIBs.

[0171]

[0178] Aspect 4: The method of aspect 2, wherein the one or more transmission windows are for reception of physical downlink shared channel communication of one or more NTN SIBs.

[0172]

[0179] Embodiment 5: The method of any of embodiments 1-4, wherein the default update periodicity of the one or more NTN SIBs is the same as the periodicity of the one or more non-NTN SIBs.

[0173]

[0180] Aspect 6: The method of any of aspects 1-5, wherein one or more repetitions of an NTN SIB of the one or more NTN SIBs within an update period are associated with the same reference time.

[0174]

[0181] Aspect 7: The method of any of aspects 1-6, wherein the reference time of at least one of the ephemeris information or feeder link timing advance information of one or more NTN SIBs is based at least in part on a particular downlink transmission time point within an update period.

[0175]

[0182] Example 8: The method of any of examples 1 to 7, wherein the information indicates at least one of a resource allocation or a modulation and coding scheme for reception of one or more NTN SIBs.

[0176]

[0183] Aspect 9: The method of aspect 8, wherein the time domain resource allocation of the resource allocation is with respect to a start of a transmission window for one or more NTN SIBs.

[0177]

[0184] Embodiment 10: The method of any of embodiments 8-9, wherein the information further indicates a message size of one or more NTN SIBs.

[0178]

[0185] Embodiment 11: The method of any of embodiments 1-10, wherein the information indicates at least one of a duration of validity or accuracy of one or more NTN SIBs.

[0179]

[0186] Aspect 12: The method of any of aspects 1 or 5-11, wherein the information indicates an update periodicity of one or more NTN SIBs using a parameter type of a SIB that is also used to indicate the periodicity of one or more non-NTN SIBs.

[0180]

[0187] Aspect 13: The method of any of aspects 1-11, wherein an update to at least one of ephemeris information or feeder link timing advance information is independent of triggering a system information update procedure.

[0181]

[0188] Aspect 14: The method of any of aspects 1, 5-11, or 13, wherein the information indicates an identifier indicating one or more of an update periodicity of one or more NTN SIBs, one or more transmission windows within an update period of one or more NTN SIBs, a time domain resource allocation for one or more NTN SIBs, a frequency domain resource allocation for one or more NTN SIBs, a modulation and coding scheme, or a message size of one or more NTN SIBs according to a table.

[0182]

[0189] Example 15: The method of any of Examples 1-14, wherein the one or more NTN SIBs include a single NTN SIB that includes ephemeris information and feeder link timing advance information.

[0183]

[0190] Aspect 16: The method of aspect 15, wherein the feeder link timing advance information indicates a feeder link timing advance with timing drift, and the information indicates at least one of a first validity duration or a first accuracy of the ephemeris information and at least one of a second validity duration or a second accuracy of the feeder link timing advance information.

[0184]

[0191] Aspect 17: The method of aspect 15, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and an update periodicity of the feeder link timing advance information is based at least in part on an update periodicity of the ephemeris information.

[0185]

[0192] Example 18: The method of any of Examples 1-14, wherein the one or more NTN SIBs include a plurality of NTN SIBs each including ephemeris information and feeder link timing advance information.

[0186]

[0193] Aspect 19: The method of any of aspects 1-14, wherein the information indicates feeder link timing advance information, the feeder link timing advance information indicating a feeder link timing advance without timing drift.

[0187]

[0194] Aspect 20: The method of any of aspects 1-15 or 17-18, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and the information indicates at least one of an update periodicity of the feeder link timing advance information or an update period of the feeder link timing advance information.

[0188]

[0195] Aspect 21: The method of any of aspects 1-15, 17-18, or 20, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and an application time of the feeder link timing advance information is based at least in part on a last slot number of a first physical downlink shared channel communication of one or more NTN SIBs or a last slot number of a first transmission window during an update period, and a system scheduling offset value.

[0189]

[0196] Aspect 22: A method of wireless communication in a non-terrestrial network (NTN) entity, comprising: outputting, for transmission to a user equipment (UE), a SIB indicating information relating to one or more NTN system information blocks (SIBs) that will include at least one of ephemeris information or feeder link timing advance information; and outputting, at least in part, one or more NTN SIBs based on the information, for transmission to the UE.

[0190]

[0197] Aspect 23: The method of aspect 22, wherein the information indicates at least one of an update periodicity of one or more NTN SIBs or one or more transmission windows within an update period of one or more NTN SIBs.

[0191]

[0198] Aspect 24: The method of aspect 23, wherein the one or more transmission windows are for transmission of physical downlink control channel communications that schedule one or more NTN SIBs.

[0192]

[0199] Aspect 25: The method of aspect 23, wherein the one or more transmission windows are for transmission of physical downlink shared channel communications of one or more NTN SIBs.

[0193]

[0200] Embodiment 26: The method of any of embodiments 22-25, wherein the default update periodicity of the one or more NTN SIBs is the same as the periodicity of the one or more non-NTN SIBs.

[0194]

[0201] Example 27: The method of any of examples 22-26, wherein one or more repetitions of an NTN SIB of the one or more NTN SIBs within an update period are associated with the same reference time.

[0195]

[0202] Example 28: The method of any of Examples 22-27, wherein the reference time of at least one of the ephemeris information or feeder link timing advance information of one or more NTN SIBs is based at least in part on a particular downlink transmission time point within an update period.

[0196]

[0203] Example 29: The method of any of examples 22-28, wherein the information indicates at least one of a resource allocation or a modulation and coding scheme for reception of one or more NTN SIBs.

[0197]

[0204] Example 30: The method of example 29, wherein the time domain resource allocation of the resource allocation is with respect to a start of a transmission window for one or more NTN SIBs.

[0198]

[0205] Embodiment 31: The method of any of embodiments 29 to 30, wherein the information further indicates a message size of one or more NTN SIBs.

[0199]

[0206] Embodiment 32: The method of any of embodiments 22-31, wherein the information indicates at least one of a duration of validity or accuracy of one or more NTN SIBs.

[0200]

[0207] Embodiment 33: The method of any of embodiments 22 or 26-32, wherein the information indicates an update periodicity of one or more NTN SIBs using a parameter type of a SIB that is also used to indicate the periodicity of one or more non-NTN SIBs.

[0201]

[0208] Example 34: The method of any of Examples 22-32, wherein an update to at least one of the ephemeris information or the feeder link timing advance information is not dependent on triggering a system information update procedure.

[0202]

[0209] Aspect 35: The method of any of aspects 22, 26-32, or 34, wherein the information indicates an identifier indicating one or more of an update periodicity of one or more NTN SIBs, one or more transmission windows within an update period of one or more NTN SIBs, a time domain resource allocation for one or more NTN SIBs, a frequency domain resource allocation for one or more NTN SIBs, a modulation and coding scheme, or a message size of one or more NTN SIBs according to a table.

[0203]

[0210] Example 36: The method of any of examples 22-35, wherein the one or more NTN SIBs include a single NTN SIB that includes ephemeris information and feeder link timing advance information.

[0204]

[0211] Aspect 37: The method of aspect 36, wherein the feeder link timing advance information indicates a feeder link timing advance with timing drift, and the information indicates at least one of a first validity duration or a first accuracy of the ephemeris information and at least one of a second validity duration or a second accuracy of the feeder link timing advance information.

[0205]

[0212]

[0081] Aspect 38: The method of aspect 36, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and an update periodicity of the feeder link timing advance information is based at least in part on an update periodicity of the ephemeris information.

[0206]

[0213] Example 39: The method of any of Examples 22-35, wherein the one or more NTN SIBs include a plurality of NTN SIBs each including ephemeris information and feeder link timing advance information.

[0207]

[0214] Example 40: The method of any of Examples 22-35, wherein the information indicates feeder link timing advance information, the feeder link timing advance information indicating a feeder link timing advance without timing drift.

[0208]

[0215] Aspect 41: The method of any of aspects 22-36 or 38-39, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and the information indicates at least one of an update periodicity of the feeder link timing advance information or an update period of the feeder link timing advance information.

[0209]

[0216] Aspect 42: The method of any of aspects 22-36, 38-39, or 41, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and an application time of the feeder link timing advance information is based at least in part on a last slot number of a first physical downlink shared channel communication of one or more NTN SIBs or a last slot number of a first transmission window during an update period, and a system scheduling offset value.

[0210]

[0217] Aspect 43: An apparatus for wireless communication, comprising: a memory having instructions; and one or more processors configured to execute the instructions and cause the apparatus to perform one or more of the methods of aspects 1-21.

[0211]

[0218] Aspect 44: A user equipment (UE), comprising at least one receiver, a memory having instructions, and one or more processors configured to execute the instructions and cause the UE to perform one or more methods of aspects 1-21, wherein the at least one receiver is configured to receive a SIB and one or more NTN SIBs.

[0212]

[0219] Example 45: An apparatus for wireless communication, comprising at least one means for performing one or more methods of examples 1-21.

[0213]

[0220] Aspect 46: A non-transitory computer-readable medium comprising one or more instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform one or more of the methods of aspects 1-21.

[0214]

[0221] Aspect 47: An apparatus for wireless communication, comprising: a memory having instructions; and one or more processors configured to execute the instructions and cause the apparatus to perform one or more of the methods of aspects 22-42.

[0215]

[0222] Aspect 48: An entity of a non-terrestrial network (NTN), comprising at least one transmitter, a memory having instructions, and one or more processors configured to execute the instructions and cause the NTN entity to perform one or more methods of aspects 22-42, wherein the at least one transmitter is configured to transmit a SIB and one or more NTN SIBs.

[0216]

[0223] Example 49: An apparatus for wireless communication, comprising at least one means for performing one or more of the methods of examples 22-42.

[0217]

[0224] Aspect 50: A non-transitory computer-readable medium comprising one or more instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform one or more of the methods of aspects 22-42.

[0218]

[0225] The above disclosure provides illustration and description, but is not intended to be exhaustive or to limit the embodiments to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or acquired from practice of the embodiments.

[0219]

[0226] The term "component" as used herein is 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, threads of execution, procedures, and / or functions, whether termed software, firmware, middleware, microcode, hardware description language, or the like. A "processor" as used herein is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, as one skilled in the art will appreciate that software and hardware may be designed to implement the systems and / or methods based at least in part on the description herein.

[0220]

[0227] As used herein, "meeting a threshold" may refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc., depending on the context.

[0221]

[0228] Although certain combinations of features are recited in the claims and / or disclosed herein, these combinations do not limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or disclosed herein. The disclosure of the various aspects includes each dependent claim in combination with any other claim in the set of claims. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" includes a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of multiple identical 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 ordering of a, b, and c).

[0222]

[0229] No element, act, or instruction used herein should be construed as critical or essential unless expressly described as such. Additionally, the articles "a" and "an" as used herein include one or more items and may be used interchangeably with "one or more." Additionally, the article "the" as used herein includes one or more items referenced with the article "the" and may be used interchangeably with "one or more." Additionally, the terms "set" and "group" as used herein include one or more items and may be used interchangeably with "one or more." When only one item is intended, the phrase "only one" or similar language is used. Additionally, terms such as "has," "have," and "having" as used herein are intended to be open-ended terms that do not limit the elements they modify (e.g., an element that "has" A may also have B). Additionally, the phrase "based on" is intended to mean "based at least in part on," unless otherwise specified. Additionally, as used herein, the term "or" is inclusive when used consecutively and may be used interchangeably with "and / or" unless otherwise noted (e.g., when used in combination with "either" or "only one of").

Claims

1. An apparatus for wireless communication, comprising: one or more memories storing instructions; one or more processors configured to execute the instructions to cause the apparatus to: obtain a system information block (SIB) indicating information related to one or more non-terrestrial network (NTN) system information blocks (SIBs); obtain the one or more NTN SIBs based at least in part on the information, wherein the one or more NTN SIBs include at least one of ephemeris information or feeder link timing advance information; communicate with one or more entities of the NTN based at least in part on the one or more NTN SIBs, wherein the reference time of the at least one of the ephemeris information or the feeder link timing advance information is based at least in part on a specific downlink transmission time; an update to the at least one of the ephemeris information or the feeder link timing advance information does not depend on triggering a system information update procedure; or the one or more NTN SIBs include a single NTN SIB including the ephemeris information and the feeder link timing advance information; at least one of the above; one or more processors configured to perform the above; and an apparatus.

2. The apparatus of claim 1, wherein the reference time of the ephemeris information is based at least in part on a specific downlink transmission time.

3. The apparatus of claim 1, wherein the reference time of the feeder link timing advance information is based at least in part on a specific downlink transmission time.

4. The apparatus of claim 1, wherein an update to the at least one of the ephemeris information or the feeder link timing advance information does not depend on triggering a system information update procedure.

5. The apparatus of claim 1, wherein the one or more NTN SIBs include a single NTN SIB including the ephemeris information and the feeder link timing advance information.

6. The apparatus according to claim 1, wherein the information indicates at least one of resource allocation for obtaining the one or more NTN SIBs, modulation and coding schemes for obtaining the one or more NTN SIBs, message size of the one or more NTN SIBs, validity duration of the one or more NTN SIBs, or accuracy of the one or more NTN SIBs.

7. The apparatus according to claim 1, wherein the feeder link timing advance information indicates a feeder link timing advance with timing drift.

8. The apparatus according to claim 1, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift.

9. The apparatus according to claim 1, wherein the information indicates the feeder link timing advance information, and the feeder link timing advance information indicates a feeder link timing advance without timing drift.

10. The apparatus according to claim 1, further comprising a receiver configured to receive the SIB and the one or more NTN SIBs, wherein the apparatus is configured as a user equipment (UE).

11. One or more devices for wireless communication, comprising: One or more memories comprising instructions; Executing the instructions to cause the one or more devices to: Output an SIB indicating information related to one or more non-terrestrial network (NTN) system information blocks (SIBs) for transmission to a user equipment (UE); Output the one or more NTN SIBs at least partially based on the information for transmission to the UE, wherein the one or more NTN STBs include at least one of ephemeris information or feeder link timing advance; Communicate with the UE at least partially based on the one or more NTN SIBs, wherein The reference time of at least one of the ephemeris information or the feeder link timing advance information is at least partially based on a specific downlink transmission time point. that an update to at least one of the ephemeris information or the feeder link timing advance information does not depend on triggering a system information update procedure, or that the one or more NTN SIBS include a single NTN SIB that includes the ephemeris information and the feeder link timing advance information, wherein at least one of the above is true, one or more processors configured to cause one or more devices comprising. **Claim 12** The one or more devices according to claim 11, wherein a reference time of the ephemeris information is at least partially based on the specific downlink transmission time. **Claim 13** The one or more devices according to claim 11, wherein a reference time of the feeder link timing advance information is at least partially based on the specific downlink transmission time. **Claim 14** i) that the update to at least one of the ephemeris information or the feeder link timing advance information does not depend on triggering the system information update procedure, ii) that the one or more NTN SIBS include a single NTN SIB that includes the ephemeris information and the feeder link timing advance information, iii) that the information indicates at least one of resource allocation for acquiring the one or more NTN SIBS, modulation and coding schemes for acquiring the one or more NTN SIBS, message size of the one or more NTN SIBS, validity duration of the one or more NTN SIBS, or accuracy of the one or more NTN SIBS, iv) that the feeder link timing advance information indicates a feeder link timing advance without timing drift, v) that the information indicates the feeder link timing advance information, and the feeder link timing advance information indicates a feeder link timing advance without timing drift, or vi) one or more transmitters configured to transmit the SIB and the one or more NTN SIBS, wherein the one or more devices are configured as one or more entities of the NTN The one or more apparatuses according to claim 11, further comprising one of them.

15. A method of wireless communication in a user equipment (UE), comprising: Obtaining a system information block (SIB) indicating information related to one or more non-terrestrial network (NTN) system information blocks (SIBs); Obtaining the one or more NTN SIBs based at least in part on the information, wherein the one or more NTN STBs include at least one of ephemeris information or feeder link timing advance information; Communicating with the NTN based at least in part on the one or more NTN SIBs, wherein The reference time of at least one of the ephemeris information or the feeder link timing advance information is at least in part based on a specific downlink transmission time; The update for at least one of the ephemeris information or the feeder link timing advance information does not depend on triggering a system information update procedure, or The one or more NTN SIBs include a single NTN SIB including the ephemeris information and the feeder link timing advance information; At least one of A method comprising.

Images