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, titled "BROADCASTING OF A NON - TERRESTRIAL NETWORK SYSTEM INFORMATION BLOCK", filed on August 5, 2021, and U.S. Non - Provisional Patent Application No. 17 / 661,996, titled "BROADCASTING OF A NON - TERRESTRIAL NETWORK SYSTEM INFORMATION BLOCK", filed on May 4, 2022, which are hereby expressly incorporated herein by reference.

[0002]

[0002] Aspects of the present disclosure generally relate to wireless communication and pertain to techniques and apparatus for broadcasting a non - terrestrial network (NTN) system information block (SIB).

Background Art

[0003]

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, including telephone, video, data, messaging, and broadcast. Typical wireless communication systems may use multiple access technologies that enable 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 published by the Third Generation Partnership Project (3GPP®).

[0004]

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

[0005]

[0005] The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at urban, national, regional, and / or global scales. New Radio (NR), sometimes called 5G, is a set of extensions to the LTE mobile standard published by 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving service, taking advantage of new spectra, and better integrating with other open standards by using orthogonal frequency division multiplexing (OFDM) with cyclic prefixes (CP) (CP-OFDM) on the downlink and CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM) (also known as, for example, discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as by supporting beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. As demand for mobile broadband access continues to rise, further improvements in LTE, NR, and other wireless access technologies remain valuable. [Overview of the project]

[0006]

[0006] Some aspects described herein relate to methods of wireless communication in user equipment (UE). The method may include receiving an SIB from an entity of a non-terrestrial network (NTN) that indicates information relating to one or more NTN system information blocks (SIBs) which will include at least one of ephemeris information or feeder link timing advance information. The method may include receiving one or more NTN SIBs from an NTN entity based at least in part on the information.

[0007]

[0007] Some aspects described herein relate to methods of wireless communication in an NTN entity. The method may include transmitting to a UE one or more SIBs that include information relating to one or more NTN SIBs, which will include at least one of ephemeris information or feeder link timing advance information. The method may include transmitting to a UE one or more NTN SIBs based at least in part on the information.

[0008]

[0008] Some embodiments described herein relate to a device for wireless communication. The device may include a memory containing instructions and one or more processors configured to execute instructions. One or more processors may be configured to execute instructions and cause the device to obtain SIBs from an NTN entity that represent information relating to one or more NTN SIBs, which will include at least one of ephemeris information or feeder link timing advance information. One or more processors may be configured to execute instructions and cause the device to obtain one or more NTN SIBs from an NTN entity based at least in part on the information.

[0009]

[0009] Some embodiments described herein relate to a device for wireless communication. The device may include a memory having instructions and one or more processors configured to execute instructions. One or more processors may be configured to execute instructions and cause the device to output an SIB showing information relating to one or more NTN SIBs, which will include at least one of ephemeris information or feeder link timing advance information, for transmission to a UE. One or more processors may be configured to execute instructions and cause the device to output one or more NTN SIBs based at least in part on the information, for transmission to a UE.

[0010]

[0010] Some embodiments described herein relate to a non-temporary computer-readable medium comprising instructions. Instructions can cause the device to obtain, when executed by one or more processors of the device, SIBs from an NTN entity that represent information relating to one or more NTN SIBs, which will include at least one of ephemeris information or feeder link timing advance information. Instructions can cause the device to obtain, when executed by one or more processors of the device, one or more NTN SIBs from an NTN entity based at least in part on the information.

[0011]

[0011] Some embodiments described herein relate to non-temporary computer-readable media comprising instructions. Instructions can cause the device to output an SIB showing information relating to one or more NTN SIBs, which, when executed by one or more processors of the device, will include at least one of ephemeris information or feeder link timing advance information, for transmission to the UE. Instructions can cause the device to output one or more NTN SIBs, at least in part, based on the information, for transmission to the UE.

[0012]

[0012] Some embodiments described herein relate to apparatus for wireless communication. The apparatus may include means for obtaining SIBs from an NTN entity that indicate information relating to one or more NTN SIBs, which will include at least one of ephemeris information or feeder link timing advance information. The apparatus may include means for obtaining one or more NTN SIBs from an NTN entity based at least in part on the information.

[0013]

[0013] Some embodiments described herein relate to devices for wireless communication. The device may include means for outputting an SIB showing information relating to one or more NTN SIBs, which will include at least one of ephemeris information or feeder link timing advance information, for transmission to a UE. The device may include means for outputting one or more NTN SIBs based at least in part on the information, for transmission to a UE.

[0014]

[0014] The embodiments are generally substantially described herein with reference to the drawings and specification and include methods, apparatus, systems, computer program products, non-temporary computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems, as shown by the drawings and specification.

[0015]

[0015] The above outlines fairly broadly the features and technical advantages of the examples provided in this disclosure so that the modes for carrying out the following inventions may be better understood. Additional features and advantages are described below. The concepts and specific examples disclosed may readily be used as a basis for modifying or designing other structures to accomplish the same purpose of this disclosure. Such equivalent configurations will not deviate from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their organization and method of operation, along with the advantages related thereto, will be better understood from the following description when considered together with the appended figures. Each of the figures is provided for illustrative and explanatory purposes and is not provided as a definition of the limitation of the claims.

[0016]

[0016] While embodiments are described in this disclosure by example to several examples, those skilled in the art will understand that such embodiments can be implemented in many different configurations and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some embodiments can 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). Embodiments can 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 embodiments and features described may include additional components and features for the implementation and practice of the claimed and described embodiments. For example, wireless signal transmission and reception 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). The embodiments described herein can be implemented in a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and structures.

[0017]

[0017] A more detailed description than that briefly summarized above can be obtained by referring to embodiments shown in part in the accompanying drawings, so that the features listed above may be understood in more detail. However, it should be noted that the accompanying drawings only show some typical embodiments of the disclosure, and therefore the description should not be considered limiting, as other equally effective embodiments may be recognized. The same reference numerals in different drawings may identify the same or similar elements. [Brief explanation of the drawing]

[0018] [Figure 1]

[0018] Figure showing an example of a wireless network according to the present disclosure. [Figure 2]

[0019] Figure showing an example of a base station communicating with a user equipment (UE) in a wireless network according to the present disclosure. [Figure 3]

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

[0021] Figure showing an example of system information scheduling according to the present disclosure. [Figure 5]

[0022] Figure showing an example of transmission of a non-terrestrial network (NTN)-specific system information block (SIB) according to the present disclosure. [Figure 6]

[0023] Figure showing an example related to broadcasting of NTN SIB according to the present disclosure. [Figure 7]

[0024] Figure showing an exemplary process related to broadcasting of NTN SIB according to the present disclosure. [Figure 8] Figure showing an exemplary process related to broadcasting of NTN SIB according to the present disclosure. [Figure 9]

[0025] Figure showing an exemplary apparatus for wireless communication according to the present disclosure. [Figure 10] Figure showing an exemplary apparatus for wireless communication according to the present disclosure.

Mode for Carrying Out the Invention

[0019]

[0026] Various aspects of the present disclosure will be described more fully hereinafter 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. It should be understood that the scope of the disclosure, whether implemented independently of any other aspect of the disclosure or implemented in combination with any other aspect of the disclosure, encompasses any aspect of the disclosure disclosed herein. For example, any number of the aspects described herein may be used to implement an apparatus or practice a method. In addition, the scope of the disclosure covers such apparatus or methods practiced using other structures, functions, or structures and functions in addition to or other than the various aspects of the disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0020]

[0027] Next, some aspects of a telecommunications system are presented with reference to various devices and techniques. These devices and techniques are described in the following detailed description and are shown 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 terms generally associated with 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure may be applicable to other RATs such as 3G RAT, 4G RAT, and / or RATs following 5G (e.g., 6G).

[0022]

[0029] Figure 1 shows an example of a wireless network 100 as described herein. The wireless network 100 may be, or may 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 (indicated as BS110a, BS110b, BS110c, and BS110d), user equipment (UEs) 120 or a number of UEs 120 (indicated as UE120a, UE120b, UE120c, UE120d, and UE120e), and / or other network entities. A base station 110 is an entity that communicates with a UE 120. A base station 110 (sometimes called a BS) may include, for example, an NR base station, an LTE base station, a node B, an eNB (e.g., for 4G), a gNB (e.g., for 5G), an access point, and / or a transmit / receive point (TRP). Each base station 110 may provide communication coverage to a specific geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” may refer to the coverage area of ​​base station 110 and / or the base station subsystem that serves this coverage area, depending on the context in which the term is used.

[0023]

[0030] Base station 110 may provide communication coverage to macrocells, picocells, femtocells, and / or other types of cells. Macrocells may cover relatively large geographical areas (e.g., a radius of several kilometers) and may enable unrestricted access by UEs 120 subscribing to the service. Picocells may cover relatively small geographical areas and may enable unrestricted access by UEs 120 subscribing to the service. Femtocells may cover relatively small geographical areas (e.g., a home) and may enable limited access by UEs 120 associated with a femtocell (e.g., UEs 120 in a limited subscriber group (CSG)). Base station 110 for macrocells may be called a macro base station. Base station 110 for picocells may be called a pico base station. Base station 110 for femtocells may be called a femto base station or home base station. In the example shown in Figure 1, BS110a may be a macro base station for macrocell 102a, BS110b may be a pico base station for picocell 102b, and BS110c may be a femto base station for femtocell 102c. A base station may support one or more (for example, three) cells.

[0024]

[0031] In some examples, cells may not necessarily be fixed, and the geographical area of ​​a cell may move according to the location of a mobile base station 110 (e.g., a mobile base station). In some examples, 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 embodiments, as shown in Figure 1, the cell may be provided by a base station 110 of a non-terrestrial network. As used herein, “non-terrestrial network” (NTN) may refer to a network whose access is provided by non-terrestrial base stations, such as base stations carried by NTN entities (e.g., satellites, balloons, airships, airplanes, unmanned aerial vehicles, high-altitude platform stations). NTN base stations may be base stations carried by NTN entities (regenerative deployment) or terrestrial base stations communicating through NTN entities (vent 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 data transmissions from an upstream station (e.g., a base station 110 or UE120) and send those data transmissions to a downstream station (e.g., a UE120 or base station 110). A relay station may be a UE120 that can relay transmissions to other UE120s. In the example shown in Figure 1, BS110d (e.g., a relay base station) may communicate with BS110a (e.g., a macro base station) and UE120d to facilitate communication between BS110a and UE120d. The base station 110 that relays communications may be called a relay station, relay base station, 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, and relay base stations. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0028]

[0035] The network controller 130 may be coupled to or communicate with a set of base stations 110, and may coordinate and control these base stations 110. The network controller 130 may communicate with the base stations 110 via a backhaul communication link. The base stations 110 may communicate with each other directly or indirectly via wireless or wireline backhaul communication links.

[0029]

[0036] UE120 may be distributed across the entire wireless network 100, and each UE120 may be stationary or mobile. UE120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE120 may be cellular phones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablets, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices, biometric devices, wearable devices (e.g., smartwatches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings or smart bracelets)), entertainment devices (e.g., music devices, video devices, and / or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system devices, and / or any other suitable devices configured to communicate via a wireless medium.

[0030]

[0037] Some UE120s may be considered machine-type communications (MTC) or advanced or enhanced machine-type communications (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with base stations, other devices (e.g., remote devices), or any other entities. Some UE120s may be considered Internet of Things (IoT) devices and / or implemented as NB-IoT (Narrowband IoT) devices. Some UE120s may be considered customer premises equipment. A UE120 may be contained within a housing that accommodates its components, such as processor components and / or memory components. In some examples, processor components and memory components may be coupled together. For example, processor components (e.g., one or more processors) and memory components (e.g., memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0031]

[0038] In general, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT is sometimes called a radio technology, air interface, etc. Frequencies are sometimes called carriers, frequency channels, etc. Each frequency may support a single RAT in a given geographical area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0032]

[0039] In some examples, two or more UE120s (shown, for example, as UE120a and UE120e) may communicate directly using one or more sidelink channels (for example, without using base station 110 as an intermediary for communication with each other). For example, UE120s may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-anything (V2X) protocols (which may include, for example, vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE120s may perform scheduling operations, resource selection operations, and / or other operations described elsewhere in this specification as being performed by base station 110.

[0033]

[0040] Devices in wireless network 100 may communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, channels, etc., depending on frequency or wavelength. For example, devices in wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands are 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 although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and papers. A similar naming issue sometimes arises with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunication Union (ITU) as the “millimeter wave” band.

[0034]

[0041] The frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. Recent 5G NR research identifies the operating band of these intermediate band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands falling within FR3 can inherit the characteristics of FR1 and / or FR2, and thus the characteristics of FR1 and / or FR2 can be effectively extended to the intermediate band frequencies. Furthermore, 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, unless otherwise specified, terms such as “sub-6GHz” can broadly refer to frequencies that may be below 6GHz, within FR1, or include midband frequencies, as used herein. Furthermore, unless otherwise specified, terms such as “millimeter wave” can broadly refer to frequencies that may include midband frequencies, within FR2, FR4, FR4-a or FR4-1, and / or FR5, or within the EHF band, as used herein. The frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are intended to be applicable to those modified frequency ranges.

[0036]

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

[0037]

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

[0038]

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

[0039]

[0046] Figure 2 shows an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 according to this disclosure. The base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≧1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≧1).

[0040]

[0047] At base station 110, the transmitting processor 220 may receive data from data source 212 addressed to UE 120 (or a set of UE 120s). The transmitting processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120, at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120, at least in part on the MCS selected for the UE 120, and may provide data symbols to the UE 120. The transmitting processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, authorizations, and / or upper-layer signaling), and may provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulated reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may, where applicable, perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, 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) indicated as modems 232a-232t. For example, each output symbol stream may be provided to a modulator component (indicated as MOD) of a modem 232. Each modem 232 may process its respective output symbol stream (e.g., for OFDM) using its respective modulator component to obtain an output sample stream. Each modem 232 may further process the output sample stream using its respective modulator components to acquire a downlink signal (e.g., convert to analog, amplify, filter, and / or upconvert).Modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) indicated as antennas 234a to 234t.

[0041]

[0048] In UE120, a set of antennas 252 (indicated as antennas 252a to 252r) may receive downlink signals from base station 110 and / or other base stations 110 and provide a set of received signals (e.g., R received signals) to a set of modems 254 (indicated as modems 254a to 254r) (e.g., R modems). For example, each received signal may be provided to a demodulator component (indicated as DEMOD) of a modem 254. Each modem 254 may use its respective demodulator component to process the received signals (e.g., filter, amplify, downconvert, and / or digitize) in order to acquire an input sample. Each modem 254 may further process the input sample (e.g., for OFDM) using its demodulator component to acquire a received symbol. A MIMO detector 256 may acquire a received symbol from a modem 254, perform MIMO detection on the received symbol where applicable, and provide a detected symbol. The receiving processor 258 may process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to the data sink 260, and provide the 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, among other things, determine the reference signal received power (RSRP) parameter, the received signal intensity indicator (RSSI) parameter, the reference signal received quality (RSRQ) parameter, and / or the CQI parameter. In some examples, one or more components of UE 120 may be contained within the housing 284.

[0042]

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

[0043]

[0050] One or more antennas (for example, antennas 234a-234t and / or antennas 252a-252r) may, among other examples, 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. 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 transmit and / or receive components such as one or more components in Figure 2.

[0044]

[0051] On the uplink, in UE120, the transmit processor 264 may receive and process data from data source 262 and control information from controller / processor 280 (for reporting, e.g., 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, if applicable, be precoded by the TX MIMO processor 266, further processed by the modem 254 (for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some examples, the modem 254 in UE120 may include a modulator and demodulator. In some examples, UE120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. A transceiver may be used by a processor (e.g., a controller / processor 280) and a memory 282 to carry out any aspect of the method described herein (for example, with reference to Figures 6 to 10).

[0045]

[0052] At base station 110, uplink signals from UE 120 and / or other UEs are received by antenna 234, processed by modem 232 (e.g., the demodulator component of modem 232, indicated as DEMOD), detected by MIMO detector 236 where applicable, and may be further processed by receiving processor 238 to obtain decoded data and control information sent by UE 120. The receiving processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include a communication unit 244, which may communicate with network controller 130 via the communication unit 244. Base station 110 may include a scheduler 246 for scheduling one or more UE 120 for downlink and / or uplink communication. In some examples, the modem 232 of base station 110 may include a modulator and a demodulator. In some examples, base station 110 includes a transceiver. The transceiver may include any combination of the antenna 234, modem 232, MIMO detector 236, receiving processor 238, transmitting 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 carry out any aspect of the method described herein (for example, with reference to Figures 6 to 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 in Figure 2 may implement one or more techniques related to NTN SIB broadcasting, as will be described in more detail elsewhere in this specification. In some embodiments, the NTN entities described herein are the base station 110, contained within the base station 110, or include one or more components of the base station 110 shown in Figure 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 in Figure 2 may implement or direct the operation of, for example, process 700 in Figure 7, process 800 in Figure 8, and / or other processes described herein. Memories 242 and 282 may store data and program code for the base station 110 and the UE 120, respectively. In some examples, memory 242 and / or memory 282 may include non-temporary computer-readable media for storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when one or more instructions are executed by one or more processors in base station 110 and / or UE 120 (e.g., directly or after compilation, conversion, and / or interpretation), one or more processors, UE 120, and / or base station 110 may perform or direct the operation of, for example, process 700 in Figure 7, process 800 in Figure 8, and / or other processes described herein. In some examples, executing an instruction may include, among other things, invoking the instruction, converting the instruction, compiling the instruction, and / or interpreting the instruction.

[0047]

[0054] In some embodiments, the UE120 includes means for obtaining an SIB from an NTN entity that shows information relating 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 one or more NTN SIBs from an NTN entity based at least in part on the information. Means for the UE120 to perform the operations described herein may include, for example, one or more of the following: a communications manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receiving processor 258, a transmitting processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0048]

[0055] In some embodiments, the base station 110, or another NTN entity, includes means for outputting an SIB showing information relating to one or more NTN SIBs, which 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. 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 following: a communications manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0049]

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

[0050]

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

[0051]

[0058] Figure 3, provided for in this disclosure, shows an example 300 of regenerative satellite deployment and an example 310 of transparent satellite deployment at NTN.

[0052]

[0059] Example 300 illustrates a regenerative satellite deployment. In Example 300, UE120 is serviced by satellite 320 via service link 330. For example, satellite 320 may include base station 110 (e.g., base station 110a) or gNB. In some embodiments, satellite 320 may be referred to as a non-terrestrial base station, regenerative repeater, or onboard processing repeater. In some embodiments, 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. Satellite 320 may transmit a downlink radio frequency signal over service link 330. Satellite 320 may provide a cell covering UE120.

[0053]

[0060] Example 310 illustrates a transparent satellite deployment, sometimes called a bent-pipe satellite deployment. In Example 310, UE120 is serviced 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 uplink radio frequency transmissions and transmit downlink radio frequency transmissions without demodulating the uplink radio frequency transmissions. In some embodiments, the satellite may frequency convert uplink radio frequency transmissions received on service link 330 to the frequency of uplink radio frequency transmissions on feeder link 360, and may amplify and / or filter the uplink radio frequency transmissions. In some embodiments, UE120 as shown in Examples 300 and 310 may be associated with Global Navigation Satellite System (GNSS) capability or Global Positioning System (GPS) capability, but not all UEs have such capability. Satellite 340 could provide cells covering UE120.

[0054]

[0061] Service link 330 may include a link between satellite 340 and UE120, and may include one or more uplinks or downlinks. Feeder link 360 may include a link between satellite 340 and gateway 350, and may include one or more uplinks (e.g., from UE120 to gateway 350) or downlinks (e.g., from gateway 350 to UE120). The uplinks of service link 330 may be indicated by reference number 330-U (not shown in Figure 3), and the downlinks of service link 330 may be indicated by reference number 330-D (not shown in Figure 3). Similarly, the uplinks of feeder link 360 may be indicated by reference number 360-U (not shown in Figure 3), and the downlinks of feeder link 360 may be indicated by reference number 360-D (not shown in Figure 3).

[0055]

[0062] Feederlink 360 and servicelink 330 may experience Doppler effects, respectively, due to the movement of satellites 320 and 340 and potentially the movement of UE120. These Doppler effects can be significantly greater than in terrestrial networks. While the Doppler effect on feederlink 360 can be compensated to some extent, it may still be associated with some amount of uncompensated frequency error. Furthermore, gateway 350 may be associated with residual frequency error, and / or satellites 320 / 340 may be associated with onboard frequency error. These sources of frequency error can cause the received downlink frequency at UE120 to drift from the target downlink frequency.

[0056]

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

[0057]

[0064] Figure 4 shows an example 400 of system information scheduling according to this disclosure.

[0058]

[0065] A base station may provide system information (SI) to the 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 an 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 other SI messages.

[0059]

[0066] SI messages carrying SIB1 may be transmitted at a fixed time location, which can facilitate the identification of SIB1. In some examples, SIB1 carries scheduling information for other SI messages, and these other SI messages are transmitted within 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) that identifies an SI message in the physical downlink control channel (PDCCH), the UE can know which SI messages are scheduled, at least partially based on the scheduling windows indicated by the scheduling information of SIB1.

[0060]

[0067] The scheduling information in SIB1 may indicate the SI window length (e.g., si-WindowLength), 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 over which a UE can expect an SIB message to be transmitted (e.g., one or more SIBs may be carried). 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 look up PDCCH to receive an SI message (e.g., 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 information within an SI message can only occur 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 the repetition or retransmission of an SI message (for example, without any change to the information within the SI message).

[0062]

[0069] As shown in Figure 4, the boundary of the SI modification period may be defined by a System Frame Number (SFN) value where SFN mod m = 0, where m is the number of radio frames during the SI modification period. In some embodiments, the value of m may be determined based on a configured coefficient value (e.g., modificationPeriodCoeff), which can have values ​​of 2, 4, 8, or 16, and a default paging cycle (e.g., PagingCycle), which can have values ​​of 32, 64, 128, or 256 radio frames. For example, as shown in the figure, if the configured coefficient 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 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 an SIB1 indicating that it should check for changes to the SI scheduling information and / or value tag (e.g., valueTag) parameter after the SI correction 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. SIs may also be sent at the request of the UE, in which case SI windows may exist, but the SI messages are not broadcast. Within an SI window, SI messages may be sent once or multiple times. However, an SIB can only be included in a single SI message, and an SIB can be included in an SI message at most once.

[0064]

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

[0065]

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

[0066]

[0073] As shown in Figure 5, the SI window may have a length (w) of 160 slots, and the NTN SIB may be the first of several 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 Figure 5, the periodicity of the SI message containing the NTN SIB may be 640 ms (e.g., T=64 radio frames). In other words, the NTN SIB may have ephemeris information and / or updated feeder link timing advance information updated every 640 ms. Therefore, as shown in the figure, the UE can acquire updated ephemeris information and / or feeder link timing advance information (e.g., updated NTN SIB) at SFN=0, SFN=64, or SFN=128, etc. (for example, here 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 correction period is greater than 640ms (for example, m = 128 wireless frames, or 1.28 seconds, as shown in the diagram), updating the NTN SIB every 640ms is not possible in current wireless networks. Therefore, the network should be able to update the NTN SIB without notifying the UE (for example, via an SI update notification paging message). In other words, the NTN SIB can change without any changes to the SI scheduling parameters or to the version of SIB1 (for example, systemInfoValueTag).

[0068]

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

[0069]

[0076] Ephemeris information can describe the satellite's orbit at NTN (for example, ephemeris information may include parameters such as a reference time, or so-called "epoch time," specifying the time over which orbital parameters are taken; Kepler orbital parameters such as the square root of the semi-major axis, eccentricity, and / or inclination; and / or perturbation parameters such as the mean difference in motion from calculated values, the rate of change of right ascension and / or inclination, and / or the amplitude of one or more sine or cosine harmonic correction terms). For example, ephemeris information may provide an equation that can be used by the UE to predict the satellite's position over time. The maximum correction periodicity of ephemeris information can be between 10 and 60 seconds, and the transmission periodicity of ephemeris information can be less than 1 second (which can be determined, for example, at least in part, on the 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 the ephemeris prediction error associated with the UE.

[0070]

[0077] The feeder link timing advance information may indicate the timing advance to be used by the UE due to delays associated with the feeder link between NTN's gateway and the satellite. 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 consider timing drift over time) or a feeder link timing advance with timing drift (e.g., a timing advance formula that considers timing drift over time).

[0071]

[0078] The correction periodicity of a feeder link timing advance without timing drift can be greater than 20 seconds (for example, assuming a 0.5 ms granularity), and the transmission periodicity of a feeder link timing advance without timing drift can be less than 1 second (for example, it can be determined at least in part on the initial access delay). A UE may read the feeder link timing advance information for a timing advance without timing drift before the information's effective time (for example, it may be delayed with respect to the signaling time of the information). In some examples, the feeder link timing advance information for a timing advance without timing drift may show a formula that a UE can use to determine the timing advance, thereby reducing the amount of time the UE has to read the feeder link timing advance information (for example, the formula may show an increase of one slot from the common offset every 30 seconds).

[0072]

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

[0073]

[0080] As described above, the NTN SIB, which carries ephemeris information and / or timing advance information (e.g., with timing drift), should be updated periodically. The update periodicity of the NTN SIB may be constrained by the need for a reference time (e.g., epoch time) update, which may also lead to updates to the content of the NTN SIB. For example, the reference time used by the UE should be the most recent time to the message reception in order to reduce prediction errors (ephemeris predictions performed by the network may be more accurate than ephemeris predictions performed by the UE, due to the use of high-performance prediction models by the network). In some cases, the reference time (e.g., epoch time) may be implicitly indicated to the UE in order to reduce signaling overhead. For example, the reference time may be based at least in part on the boundary of the downlink signal (e.g., the NTN SIB).

[0074]

[0081] If ephemeris information is updated via NTN SIB every SI period, then repetitions of NTN SIB may be transmitted within an SI period. Here, repetitions of NTN SIB within an SI period may be associated with the same reference time; that is, a single reference time may be used for each SI period. The network may predict the position and / or velocity of NTN satellites at a reference time (e.g., the time at the end of the first transmission slot during the period when the satellite is away) based at least in part on the most recent GNSS readings.

[0075]

[0082] Therefore, in NTN, there are several SI parameters that are treated differently from those in terrestrial networks due to the need to periodically update the SI parameters as the satellite's position changes relative to the ground. For example, ephemeris information is used to describe the satellite's orbit in the sky, so ephemeris information is generally unique to NTN, and terrestrial networks do not have SI parameters like ephemeris. In another example, feeder link timing advance can also be based at least partially on the satellite's position, but the timing advance used in terrestrial networks does not need to take satellite movement into account.

[0076]

[0083] Generally, when one or more SI parameters are updated, the UE is typically 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 paging messages to notify the UE when SI parameters need to be updated can lead to signaling overhead, which can be particularly problematic for NTN due to large propagation delays and / or satellite motion potentially resulting in frequent changes to SI parameters. Furthermore, SI parameters for NTN, 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, it may result in the UE becoming out of sync with the base station or satellite, or communication to or from the UE failing.

[0077]

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

[0078]

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

[0079]

[0086] Figure 6 shows an example 600 relating to NTN SIB broadcasting as described herein. As shown in Figure 6, example 600 includes communication between NTN entity 605 and UE 120. In some embodiments, NTN entity 605 and UE 120 may be contained within a wireless network such as wireless network 100 (e.g., NTN). In some embodiments, NTN entity 605 may be an NTN base station 110, an NTN gateway 350, an NTN satellite 320, an NTN satellite 340, etc.

[0080]

[0087] As indicated by reference number 610, NTN entity 605 may transmit an SIB containing information relating to one or more NTN SIBs, and UE 120 may receive it. As described herein, an NTN SIB may contain at least one of ephemeris information (e.g., timing advance with or without timing drift) or feeder link timing advance information. In some embodiments, an information-containing SIB may also carry access information. For example, an information-containing SIB may be SIB1.

[0081]

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

[0082]

[0089] In a configuration in which PDCCH is used to schedule physical downlink shared channel (PDSCH) communication of NTN SIB, the transmit window may be for NTN entity 605 to transmit PDCCH communication to schedule PDSCH communication and for UE 120 to receive it (for example, the transmit window is for PDCCH decoding). In a configuration in which PDCCH is not used, the transmit window may be for NTN entity 605 to transmit NTN SIB PDSCH communication (for example, PDSCH communication of ephemeris information and / or feeder link timing advance information) and for UE 120 to receive it.

[0083]

[0090] In some embodiments, the default update periodicity of one or more NTN SIBs (e.g., used when update periodicity is not indicated) may be the same as the periodicity of one or more non-NTN SIBs (e.g., SIB type 2 (SIB2), SIB type 3 (SIB3), etc.) (e.g., the default periodicity or the periodicity indicated in SIB1). In some embodiments, one or more repetitions of an NTN SIB within an update period may be associated with the same reference time (e.g., epoch time). 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 embodiments, the reference time for an NTN SIB (for example, for one or more iterations of an NTN SIB associated with the same reference time) may be based at least in part on a particular downlink transmit timepoint (for example, with respect to a satellite) within the update period. For example, the reference time for an SI message of ephemeris information may be a particular downlink timepoint within the update period on an NTN satellite. The downlink transmit timepoint used for the reference time may be configured, specified, or otherwise provisioned for the UE120, as described herein, to thereby enable implicit indication of the reference time to the UE120. The downlink transmit timepoint may be, for example, the end of the last downlink slot of the PDSCH carrying the NTN SIB (for example, carrying ephemeris information and / or feeder link timing advance information) in the first transmit window of the update period on the satellite, if a transmit window is specified. The downlink transmit timepoint may be the end of the first downlink slot of the update period on the satellite, if no transmit window is specified.

[0085]

[0092] In some embodiments, information relating to one or more NTN SIBs may indicate resource allocations and / or MCS for receiving NTN SIBs in the UE120. Thus, the UE120 can receive PDSCH communications of NTN SIBs based at least partially on the resource allocations and / or MCS indicated in the information, and the PDCCH does not need to be used to schedule PDSCH communications. The time-domain resource allocation of the resource allocation may be relative to (e.g., based on) the start of the transmit window for one or more NTN SIBs. In some embodiments, information relating to one or more NTN SIBs may indicate the message size of one or more NTN SIBs. For example, if an NTN SIB may use a variable message size, the information may include an indication of the message size.

[0086]

[0093] In some embodiments, information relating to one or more NTN SIBs may indicate the effective duration and / or precision of one or more NTN SIBs (e.g., based on a specific precision for each subcarrier interval). The effective duration and / or precision may be expressed in units of update interval (e.g., as a multiplier of update interval). In some embodiments, the information may indicate a first effective duration and / or first precision of ephemeris information and a second effective duration and / or second precision of feeder link timing advance information.

[0087]

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

[0088]

[0095] In some embodiments, information relating to one or more NTN SIBs may indicate identifiers of entries in a table stored by the UE120. The table (e.g., a lookup table) may identify various combinations of NTN SIB update periodicity, transmission windows within the NTN SIB update period (e.g., NTN SIB PDCCH or PDSCH), time-domain resource allocation for NTN SIB, frequency-domain resource allocation for NTN SIB, MCS for NTN SIB, and / or NTN SIB message sizes. Thus, the identifier may, according to the table, indicate a specific combination of NTN SIB update periodicity, transmission windows within the NTN SIB update period, time-domain resource allocation for NTN SIB, frequency-domain resource allocation for NTN SIB, MCS for NTN SIB, and / or NTN SIB message sizes.

[0089]

[0096] In some embodiments, one or more NTN SIBs may include a single NTN SIB containing ephemeris information and feeder link timing advance information (for example, ephemeris information and feeder link timing advance information may be transmitted together in one NTN SIB). In some embodiments, one or more NTN SIBs may include multiple NTN SIBs, each containing ephemeris information and feeder link timing advance information (for example, ephemeris information may be transmitted in a first NTN SIB, and feeder link timing advance information may be transmitted in a second NTN SIB).

[0090]

[0097] In some embodiments, if the feeder link timing advance information indicates a feeder link timing advance with timing drift, information relating to one or more NTN SIBs may provide indications of the effective duration and / or precision of the ephemeris information and the feeder link timing advance information, respectively (for example, when ephemeris information and feeder link timing advance information are transmitted together in one NTN SIB). For example, the information may indicate a first effective duration and / or first precision of the ephemeris information and a second effective duration and / or second precision of the feeder link timing advance information, as described above. In some embodiments, 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 at least partially based on the update periodicity of the ephemeris information (for example, when ephemeris information and feeder link timing advance information are transmitted together in one NTN SIB). For example, the update periodicity of feeder link timing advance information can be represented by units of the update periodicity of ephemeris information.

[0091]

[0098] In some embodiments, if the feeder link timing advance information indicates a feeder link timing advance without timing drift, information related to one or more NTN SIBs may indicate the feeder link timing advance information (for example, the feeder link timing advance information is not indicated in the NTN SIB, but rather SIB1 indicates such information). Here, updates to the feeder link timing advance information may be performed using a system information update procedure, as described herein. In some embodiments, if the feeder link timing advance information indicates a feeder link timing advance without timing drift, information related to one or more NTN SIBs may indicate the update periodicity and / or update duration of the feeder link timing advance information (but may not indicate, for example, the effective duration and / or accuracy of the feeder link timing advance information).

[0092]

[0099] In some embodiments, when 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 (for example, by UE120) is the last slot number (m) of the first PDSCH communication of one or more NTN SIBs during the update period, or the last slot number (m) of the first transmit window of one or more transmit windows during the update period, and the system scheduling offset value (K offset ) and may be based at least partially on the following. For example, the application time of the feeder link timing advance (e.g., common offset) is based on uplink slot number m+K offset It can be +x, where x is a constant value such as 1 or 2.

[0093]

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

[0094]

[0101] As indicated by reference number 615, based at least in part on information relating to one or more NTN SIBs in the SIB (e.g., in SIB1), the NTN entity 605 may transmit one or more NTN SIBs, which the UE 120 may receive. For example, the UE 120 may receive one or more NTN SIBs according to the indicated update periodicity (e.g., within an update period according to the update periodicity), according to one or more indicated transmission windows, according to the indicated resource allocation and / or MCS, etc. During each update period (e.g., without SI update notification paging), as described herein, 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 number 620, UE120 and NTN entity 605 may communicate at least partially based on one or more NTN SIBs. That is, UE120 and NTN entity 605 may communicate at least partially based on ephemeris information and / or feeder link timing advance information. For example, UE120 may communicate with NTN entity 605 using ephemeris information and / or feeder link timing advance information (for example, according to reference time, validity duration, and / or precision, as described herein).

[0096]

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

[0097]

[0104] Figure 7 shows an exemplary process 700 performed by, for example, a UE according to the present disclosure. The exemplary process 700 is an example in which a UE (e.g., UE120) performs operations related to NTN SIB broadcasting.

[0098]

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

[0099]

[0106] As further shown in Figure 7, in some embodiments, process 700 may include receiving one or more NTN SIBs from an NTN entity based at least partially on the information (block 720). For example, a UE (using, for example, the communications manager 140 and / or receiving component 902 shown in Figure 9) may receive one or more NTN SIBs from an NTN entity based at least partially on the information, as described above.

[0100]

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

[0101]

[0108] In the first embodiment, the information indicates at least one of the update periodicities of one or more NTN SIBs or one or more transmission windows within the update period of one or more NTN SIBs.

[0102]

[0109] In the second embodiment, either alone or in combination with the first embodiment, one or more transmit windows are for receiving PDCCH communications that schedule one or more NTN SIBs.

[0103]

[0110] In the third embodiment, one or more transmission windows, either alone or in combination with one or more of the first and second embodiments, are for receiving one or more NTN SIB PDSCH communications.

[0104]

[0111] In the fourth aspect, either 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 the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, one or more repetitions of one or more NTN SIBs within the renewal period are associated with the same reference time.

[0106]

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

[0107]

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

[0108]

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

[0109]

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

[0110]

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

[0111]

[0118] In the eleventh embodiment, either alone or in combination with one or more of the first to tenth embodiments, the information indicates the update periodicity of one or more NTN SIBs using SIB parameter types that are also used to indicate the periodicity of one or more non-NTN SIBs.

[0112]

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

[0113]

[0120] In the 13th aspect, either alone or in combination with one or more of the first to 12 aspects, the information includes identifiers indicating one or more of the following, according to a table: update periodicity of one or more NTN SIBs, one or more transmission windows within the update period of one or more NTN SIBs, time-domain resource allocation for one or more NTN SIBs, frequency-domain resource allocation for one or more NTN SIBs, MCS, or message size of one or more NTN SIBs.

[0114]

[0121] In the 14th embodiment, one or more NTN SIBs, either alone or in combination with one or more of the first to 13 embodiments, include a single NTN SIB that includes ephemeris information and feeder link timing advance information.

[0115]

[0122] In the 15th aspect, either alone or in combination with one or more of the first to 14th 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 effective duration or a first precision of the ephemeris information and at least one of a second effective duration or a second precision of the feeder link timing advance information.

[0116]

[0123] In the sixteenth aspect, either 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 the update periodicity of the feeder link timing advance information is at least partially based on the update periodicity of the ephemeris information.

[0117]

[0124] In the 17th embodiment, one or more NTN SIBs, either alone or in combination with one or more of the first to 16th embodiments, include multiple NTN SIBs, each containing ephemeris information and feeder link timing advance information.

[0118]

[0125] In the 18th aspect, either alone or in combination with one or more of the 1st to 17th aspects, the information represents feeder link timing advance information, and the feeder link timing advance information represents a feeder link timing advance without timing drift.

[0119]

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

[0120]

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

[0121]

[0128] Figure 7 shows an exemplary block of process 700, but in some embodiments, process 700 may include additional blocks, fewer blocks, different blocks, or blocks configured differently from those shown in Figure 7. Additionally or alternatively, two or more blocks of process 700 may be executed in parallel.

[0122]

[0129] Figure 8 shows an exemplary process 800 as performed by, for example, an NTN entity, as described herein. The exemplary process 800 is an example in which an NTN entity (e.g., base station 110, satellite 320, satellite 340, gateway 350, etc.) performs operations related to broadcasting of the NTN SIB.

[0123]

[0130] As shown in Figure 8, in some embodiments, process 800 may include sending an SIB to the UE that contains information relating to one or more NTN SIBs, which will include at least one of ephemeris information or feeder link timing advance information (block 810). For example, an NTN entity (for example, using the communications manager 150 and / or transmission component 1004 shown in Figure 10) may send an SIB to the UE that contains information relating to one or more NTN SIBs, which will include at least one of ephemeris information or feeder link timing advance information, as described above.

[0124]

[0131] As further shown in Figure 8, in some embodiments, process 800 may include transmitting one or more NTN SIBs to the UE based at least partially on the information (block 820). For example, an NTN entity (for example, using the communications manager 150 and / or transmission component 1004 shown in Figure 10) may transmit one or more NTN SIBs to the UE based at least partially on the information, as described above.

[0125]

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

[0126]

[0133] In the first embodiment, the information indicates at least one of the update periodicities of one or more NTN SIBs or one or more transmission windows within the update period of one or more NTN SIBs.

[0127]

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

[0128]

[0135] In the third embodiment, one or more transmission windows, either alone or in combination with one or more of the first and second embodiments, are for the transmission of one or more NTN SIB PDSCH communications.

[0129]

[0136] In the fourth aspect, either 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 the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, one or more repetitions of one or more NTN SIBs within the renewal period are associated with the same reference time.

[0131]

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

[0132]

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

[0133]

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

[0134]

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

[0135]

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

[0136]

[0143] In the eleventh embodiment, either alone or in combination with one or more of the first to tenth embodiments, the information indicates the update periodicity of one or more NTN SIBs using SIB parameter types that are also used to indicate the periodicity of one or more non-NTN SIBs.

[0137]

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

[0138]

[0145] In the 13th aspect, either alone or in combination with one or more of the first to 12 aspects, the information includes identifiers indicating one or more of the following, according to a table: update periodicity of one or more NTN SIBs, one or more transmission windows within the update period of one or more NTN SIBs, time-domain resource allocation for one or more NTN SIBs, frequency-domain resource allocation for one or more NTN SIBs, MCS, or message size of one or more NTN SIBs.

[0139]

[0146] In the 14th embodiment, one or more NTN SIBs, either alone or in combination with one or more of the first to 13 embodiments, include a single NTN SIB that includes ephemeris information and feeder link timing advance information.

[0140]

[0147] In the 15th aspect, either alone or in combination with one or more of the first to 14th 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 effective duration or a first precision of the ephemeris information and at least one of a second effective duration or a second precision of the feeder link timing advance information.

[0141]

[0148] In the sixteenth aspect, either 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 the update periodicity of the feeder link timing advance information is at least partially based on the update periodicity of the ephemeris information.

[0142]

[0149] In the 17th embodiment, one or more NTN SIBs, either alone or in combination with one or more of the first to 16th embodiments, include multiple NTN SIBs, each containing ephemeris information and feeder link timing advance information.

[0143]

[0150] In the 18th aspect, either alone or in combination with one or more of the 1st to 17th aspects, the information represents feeder link timing advance information, and the feeder link timing advance information represents a feeder link timing advance without timing drift.

[0144]

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

[0145]

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

[0146]

[0153] Figure 8 shows an exemplary block of process 800, but in some embodiments, process 800 may include additional blocks, fewer blocks, different blocks, or blocks configured differently from those shown in Figure 8. Additional or alternative, two or more blocks of process 800 may be executed in parallel.

[0147]

[0154] Figure 9 shows an exemplary apparatus 900 for wireless communication. Apparatus 900 may be a UE, or a UE may include apparatus 900. In some embodiments, apparatus 900 includes a receiving component 902 and a transmitting component 904, which may communicate with each other (for example, via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, base station, or another wireless communication device) using the receiving component 902 and the transmitting component 904. Further as shown, 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 embodiments, the apparatus 900 may be configured to perform one or more operations described herein with respect to Figure 6. Alternatively, the apparatus 900 may be configured to perform one or more processes, or combinations thereof, described herein, such as process 700 in Figure 7. In some embodiments, the apparatus 900 and / or one or more components shown in Figure 9 may include one or more components of the UE described with respect to Figure 2. Alternatively, one or more components shown in Figure 9 may be implemented within one or more components described with respect to Figure 2. Alternatively, one or more components of a set of components may be implemented, at least partially, as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-temporary 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 from the device 906, such as reference signals, control information, data communications, or combinations thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some embodiments, the receiving component 902 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) and provide the processed signals to one or more other components of the device 900. In some embodiments, the receiving component 902 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or combinations thereof of the UE described with respect to Figure 2.

[0150]

[0157] The transmitting component 904 may transmit communications to the device 906, such as reference signals, control information, data communications, or a combination thereof. In some embodiments, one or more other components of the device 900 may generate communications and provide the transmitted component 904 with the generated communications for transmission to the device 906. In some embodiments, the transmitting component 904 may perform signal processing on the generated communications (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 906. In some embodiments, the transmitting component 904 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or a combination thereof, as described with respect to Figure 2. In some embodiments, the transmitting component 904 may be collated with the receiving component 902 in the transceiver.

[0151]

[0158] The receiving component 902 may receive an SIB from an NTN entity (e.g., device 906) that contains information relating to one or more NTN SIBs, which 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 an NTN entity based at least partially on the information. The receiving component 902 and / or the transmitting component 904 may communicate with an NTN entity based at least partially on one or more NTN SIBs. The SI component 908 may process, store, apply, etc., the SI (e.g., ephemeris information and / or feeder link timing advance information) in one or more NTN SIBs.

[0152]

[0159] In some examples, the means for transmitting, outputting, or sending (or for outputting for transmission) may include one or more antennas, modulators, transmit MIMO processors, transmit processors, or combinations thereof of the UE described above with respect to Figure 2.

[0153]

[0160] In some examples, the means for receiving (or acquiring) may include one or more antennas, demodulators, MIMO detectors, receiving processors, or combinations thereof of the UE described above with respect to Figure 2.

[0154]

[0161] In some cases, rather than actually transmitting signals and / or data, a device may have an interface (means for outputting) for outputting 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 receiving) for acquiring 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 via a bus interface for reception. In various embodiments, the RF front end may include various components, such as transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc., as shown in the example in Figure 2.

[0155]

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

[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 from 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 (one or more) 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] Figure 10 shows an exemplary apparatus 1000 for wireless communication. Apparatus 1000 may be a base station or another NTN entity, or a base station or another NTN entity may include apparatus 1000. In some embodiments, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004, which may communicate with each other (for example, via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, base station, or another wireless communication device) using the receiving component 1002 and the transmitting component 1004. Furthermore, as shown, 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 embodiments, the device 1000 may be configured to perform one or more operations described herein with respect to Figure 6. Alternatively, the device 1000 may be configured to perform one or more processes, or combinations thereof, described herein, such as process 800 in Figure 8. In some embodiments, the device 1000 and / or one or more components shown in Figure 10 may include one or more components of the base station described with respect to Figure 2. Alternatively, one or more components shown in Figure 10 may be implemented within one or more components described with respect to Figure 2. Alternatively, one or more components of a set of components may be implemented, at least partially, as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-temporary 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 from the device 1006, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some embodiments, the receiving component 1002 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) and provide the processed signals to one or more other components of the device 1000. In some embodiments, the receiving component 1002 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof, of the base station described with respect to Figure 2.

[0160]

[0167] The transmitting component 1004 may transmit communications to the device 1006, such as reference signals, control information, data communications, or a combination thereof. In some embodiments, one or more other components of the device 1000 may generate communications and provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some embodiments, the transmitting component 1004 may perform signal processing on the generated communications (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 1006. In some embodiments, the transmitting component 1004 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or a combination thereof, as described with respect to Figure 2. In some embodiments, the transmitting component 1004 may be collated with the receiving component 1002 in the transceiver.

[0161]

[0168] The transmitting component 1004 may transmit an SIB to the UE (e.g., device 1006) that represents information relating 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 one or more NTN SIBs to the UE based at least partially on the information. The receiving component 1002 and / or the transmitting component 1004 may communicate with the UE based at least partially on one or more NTN SIBs. The SI component 1008 may generate, process, store, etc., the SI (e.g., ephemeris information and / or feeder link timing advance information) of one or more NTN SIBs.

[0162]

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

[0163]

[0170] In some examples, the means for receiving (or acquiring) may include one or more antennas, demodulators, MIMO detectors, receiving processors, or combinations thereof, of the base station or another NTN entity described above with respect to Figure 2.

[0164]

[0171] In some cases, rather than actually transmitting signals and / or data, a device may have an interface (means for outputting) for outputting 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 receiving) for acquiring 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 via a bus interface for reception. In various embodiments, the RF front end may include various components, such as transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc., as shown in the example in Figure 2.

[0165]

[0172] In some examples, the means for determining, obtaining, or sending may include various processing system components such as receiving processors, transmitting processors, controllers / processors, memory, or combinations thereof, of the base station or another NTN entity described above with respect to Figure 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 from 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 (one or more) 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 an overview of some aspects of this disclosure.

[0168]

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

[0169]

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

[0170]

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

[0171]

[0178] Embodiment 4: The method of Embodiment 2, wherein one or more transmission windows are for receiving one or more NTN SIB physical downlink shared channel communications.

[0172]

[0179] Embodiment 5: Any method from Embodiments 1 to 4, wherein the default update periodicity of one or more NTN SIBs is the same as the periodicity of one or more non-NTN SIBs.

[0173]

[0180] Embodiment 6: Any method from Embodiments 1 to 5, wherein one or more repetitions of an NTN SIB among one or more NTN SIBs within the renewal period are associated with the same reference time.

[0174]

[0181] Embodiment 7: Any method of Embodiments 1 to 6, wherein at least one reference time among one or more NTN SIB ephemeris information or feeder link timing advance information is at least partially based on a specific downlink transmission time within the update period.

[0175]

[0182] Embodiment 8: Any method from Embodiments 1 to 7, wherein the information indicates at least one of the resource allocation or modulation and coding schemes for receiving one or more NTN SIBs.

[0176]

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

[0177]

[0184] Embodiment 10: Any method of Embodiments 8 to 9 wherein the information further indicates the message size of one or more NTN SIBs.

[0178]

[0185] Embodiment 11: A method in any of Embodiments 1 to 10, wherein the information indicates at least one of the effective duration or accuracy of one or more NTN SIBs.

[0179]

[0186] Embodiment 12: A method in any of Embodiments 1 or 5 to 11, wherein the information indicates the update periodicity of one or more NTN SIBs using SIB parameter types that are also used to indicate the periodicity of one or more non-NTN SIBs.

[0180]

[0187] Embodiment 13: Any method of Embodiments 1 to 11, wherein updating at least one of ephemeris information or feeder link timing advance information does not depend on triggering a system information update procedure.

[0181]

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

[0182]

[0189] Embodiment 15: The method according to any one of Embodiments 1 to 14, wherein one or more NTN SIBs include a single NTN SIB containing ephemeris information and feeder link timing advance information.

[0183]

[0190] Embodiment 16: The method of Embodiment 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 effective duration or a first precision of the ephemeris information and at least one of a second effective duration or a second precision of the feeder link timing advance information.

[0184]

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

[0185]

[0192] Embodiment 18: The method according to any one of Embodiments 1 to 14, wherein one or more NTN SIBs include ephemeris information and feeder link timing advance information, respectively.

[0186]

[0193] Embodiment 19: Any method according to Embodiments 1 to 14, wherein the information indicates feeder link timing advance information, and the feeder link timing advance information indicates a feeder link timing advance without timing drift.

[0187]

[0194] Embodiment 20: The method according to any one of Embodiments 1 to 15 or 17 to 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 the update periodicity of the feeder link timing advance information or the update period of the feeder link timing advance information.

[0188]

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

[0189]

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

[0190]

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

[0191]

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

[0192]

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

[0193]

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

[0194]

[0201] Embodiment 27: Any method of Embodiments 22 to 26, wherein one or more repetitions of an NTN SIB among one or more NTN SIBs within the renewal period are associated with the same reference time.

[0195]

[0202] Embodiment 28: Any method of Embodiments 22 to 27, wherein at least one reference time among one or more NTN SIB ephemeris information or feeder link timing advance information is at least partially based on a specific downlink transmission time within the update period.

[0196]

[0203] Embodiment 29: Any method of Embodiments 22 to 28, wherein the information indicates at least one of one resource allocation or modulation and coding schemes for receiving one or more NTN SIBs.

[0197]

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

[0198]

[0205] Embodiment 31: Any method of Embodiments 29 to 30 wherein the information further indicates the message size of one or more NTN SIBs.

[0199]

[0206] Embodiment 32: A method in any of Embodiments 22 to 31, wherein the information indicates at least one of the effective duration or accuracy of one or more NTN SIBs.

[0200]

[0207] Embodiment 33: A method of any of Embodiments 22 or 26-32, wherein the information indicates the update periodicity of one or more NTN SIBs using SIB parameter types that are also used to indicate the periodicity of one or more non-NTN SIBs.

[0201]

[0208] Embodiment 34: Any method of Embodiments 22 to 32, wherein updating at least one of ephemeris information or feeder link timing advance information does not depend on triggering a system information update procedure.

[0202]

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

[0203]

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

[0204]

[0211] Embodiment 37: The method of Embodiment 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 effective duration or a first precision of the ephemeris information and at least one of a second effective duration or a second precision of the feeder link timing advance information.

[0205]

[0212] Embodiment 38: The method of Embodiment 36, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and the update periodicity of the feeder link timing advance information is at least partially based on the update periodicity of the ephemeris information.

[0206]

[0213] Embodiment 39: The method according to any one of Embodiments 22 to 35, wherein one or more NTN SIBs include ephemeris information and feeder link timing advance information, respectively.

[0207]

[0214] Embodiment 40: Any method according to Embodiments 22 to 35, wherein the information indicates feeder link timing advance information, and the feeder link timing advance information indicates a feeder link timing advance without timing drift.

[0208]

[0215] Embodiment 41: The method according to any of Embodiments 22 to 36 or 38 to 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 the update periodicity of the feeder link timing advance information or the update period of the feeder link timing advance information.

[0209]

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

[0210]

[0217] Embodiment 43: A device for wireless communication, comprising a memory containing instructions and one or more processors configured to execute instructions and cause the device to implement one or more methods from Embodiments 1 to 21.

[0211]

[0218] Embodiment 44: A user device (UE) comprising at least one receiver, a memory having instructions, and one or more processors configured to execute instructions and cause the UE to implement one or more methods from Embodiments 1 to 21, wherein at least one receiver is configured to receive an SIB and one or more NTN SIBs.

[0212]

[0219] Embodiment 45: An apparatus for wireless communication comprising at least one means for carrying out one or more methods from Embodiments 1 to 21.

[0213]

[0220] Embodiment 46: A non-temporary computer-readable medium comprising one or more instructions that, when executed by one or more processors of the device, cause the device to perform one or more of the methods of Embodiments 1 to 21.

[0214]

[0221] Embodiment 47: A device for wireless communication, comprising a memory containing instructions and one or more processors configured to execute instructions and cause the device to implement one or more methods from Embodiments 22 to 42.

[0215]

[0222] Embodiment 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 instructions and cause the NTN entity to implement one or more methods of Embodiments 22 to 42, wherein at least one transmitter is configured to transmit an SIB and one or more NTN SIBs.

[0216]

[0223] Embodiment 49: An apparatus for wireless communication comprising at least one means for carrying out one or more methods from Embodiments 22 to 42.

[0217]

[0224] Embodiment 50: A non-temporary computer-readable medium comprising one or more instructions that, when executed by one or more processors of the device, cause the device to perform one or more of the methods of Embodiments 22 to 42.

[0218]

[0225] The above disclosures are illustrative and explanatory, but are not exhaustive, nor do they limit the embodiments to the exact forms disclosed. Modifications and variations may be made in light of the above disclosures or derived from the practice of the embodiments.

[0219]

[0226] As used herein, the term “components” is to be broadly interpreted as hardware, and / or combinations of hardware and software. “Software” should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, regardless of the names such as software, firmware, middleware, microcode, and hardware description languages, among others. As used herein, “processor” is implemented by hardware, and / or combinations of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in different forms of hardware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited in its form. Therefore, as those skilled in the art will understand, software and hardware can be designed to implement systems and / or methods based at least in part on the descriptions herein; thus, the operation and behavior of systems and / or methods are described herein without reference to specific software code.

[0220]

[0227] As used herein, "meeting a threshold" may mean, depending on the context, that a value is 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, or not equal to the threshold.

[0221]

[0228] Certain combinations of features are enumerated in the claims and / or disclosed herein, but these combinations do not limit the disclosure of various embodiments. Many of these features may be combined in ways not specifically enumerated in the claims and / or disclosed herein. Disclosure of various embodiments includes each dependent claim in combination with any other claims in the set of claims. The phrase “at least one of” the list of items used herein refers to any combination of those items, including a single member. For 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] Any element, action, or instruction used herein should not be construed as important or essential unless expressly stated otherwise. Furthermore, 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 referred to with the article “the” and may be used interchangeably with “one or more.” Furthermore, 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 words are used. Also, terms such as “has,” “have,” and “having” as used herein are open-ended terms that do not limit the elements they modify (for example, an element that “has” A may also have B). Furthermore, the phrase “based on” means “at least partially based on” unless otherwise specified. Furthermore, the term “or” as used herein is inclusive when used consecutively, and may be used interchangeably with “and / or” unless otherwise specified (for example, when used in combination with “either” or “only one of”). The invention described in the original claims of this application is listed below. [C1] A device for wireless communication, Memory containing instructions, The command is executed, and the device is instructed to: Obtaining an SIB from an entity of a non-terrestrial network (NTN) that indicates information relating to one or more NTN system information blocks (SIBs) that will contain at least one of ephemeris information or feeder link timing advance information, Obtaining one or more NTN SIBs from the aforementioned NTN entities based at least partially on the aforementioned information. One or more processors configured to perform the following: A device equipped with the following features. [C2] The apparatus according to C1, wherein the information indicates at least one of the renewal periodicity of one or more NTN SIBs or one or more transmission windows within the renewal period of one or more NTN SIBs. [C3] The apparatus according to C2, wherein the one or more transmission windows are for receiving at least one of the following: physical downlink control channel communication scheduling the one or more NTN SIBs or physical downlink shared channel communication of the one or more NTN SIBs. [C4] The apparatus according to C1, wherein, during the renewal period, one or more repetitions of the NTN SIB among the one or more NTN SIBs are associated with the same reference time. [C5] The apparatus according to C1, wherein the at least one reference time among the ephemeris information or feeder link timing advance information of one or more NTN SIBs is at least partially based on a specific downlink transmission time within the update period. [C6] The apparatus according to C1, wherein the information indicates at least one of the following: resource allocation for receiving the one or more NTN SIBs, modulation and coding scheme for receiving 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. [C7] The apparatus according to C1, wherein the information indicates the update periodicity of one or more NTN SIBs using the parameter type of the SIB, which is also used to indicate the periodicity of one or more non-NTN SIBs. [C8] The apparatus according to C1, wherein updating at least one of the ephemeris information or the feeder link timing advance information does not depend on triggering a system information update procedure. [C9] The apparatus according to C1, wherein the information indicates identifiers that, according to a table, represent one or more of the following: the update periodicity of the one or more NTN SIBs, one or more transmission windows within the update period of the one or more NTN SIBs, time-domain resource allocation for the one or more NTN SIBs, frequency-domain resource allocation for the one or more NTN SIBs, modulation and coding schemes, or message sizes of the one or more NTN SIBs. [C10] The apparatus according to C1, wherein one or more NTN SIBs include a single NTN SIB containing the ephemeris information and the feeder link timing advance information. [C11] The aforementioned feeder link timing advance information is, A feeder link timing advance with timing drift, wherein the information indicates at least one of a first effective duration or a first precision of the ephemeris information and at least one of a second effective duration or a second precision of the feeder link timing advance information, or A feeder link timing advance without timing drift, wherein the update periodicity of the feeder link timing advance information is at least partially based on the update periodicity of the ephemeris information. The apparatus described in C10, which represents one of the following. [C12] The apparatus according to C1, wherein the aforementioned information indicates feeder link timing advance information, and the feeder link timing advance information indicates a feeder link timing advance without timing drift. [C13] The aforementioned feeder link timing advance information indicates a feeder link timing advance without timing drift. The information indicates at least one of the update periodicity of the feeder link timing advance information or the update period of the feeder link timing advance information. The apparatus described in C1. [C14] The aforementioned feeder link timing advance information indicates a feeder link timing advance without timing drift. The application time of the feeder link timing advance information is at least partially based on the last slot number of the first physical downlink shared channel communication of one or more NTN SIBs or the last slot number of the first transmission window during the update period and a system scheduling offset value. The apparatus described in C1. [C15] The apparatus further comprises a receiver configured to receive the aforementioned SIB and one or more NTN SIBs, wherein the apparatus is configured as a UE. The apparatus described in C1. [C16] A device for wireless communication, Memory containing instructions, The command is executed, and the device is instructed to: To output an SIB that shows information relating to one or more non-terrestrial network (NTN) system information blocks (SIBs) that will include at least one of ephemeris information or feeder link timing advance information for transmission to user equipment (UE), For transmission to the aforementioned UE, output one or more NTN SIBs based at least partially on the aforementioned information. One or more processors configured to perform the following: A device equipped with the following features. [C17] The apparatus according to C16, wherein the information indicates at least one of the renewal periodicity of one or more NTN SIBs or one or more transmission windows within the renewal period of one or more NTN SIBs. [C18] The apparatus according to C16, wherein, during the renewal period, one or more repetitions of the NTN SIB among the one or more NTN SIBs are associated with the same reference time. [C19] The apparatus according to C16, wherein the at least one reference time among the ephemeris information or feeder link timing advance information of one or more NTN SIBs is at least partially based on a specific downlink transmission time within the update period. [C20] The apparatus according to C16, wherein the information indicates at least one of the resource allocation or modulation and coding schemes for receiving one or more NTN SIBs. [C21] The apparatus according to C16, wherein the information indicates the update periodicity of one or more NTN SIBs using the parameter type of the SIB, which is also used to indicate the periodicity of one or more non-NTN SIBs. [C22] The apparatus according to C16, wherein updating at least one of the ephemeris information or the feeder link timing advance information does not depend on triggering a system information update procedure. [C23] The apparatus according to C16, wherein the one or more NTN SIBs include a single NTN SIB that includes the ephemeris information and the feeder link timing advance information. [C24] The apparatus according to C16, wherein the information indicates feeder link timing advance information, and the feeder link timing advance information indicates a feeder link timing advance without timing drift. [C25] The aforementioned feeder link timing advance information indicates a feeder link timing advance without timing drift. The information indicates at least one of the update periodicity of the feeder link timing advance information or the update period of the feeder link timing advance information. The apparatus described in C16. [C26] The aforementioned feeder link timing advance information indicates a feeder link timing advance without timing drift. The application time of the feeder link timing advance information is at least partially based on the last slot number of the first physical downlink shared channel communication of one or more NTN SIBs or the last slot number of the first transmission window during the update period and a system scheduling offset value. The apparatus described in C16. [C27] The apparatus further comprises a transmitter configured to transmit the SIB and one or more NTN SIBs, wherein the apparatus is configured as an entity of NTN. The apparatus described in C16. [C28] A method for wireless communication in user equipment (UE), Obtaining an SIB from an entity of a non-terrestrial network (NTN) that indicates information relating to one or more NTN system information blocks (SIBs) that will contain at least one of ephemeris information or feeder link timing advance information, Obtaining one or more NTN SIBs from the aforementioned NTN entities based at least partially on the aforementioned information. A method that includes [a certain feature]. [C29] The method according to C28, wherein the at least one reference time among the ephemeris information or feeder link timing advance information of one or more NTN SIBs is at least partially based on a specific downlink transmission time within the update period. [C30] The method according to C28, wherein the update of at least one of the ephemeris information or the feeder link timing advance information does not depend on triggering a system information update procedure.

Claims

1. A device for wireless communication, At least one transceiver, One or more memories containing instructions, The command is executed, and the device is instructed to: Receiving an SIB via the at least one transceiver that indicates information relating to one or more non-terrestrial network (NTN) system information blocks (SIBs), wherein the information indicates at least one of the following: resource allocation for acquiring the one or more NTN SIBs, modulation and coding scheme 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 precision of the one or more NTN SIBs. The system receives one or more NTN SIBs based on the information via the at least one transceiver, and the one or more NTN SIBs include at least one of ephemeris information or feeder link timing advance information. Communicating with one or more entities of NTN based on one or more NTN SIBs via the at least one transceiver, and herein, The reference time for at least one of the ephemeris information or the feeder link timing advance information is based on a specific downlink transmission time. One or more processors configured to perform the following: A device equipped with the following features.

2. A device for wireless communication, At least one transceiver, One or more memories containing instructions, The command is executed, and the device is instructed to: Receiving an SIB via the at least one transceiver that indicates information relating to one or more non-terrestrial network (NTN) system information blocks (SIBs), wherein the information indicates at least one of the following: resource allocation for acquiring the one or more NTN SIBs, modulation and coding scheme 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 precision of the one or more NTN SIBs. The system receives one or more NTN SIBs based on the information via the at least one transceiver, and the one or more NTN SIBs include at least one of ephemeris information or feeder link timing advance information. Communicating with one or more entities of NTN based on one or more NTN SIBs via the at least one transceiver, and herein, The update of at least one of the ephemeris information or the feeder link timing advance information does not depend on triggering a system information update procedure. One or more processors configured to perform the following: A device equipped with the following features.

3. A device for wireless communication, At least one transceiver, One or more memories containing instructions, The command is executed, and the device is instructed to: Receiving an SIB via the at least one transceiver that indicates information relating to one or more non-terrestrial network (NTN) system information blocks (SIBs), wherein the information indicates at least one of the following: resource allocation for acquiring the one or more NTN SIBs, modulation and coding scheme 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 precision of the one or more NTN SIBs. The system receives one or more NTN SIBs based on the information via the at least one transceiver, and the one or more NTN SIBs include at least one of ephemeris information or feeder link timing advance information. Communicating with one or more entities of NTN based on one or more NTN SIBs via the at least one transceiver, and herein, The one or more NTN SIBs include a single NTN SIB that includes the ephemeris information and the feeder link timing advance information. One or more processors configured to perform the following: A device equipped with the following features.

4. The apparatus according to claim 1, wherein the reference time for the ephemeris information is based on a specific downlink transmission time.

5. The apparatus according to claim 1, wherein the reference time for the feeder link timing advance information is based on a specific downlink transmission time.

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

7. The apparatus according to claim 1, wherein the one or more NTN SIBs include a single NTN SIB containing the ephemeris information and the feeder link timing advance information.

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

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

10. The apparatus according to claim 1, wherein the information relating to one or more NTN SIBs indicates the feeder link timing advance information, and the feeder link timing advance information indicates a feeder link timing advance without timing drift.

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

12. One or more devices for wireless communication, One or more memories containing instructions, The command is executed, and the one or more devices are: Outputting an SIB indicating information relating to one or more non-terrestrial network (NTN) system information blocks (SIBs) for transmission to a user equipment (UE), wherein the information indicates at least one of the following: resource allocation for acquiring the one or more NTN SIBs, modulation and coding scheme 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 precision of the one or more NTN SIBs. For transmission to the UE, output one or more NTN SIBs based on the information, and each of the one or more NTN SIBs includes at least one of ephemeris information or feeder link timing advance information. To communicate with the UE based on the aforementioned one or more NTN SIBs, and herein, The reference time for at least one of the ephemeris information or the feeder link timing advance information is based on a specific downlink transmission time. One or more processors configured to perform the following: One or more devices comprising:

13. One or more devices for wireless communication, One or more memories containing instructions, The command is executed, and the one or more devices are: Outputting an SIB indicating information relating to one or more non-terrestrial network (NTN) system information blocks (SIBs) for transmission to a user equipment (UE), wherein the information indicates at least one of the following: resource allocation for acquiring the one or more NTN SIBs, modulation and coding scheme 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 precision of the one or more NTN SIBs. For transmission to the UE, output one or more NTN SIBs based on the information, and each of the one or more NTN SIBs includes at least one of ephemeris information or feeder link timing advance information. To communicate with the UE based on the aforementioned one or more NTN SIBs, and herein, The update of at least one of the ephemeris information or the feeder link timing advance information does not depend on triggering a system information update procedure. One or more processors configured to perform the following: One or more devices comprising:

14. One or more devices for wireless communication, One or more memories containing instructions, The command is executed, and the one or more devices are: Outputting an SIB indicating information relating to one or more non-terrestrial network (NTN) system information blocks (SIBs) for transmission to a user equipment (UE), wherein the information indicates at least one of the following: resource allocation for acquiring the one or more NTN SIBs, modulation and coding scheme 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 precision of the one or more NTN SIBs. For transmission to the UE, output one or more NTN SIBs based on the information, and each of the one or more NTN SIBs includes at least one of ephemeris information or feeder link timing advance information. To communicate with the UE based on the aforementioned one or more NTN SIBs, and herein, The one or more NTN SIBs include a single NTN SIB that includes the ephemeris information and the feeder link timing advance information. One or more processors configured to perform the following: One or more devices comprising:

15. One or more devices according to claim 12, wherein the reference time for the ephemeris information is based on the specific downlink transmission time.

16. One or more devices according to claim 12, wherein the reference time of the feeder link timing advance information is based on the specific downlink transmission time.

17. One or more devices according to claim 13, wherein the update of at least one of the ephemeris information or the feeder link timing advance information does not depend on triggering the system information update procedure.

18. The one or more apparatus according to claim 12, wherein the one or more NTN SIBs include a single NTN SIB that includes the ephemeris information and the feeder link timing advance information.

19. One or more devices according to claim 12, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift.

20. The one or more apparatus according to claim 12, wherein the information relating to one or more NTN SIBs indicates the feeder link timing advance information, and the feeder link timing advance information indicates a feeder link timing advance without timing drift.

21. One or more transmitters configured to transmit the SIB and one or more NTN SIBs, wherein the one or more devices are configured as one or more entities of NTN One or more devices according to claim 12, further comprising:

22. A method of wireless communication using user equipment (UE), Receiving an SIB that indicates information relating to one or more non-terrestrial network (NTN) system information blocks (SIBs), wherein the information indicates at least one of the following: resource allocation for acquiring the one or more NTN SIBs, modulation and coding scheme 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 precision of the one or more NTN SIBs. Based on the aforementioned information, one or more NTN SIBs are received, and each of the one or more NTN SIBs includes at least one of ephemeris information or feeder link timing advance information. To communicate with NTN based on the aforementioned one or more NTN SIBs, and herein, The reference time for at least one of the ephemeris information or the feeder link timing advance information is based on a specific downlink transmission time. A method that includes [a certain feature].

23. A method of wireless communication using user equipment (UE), Receiving an SIB that indicates information relating to one or more non-terrestrial network (NTN) system information blocks (SIBs), wherein the information indicates at least one of the following: resource allocation for acquiring the one or more NTN SIBs, modulation and coding scheme 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 precision of the one or more NTN SIBs. Based on the aforementioned information, one or more NTN SIBs are received, and each of the one or more NTN SIBs includes at least one of ephemeris information or feeder link timing advance information. To communicate with NTN based on the aforementioned one or more NTN SIBs, and herein, The update of at least one of the ephemeris information or the feeder link timing advance information does not depend on triggering a system information update procedure. A method that includes [a certain feature].

24. A method of wireless communication using user equipment (UE), Receiving an SIB that indicates information relating to one or more non-terrestrial network (NTN) system information blocks (SIBs), wherein the information indicates at least one of the following: resource allocation for acquiring the one or more NTN SIBs, modulation and coding scheme 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 precision of the one or more NTN SIBs. Based on the aforementioned information, one or more NTN SIBs are received, and each of the one or more NTN SIBs includes at least one of ephemeris information or feeder link timing advance information. To communicate with NTN based on the aforementioned one or more NTN SIBs, and herein, The one or more NTN SIBs include a single NTN SIB that includes the ephemeris information and the feeder link timing advance information. A method that includes [a certain feature].

Images