Broadcast of non-terrestrial network system information blocks
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- QUALCOMM INC
- Filing Date
- 2022-06-16
- Publication Date
- 2026-08-07
Smart Images

Figure CN117643115B_ABST
Abstract
Description
[0001] Cross-references to related applications
[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 203,961, filed August 5, 2021, entitled “BROADCASTING OF A NON-TERRESTRIAL NETWORK SYSTEM INFORMATION BLOCK,” and U.S. Non-Provisional Patent Application No. 17 / 661,996, filed May 4, 2022, entitled “BROADCASTING OF A NON-TERRESTRIAL NETWORK SYSTEM INFORMATION BLOCK,” which are hereby expressly incorporated herein by reference. Technical Field
[0003] Various aspects of this disclosure generally relate to technologies and apparatus for wireless communication and broadcasting of information blocks (SIBs) for non-terrestrial network (NTN) systems. Background Technology
[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).
[0005] 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 communication. "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.
[0006] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is a collection of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention
[0007] Some aspects described herein relate to a method for conducting wireless communication at a user equipment (UE). This method may include receiving a System Information Block (SIB) from an entity of a non-terrestrial network (NTN), the SIB indicating information relating to one or more NTN SIBs that 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 the NTN entity based at least in part on this information.
[0008] Some aspects described herein relate to a method for conducting wireless communication at an entity of an NTN. This method may include sending an SIB to a UE, the SIB indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information. The method may include sending one or more NTN SIBs to the UE based at least in part on this information.
[0009] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: a memory including instructions; and one or more processors configured to execute the instructions. The one or more processors may be configured to execute the instructions and cause the apparatus to obtain an SIB from an NTN entity, the SIB indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information. The one or more processors may be configured to execute the instructions and cause the apparatus to obtain one or more NTN SIBs from the NTN entity at least in part based on the information.
[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: a memory including instructions; and one or more processors configured to execute the instructions. The one or more processors may be configured to execute the instructions and cause the apparatus to output an SIB for transmission to a UE, the SIB indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information. The one or more processors may be configured to execute the instructions and cause the apparatus to output one or more NTN SIBs for transmission to the UE, at least in part based on the information.
[0011] Some aspects described herein relate to a non-transitory computer-readable medium including instructions. When executed by one or more processors of the device, the instructions cause the device to obtain an SIB from an entity of an NTN, the SIB indicating information relating to one or more NTN SIBs that include at least one of ephemeris information or feeder link timing advance information. When executed by one or more processors of the device, the instructions cause the device to obtain one or more NTN SIBs from an entity of the NTN at least in part based on this information.
[0012] Some aspects described herein relate to a non-transitory computer-readable medium including instructions. When executed by one or more processors of the device, the instructions cause the device to output an SIB for transmission to a UE, the SIB indicating information relating to one or more NTN SIBs that include at least one of ephemeris information or feeder link timing advance information. When executed by one or more processors of the device, the instructions cause the device to output one or more NTN SIBs for transmission to a UE, at least in part, based on this information.
[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for obtaining an SIB from an entity of an NTN, the SIB indicating information relating to one or more NTN SIBs, including at least one of ephemeris information or feeder link timing advance information. The apparatus may include components for obtaining one or more NTN SIBs from an entity of the NTN, at least in part, based on this information.
[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for outputting an SIB for transmission to a UE, the SIB indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information. The apparatus may include components for outputting one or more NTN SIBs for transmission to a UE, at least in part based on this information.
[0015] The aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems, as fully described herein with reference to the accompanying drawings and description, and as shown in the accompanying drawings and description.
[0016] The features and technical advantages of the examples according to this disclosure have been summarized quite extensively above to better understand the specific embodiments described below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not as a limitation of the claims.
[0017] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects may be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / procurement equipment, medical devices, and / or artificial intelligence devices). Aspects 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 described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers) for analog and digital purposes. The aspects described herein can be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes, and configurations. Attached Figure Description
[0018] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly outlined above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not intended to limit its scope, as the specification may acknowledge other equally valid aspects. The same reference numerals in different drawings may identify the same or similar elements.
[0019] Figure 1 This is a diagram illustrating an example of a wireless network according to this disclosure.
[0020] Figure 2 This is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.
[0021] Figure 3 The diagram illustrates examples of regenerative satellite deployment and transparent satellite deployment in a non-terrestrial network (NTN) according to this disclosure.
[0022] Figure 4 This is a diagram illustrating an example of system information scheduling according to this disclosure.
[0023] Figure 5 This is a diagram illustrating an example of the transmission of the NTN Private System Information Block (SIB) according to this disclosure.
[0024] Figure 6 This is a diagram illustrating an example of a broadcast associated with NTN SIB according to this disclosure.
[0025] Figures 7 to 8 This is a diagram illustrating an example process associated with broadcasting NTN SIB according to this disclosure.
[0026] Figures 9 to 10 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation
[0027] The various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of the disclosure herein, whether implemented independently or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods practiced using structures, functions, or structures and functions other than or different from the aspects of the disclosure set forth herein. It should be understood that any aspect of this disclosure herein may be embodied by one or more elements of the claims.
[0028] Several aspects of a telecommunications system will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed embodiments and are illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0029] Although the aspects may be described herein using terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT), the aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G).
[0030] Figure 1 This is a diagram illustrating an example of a wireless network 100 according to this disclosure. 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, as well as other examples. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. Base station 110 is the entity that communicates with UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a Transmit / Receive Point (TRP). Each base station 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term “cell” can refer to the coverage area of base station 110 and / or the base station subsystem serving that coverage area.
[0031] Base station 110 can provide communication coverage for macro cells, pico cells, femtocells, and / or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femtocell can cover a relatively small geographic area (e.g., a home) and can allow restricted access by UE 120 associated with a femtocell (e.g., UE 120 in a Closed User Group (CSG)). Base station 110 for macro cells can be referred to as a macro base station. Base station 110 for pico cells can be referred to as a pico base station. Base station 110 for femtocells can be referred to as a femtocell or a home base station. Figure 1 In the example shown, BS110a can be a macro base station for macro cell 102a, BS110b can be a pico base station for pico cell 102b, and BS110c can be a femto base station for femto cell 102c. A base station can support one or more (e.g., three) cells.
[0032] In some examples, the cell may not necessarily be stationary, and the geographical area of the cell may move depending on the location of a mobile base station 110 (e.g., a mobile base station). In some examples, base stations 110 may interconnect with each other and / or interconnect to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 using any suitable transmitting network through various types of backhaul interfaces (such as direct physical connections or virtual networks).
[0033] In some aspects, such as Figure 1 As shown, the cell can be provided by a non-terrestrial network base station 110. As used herein, "non-terrestrial network" (NTN) can refer to a network accessed by non-terrestrial base stations, such as base stations carried by NTN entities (e.g., satellites, balloons, airships, aircraft, unmanned aerial vehicles, high-altitude platform stations). NTN base stations can be base stations carried by NTN entities (regenerative deployments) or terrestrial base stations communicating via NTN entities (bent-pipe or transparent deployments).
[0034] Wireless network 100 may include one or more relay stations. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., base station 110 or UE 120) and transmitting data to a downstream station (e.g., UE 120 or base station 110). A relay station may be a UE 120 capable of relaying transmissions for other UEs 120. Figure 1In the example shown, BS110d (e.g., a relay base station) can communicate with BS110a (e.g., a macro base station) and UE 120d to facilitate communication between BS110a and UE 120d. The base station 110 for relay communication may be referred to as a relay station, relay base station, relay, etc.
[0035] Wireless network 100 can be a heterogeneous network, comprising different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 can have different transmit power levels, different coverage areas, and / or different effects on interference in wireless network 100. For example, macro base stations can have high transmit power levels (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations can have lower transmit power levels (e.g., 0.1 watts to 2 watts).
[0036] Network controller 130 may be coupled to or communicate with a set of base stations 110, and may provide coordination and control for these base stations 110. Network controller 130 may communicate with base stations 110 via a backhaul communication link. Base stations 110 may also communicate directly with each other, or indirectly via a wireless backhaul link or a wired backhaul link.
[0037] UE 120 can be distributed across the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, and / or any other suitable device configured to communicate via a wireless medium.
[0038] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (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 a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered client equipment. UEs 120 may be included within a housing that houses components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.
[0039] In summary, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency in a given geographical area can support a single RAT to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.
[0040] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as a medium to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.
[0041] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., by frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “below 6GHz” band in various documents and articles. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz-300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).
[0042] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands used for these IF bands as the frequency range name FR3 (7.125GHz-24.25GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to IF band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6GHz. For example, three higher operating bands have been designated as the frequency range names FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.
[0043] Considering the examples above, unless otherwise explicitly stated, it should be understood that the terms "below 6 GHz," etc., if used herein, can broadly refer to frequencies that can be below 6 GHz, within FR1, or may include intermediate frequency bands. Furthermore, unless otherwise explicitly stated, it should be understood that the terms "millimeter wave," etc., if used herein, can broadly refer to frequencies that may include intermediate frequency bands, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or within the EHF band. It is considered that frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.
[0044] In some respects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may obtain a System Information Block (SIB) from an entity of the NTN, the System Information Block (SIB) indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information; and obtain one or more NTN SIBs from the entity of the NTN at least in part based on that information. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.
[0045] In some respects, base station 110 or another NTN entity may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may output an SIB for transmission to the UE, the SIB indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information; and output one or more NTN SIBs for transmission to the UE based at least in part on such information. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.
[0046] As indicated above, Figure 1 Provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The descriptions are different.
[0047] Figure 2 This is a diagram illustrating an example 200 of communication between a base station 110 and a UE 120 in a wireless network 100 according to the present 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).
[0048] At base station 110, transmitting processor 220 can receive data from data source 212 intended for use with UE 120 (or a set of UEs 120). Transmitting processor 220 can select one or more modulation and coding schemes (MCS) for UE 120, at least in part, based on one or more Channel Quality Indicators (CQIs) received from UE 120. Base station 110 can process (e.g., encode and modulate) the data for UE 120, at least in part, based on the selected MCS(s) for UE 120, and can provide data symbols for UE 120. Transmitting processor 220 can process system information (e.g., for Semi-Static Resource Partition Information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling), and provide overhead symbols and control symbols. Transmitting processor 220 can generate reference symbols for reference signals (e.g., Cell-Specific Reference Signal (CRS) or Demodulation Reference Signal (DMRS)) and synchronization signals (e.g., Primary Synchronization Signal (PSS) or Secondary Synchronization Signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of corresponding modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can further use a corresponding modulator component to process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) to obtain a downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) via a set of corresponding antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).
[0049] At UE 120, an array of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from base station 110 and / or other base stations 110 and can provide an array of received signals (e.g., R received signals) to an array of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each modem 254 can use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from modem 254, perform MIMO detection on these received symbols where applicable, and provide the detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide data for decoding of the UE 120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or CQI. In some examples, one or more components of the UE 120 may be included in the housing 284.
[0050] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.
[0051] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, an assembly of one or more antenna elements, and / or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, an assembly of one or more antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, an assembly of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), an assembly of coplanar antenna elements, an assembly of non-coplanar antenna elements, and / or be coupled to one or more transmitting and / or receiving components (such as...). Figure 2 One or more antenna elements (one or more components in a device).
[0052] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-encoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some examples, the modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modem(s) 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., references). Figures 6 to 10 ).
[0053] At base station 110, uplink signals from UE 120 and / or other UEs can be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232 shown as DEMOD), detected by MIMO detector 236 (where applicable), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and can communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communication. In some examples, modem 232 of base station 110 may include modulator and demodulator. In some examples, base station 110 includes transceiver. The transceiver may include any combination of antenna(s) 234, modem(s) 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., references). Figures 6 to 10 ).
[0054] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2 Any other component(s) within it can perform one or more techniques associated with broadcasting the NTN SIB, as described in more detail elsewhere herein. In some respects, the NTN entity described herein is Figure 2 The base station 110 shown is included in the base station 110, or includes one or more components of the base station 110. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component (or multiple components) within it can perform or direct, for example... Figure 7 The process 700 Figure 8 The operation of process 800 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly executed, or executed after compilation, transformation, and / or interpretation), these one or more instructions may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 7 The process 700 Figure 8 The operation of process 800 and / or other processes described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, among others.
[0055] In some aspects, UE 120 includes components for obtaining an SIB from an entity of the NTN, the SIB indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information; and / or components for obtaining one or more NTN SIBs from an entity of the NTN at least in part based on such information. Components for UE 120 to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.
[0056] In some aspects, base station 110 or another NTN entity includes components for outputting an SIB for transmission to a UE, the SIB indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information; and / or components for outputting one or more NTN SIBs for transmission to a UE based at least in part on the information. Components for base station 110 or another NTN entity to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.
[0057] Although Figure 2 The boxes in the diagram are shown as different components, but the functions described above for these boxes can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by controller / processor 280 or under the control of controller / processor 280.
[0058] As indicated above, Figure 2 Provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The descriptions are different.
[0059] Figure 3 The figure shows an example 300 of regenerative satellite deployment and an example 310 of transparent satellite deployment in NTN according to this disclosure.
[0060] Example 300 illustrates a regenerative satellite deployment. In Example 300, UE 120 is served by satellite 320 via serving link 330. For example, satellite 320 may include base station 110 (e.g., base station 110a) or gNB. In some aspects, satellite 320 may be referred to as a non-terrestrial base station, a regenerative repeater, or an onboard processing repeater. In some aspects, satellite 320 may demodulate uplink radio frequency signals and may modulate baseband signals derived from uplink radio signals to generate downlink radio frequency transmissions. Satellite 320 may transmit downlink radio frequency signals over serving link 330. Satellite 320 may provide cell coverage for UE 120.
[0061] Example 310 illustrates a transparent satellite deployment, which may also be referred to as a bend-tube satellite deployment. In Example 310, UE 120 is served by satellite 340 via serving 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 RF transmissions and may transmit downlink RF transmissions without demodulating the uplink RF transmissions. In some aspects, the satellite may convert the uplink RF transmission frequency received on serving link 330 to the uplink RF transmission frequency on feeder link 360, and may amplify and / or filter the uplink RF transmissions. In some aspects, UE 120 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 capabilities. Satellite 340 may provide cell coverage for UE 120.
[0062] Service link 330 may include a link between satellite 340 and UE 120, 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 UE 120 to gateway 350) or downlinks (e.g., from gateway 350 to UE 120). The uplink of service link 330 may be designated by reference numeral 330-U. Figure 3 (not shown in the figure) indicates, and the downlink of serving link 330 can be indicated by reference numeral 330-D ( Figure 3 (Not shown in the figure). Similarly, the uplink of feeder link 360 can be indicated by the reference numeral 360-U (…). Figure 3 (not shown in the figure) indicates, and the downlink of feeder link 360 can be indicated by the figure mark 360-D ( Figure 3 (Not shown in the text) Instructions.
[0063] Due to the movement of satellites 320 and 340 and the potential movement of UE 120, feeder link 360 and service link 330 may each experience Doppler effects. These Doppler effects may be significantly greater than those in terrestrial networks. The Doppler effects on feeder link 360 can be compensated for to some extent, but may still be associated with a certain amount of uncompensated frequency error. Furthermore, gateway 350 may be associated with residual frequency errors, and / or satellites 320 / 340 may be associated with onboard frequency errors. These sources of frequency errors may cause the downlink frequency received at UE 120 to deviate from the target downlink frequency.
[0064] As indicated above, Figure 3 Provided as an example. Other examples are available with reference to [the relevant information]. Figure 3The descriptions are different.
[0065] Figure 4 This is a diagram illustrating an example 400 of system information scheduling according to this disclosure.
[0066] A base station can provide System Information (SI) to the UEs it covers. SI may include physical layer information (e.g., in a main information block), access information (e.g., in SIB type 1 (SIB1)), and / or other information for communication between the UE and the base station (e.g., in one or more other types of SIBs). One or more SIBs may be carried in an SI message. For example, SIB1 may be carried alone in an SI message, and one or more other SIBs may be carried in another SI message.
[0067] An SI message carrying SIB1 can be sent at a fixed time and 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 sent in non-overlapping scheduling windows (e.g., scheduling windows that do not overlap with each other or the window of SIB1). Therefore, when the UE receives downlink control information (DCI) identifying an SI message in the physical downlink control channel (PDCCH), the UE can know at least in part which SI message is being scheduled based on the scheduling window indicated by the scheduling information of SIB1.
[0068] The scheduling information in SIB1 can indicate the SI window length (e.g., si-WindowLength), which is a common parameter for SI messages. That is, the SI window length is the same for all scheduled SI messages. The SI window length defines the length of the SI window in which the UE can expect to send SIB messages (e.g., messages that can carry one or more SIBs). The UE can use a specific formula to determine the start time position of the SI window. Within the SI window, the UE can search the PDCCH (e.g., using the SI Radio Network Temporary Identifier (SI-RNTI) to perform decoding of control communications) to receive SI messages. The scheduling information in SIB1 can also indicate the SI periodicity (e.g., si-Periodicity) of each SI message, which identifies the time interval between consecutive SI windows (e.g., each SI message can have a separately configured SI periodicity).
[0069] Changes to the information in an SI message can only occur after the upcoming boundary of the SI modification cycle (unless the SI message is used for Earthquake and Tsunami Warning Systems (ETWS), Commercial Mobile Alarm Systems (CMAS), Location Assistance Data, SIB Type 9 (SIB9), etc.). Multiple SI windows can appear between SI modification boundaries for repeating or retransmitting SI messages (e.g., without changing the information in the SI message).
[0070] like Figure 4 As shown, the boundary of the SI modification period can be defined by the system frame number (SFN) value of SFN modm = 0, where m is the number of radio frames in the SI modification period. In some aspects, the value of m can be determined based on a configuration factor value (e.g., modificationPeriodCoeff) that can have values of 2, 4, 8, or 16, and a default paging period (e.g., PagingCycle) that can have values of 32, 64, 128, or 256 radio frames. For example, as shown, with a configuration factor value of two and a default paging period of 64 radio frames, the SI modification period can include 128 radio frames (e.g., corresponding to 1.28 seconds). Continuing this example, a new SIB1 can be obtained at SFN mod128 = 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 can obtain a new SIB1 after the SI modification period boundary. If the UE receives an SI update notification, it can receive SIB1 after the SI modification period to check for changes in SI scheduling information and / or value tag (e.g., valueTag) parameters. If the SIB1 stored by the UE is valid (i.e., no SIB1 change notification has been received), all other SIBs (e.g., those used for scheduling and / or content) can also be considered valid (e.g., unchanged).
[0071] like Figure 4 As shown, if three SI messages are scheduled, the SI period can include three non-overlapping SI windows. SIs can also be sent according to the UE's request; in this case, an SI window may exist, but SI messages are not broadcast. Within an SI window, an SI message can be sent once or multiple times. However, an SIB is only included in a single SI message, and an SIB is included at most once within an SI message.
[0072] As indicated above, Figure 4 Provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The descriptions are different.
[0073] Figure 5This is a diagram illustrating example 500 of the transmission of an NTN-specific SIB according to this disclosure. An NTN-specific SIB (which may be referred to herein as an NTN SIB) is an SIB that carries information for communication within the 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 a whole or part of a feeder link common to multiple UEs. An NTN SIB may be a new SIB type that can be indicated by the SIB type information parameter (e.g., SIB-TypeInfo) of SIB1.
[0074] like Figure 5 As shown, the SI window can have a length (w) of 160 time slots, and the NTN SIB can be the first of multiple scheduled SIBs (i.e., for the NTN SIB, n=1). The SI periodicity (T) can be configured to a value from 80 milliseconds (ms) to 5.12 seconds. Figure 5 As shown, the periodicity of the SI message including the NTN SIB can be 640ms (e.g., T = 64 radio frames). In other words, the NTN SIB can update ephemeris information and / or update feeder link timing advance information every 640ms. Therefore, as shown, the UE can obtain updated ephemeris information and / or feeder link timing advance information (e.g., updated NTN SIB) at SFN = 0, SFN = 64, or SFN = 128, etc. (e.g., the slot number (a) used to obtain the updated NTN SIB is represented as slot a = (n-1)wmod 10).
[0075] However, if the SI modification period is greater than 640ms (e.g., m = 128 radio frames, or 1.28 seconds, as shown in the figure), it is not possible to update the NTN SIB every 640ms in the current wireless network. Therefore, the network should be able to update the NTN SIB without notifying the UE (e.g., via an SI update notification paging message). In other words, the NTN SIB can be changed without altering the SI scheduling parameters or the version of SIB1 (e.g., systemInfoValueTag).
[0076] As indicated above, Figure 5 Provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The descriptions are different.
[0077] Ephemeris information can describe the trajectory of satellites in the NTN (e.g., ephemeris information may include parameters such as a reference time or so-called "epoch time," which specifies the time at which orbital parameters are acquired, Keplerian orbital parameters such as the square root of the semi-major axis, eccentricity and / or tilt angle, and / or perturbation parameters such as the mean difference in motion from calculated values, the rate of change of right ascension and / or tilt angle, and / or the magnitude of one or more sine or cosine harmonic correction terms, etc.). For example, ephemeris information can indicate a formula that the UE can use to predict the position of a satellite over time. The maximum modification period of ephemeris information can be from 10 seconds to 60 seconds, and the transmission period of ephemeris information can be less than one second (e.g., it can be determined at least in part based on the initial access delay). The UE can determine when to read 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.
[0078] Feed link timing advance information can indicate the timing advance to be used by the UE due to the delay associated with the feed link between the gateway and the NTN's satellites. Feed link timing advance information can indicate feed link timing advance without timing drift (e.g., timing advance value without considering timing drift over time) or feed link timing advance with timing drift (e.g., timing advance formula considering timing drift over time).
[0079] The modification periodicity of feeder link timing advance without timing drift can be greater than 20 seconds (e.g., assuming a 0.5ms granularity), and the transmission periodicity of feeder link timing advance without timing drift can be less than one second (e.g., it can be determined at least in part based on the initial access delay). For timing advance without timing drift, the UE can read the feeder link timing advance information before the effective time of the information (e.g., it can be delayed relative to the signaling time of the information). In some examples, for timing advance without timing drift, the feeder link timing advance information can indicate a formula that the UE can use to determine the timing advance, thereby reducing the UE's reading of the feeder link timing advance information (e.g., the formula can indicate an increase of one time slot every 30 seconds from the common offset).
[0080] The maximum modification periodicity of feeder link timing advance with timing drift can be 10 to 20 seconds in FR1, or 2 to 5 seconds in FR2, and the transmission periodicity of feeder link timing advance with timing drift can be less than one second (e.g., it can be determined at least in part based on the initial access delay). If a common timing advance offset is used (e.g., no timing drift), the UE can read the feeder link timing advance information immediately after the information update. Otherwise, if timing drift is used, the UE can delay reading the information for a period of time after the information update (however, beyond this period, the UE's prediction error may deteriorate rapidly).
[0081] As described above, the NTN SIB carrying ephemeris information and / or timing advance information (e.g., with timing drift) should be updated periodically. The periodicity of NTN SIB updates may be constrained by the need to update the reference time (e.g., epoch time), 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 latest time relative to message reception to reduce prediction errors (ephemeris predictions performed by the network may be more accurate than those performed by the UE due to the network's use of complex prediction models). In some examples, the reference time (e.g., epoch time) can be implicitly indicated to the UE to reduce signaling overhead. For example, the reference time may be based at least in part on the boundaries of downlink signaling (e.g., for the NTN SIB).
[0082] With ephemeris information updated via NTN SIB in each SI cycle, repetitions of NTN SIB can be transmitted within the SI cycle. Here, repetitions of NTN SIB within the SI cycle can be associated with the same reference time. That is, a single reference time can be used for each SI cycle. The network can predict the position and / or velocity of NTN satellites at the reference time (e.g., the time at the end of the first transmission slot within the period of satellite departure) based at least in part on the latest GNSS reads.
[0083] Therefore, in NTNs, some SI parameters are handled differently from those in terrestrial networks because the satellite's position needs to be updated periodically as its position changes relative to the ground. For example, ephemeris information is typically used exclusively in NTNs to describe the satellite's trajectory in the sky, and similar SI parameters do not exist in terrestrial networks. In another example, feeder link timing advance can also be based at least in part on the satellite's position, whereas timing advance used in terrestrial networks does not need to take into account satellite movement.
[0084] Generally, when one or more SI parameters are updated, the UE is usually notified via a paging message, and the UE is then expected to reacquire one or more SIBs to refresh those SI parameters. However, sending paging messages to notify the UE when SI parameters need to be updated can incur signaling overhead, which can be particularly problematic in NTNs because large propagation delays and / or satellite motion can cause frequent changes in SI parameters. Furthermore, SI parameters used in NTNs (such as ephemeris information and feeder link timing advance information) may need to be updated more frequently than allowed by the SI modification cycle. If such SI parameters are not updated at the necessary frequency, the UE may lose synchronization with the base station or satellite, and communications to or from the UE may fail.
[0085] In some of the techniques and apparatus described herein, scheduling information for NTN SIBs can be provided in the SIB (e.g., SIB1). In some aspects, the update cycle of the NTN SIB and the transmission window of the NTN SIB within the SI cycle can be indicated in the SIB1. In some aspects, the SIB1 may include an indication of the validity duration and / or accuracy of the NTN SIB. In some aspects, the SIB1 may include resource allocation and / or MCS for the NTN SIB to avoid the need to schedule the NTN SIB via the PDCCH.
[0086] The techniques described herein enable the updating of ephemeris information and / or feeder link timing advance information without triggering the SI update process via paging messages. For example, the UE can obtain updated ephemeris information and / or feeder link timing advance information based on scheduling information in SIB1, without needing to notify the UE via paging. In this way, signaling overhead is reduced. Furthermore, as mentioned above, the UE can receive resource allocations for the NTN SIB in SIB1 instead of via PDCCH, thereby further reducing signaling overhead.
[0087] Figure 6 This is a diagram illustrating example 600 associated with a broadcast of NTN SIB according to this disclosure. Figure 6 As shown, Example 600 includes communication between NTN entity 605 and UE 120. In some aspects, NTN entity 605 and UE 120 may be included in a wireless network (such as wireless network 100 (e.g., NTN)). In some aspects, NTN entity 605 may be an NTN base station 110, an NTN gateway 350, an NTN satellite 320, an NTN satellite 340, etc.
[0088] As indicated by reference numeral 610, NTN entity 605 may transmit an SIB indicating information relating to one or more NTN SIBs, and UE 120 may receive the SIB. As described herein, the NTN SIBs may include at least one of ephemeris information or feeder link timing advance information (e.g., timing advance with timing drift or timing advance without timing drift). In some aspects, the SIB indicating this information may also carry access information. For example, the SIB indicating this information may be SIB1.
[0089] In some aspects, information relating to one or more NTN SIBs may indicate the update periodicity of one or more NTN SIBs (e.g., for an SI message that includes one or more NTN SIBs) and / or may indicate one or more transmission windows (also referred to herein as scheduling windows or SI windows) within the update period of one or more NTN SIBs (e.g., for an SI message that includes one or more NTN SIBs). As described herein, the update periodicity may be an SI periodicity, ephemeris information, and / or feeder link timing advance information updated to that SI periodicity. As described herein, the update period may be an SI period, defined by the update periodicity and including one or more transmission windows for repeating or retransmitting one or more NTN SIBs (e.g., an SI message that includes one or more NTN SIBs). The SIB may indicate information relating to one or more NTN SIBs (e.g., update periodicity and / or transmission windows) separately (e.g., using different parameter types) from the information (e.g., update periodicity and / or transmission windows) indicated in the SIB relating to one or more non-NTN SIBs.
[0090] In the aspect where the PDCCH is used to schedule Physical Downlink Shared Channel (PDSCH) communication for (multiple) NTN SIBs, the transmission window can be used for PDCCH communication that is transmitted by NTN entity 605 and received by UE 120 to schedule PDSCH communication (e.g., the transmission window is used for PDCCH decoding). In the aspect where the PDCCH is not used, the transmission window can be used for PDSCH communication that is transmitted by NTN entity 605 and received by UE 120 for (multiple) NTN SIBs (e.g., PDSCH communication for ephemeris information and / or feeder link timing advance information).
[0091] In some respects, the default update periodicity of one or more NTN SIBs (e.g., used if no update periodicity is specified) can be the same as the periodicity (e.g., the default periodicity or the periodicity indicated in SIB1) of one or more non-NTN SIBs (e.g., SIB type 2 (SIB2), SIB type 3 (SIB3), etc.). In some respects, one or more repetitions of an NTN SIB within an update period can be associated with the same reference time (e.g., epoch time, etc.). For example, SI messages containing ephemeris information transmitted within a single update period can use the same reference time. However, different SIBs or information elements transmitted within an update period can be associated with different reference times.
[0092] In some respects, the reference time of (multiple) NTN SIBs (e.g., one or more repetitions of NTN SIBs associated with the same reference time) can be based at least in part on a specific downlink transmission time point within an update cycle (e.g., relative to a satellite). For example, the reference time of an SI message containing ephemeris information can be a specific downlink time point within an update cycle at the satellite of the NTN. The downlink transmission time point used for the reference time can be configured, specified, or otherwise provided to the UE 120 to provide an implicit indication of the reference time for the UE 120, as described herein. For example, if a transmission window is specified, the downlink transmission time point can be the end of the last downlink slot of the PDSCH carrying the NTNSIB (e.g., carrying ephemeris information and / or feeder link timing advance information) in the first transmission window of the update cycle at the satellite. For example, if no transmission window is specified, the downlink transmission time point can be the end of the first downlink slot of the update cycle at the satellite.
[0093] In some aspects, information relating to one or more NTN SIBs may indicate resource allocation and / or MCS for receiving the NTN SIBs(s) at UE 120. In this way, UE 120 may receive PDSCH communication of the NTN SIBs(s)(s) based at least in part on the resource allocation and / or MCS indicated in the information, and it is not necessary to use PDCCH to schedule PDSCH communication. The time-domain resource allocation of the resource allocation may be relative to (e.g., referenced to) the start of the transmission window of one or more NTN SIBs. In some aspects, information relating to one or more NTN SIBs may indicate the message size of the one or more NTN SIBs. For example, if the NTN SIBs can use variable message sizes, the information may include an indication of the message size.
[0094] In some aspects, information relating to one or more NTN SIBs may indicate the validity duration and / or accuracy of one or more NTN SIBs (e.g., with reference to a specific accuracy per subcarrier interval). The validity duration and / or accuracy may be indicated in units of update cycles (e.g., indicated as a multiplier of update cycles). In some aspects, this information may indicate a first validity duration and / or first accuracy of ephemeris information and a second validity duration and / or second accuracy of feeder link timing advance information.
[0095] In some respects, mechanisms such as those described herein for indicating scheduling information for one or more non-NTN SIBs (e.g., SIB2, SIB3, etc.) (e.g., the si-Periodicity parameter in SIB1) can also be used to indicate scheduling information for one or more NTN SIBs. For example, information relating to one or more NTN SIBs can be used to indicate the update periodicity of one or more NTN SIBs using a parameter type of the SIB (e.g., the si-Periodicity parameter type), which is also used to indicate the periodicity of one or more non-NTN SIBs. In other words, the update period of an NTN SIB can be defined in the same way as the SI period of another SIB (e.g., in SIB1). The update period can be small enough to accommodate the random access channel (RACH) delay. In some respects, one or more SI windows (e.g., a first SI window and a third SI window of the SI period) can be specified or defined for the transmission of an NTN SIB.
[0096] In some respects, information relating to one or more NTN SIBs can indicate the identifier of an entry in a table stored by the UE 120. This table (e.g., a lookup table) can identify various combinations of the NTN SIB's update periodicity, the transmission window within the NTN SIB's update period (e.g., the NTN SIB's PDCCH or PDSCH), the NTN SIB's time-domain resource allocation, the NTN SIB's frequency-domain resource allocation, the NTN SIB's MCS, and / or the NTN SIB's message size. Therefore, according to this table, the identifier can indicate a specific combination of the NTN SIB's update periodicity, the transmission window within the NTN SIB's update period, the NTN SIB's time-domain resource allocation, the NTN SIB's frequency-domain resource allocation, the NTN SIB's MCS, and / or the NTN SIB's message size.
[0097] In some aspects, one or more NTN SIBs may include a single NTN SIB that includes ephemeris information and feeder link timing advance information (e.g., the ephemeris information and feeder link timing advance information may be transmitted together in one NTN SIB). In other aspects, one or more NTN SIBs may include multiple NTN SIBs that each include ephemeris information and feeder link timing advance information (e.g., the ephemeris information may be transmitted in a first NTN SIB, while the feeder link timing advance information may be transmitted in a second NTN SIB).
[0098] In some aspects, if feeder link timing advance information indicates a feeder link timing advance with timing drift, information relating to one or more NTN SIBs can provide a corresponding indication of the validity duration and / or accuracy of the ephemeris information and the feeder link timing advance information (e.g., when the ephemeris information and the feeder link timing advance information are transmitted together in one NTN SIB). For example, this information can indicate a first validity duration and / or a first accuracy of the ephemeris information and a second validity duration and / or a second accuracy of the feeder link timing advance information, as described herein. In some aspects, if feeder link timing advance information indicates a feeder link timing advance without timing drift, the update periodicity of the feeder link timing advance information can be based at least in part on the update periodicity of the ephemeris information (e.g., when the ephemeris information and the feeder link timing advance information are transmitted together in one NTN SIB). For example, the update periodicity of the feeder link timing advance information can be indicated in units of the update periodicity of the ephemeris information.
[0099] In some aspects, if the feeder link timing advance information indicates a feeder link timing advance without timing drift, then information related to one or more NTN SIBs can indicate the feeder link timing advance information (e.g., SIB1 indicates the feeder link timing advance information, rather than such information indicated in the NTN SIB). Here, the updating of the feeder link timing advance information can use a system information update procedure as described herein. In some aspects, if the feeder link timing advance information indicates a feeder link timing advance without timing drift, then information related to one or more NTN SIBs can indicate the update periodicity and / or update cycle of the feeder link timing advance information (e.g., but may not indicate the validity duration and / or accuracy of the feeder link timing advance information).
[0100] In some respects, if the feeder link timing advance information indicates a feeder link timing advance without timing drift, the application time of the feeder link timing advance information (e.g., the application time performed by UE 120) may be based at least in part on the last timeslot number (m) of the first PDSCH communication of one or more NTN SIBs in the update cycle, or the last timeslot number (m) of the first transmission window in one or more transmission windows in the update cycle, and the system scheduling offset value (K). offset For example, the application time of feeder link timing advance (e.g., common offset) could be uplink timeslot number m+K. offset In +x, x is a constant value, such as 1 or 2.
[0101] As described herein, the periodicity of NTN SIB updates can indicate the periodicity of updating ephemeris information and / or feeder link timing advance information. Therefore, an update to one or more NTN SIBs can include (updated) ephemeris information and / or feeder link timing advance information without triggering (e.g., independently of triggering) system information update processes. That is, updates do not trigger SIB modifications and associated paging, as described herein.
[0102] As indicated by reference numeral 615, NTN entity 605 may transmit one or more NTN SIBs at least in part based on information relating to one or more NTN SIBs in SIB (e.g., SIB1), and UE 120 may receive one or more NTN SIBs. For example, UE 120 may receive one or more NTN SIBs based on an indicated update periodicity (e.g., within an update period based on the update periodicity), one or more indicated transmission windows, indicated resource allocation, and / or MCS, etc. As described herein, in each update period (e.g., and without SI update notification paging), UE 120 may receive one or more updated NTN SIBs including updated ephemeris information and / or updated feeder link timing advance information.
[0103] As indicated by reference numeral 620, UE 120 and NTN entity 605 may communicate, at least in part, based on one or more NTNSIBs. That is, UE 120 and NTN entity 605 may communicate, at least in part, based on ephemeris information and / or feeder link timing advance information. For example, UE 120 may communicate with NTN entity 605 using ephemeris information and / or feeder link timing advance information (e.g., based on reference time, validity duration, and / or accuracy, as described herein).
[0104] As indicated above, Figure 6 Provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The descriptions are different.
[0105] Figure 7 This is a diagram illustrating an example process 700 performed by a UE according to this disclosure. Example process 700 is an example in which a UE (e.g., UE 120) performs an operation associated with a broadcast of the NTN SIB.
[0106] like Figure 7 As shown, in some aspects, process 700 may include receiving an SIB from an entity of the NTN, the SIB indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information (box 710). For example, the UE (e.g., using...) Figure 9The communication manager 140 and / or receiving unit 902 depicted herein may receive an SIB from an entity of the NTN, the SIB indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information, as described above.
[0107] like Figure 7 As further shown, in some aspects, process 700 may include receiving one or more NTN SIBs from an entity of the NTN (box 720) at least in part based on this information. For example, the UE (e.g., using...) Figure 9 The communication manager 140 and / or receiving component 902 depicted herein can receive one or more NTN SIBs from an entity of the NTN, at least in part, based on this information, as described above.
[0108] Process 700 may include additional aspects, such as any single aspect and / or any combination of aspects of one or more other processes described below and / or in conjunction with other parts of this document.
[0109] In the first aspect, the information indicates at least one of the following: the update periodicity of one or more NTN SIBs, or one or more transmission windows within the update period of one or more NTN SIBs.
[0110] In the second aspect, either alone or in combination with the first aspect, one or more transmission windows are used to receive PDCCH communications that schedule one or more NTN SIBs.
[0111] In the third aspect, either alone or in combination with one or more of the first and second aspects, one or more transmission windows are used to receive PDSCH communications of one or more NTN SIBs.
[0112] 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.
[0113] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, during the update cycle, one or more repetitions of one or more NTN SIBs are associated with the same reference time.
[0114] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the reference time of one or more NTN SIBs is based at least in part on a specific downlink transmission time point within the update cycle.
[0115] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, the information indicates a resource allocation for receiving one or more NTN SIBs or at least one of the MCSs.
[0116] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the temporal allocation of resources is relative to the start of the transmission window of one or more NTN SIBs.
[0117] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the information also indicates the message size of one or more NTN SIBs.
[0118] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the information indicates at least one of the validity duration or accuracy of one or more NTN SIBs.
[0119] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the information uses the parameter type of the SIB to indicate the update periodicity of one or more NTN SIBs, which is also used to indicate the periodicity of one or more non-NTN SIBs.
[0120] In the twelfth aspect, updates to one or more NTN SIBs, either alone or in combination with one or more of the first to eleventh aspects, include at least one of ephemeris information or feeder link timing advance information, without triggering a system information update process.
[0121] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the information indicator identifier indicates one or more of the following according to the 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, the time domain resource allocation of one or more NTN SIBs, the frequency domain resource allocation of one or more NTN SIBs, the message size of the MCS or one or more NTN SIBs.
[0122] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, one or more NTN SIBs include a single NTN SIB that includes ephemeris information and feeder link timing advance information.
[0123] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the feeder link timing advance information indicates a feeder link timing advance with timing drift, and the information indicates at least one of a first validity duration or a first accuracy of the ephemeris information and at least one of a second validity duration or a second accuracy of the feeder link timing advance information.
[0124] 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.
[0125] In the seventeenth aspect, either alone or in combination with one or more of the first to sixteenth aspects, one or more NTN SIBs include multiple NTN SIBs, each of which includes ephemeris information and feeder link timing advance information.
[0126] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the information indicates feeder link timing advance information, and the feeder link timing advance information indicates feeder link timing advance without timing drift.
[0127] In the nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, the feeder link timing advance information indicates a feeder link timing advance without timing drift, and the information indicates at least one of the update periodicity of the feeder link timing advance information or the update cycle of the feeder link timing advance information.
[0128] In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the feeder link timing advance information indicates a feeder link timing advance without timing drift, and the application time of the feeder link timing advance information is based at least in part on the last timeslot number of the first PDSCH communication of one or more NTN SIBs or the last timeslot number of the first transmission window in the update cycle and the system scheduling offset value.
[0129] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include... Figure 7 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the diagram of process 700 may be executed in parallel.
[0130] Figure 8This is a diagram illustrating an example process 800 performed, for example, by an NTN entity according to this disclosure. Example process 800 is an example in which an NTN entity (e.g., base station 110, satellite 320, satellite 340, gateway 350, etc.) performs operations associated with the broadcast of an NTN SIB.
[0131] like Figure 8 As shown, in some aspects, process 800 may include sending an SIB to the UE, the SIB indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information (box 810). For example, an NTN entity (e.g., using...) Figure 10 The communication manager 150 and / or the transmitting component 1004 depicted herein may transmit an SIB to the UE, the SIB indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information, as described above.
[0132] like Figure 8 As further shown, in some aspects, process 800 may include sending one or more NTN SIBs to the UE (box 820) at least in part based on this information. For example, an NTN entity (e.g., using...) Figure 10 The communication manager 150 and / or the transmitting component 1004 depicted herein may transmit one or more NTN SIBs to the UE, at least in part, based on this information, as described above.
[0133] Process 800 may include additional aspects, such as any single aspect and / or any combination of aspects of one or more other processes described below and / or in conjunction with those described elsewhere herein.
[0134] In a first aspect, the information indicates at least one of the following: the update periodicity of one or more NTN SIBs, or one or more transmission windows within the update period of one or more NTN SIBs.
[0135] In the second aspect, either alone or in combination with the first aspect, one or more transmission windows are used to transmit PDCCH communications that schedule one or more NTN SIBs.
[0136] In the third aspect, either alone or in combination with one or more of the first and second aspects, one or more transmission windows are used to transmit one or more NTN SIB PDSCH communications.
[0137] 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.
[0138] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, during the update cycle, one or more repetitions of one or more NTN SIBs are associated with the same reference time.
[0139] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the reference time of one or more NTN SIBs is based at least in part on a specific downlink transmission time point within the update cycle.
[0140] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, the information indicates a resource allocation for receiving one or more NTN SIBs or at least one of the MCSs.
[0141] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the temporal allocation of resources is relative to the start of the transmission window of one or more NTN SIBs.
[0142] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the information also indicates the message size of one or more NTN SIBs.
[0143] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the information indicates at least one of the validity duration or accuracy of one or more NTN SIBs.
[0144] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the information uses the parameter type of the SIB to indicate the update periodicity of one or more NTN SIBs, which is also used to indicate the periodicity of one or more non-NTN SIBs.
[0145] In the twelfth aspect, updates to one or more NTN SIBs, either alone or in combination with one or more of the first to eleventh aspects, include at least one of ephemeris information or feeder link timing advance information, without triggering a system information update process.
[0146] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the information indicator identifier indicates one or more of the following according to the 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, the time domain resource allocation of one or more NTN SIBs, the frequency domain resource allocation of one or more NTN SIBs, the message size of the MCS or one or more NTN SIBs.
[0147] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, one or more NTN SIBs include a single NTN SIB that includes ephemeris information and feeder link timing advance information.
[0148] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the feeder link timing advance information indicates a feeder link timing advance with timing drift, and the information indicates at least one of a first validity duration or a first accuracy of the ephemeris information and at least one of a second validity duration or a second accuracy of the feeder link timing advance information.
[0149] 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.
[0150] In the seventeenth aspect, either alone or in combination with one or more of the first to sixteenth aspects, one or more NTN SIBs include multiple NTN SIBs, each of which includes ephemeris information and feeder link timing advance information.
[0151] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the information indicates feeder link timing advance information, and the feeder link timing advance information indicates feeder link timing advance without timing drift.
[0152] In the nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, the feeder link timing advance information indicates a feeder link timing advance without timing drift, and the information indicates at least one of the update periodicity of the feeder link timing advance information or the update cycle of the feeder link timing advance information.
[0153] In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the feeder link timing advance information indicates a feeder link timing advance without timing drift, and the application time of the feeder link timing advance information is based at least in part on the last timeslot number of the first PDSCH communication of one or more NTN SIBs or the last timeslot number of the first transmission window in the update cycle and the system scheduling offset value.
[0154] although Figure 8 An example box of process 800 is shown, but in some respects, process 800 may include... Figure 8 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 800 may be executed in parallel.
[0155] Figure 9 This is a diagram of an example device 900 for wireless communication. Device 900 may be a UE, or a UE may include device 900. In some aspects, device 900 includes a receiving component 902 and a transmitting component 904 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 900 can use the receiving component 902 and the transmitting component 904 to communicate with another device 906 (such as a UE, a base station, or another wireless communication device). As further shown, device 900 may include a communication manager 140. Communication manager 140 may include SI component 908, etc.
[0156] In some respects, device 900 can be configured to perform the functions described herein. Figure 6 One or more operations described herein. Additionally or alternatively, apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 Processes 700 or combinations thereof. In some aspects, apparatus 900 and / or Figure 9 One or more components shown may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 9 One or more components shown can be combined Figure 2 Implemented within one or more of the described components. Additionally or alternatively, one or more of the 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-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.
[0157] Receiver 902 may receive communications from device 906, such as reference signals, control information, data communications, or combinations thereof. Receiver 902 may provide the received communications to one or more other components of device 900. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signals to one or more other components of device 900. In some aspects, receiver 902 may include combinations of... Figure 2The described UE includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.
[0158] Transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 906. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 906. In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples) on the generated communications and can transmit the processed signals to device 906. In some aspects, transmitting component 904 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 904 may be co-located with the receive component 902 in a transceiver.
[0159] The receiving unit 902 can receive an SIB from an NTN entity (e.g., device 906) that indicates information relating to one or more NTN SIBs, including at least one of ephemeris information or feeder link timing advance information. The receiving unit 902 can receive one or more NTN SIBs from the NTN entity based at least in part on this information. The receiving unit 902 and / or the transmitting unit 904 can communicate with the NTN entity based at least in part on one or more NTN SIBs. The SI unit 908 can process, store, and apply SIs (e.g., ephemeris information and / or feeder link timing advance information) from one or more NTN SIBs.
[0160] In some examples, components used for sending, outputting, or transmitting (or components used for outputting for sending) may include the above-mentioned combinations. Figure 2 The described UE includes one or more antennas, modulators, transmit MIMO processors, transmit processors, or combinations thereof.
[0161] In some examples, the component used for receiving (or the component used for obtaining) may include the above-mentioned combination. Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receiver processors, or combinations thereof.
[0162] In some cases, a device may not actually transmit, for example, signals and / or data, but may instead have an interface (a component for output) 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, a device may not actually receive signals and / or data, but may instead have an interface (a component 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 for reception via a bus interface. In various aspects, an RF front-end may include a variety of components, including, for example, in Figure 2 The examples in the document describe transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc.
[0163] In some examples, the component used for determining, the component used for obtaining, or the component used for transmitting may include the elements described above. Figure 2 The various processing system components of the UE described include, for example, a receive processor, a transmit processor, a controller / processor, a memory, or a combination thereof.
[0164] Figure 9 The number and arrangement of components shown are provided as an example. In practice, they can exist in... Figure 9 Those shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, in Figure 9 The set (one or more) components shown can be performed by being described as being in Figure 9 The other set of components shown performs one or more functions.
[0165] Figure 10 This is a diagram of an example device 1000 for wireless communication. Device 1000 may be a base station or another NTN entity, or a base station or another NTN entity may include device 1000. In some aspects, device 1000 includes a receiving component 1002 and a transmitting component 1004 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1000 can use the receiving component 1002 and the transmitting component 1004 to communicate with another device 1006 (such as a UE, a base station, or another wireless communication device). As further shown, device 1000 may include a communication manager 150. Communication manager 150 may include SI component 1008, etc.
[0166] In some respects, device 1000 can be configured to perform the functions described herein. Figure 6 One or more operations described herein. Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 Processes 800 or combinations thereof. In some aspects, apparatus 1000 and / or Figure 10 One or more components shown may include a combination Figure 2 One or more components of the described base station. Additionally or alternatively, Figure 10 One or more components shown can be combined Figure 2 Implemented within one or more of the described components. Additionally or alternatively, one or more of the 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-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.
[0167] Receiver 1002 may receive communications from device 1006, such as reference signals, control information, data communications, or combinations thereof. Receiver 1002 may provide the received communications to one or more other components of device 1000. In some aspects, receiver 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signals to one or more other components of device 1000. In some aspects, receiver 1002 may include combinations of... Figure 2 The described base station includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.
[0168] The transmitting component 1004 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 can generate communications and provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples) on the generated communications and can transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include combinations of... Figure 2 The described base station includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1004 may be co-located with the receive component 1002 in a transceiver.
[0169] Transmitting component 1004 may transmit an SIB to the UE (e.g., device 1006) indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information. Transmitting component 1004 may transmit one or more NTN SIBs to the UE based at least in part on this information. Receiving component 1002 and / or transmitting component 1004 may communicate with the UE based at least in part on one or more NTN SIBs. SI component 1008 may generate, process, store SIs (e.g., ephemeris information and / or feeder link timing advance information) or perform other operations for one or more NTN SIBs.
[0170] In some examples, components used for sending, outputting, or transmitting (or components used for outputting for sending) may include the above-mentioned combinations. Figure 2 The described base station or another NTN entity has one or more antennas, modulators, transmit MIMO processors, transmit processors, or combinations thereof.
[0171] In some examples, the component used for receiving (or the component used for obtaining) may include the above-mentioned combination. Figure 2 The described base station or another NTN entity has one or more antennas, demodulators, MIMO detectors, receiver processors, or combinations thereof.
[0172] In some cases, a device may not actually transmit, for example, signals and / or data, but may instead have an interface (a component for output) 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, a device may not actually receive signals and / or data, but may instead have an interface (a component 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 for reception via a bus interface. In various aspects, an RF front-end may include a variety of components, including, for example, in Figure 2 The examples in the document describe transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc.
[0173] In some examples, the component used for determining, the component used for obtaining, or the component used for transmitting may include the elements described above. Figure 2 The various processing system components of the base station or another NTN entity described, such as a receive processor, a transmit processor, a controller / processor, a memory, or a combination thereof.
[0174] Figure 10 The number and arrangement of components shown are provided as an example. In reality, they can exist in conjunction with... Figure 10Those shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 10 The two or more components shown can be implemented within a single component, or Figure 10 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, in Figure 10 The set (one or more) components shown can be performed by being described as being in Figure 10 The other set of components shown performs one or more functions.
[0175] The following provides an overview of some aspects of this disclosure:
[0176] Aspect 1: A method for wireless communication at a user equipment (UE), comprising: obtaining a system information block (SIB) from an entity of a non-terrestrial network (NTN), the system information block (SIB) indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information; and obtaining the one or more NTN SIBs from the entity of the NTN at least in part based on the information.
[0177] Aspect 2: According to the method of aspect 1, wherein the information indicates at least one of the following: the update periodicity of the one or more NTN SIBs, or one or more transmission windows within the update period of the one or more NTN SIBs.
[0178] Aspect 3: According to the method of aspect 2, wherein the one or more transmission windows are used to receive physical downlink control channel communications that schedule the one or more NTN SIBs.
[0179] Aspect 4: According to the method of aspect 2, wherein the one or more transmission windows are used to receive physical downlink shared channel communication of the one or more NTN SIBs.
[0180] Aspect 5: The method according to any one of Aspects 1-4, wherein the default update periodicity of the one or more NTN SIBs is the same as the periodicity of the one or more non-NTN SIBs.
[0181] Aspect 6: The method according to any one of Aspects 1-5, wherein during the update cycle, one or more repetitions of the NTN SIBs in the one or more NTN SIBs are associated with the same reference time.
[0182] Aspect 7: The method according to any one of Aspects 1-6, wherein the reference time of at least one of the ephemeris information of one or more NTN SIBs or the feeder link timing advance information is at least partially based on a specific downlink transmission time point within the update cycle.
[0183] Aspect 8: The method according to any one of Aspects 1-7, wherein the information indicates at least one of the resource allocation or modulation and coding schemes for receiving the one or more NTN SIBs.
[0184] Aspect 9: According to the method of aspect 8, the time-domain resource allocation of the resource allocation is relative to the start of the transmission window of the one or more NTN SIBs.
[0185] Aspect 10: The method according to any one of Aspects 8-9, wherein the information further indicates the message size of the one or more NTN SIBs.
[0186] Aspect 11: The method according to any one of Aspects 1-10, wherein the information indicates at least one of the validity duration or accuracy of the one or more NTN SIBs.
[0187] Aspect 12: The method according to any one of Aspect 1 or 5-11, wherein the information uses the parameter type of the SIB to indicate the update periodicity of the one or more NTN SIBs, and the parameter type is also used to indicate the periodicity of one or more non-NTN SIBs.
[0188] Aspect 13: The method according to any one of Aspects 1-11, wherein the update of at least one of the ephemeris information or the feeder link timing advance information is independent of triggering the system information update process.
[0189] Aspect 14: The method according to any one of Aspects 1, 5-11 or 13, wherein the information indicates an identifier, the identifier indicating one or more of the following according to a table: 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, the time-domain resource allocation of the one or more NTN SIBs, the frequency-domain resource allocation of the one or more NTN SIBs, the modulation and coding scheme, or the message size of the one or more NTN SIBs.
[0190] Aspect 15: The method according to any one of Aspects 1-14, wherein the one or more NTN SIBs comprise a single NTN SIB, the single NTN SIB comprising the ephemeris information and the feeder link timing advance information.
[0191] Aspect 16: According to the method of aspect 15, wherein the feeder link timing advance information indicates a feeder link timing advance with timing drift, and wherein the information indicates at least one of a first validity duration or a first accuracy of the ephemeris information and at least one of a second validity duration or a second accuracy of the feeder link timing advance information.
[0192] Aspect 17: According to the method of aspect 15, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and wherein the update periodicity of the feeder link timing advance information is at least partially based on the update periodicity of the ephemeris information.
[0193] Aspect 18: The method according to any one of Aspects 1-14, wherein the one or more NTN SIBs comprise a plurality of NTN SIBs, the plurality of NTN SIBs respectively comprising the ephemeris information and the feeder link timing advance information.
[0194] Aspect 19: The method according to any one of Aspects 1-14, wherein the information indicates feeder link timing advance information, and the feeder link timing advance information indicates feeder link timing advance without timing drift.
[0195] Aspect 20: The method according to any one of Aspects 1-15 or 17-18, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and wherein the information indicates at least one of the update periodicity of the feeder link timing advance information or the update cycle of the feeder link timing advance information.
[0196] Aspect 21: The method according to any one of Aspects 1-15, 17-18 or 20, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and wherein the application time of the feeder link timing advance information is based at least in part on the last timeslot number of the first physical downlink shared channel communication of the one or more NTN SIBs or the last timeslot number of the first transmission window in the update period and the system scheduling offset value.
[0197] Aspect 22: A method for wireless communication at an entity in a non-terrestrial network (NTN), comprising: outputting a system information block (SIB) for transmission to a user equipment (UE), the system information block (SIB) indicating information relating to one or more NTN SIBs that will include at least one of ephemeris information or feeder link timing advance information; and outputting the one or more NTN SIBs for transmission to the UE based at least in part on the information.
[0198] Aspect 23: According to the method of aspect 22, wherein the information indicates at least one of the following: the update periodicity of the one or more NTN SIBs, or one or more transmission windows within the update period of the one or more NTN SIBs.
[0199] Aspect 24: According to the method of aspect 23, wherein the one or more transmission windows are used to transmit physical downlink control channel communications that schedule the one or more NTN SIBs.
[0200] Aspect 25: According to the method of aspect 23, wherein the one or more transmission windows are used to transmit physical downlink shared channel communication of the one or more NTN SIBs.
[0201] Aspect 26: The method according to any one of Aspects 22-25, wherein the default update periodicity of the one or more NTN SIBs is the same as the periodicity of the one or more non-NTN SIBs.
[0202] Aspect 27: The method according to any one of Aspects 22-26, wherein during the update cycle, one or more repetitions of the NTN SIBs in the one or more NTN SIBs are associated with the same reference time.
[0203] Aspect 28: The method according to any one of Aspects 22-27, wherein the reference time of at least one of the ephemeris information of one or more NTN SIBs or the feeder link timing advance information is at least partially based on a specific downlink transmission time point within the update cycle.
[0204] Aspect 29: The method according to any one of Aspects 22-28, wherein the information indicates at least one of the resource allocation or modulation and coding schemes for receiving the one or more NTN SIBs.
[0205] Aspect 30: According to the method of aspect 29, the time-domain resource allocation of the resource allocation is relative to the start of the transmission window of the one or more NTN SIBs.
[0206] Aspect 31: The method according to any one of Aspects 29-30, wherein the information further indicates the message size of the one or more NTN SIBs.
[0207] Aspect 32: The method according to any one of aspects 22-31, wherein the information indicates at least one of the validity duration or accuracy of the one or more NTN SIBs.
[0208] Aspect 33: The method according to any one of Aspects 22 or 26-32, wherein the information uses the parameter type of the SIB to indicate the update periodicity of the one or more NTN SIBs, and the parameter type is also used to indicate the periodicity of one or more non-NTN SIBs.
[0209] Aspect 34: The method according to any one of Aspects 22-32, wherein the update of at least one of the ephemeris information or the feeder link timing advance information is independent of triggering the system information update process.
[0210] Aspect 35: The method according to any one of Aspects 22, 26-32 or 34, wherein the information indicates an identifier, the identifier indicating one or more of the following according to a table: 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, the time-domain resource allocation of the one or more NTN SIBs, the frequency-domain resource allocation of the one or more NTN SIBs, the modulation and coding scheme, or the message size of the one or more NTN SIBs.
[0211] Aspect 36: The method according to any one of Aspects 22-35, wherein the one or more NTN SIBs comprise a single NTN SIB, the single NTN SIB comprising the ephemeris information and the feeder link timing advance information.
[0212] Aspect 37: According to the method of aspect 36, wherein the feeder link timing advance information indicates a feeder link timing advance with timing drift, and wherein the information indicates at least one of a first validity duration or a first accuracy of the ephemeris information and at least one of a second validity duration or a second accuracy of the feeder link timing advance information.
[0213] Aspect 38: According to the method of aspect 36, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and wherein the update periodicity of the feeder link timing advance information is at least partially based on the update periodicity of the ephemeris information.
[0214] Aspect 39: The method according to any one of Aspects 22-35, wherein the one or more NTN SIBs comprise a plurality of NTN SIBs, the plurality of NTN SIBs respectively comprising the ephemeris information and the feeder link timing advance information.
[0215] Aspect 40: The method according to any one of Aspects 22-35, wherein the information indicates feeder link timing advance information, and the feeder link timing advance information indicates feeder link timing advance without timing drift.
[0216] Aspect 41: The method according to any one of Aspects 22-36 or 38-39, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and wherein the information indicates at least one of the update periodicity of the feeder link timing advance information or the update cycle of the feeder link timing advance information.
[0217] Aspect 42: The method according to any one of Aspects 22-36, 38-39 or 41, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift, and wherein the application time of the feeder link timing advance information is based at least in part on the last timeslot number of the first physical downlink shared channel communication of the one or more NTN SIBs or the last timeslot number of the first transmission window in the update period and the system scheduling offset value.
[0218] Aspect 43: An apparatus for wireless communication, comprising: a memory including instructions; and one or more processors configured to execute the instructions and cause the apparatus to perform the method according to one or more of aspects 1-21.
[0219] Aspect 44: A user equipment (UE) comprising: at least one receiver; a memory including instructions; and one or more processors configured to execute the instructions and cause the UE to perform the method according to one or more aspects of aspects 1-21, wherein the at least one receiver is configured to receive the SIB and the one or more NTN SIBs.
[0220] Aspect 45: An apparatus for wireless communication, comprising: at least one component, said at least one component being configured to perform the method according to one or more aspects of aspects 1-21.
[0221] Aspect 46: A non-transitory computer-readable medium comprising: one or more instructions, which, when executed by one or more processors of the device, cause the device to perform the method according to one or more aspects of aspects 1-21.
[0222] Aspect 47: An apparatus for wireless communication, comprising: a memory including instructions; and one or more processors configured to execute the instructions and cause the apparatus to perform the method according to one or more aspects 22-42.
[0223] Aspect 48: An entity of a non-terrestrial network (NTN) comprising: at least one transmitter; a memory including instructions; and one or more processors configured to execute the instructions and cause the entity of the NTN to perform the method according to one or more aspects of aspects 22-42, wherein the at least one transmitter is configured to transmit the SIB and the one or more NTN SIBs.
[0224] Aspect 49: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more aspects 22-42.
[0225] Aspect 50: A non-transitory computer-readable medium comprising: one or more instructions, which, when executed by one or more processors of the device, cause the device to perform the method according to one or more aspects of aspects 22-42.
[0226] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or from practice in these aspects.
[0227] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, application programs, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, and other examples. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent to those skilled in the art that the systems and / or methods described herein can be implemented in various 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 limiting in any way. Therefore, no specific software code is referred to in the description of the operation and behavior of the systems and / or methods herein, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.
[0228] As used in this article, depending on the context, “meeting the threshold” can refer to a value that 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, not equal to the threshold, etc.
[0229] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the aspects. Many of these features can be combined in ways not specifically recited in the claims and / or not disclosed in the specification. The disclosure of the aspects includes each dependent claim in combination with each other claim in the claim set. As used herein, the phrase “at least one of” in the list of entries refers to any combination of these entries (including a single member). As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiples of the same element (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).
[0230] No element, action, or instruction used herein should be construed as critical or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “one” are intended to include one or more entries and are interchangeable with “one or more.” Similarly, as used herein, the article “the” is intended to include one or more entries connected with the article “the” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more entries and are interchangeable with “one or more.” The phrase “only one” or similar terminology will be used when referring to only one entry. Moreover, as used herein, the terms “have,” “possess,” “have,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Additionally, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one of”).
Claims
1. An apparatus for wireless communication, comprising: One or more memories, the one or more memories including instructions; and One or more processors, the one or more processors being configured to execute the instructions and cause the device to: Obtain an indication of an SIB relating to one or more Non-Terrestrial Network (NTN) System Information Blocks (SIBs); The one or more NTN SIBs are obtained at least in part based on the information provided, the one or more NTN SIBs including at least one of ephemeris information or feeder link timing advance information. as well as Communication with one or more entities of the NTN is based at least in part on one or more NTN SIBs, wherein at least one of the following conditions exists: The reference time of at least one of the ephemeris information or the feeder link timing advance information is at least partially based on a specific downlink transmission time point. Updates to at least one of the ephemeris information or the feeder link timing advance information are independent of the triggering system information update process, or The one or more NTN SIBs include a single NTN SIB, which includes the ephemeris information and the feeder link timing advance information.
2. The apparatus of claim 1, wherein the reference time of the ephemeris information is at least partially based on the specific downlink transmission time.
3. The apparatus of claim 1, wherein the reference time of the feeder link timing advance information is at least partially based on the specific downlink transmission time point.
4. The apparatus of claim 1, wherein the update of at least one of the ephemeris information or the feeder link timing advance information is independent of the triggering system information update process.
5. The apparatus of claim 1, wherein the one or more NTN SIBs comprise a single NTN SIB, the single NTN SIB comprising the ephemeris information and the feeder link timing advance information.
6. The apparatus of claim 1, wherein the information indicates at least one of the following: resource allocation for obtaining the one or more NTN SIBs, modulation and coding schemes for obtaining the one or more NTN SIBs, message size of the one or more NTN SIBs, validity duration of the one or more NTN SIBs, or accuracy of the one or more NTN SIBs.
7. The apparatus of claim 1, wherein the feeder link timing advance information indicates a feeder link timing advance with timing drift.
8. The apparatus of claim 1, wherein the feeder link timing advance information indicates a feeder link timing advance without timing drift.
9. The apparatus of claim 1, wherein the information indicates feeder link timing advance information, and the feeder link timing advance information indicates feeder link timing advance without timing drift.
10. The apparatus according to claim 1, further comprising: A receiver configured to receive the SIB and the one or more NTN SIBs, wherein the device is configured as a user equipment (UE).
11. An apparatus for wireless communication, comprising: One or more memories, the one or more memories including instructions; and One or more processors, the one or more processors being configured to execute the instructions and cause the one or more means: Output a System Information Block (SIB) for transmission to the User Equipment (UE), the SIB indicating information related to one or more Non-Terrestrial Network (NTN) SIBs. The one or more NTN SIBs are output at least in part based on the information for transmission to the UE, the one or more NTN SIBs including at least one of ephemeris information or feeder link timing advance information. as well as The UE communicates with the NTN SIB at least in part, wherein at least one of the following conditions exists: The reference time of at least one of the ephemeris information or the feeder link timing advance information is at least partially based on a specific downlink transmission time point. Updates to at least one of the ephemeris information or the feeder link timing advance information are independent of the triggering system information update process, or The one or more NTN SIBs include a single NTN SIB, which includes the ephemeris information and the feeder link timing advance information.
12. The apparatus of claim 11, wherein the reference time of the ephemeris information is at least partially based on the specific downlink transmission time.
13. The apparatus of claim 11, wherein the reference time of the feeder link timing advance information is at least partially based on the specific downlink transmission time point.
14. The apparatus of claim 11, wherein the update of at least one of the ephemeris information or the feeder link timing advance information is independent of triggering the system information update process.
15. The apparatus of claim 11, wherein the one or more NTN SIBs comprise a single NTN SIB, the single NTN SIB comprising the ephemeris information and the feeder link timing advance information.
16. The apparatus of claim 11, wherein the information indicates at least one of the following: resource allocation for obtaining the one or more NTN SIBs, modulation and coding schemes for obtaining the one or more NTN SIBs, message size of the one or more NTN SIBs, validity duration of the one or more NTN SIBs, or accuracy of the one or more NTN SIBs.
17. The apparatus of claim 11, wherein the feeder link timing advance information indicates feeder link timing advance with timing drift or feeder link timing advance without timing drift.
18. The apparatus of claim 11, wherein the information indicates feeder link timing advance information, and the feeder link timing advance information indicates feeder link timing advance without timing drift.
19. The apparatus of claim 11, further comprising: One or more transmitters configured to transmit the SIB and the one or more NTN SIBs, wherein the one or more means are configured as one or more entities of the NTN.
20. A method for conducting wireless communication at a user equipment (UE), comprising: Obtain an indication of an SIB relating to one or more Non-Terrestrial Network (NTN) System Information Blocks (SIBs); as well as The one or more NTN SIBs are obtained at least in part based on the information provided, the one or more NTN SIBs including at least one of ephemeris information or feeder link timing advance information. as well as Communication with the NTN is based at least in part on one or more NTN SIBs, wherein at least one of the following conditions exists: The reference time of at least one of the ephemeris information or the feeder link timing advance information is at least partially based on a specific downlink transmission time point. Updates to at least one of the ephemeris information or the feeder link timing advance information are independent of the triggering system information update process, or The one or more NTN SIBs include a single NTN SIB, which includes the ephemeris information and the feeder link timing advance information.
Citation Information
Patent Citations
Mac-ce command action timing control in non-terrestrial networks
US20220124660A1