Report of user equipment timing mismatch in non-terrestrial networks
By reporting timing mismatches, UEs in non-terrestrial networks enable optimized communication scheduling, reducing collisions and delays, thus improving communication efficiency.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- QUALCOMM INC
- Filing Date
- 2026-02-18
- Publication Date
- 2026-06-04
AI Technical Summary
In non-terrestrial wireless communication networks, user equipment (UE) experiences timing mismatches between uplink and downlink timelines due to propagation delays, leading to collisions and inefficiencies in communication with satellites.
UEs determine and report timing mismatch information to satellites, allowing for adjusted communication scheduling to prevent collisions and optimize uplink and downlink operations.
Reduces dropped communications, minimizes delays, and decreases retransmissions by aligning UE timing with satellite schedules, enhancing communication efficiency in non-terrestrial networks.
Smart Images

Figure 2026091845000001_ABST
Abstract
Description
Technical Field
[0001] Cross - reference to Related Applications This patent application claims priority to U.S. Provisional Patent Application No. 62 / 706,060, filed Jul. 29, 2020, entitled "USER EQUIPMENT TIMING MISALIGNMENT REPORTING IN NON - TERRESTRIAL NETWORKS", and U.S. Non - Provisional Patent Application No. 17 / 303,801, filed Jun. 8, 2021, entitled "USER EQUIPMENT TIMING MISALIGNMENT REPORTING IN NON - TERRESTRIAL NETWORKS", which are hereby incorporated by reference in their entirety.
[0002] Aspects of the present disclosure generally relate to wireless communication and, more particularly, to techniques and apparatus for user equipment (UE) timing misalignment reporting in non - terrestrial networks.
Background Art
[0003] Wireless communication systems are widely deployed to provide various telecommunications services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ a multiple access technology that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single - carrier frequency division multiple access (SC - FDMA) systems, time - division synchronous code division multiple access (TD - SCDMA) systems, and long - term evolution (LTE). LTE / LTE - Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standards published by the Third Generation Partnership Project (3GPP™).
[0004] A wireless network may include several base stations (BS) that can support communication for several user devices (UEs). UEs may communicate with BS via downlink and uplink. “Downlink” (or “forward link”) refers to the communication link from BS to UE, and “uplink” (or “reverse link”) refers to the communication link from UE to BS. As will be described in more detail herein, BS may also be called node B, gNB, access point (AP), radio head, transmit / receive point (TRP), new radio (NR) BS, 5G node B, etc.
[0005] The multiple access technologies described above are employed in various telecommunications standards to provide a common protocol that enables different user devices to communicate across cities, nations, regions, and even globally. NR, sometimes referred to as 5G, is a set of extensions to the LTE mobile standard published by 3GPP®. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving service, utilizing new spectra, using orthogonal frequency division multiplexing (OFDM) with cyclic prefixes (CP) on the downlink (DL) and CP-OFDM and / or SC-FDM (also known as, for example, discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), as well as better integrating with other open standards that support beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain valuable. [Overview of the Initiative] [Means for solving the problem]
[0006] In some embodiments, a method of wireless communication performed by user equipment (UE) includes the steps of determining timing mismatch information about a timing mismatch between the uplink timeline and downlink timeline of the UE associated with a non-terrestrial cell, and transmitting the timing mismatch information to a satellite associated with the non-terrestrial cell.
[0007] In some embodiments, a method of wireless communication performed by a UE includes the steps of: receiving instructions to transmit an uncompensated uplink signal to a satellite associated with a non-terrestrial cell; and transmitting an uncompensated uplink signal to the satellite, at least in part on having received the instructions, such that the uncompensated uplink signal is not adjusted, at least in part on having adjusted for timing mismatches between the uplink timeline and the downlink timeline associated with the non-terrestrial cell.
[0008] In some embodiments, the UE for wireless communications includes a memory and one or more processors coupled to the memory, the memory and one or more processors configured to determine timing mismatch information about timing mismatches between uplink timelines and downlink timelines associated with a non-terrestrial cell, and to transmit the timing mismatch information to a satellite associated with the non-terrestrial cell.
[0009] In some embodiments, a UE for wireless communications includes a memory and one or more processors coupled to the memory, the memory and one or more processors configured to receive instructions to transmit an uncompensated uplink signal to a satellite associated with a non-terrestrial cell, and, at least in part, based on having received the instructions, transmit an uncompensated uplink signal to the satellite such that the uncompensated uplink signal is not adjusted, at least in part, for timing mismatches between the uplink timeline and the downlink timeline associated with the non-terrestrial cell.
[0010] In some embodiments, a non-temporary computer-readable medium storing a set of instructions for wireless communication includes, when executed by one or more processors of the UE, one or more instructions causing the UE to determine timing mismatch information about a timing mismatch between an uplink timeline and a downlink timeline associated with a non-terrestrial cell, and to transmit the timing mismatch information to a satellite associated with the non-terrestrial cell.
[0011] In some embodiments, a non-temporary computer-readable medium storing a set of instructions for wireless communication includes, when executed by one or more processors of the UE, one or more instructions causing the UE to receive an instruction to transmit an uncompensated uplink signal to a satellite associated with a non-terrestrial cell, and, at least in part, based on having received the instruction, to transmit an uncompensated uplink signal to the satellite such that the uncompensated uplink signal is not adjusted, at least in part, for timing mismatches between the uplink timeline and the downlink timeline associated with the non-terrestrial cell.
[0012] In some embodiments, the apparatus for wireless communications includes means for determining timing mismatch information about timing mismatches between uplink timelines and downlink timelines associated with a non-terrestrial cell, and means for transmitting the timing mismatch information to a satellite associated with the non-terrestrial cell.
[0013] In some embodiments, the apparatus for wireless communications includes means for receiving instructions to transmit an uncompensated uplink signal to a satellite associated with a non-terrestrial cell, and means for transmitting an uncompensated uplink signal to the satellite, at least in part on the basis of having received the instructions, such that the uncompensated uplink signal is not adjusted, at least in part on the basis of timing mismatches between the uplink timeline and the downlink timeline associated with the non-terrestrial cell.
[0014] Embodiments generally include methods, apparatus, systems, computer program products, non-temporary computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems, as fully described herein with reference to the drawings and this specification, and as shown herein.
[0015] The above provides a fairly broad overview of the features and technical advantages of the examples provided in this disclosure so that the modes for carrying out the following inventions may be better understood. Additional features and advantages are described below. The concepts and examples disclosed may readily be used as a basis for modifying or designing other structures to accomplish the same objectives of this disclosure. Such equivalent structures will not deviate from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their organization and method of operation, will be better understood from the following description, along with the relevant advantages, when considered together with the accompanying figures. Each of the figures is provided for illustrative and explanatory purposes and is not provided as a definition of the limitation of the claims.
[0016] While embodiments are illustrated in this disclosure by several examples, those skilled in the art will understand that such embodiments can be implemented in many different configurations and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some embodiments can be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, or artificial intelligence-enabled devices). Embodiments can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices incorporating the embodiments and features described may include additional components and features for implementation and practice of the claimed and described embodiments. For example, wireless signal transmission and reception may include several components for analog and digital applications (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or summers). The embodiments described herein are intended to be applicable to a wide variety of devices, components, systems, distributed configurations, or end-user devices of various sizes, shapes, and structures.
[0017] To allow for a more detailed understanding of the features enumerated above in this disclosure, some of them may be described in more detail by referring to the embodiments shown in the accompanying drawings, which provide a more detailed explanation than that briefly summarized above. However, since this description may allow for other equally effective embodiments, it should be noted that the accompanying drawings should not be considered to represent only some typical embodiments of this disclosure and therefore to be limited in scope. The same reference numerals in different drawings may identify the same or similar elements. [Brief explanation of the drawing]
[0018] [Figure 1] This figure shows an example of a wireless network as described in this disclosure. [Figure 2] This figure shows an example of a base station communicating with a UE in a wireless network, as disclosed herein. [Figure 3] This figure shows an example of a frame structure in a wireless communication network as disclosed herein. [Figure 4] This figure shows an example of regenerative satellite deployment in a non-terrestrial network and an example of transparent satellite deployment. [Figure 5] This figure shows an example of timing matching in a non-terrestrial network as described in this disclosure. [Figure 6] This figure shows an example of what is associated with UE timing mismatch reporting in non-terrestrial networks as described in this disclosure. [Figure 7] This figure shows an example of what is associated with UE timing mismatch reporting in non-terrestrial networks as described in this disclosure. [Figure 8] This figure shows an exemplary process associated with UE timing mismatch reporting in non-terrestrial networks as described in this disclosure. [Figure 9] This figure shows an exemplary process associated with UE timing mismatch reporting in non-terrestrial networks as described in this disclosure. [Figure 10] This is a block diagram of an exemplary device for wireless communication as disclosed herein. [Modes for carrying out the invention]
[0019] Various aspects of the present disclosure will be described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, the scope of the present disclosure is intended to include any other aspect of the present disclosure, whether implemented independently of any other aspect of the present disclosure or in combination with any other aspect of the present disclosure. Those skilled in the art should understand that, for example, an apparatus may be implemented using any number of aspects described herein, or a method may be practiced. Additionally, the scope of the present disclosure is intended to include such apparatus or methods practiced using other structures, functions, or structures and functions in addition to, or other than, the various aspects of the present disclosure described herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of the claims.
[0020] Next, some aspects of a telecommunications system are presented with reference to various devices and techniques. These devices and techniques are described in the context of implementing the following inventions and are shown in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or as software depends on the particular application and the design constraints imposed on the overall system.
[0021] Aspects may be described herein using terms generally associated with 5G or NR radio access technology (RAT), but it should be noted that aspects of the present disclosure may be applicable to other RATs such as 3G RAT, 4G RAT, and / or RATs after 5G (e.g., 6G).
[0022] Figure 1 shows an example of a wireless network 100 as described herein. The wireless network 100 may be, or may include, elements of a 5G (NR) network and / or an LTE network, even in this example. The wireless network 100 may include several base stations 110 (indicated as BS110a, BS110b, BS110c, and BS110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UE) and may also be called an NR BS, node B, gNB, 5G node B (NB), access point, transmit / receive point (TRP), etc. Each BS may provide communication coverage to a specific geographic area. In 3GPP®, the term “cell” may, depending on the context in which the term is used, refer to the coverage area of a BS and / or a BS subsystem that serves that coverage area.
[0023] A BS may provide communication coverage to macrocells, picocells, femtocells, and / or other types of cells. A macrocell may cover a relatively large geographical area (e.g., a radius of several kilometers) and may enable unrestricted access by UEs subscribing to the service. A picocell may cover a relatively small geographical area and may enable unrestricted access by UEs subscribing to the service. A femtocell may cover a relatively small geographical area (e.g., a home) and may enable limited access by UEs associated with a femtocell (e.g., UEs within a Limited Subscriber Group (CSG)). A BS for a macrocell is sometimes called a macroBS. A BS for a picocell is sometimes called a picoBS. A BS for a femtocell is sometimes called a femtoBS or homeBS. In the example shown in Figure 1, BS110a may be a macroBS for macrocell 102a, BS110b may be a picoBS for picocell 102b, and BS110c may be a femtoBS for femtocell 102c. A BS may support one or more (for example, three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” may be used interchangeably in this specification.
[0024] In some embodiments, cells may not necessarily be stationary, and the geographical area of a cell may move according to the location of the mobile BS. In some embodiments, BSs may be interconnected with one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.
[0025] The wireless network 100 may also include relay stations. A relay station is an entity that can receive data transmissions from upstream stations (e.g., BS or UE) and send those data transmissions to downstream stations (e.g., UE or BS). A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in Figure 1, relay BS110d may communicate with macro BS110a and UE120d to facilitate communication between BS110a and UE120d. Relay BS may also be called relay stations, relay base stations, or relays.
[0026] The wireless network 100 may be a heterogeneous network including different types of BS, such as macro BS, pico BS, femto BS, and relay BS. These different types of BS may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, macro BS may have high transmit power levels (e.g., 5-40 watts), while pico BS, femto BS, and relay BS may have lower transmit power levels (e.g., 0.1-2 watts).
[0027] The network controller 130 may be coupled to a set of BSs and may coordinate and control these BSs. The network controller 130 may communicate with the BSs via backhaul. The BSs may also communicate with each other directly or indirectly via wireless or wireline backhaul.
[0028] UE120 (for example, 120a, 120b, 120c) may be distributed across the entire wireless network 100, and each UE may be fixed or mobile. UEs may also be called access terminals, terminals, mobile stations, subscriber units, stations, etc. UEs may be cellular phones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablets, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices or equipment, biosensors / devices, wearable devices (smartwatches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), entertainment devices (e.g., music or video devices, or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system devices, or any other suitable devices configured to communicate wirelessly or via wired media.
[0029] Some UEs may be considered machine-type communications (MTC) UEs, or advanced or enhanced machine-type communications (eMTC) UEs. MTC UEs and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with base stations, other devices (e.g., remote devices), or any other entities. Wireless nodes may provide connectivity or network access for a network (e.g., the Internet or a wide area network such as a cellular network) via, for example, wired or wireless communication links. Some UEs may be considered Internet of Things (IoT) devices and / or implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). UE120 may be contained within a housing that accommodates components of UE120, such as processor components and / or memory components. In some embodiments, the processor components and memory components may be coupled to each other. For example, processor components (e.g., one or more processors) and memory components (e.g., memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.
[0030] In general, any number of wireless networks may be deployed in a given geographical area. Each wireless network may support a specific RAT and operate on one or more frequencies. RATs are sometimes called wireless technologies or air interfaces. Frequencies are sometimes called carriers or frequency channels. Each frequency may support a single RAT in a given geographical area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
[0031] In some embodiments, two or more UE120s (for example, indicated as UE120a and UE120e) may communicate directly using one or more sidelink channels (for example, without using the base station 110 as an intermediary for communication with each other). For example, the UE120s may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include, for example, vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In this case, the UE120s may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.
[0032] Devices in the wireless network 100 may communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, channels, etc., based on frequency or wavelength. For example, devices in the wireless network 100 may communicate using an operating band having a first frequency range (FR1) that can range from 410 MHz to 7.125 GHz, and / or using an operating band having a second frequency range (FR2) that can range from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes called intermediate band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the “sub-6 GHz” band. Similarly, FR2 is often referred to as the “millimeter wave” band, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) which is identified by the International Telecommunication Union (ITU) as the “millimeter wave” band. Therefore, unless otherwise specified, terms such as “sub-6GHz” can broadly refer to frequencies below 6GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125GHz) as used herein. Similarly, unless otherwise specified, terms such as “millimeter wave” can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25GHz) as used herein. The frequencies included in FR1 and FR2 may be modified, and the techniques described herein are intended to be applicable to those modified frequency ranges.
[0033] In some embodiments, the wireless network 100 may include one or more non-terrestrial network (NTN) deployments, in which non-terrestrial wireless communication devices may include BS110f (referred interchangeably herein as "non-terrestrial BS," "non-terrestrial base station," "satellite base station," or "satellite"), relay stations (referred interchangeably herein as "non-terrestrial relay stations" or "satellite relay stations"), etc. As used herein, "NTN" may refer to a network whose access is facilitated by non-terrestrial BS110f, non-terrestrial relay stations, etc. The satellite may provide non-terrestrial cells, which may at least partially overlap with one or more cells provided by ground-based BS, and may encompass one or more cells provided by ground-based BS, etc. In some embodiments, the satellite may be associated with a non-terrestrial BS (for example, the BS may be mounted on the satellite). In some embodiments, the satellite may be associated with a terrestrial BS or a ground-based BS.
[0034] The wireless network 100 may include any number of non-terrestrial wireless communication devices. Non-terrestrial wireless communication devices may include satellites, high-altitude platforms (HAPs), etc. HAPs may include balloons, airships, airplanes, unmanned aerial vehicles, etc. Non-terrestrial wireless communication devices may be part of NTN, which is separate from the wireless network 100. Alternatively, NTN may be part of the wireless network 100. Satellites may communicate directly and / or indirectly with other entities in the wireless network 100 using satellite communications. Other entities may include UEs, other satellites in one or more NTN deployments, other types of BS (e.g., fixed BS or ground-based BS), relay stations, one or more components and / or devices included in the core network of the wireless network 100, etc.
[0035] As stated above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.
[0036] Figure 2 shows an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 according to this disclosure. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, where generally T≧1 and R≧1.
[0037] At base station 110, the transmit processor 220 may receive data for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE at least in part based on the channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE at least in part based on the MCS selected for the UE, and provide data symbols to all UEs. The transmit processor 220 may also process system information and control information (e.g., CQI requests, authorizations, and / or upper-layer signaling) (e.g., for semi-static resource partitioning information (SRPI)) and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulated reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may, where applicable, perform spatial processing (e.g., precoding) on data symbols, control symbols, overhead symbols, and / or reference symbols, and provide T output symbol streams to T modulators (MODs) 232a-232t. Each modulator 232 may process its respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process the output sample stream (e.g., convert to analog, amplify, filter, and upconvert) to obtain a downlink signal. The T downlink signals from modulators 232a-232t may each be transmitted via T antennas 234a-234t.
[0038] In UE120, antennas 252a-252r may receive downlink signals from base station 110 and / or other base stations, and each may provide the received signals to demodulators (DEMOD) 254a-254r. Each demodulator 254 may adjust the received signals (e.g., filter, amplify, downconvert, and digitize) to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM) to obtain received symbols. MIMO detector 256 may obtain received symbols from all R demodulators 254a-254r, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiving processor 258 may process the detected symbols (e.g., demodulate and decode), provide the decoded data for UE120 to data sink 260, and provide the decoded control and system information to controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may, in some examples, determine the reference signal received power (RSRP) parameter, the received signal strength indicator (RSSI) parameter, the reference signal received quality (RSRQ) parameter, and / or the channel quality indicator (CQI) parameter. In some embodiments, one or more components of the UE120 may be contained within the housing 284.
[0039] The network controller 130 may include a communication unit 294, a controller / processor 290, and memory 292. The network controller 130 may include, for example, one or more devices in the core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.
[0040] An antenna (for example, antennas 234a-234t and / or antennas 252a-252r) may include, or be contained within, one or more antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays, even in the example. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include a set of coplanar antenna elements and / or a set of non-coplanar antenna elements. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include antenna elements in a single housing and / or antenna elements in multiple housings. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements coupled to one or more transmitting and / or receiving components, such as one or more components in Figure 2.
[0041] On the uplink, in UE120, the transmit processor 264 may receive and process data from data source 262 and control information (for reporting, including RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may, where applicable, be precoded by TX MIMO processor 266, further processed by modulators 254a-254r (for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some embodiments, the modulators and demodulators of UE120 (e.g., MOD / DEMOD 254) may be included in the modem of UE120. In some embodiments, UE120 includes transceivers. The transceiver may include any combination of an antenna 252, a modulator and / or demodulator 254, a MIMO detector 256, a receiving processor 258, a transmitting processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (e.g., a controller / processor 280) and memory 282 to perform any aspect of the methods described herein (e.g., as described with reference to Figures 6 to 9).
[0042] At base station 110, uplink signals from UE 120 and other UEs may be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 where applicable, and further processed by receiving processor 238 to obtain decoded data and control information sent by UE 120. The receiving processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include a communication unit 244 and communicate with network controller 130 via the communication unit 244. Base station 110 may include a scheduler 246 for scheduling UE 120 for downlink and / or uplink communication. In some embodiments, the modulator and demodulator of base station 110 (e.g., MOD / DEMOD 232) may be included in the modem of base station 110. In some embodiments, base station 110 includes a transceiver. The transceiver may include any combination of an antenna 234, a modulator and / or demodulator 232, a MIMO detector 236, a receiving processor 238, a transmitting processor 220, and / or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., a controller / processor 240) and memory 242 to perform any aspect of the methods described herein (e.g., as described with reference to Figures 6 to 9).
[0043] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other components in Figure 2 may perform one or more techniques associated with UE timing mismatch reporting in non-terrestrial networks, as described in more detail elsewhere in this specification. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other components in Figure 2 may perform or direct the operation of, for example, process 800 in Figure 8, process 900 in Figure 9, and / or other processes as described herein. Memories 242 and 282 may store data and program code for base station 110 and UE 120, respectively. In some embodiments, memories 242 and / or memories 282 may include non-temporary computer-readable media for storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when one or more instructions are executed by one or more processors in the base station 110 and / or UE 120 (for example, immediately or after compilation, conversion, and / or interpretation), one or more processors, UE 120, and / or base station 110 can be caused to perform or direct the operation of, for example, process 800 in Figure 8, process 900 in Figure 9, and / or other processes described herein. In some embodiments, executing an instruction may include, among other things, invoking the instruction, converting the instruction, compiling the instruction, and / or interpreting the instruction.
[0044] In some embodiments, the UE120 may include means for determining timing mismatch information regarding timing mismatches between uplink timelines and downlink timelines associated with a non-terrestrial cell, and means for transmitting the timing mismatch information to satellite 110f associated with the non-terrestrial cell. In some embodiments, such means may include one or more components of the UE120 described with respect to Figure 2, such as the controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, and receive processor 258.
[0045] Although the blocks in Figure 2 are shown as individual components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination of components, or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.
[0046] As described above, Figure 2 is provided as an example. Other examples may differ from those described with respect to Figure 2.
[0047] Figure 3 shows an example of a frame structure in a wireless communication network according to the present disclosure. The frame structure shown in Figure 3 is for frequency division duplexing (FDD) in telecommunication systems such as LTE and NR. The transmission timeline for the downlink and uplink, respectively, may be divided into units of radio frames (sometimes called frames). Each radio frame may have a predetermined duration (e.g., 10 milliseconds (ms)) and may be divided into a set of Z (Z≧1) subframes (e.g., with indices from 0 to Z-1). Each subframe may have a predetermined duration (e.g., 1 ms) and may contain a set of slots (e.g., 2m slots per subframe are shown in Figure 3, where m is a numerology index used for transmission, such as 0, 1, 2, 3, 4, etc.). Each slot may contain a set of L symbol periods. For example, each slot may contain 14 symbol periods, 7 symbol periods, or another number of symbol periods (e.g., as shown in Figure 3). If a subframe contains two slots (for example, when m=1), the subframe may contain 2L symbol periods, where each of the 2L symbol periods in the subframe may be assigned an index from 0 to 2L-1. In some embodiments, the scheduling unit for the FDD may be frame-based, subframe-based, slot-based, mini-slot-based, symbol-based, etc.
[0048] As described above, Figure 3 is provided as an example. Other examples may differ from those described with respect to Figure 3.
[0049] Figure 4 shows an example 400 of regenerative satellite deployment in a non-terrestrial network and an example 410 of transparent satellite deployment as described herein.
[0050] Example 400 illustrates a regenerative satellite deployment. In Example 400, UE120 is serviced by satellite 420 via service link 430. For example, satellite 420 may include satellite 110f. In some embodiments, satellite 420 may be referred to as a non-terrestrial base station, regenerative repeater, onboard processing repeater, etc. In some embodiments, satellite 420 may demodulate the uplink radio frequency signal and modulate the baseband signal derived from the uplink radio signal to generate a downlink radio frequency transmission. Satellite 420 may transmit the downlink radio frequency signal over service link 430. Satellite 420 may provide a cell covering UE120.
[0051] Example 410 illustrates a transparent satellite deployment, sometimes called a vent-pipe satellite deployment. In Example 410, UE120 is serviced by satellite 440 via service link 430. Satellite 440 may be a transparent satellite. Satellite 440 may relay signals received from gateway 450 (e.g., ground base BS110) via feeder link 460. For example, the satellite may receive an uplink radio frequency transmission and transmit a downlink radio frequency transmission without demodulating the uplink radio frequency transmission. In some embodiments, the satellite may frequency convert the uplink radio frequency transmission received on service link 430 to the frequency of the uplink radio frequency transmission on feeder link 460, and may amplify and / or filter the uplink radio frequency transmission. In some embodiments, UE120 as shown in Examples 400 and 410 may be associated with Global Navigation Satellite System (GNSS) capability, Global Positioning System (GPS) capability, etc., but not all UEs have such capabilities. Satellite 440 may provide cells that cover UE120.
[0052] Service link 430 may include a link between satellite 440 and UE120, and may include one or more uplinks or downlinks. Feeder link 460 may include a link between satellite 440 and gateway 450, and may include one or more uplinks (for example, from UE120 to gateway 450) or downlinks (for example, from gateway 450 to UE120). The uplink of service link 430 may be indicated by reference number 430-U, and the downlink of service link 430 may be indicated by reference number 430-D. Similarly, the uplink of feeder link 460 may be indicated by reference number 460-U (not shown in Figure 4), and the downlink of feeder link 460 may be indicated by reference number 460-D (not shown in Figure 4).
[0053] Feeder link 460 and service link 430 may be subject to Doppler effects due to the movement of satellites 420 and 440, and potentially the movement of UE120, respectively. These Doppler effects can be significantly greater than those in terrestrial networks. While Doppler effects on feeder link 460 may be compensated to some extent, they may still be associated with a small amount of uncompensated frequency error. Furthermore, gateway 450 may be associated with residual frequency error, and / or satellites 420 / 440 may be associated with onboard frequency error. These sources of frequency error may cause the received downlink frequency at UE120 to drift from the target downlink frequency.
[0054] As described above, Figure 4 is provided as an example. Other examples may differ from those described with respect to Figure 4.
[0055] Figure 5 shows an example 500 of timing matching in a non-terrestrial network as described in this disclosure. As shown in Figure 5, satellite 110 may be timing-matched with one or more UE120s (e.g., UE120-1, UE120-2, etc.) served in the non-terrestrial cell of satellite 110.
[0056] As further shown in Figure 5, satellite 110 may be associated with an uplink timeline 512 containing multiple time-domain resources (e.g., slots or subframes 0-16) for uplink communications in non-terrestrial cells, and may be associated with a downlink timeline 514 containing multiple time-domain resources (e.g., slots or subframes 0-16) for downlink communications in non-terrestrial cells. From the perspective of satellite 110, the uplink timeline 512 and the downlink timeline 514 may be timing-matched (e.g., slot or subframe 0 of uplink timeline 512 is timing-matched with slot or subframe 0 of downlink timeline 514, etc.).
[0057] Due to the distance between UE120-1 and satellite BS110, and the distance between UE120-2 and satellite 110, propagation delays occur for communications between UE120-1 and satellite 110, and between UE120-2 and satellite 110. As a result, from the perspective of UE120-1, the uplink timeline 522 and downlink timeline 524 for UE120-1 are mismatched. UE120-1 may determine a timing mismatch 526 between the uplink timeline 522 and the downlink timeline 524. The timing mismatch 526 may include an offset of N slots or subframes (or another amount of time domain resources, or another duration, etc.) between slot or subframe 0 of the uplink timeline 522 and slot or subframe 0 of the downlink timeline 524. In detail, the uplink timeline 522 may be shifted or adjusted in time by N slots or subframes so that UE120-1 starts the uplink transmit 528 earlier to compensate for propagation delays between UE120-1 and satellite 110. If UE120-1 is a half-duplex UE (or another type of UE that cannot perform simultaneous transmit and receive), the slots or subframes used for the uplink transmit 528 may be unavailable for downlink receive for UE120-1. Furthermore, slots, subframes or other time-domain resources on either side of the slots or subframes used for the uplink transmit 528 may be unavailable to provide a guard period for UE120-1 to transition between transmit and receive.
[0058] As further shown in Figure 5, UE120-2 may be located closer to satellite 110 than UE120-1. Therefore, the adjustment between the uplink timeline 532 and the downlink timeline 534 for UE120-2 may be relatively smaller than the adjustment for UE120-1 due to the smaller propagation delay. In these cases, UE120-2 may determine a timing mismatch 536 to compensate for the propagation delay and include ND slots or subframes, where D is at least partially based on the distance between UE120-2 and satellite 110. In detail, the uplink timeline 532 may be shifted or adjusted forward in time by N minus D(ND) slots or subframes so that UE120-2 starts the uplink transmit 538 earlier to compensate for the propagation delay between UE120-2 and satellite 110. In some cases, for a specific value of D (for example, when D=5), the same uplink subframe / slot index (N) may result in different unavailable downlink subframe / slot indices in UE120-1 and 120-2.
[0059] As described above, Figure 5 is provided as an example. Other examples may differ from those described with respect to Figure 5.
[0060] As described above, a UE in a non-terrestrial network may determine a timing mismatch between the uplink timeline and the downlink timeline for a UE associated with a satellite. However, the satellite may be unaware of the timing mismatch (for example, because at least some component of this mismatch was estimated by the UE based on, for example, its geolocation information, or satellite ephemeris information, or any combination thereof), which may cause the satellite to schedule overlapping uplink and downlink communications with the UE. These overlapping communications may be called collisions (for example, collisions between an uplink transmit for the UE and a downlink receive for the UE) if the UE cannot (or is unable to) handle simultaneous transmissions (for example, if the UE is a half-duplex UE). These collisions may cause one or more downlink communications to be dropped or unreceivable at the UE, may cause delays in uplink communications being transmitted to the satellite, may increase retransmissions between the UE and the satellite, and so on.
[0061] Several embodiments described herein provide techniques and apparatus for UE timing mismatch reporting in non-terrestrial networks. In some embodiments, a UE (e.g., UE120) may determine timing mismatch information about timing mismatches between uplink and downlink timelines for a non-terrestrial cell associated with a satellite (e.g., satellite 110, satellite 420, etc.). The UE may transmit the timing mismatch information to the satellite, which enables the satellite to schedule and / or configure communications between the UE and the satellite accordingly. In this way, the satellite may schedule and / or configure communications between the UE and the satellite in a manner that reduces and / or prevents collisions between uplink transmissions and downlink receptions for the UE. This can reduce the amount of downlink communications that are dropped or cannot be received by the UE, reduce the delay of uplink communications being transmitted to the satellite, reduce retransmissions between the UE and the satellite, and so on. The techniques and apparatus described herein may be used in NB-IoT communications, enhanced mobile broadband (eMBB) communications, and / or other types of communications.
[0062] Figure 6 shows an example 600 associated with UE timing mismatch reporting in a non-terrestrial network as described herein. As shown in Figure 6, example 600 may include communication between UE 120 and satellite 110 (e.g., satellite 420). In some embodiments, UE 120 and satellite 110 may be included in a wireless network such as wireless network 100. In some embodiments, UE 120 and satellite 110 may communicate over a wireless access link or service link 430, the service link 430 may include uplink 430-U and downlink 430-D.
[0063] In some embodiments, UE120 may be serviced by a non-terrestrial cell associated with and / or provided by satellite 110. In some embodiments, UE120 and BS110 may communicate at least partially on uplink timelines (e.g., uplink timeline 512, uplink timeline 522, uplink timeline 532, etc.) and downlink timelines (e.g., downlink timeline 514, downlink timeline 524, downlink timeline 534, etc.).
[0064] As shown by reference numeral 602 in Figure 6, UE120 may determine timing mismatch information for timing mismatches between the uplink timeline and downlink timeline for non-terrestrial cells (e.g., timing mismatch 526, timing mismatch 536, etc.) (for example, using the receiving processor 258, transmitting processor 264, controller / processor 280, memory 282, determination component 1008 in Figure 10 (described below), etc.). In some embodiments, UE120 may determine timing mismatch information based at least in part on the geolocation of UE120. Geolocation may be determined at least in part on triangulation techniques, at least in part on GPS or GNSS satellite positioning information, etc.
[0065] Timing mismatch information may include various types of information associated with the timing mismatch. For example, timing mismatch information may include instructions for the geolocation of UE120. As another example, timing mismatch information may include instructions for the timing mismatch. As described above, the timing mismatch determined by UE120 may be a relatively large timing mismatch, larger than a timing advance that can be detected by satellite 110 as part of the random access procedure and communicated to UE120.
[0066] Timing mismatch may be expressed as an offset between the uplink timeline and the downlink timeline for a non-terrestrial cell associated with satellite 110. In some embodiments, UE 120 may explicitly indicate the actual estimated or determined magnitude of the offset. For example, UE 120 may explicitly indicate the estimated or determined magnitude of the offset as a time quantity between the uplink timeline and the downlink timeline (e.g., in milliseconds, seconds, etc.), as a quantity of one or more types of time-domain resources between the uplink timeline and the downlink timeline (e.g., a quantity of slots, a quantity of subframes, a quantity of radio frames, etc.)
[0067] In some embodiments, UE120 may indicate a range that includes the offset. For example, UE120 may indicate a range of durations from which the duration of the offset is included (e.g., a range of durations that are incremented by a specific amount of time). As another example, UE120 may indicate a range of time domain resources from which the amount of time domain resources of the offset is included (e.g., a range of slot amounts, a range of subframe amounts, etc.).
[0068] As further shown in Figure 6 by reference no. 604, UE120 may transmit timing mismatch information to satellite 110 (for example, using antenna 252, transmit processor 264, TX MIMO processor 266, MOD254, controller / processor 280, memory 282, transmit component 1004 in Figure 10, etc.). UE120 may transmit timing mismatch information in one or more types of uplink communications, such as uplink control information (UCI) communications, media access control element (MAC-CE) communications, radio resource control (RRC) communications, or other types of uplink communications.
[0069] UE120 may transmit timing alignment information at various times and at least partially based on various triggers or events. For example, UE120 may transmit timing alignment information at least partially based on having received an instruction from satellite 110 to transmit timing misalignment information (e.g., using antenna 252, DEMOD 254, MIMO detector 256, receiving processor 258, controller / processor 280, memory 282, receiving component 1002 in Figure 10, etc.). The instruction may be included in downlink control information (DCI) communication, MAC-CE communication, RRC communication, physical downlink control channel (PDCCH) communication, or another type of downlink communication.
[0070] As another example, UE120 may transmit timing mismatch information on periodic or semi-persistent uplink authorizations (e.g., received from satellite 110). In these cases, UE120 may transmit timing mismatch information on uplink resources (e.g., slots, symbols, subframes, resource blocks, subcarriers, etc.) scheduled, allocated, and / or configured for UE120 in the periodic or semi-persistent uplink authorization.
[0071] As another example, the UE120 may transmit timing mismatch information based at least in part on having detected, determined, and / or identified an event. The event may include, for example, an event defined or identified in a wireless communication standard or specification, an event contained in a table or another type of data structure, an event associated with the amount of change between the most recent timing mismatch and a previously determined timing mismatch (for example, an event associated with a determination that the amount of change meets a threshold change), and / or other types of events.
[0072] In some embodiments, a collision may occur in UE 120 between the transmission of timing mismatch information to satellite 110 and the reception of a downlink transmission from satellite 110. For example, a collision may occur because satellite 110 is unaware of a timing mismatch between the uplink timeline and the downlink timeline for UE 120, resulting in satellite 110 scheduling or configuring overlapping transmissions. UE 120 may identify the collision at least in part based on determining an overlap between one or more time-domain resources (e.g., symbols, slots, subframes, etc.) to which timing mismatch information should be transmitted and one or more time-domain resources to which the downlink transmission should be received (e.g., using a receiving processor 258, a transmitting processor 264, a controller / processor 280, memory 282, a determination component 1008 in Figure 10, etc.). In some embodiments, the UE120 may identify a collision based at least in part on determining an overlap between one or more guard periods or return time domain resources on either side of one or more time domain resources to which timing mismatch information is to be transmitted and one or more time domain resources to which downlink transmissions are to be received.
[0073] In these cases, the UE120 may determine the priority associated with the downlink transmission (e.g., transmit priority, quality of service (QoS) priority, physical channel priority, and / or other type of priority) and the priority associated with the uplink transmission to which the timing mismatch information should be transmitted (using, for example, the receive processor 258, transmit processor 264, controller / processor 280, memory 282, decision component 1008, etc.), and may decide to transmit the timing mismatch information on at least partially the basis that the priority associated with the uplink transmission is higher than the priority associated with the downlink transmission.
[0074] In some embodiments, UE120 may continue to determine and transmit timing mismatch information to satellite 110 periodically and / or aperiodically (for example, at least in part based on another event or trigger). For example, UE120 may transmit updated timing mismatch information associated with an updated timing mismatch at a given time interval, at least in part based on detecting a threshold change between the timing mismatch and the updated timing mismatch.
[0075] In this way, UE120 may determine timing mismatch information about timing mismatches between the uplink timeline and the downlink timeline for a non-terrestrial cell associated with satellite 110. UE120 may transmit the timing mismatch information to satellite 110, which enables satellite 110 to schedule and / or configure communications between UE120 and satellite 110 accordingly. In this way, satellite 110 may schedule and / or configure communications between UE120 and satellite 110 in a manner that reduces and / or prevents collisions between uplink transmissions and downlink receptions for UE120. This can reduce the amount of downlink communications that are dropped or cannot be received at UE120, reduce the delay of uplink communications being transmitted to satellite 110, reduce retransmissions between UE120 and satellite 110, and so on.
[0076] As described above, Figure 6 is provided as an example. Other examples may differ from those described with respect to Figure 6.
[0077] Figure 7 shows an example 700 associated with UE timing mismatch reporting in a non-terrestrial network as described herein. As shown in Figure 7, example 700 may include communication between UE 120 and satellite 110 (e.g., satellite 420). In some embodiments, UE 120 and satellite 110 may be included in a wireless network such as wireless network 100. In some embodiments, UE 120 and satellite 110 may communicate over a wireless access link or service link 430, the service link 430 may include uplink 430-U and downlink 430-D.
[0078] In some embodiments, UE120 may be serviced by a non-terrestrial cell associated with and / or provided by satellite 110. In some embodiments, UE120 and BS110 may communicate at least partially on uplink timelines (e.g., uplink timeline 512, uplink timeline 522, uplink timeline 532, etc.) and downlink timelines (e.g., downlink timeline 514, downlink timeline 524, downlink timeline 534, etc.).
[0079] As shown by reference numeral 702 in Figure 7, UE120 may receive instructions to transmit an uncompensated uplink signal to satellite 110 (using, for example, antenna 252, DEMOD 254, MIMO detector 256, receiving processor 258, controller / processor 280, memory 282, receiving component 1002, etc.). In some embodiments, UE120 may receive instructions in downlink communications from satellite 110, such as DCI communications, MAC-CE communications, RRC communications, PDCCH communications, and / or other types of downlink communications. The uncompensated uplink signal may be an uplink signal that UE120 will transmit without adjustment based at least in part on a timing mismatch (determined by UE120) between the uplink timeline and the downlink timeline for a non-terrestrial cell associated with satellite 110.
[0080] As further shown in Figure 7 by reference no. 704, UE120 may transmit an uncompensated uplink signal to satellite 110, at least in part, based on having received instructions (e.g., using antenna 252, transmit processor 264, TX MIMO processor 266, MOD254, controller / processor 280, memory 282, transmit component 1004, etc.). In some embodiments, UE120 may transmit an uncompensated uplink signal as part of a Random Access Channel (RACH) procedure or an Initial Access procedure. For example, UE120 may transmit a RACH preamble transmission over a Physical Random Access Channel (PRACH) during a RACH procedure.
[0081] In this way, satellite 110 may receive an uncompensated uplink signal, measure the uncompensated uplink signal to determine a timing mismatch for UE 120, and schedule communication with UE 120 based at least in part on the timing mismatch.
[0082] As described above, Figure 7 is provided as an example. Other examples may differ from those described with respect to Figure 7.
[0083] Figure 8 shows an exemplary process 800 performed by, for example, a UE, as described in this disclosure. The exemplary process 800 is an example of an operation performed by a UE (e.g., UE120) in a non-terrestrial network that is associated with UE timing mismatch reporting.
[0084] As shown in Figure 8, in some embodiments, process 800 may include determining timing mismatch information about timing mismatches between uplink timelines and downlink timelines associated with a non-terrestrial cell (block 810). For example, a UE (e.g., using a receive processor 258, a transmit processor 264, a controller / processor 280, memory 282, a determination component 1008, etc.) may determine timing mismatch information about timing mismatches between uplink timelines and downlink timelines associated with a non-terrestrial cell, as described above.
[0085] As further shown in Figure 8, in some embodiments, process 800 may include transmitting timing mismatch information to a satellite associated with the non-terrestrial cell (block 820). For example, a UE (e.g., using antenna 252, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280, memory 282, transmit component 1004, etc.) may transmit timing mismatch information to a satellite associated with the non-terrestrial cell as described above.
[0086] Process 800 may include additional embodiments, such as any single embodiment or any combination of embodiments, as described below and / or elsewhere in this specification with respect to one or more other processes.
[0087] In the first embodiment, the timing mismatch information includes at least one of a timing mismatch instruction or a UE geolocation instruction. In the second embodiment, either alone or in combination with the first embodiment, the timing mismatch information includes a timing mismatch instruction, and the timing mismatch information instruction includes an offset instruction between the uplink timeline and the downlink timeline. In the third embodiment, either alone or in combination with one or more of the first and second embodiments, the offset is expressed as at least one of a slot amount between the uplink timeline and the downlink timeline, a subframe amount between the uplink timeline and the downlink timeline, a radio frame amount between the uplink timeline and the downlink timeline, or a time amount between the uplink timeline and the downlink timeline.
[0088] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the offset instruction is provided from among a plurality of candidate offsets configured for the UE. In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the process 800 includes determining a measured offset (for example, using a receiving processor 258, a transmitting processor 264, a controller / processor 280, a memory 282, a decision component 1008, etc.) and selecting a candidate offset from among a plurality of candidate offsets that is closest to the measured offset as an offset for timing mismatch. In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the offset is indicated as a duration range from a plurality of duration ranges or as a time domain resource range from a plurality of time domain resource ranges.
[0089] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the process 800 includes identifying a collision between the transmission of an uplink transmission containing timing mismatch information and the reception of a downlink transmission (for example, using the receiving processor 258, transmitting processor 264, controller / processor 280, memory 282, etc.) and deciding to transmit the timing mismatch information (for example, using the receiving processor 258, transmitting processor 264, controller / processor 280, memory 282, decision component 1008, etc.) on at least partially based on the fact that the priority associated with the uplink transmission is higher than the priority associated with the downlink transmission.
[0090] In the eighth aspect, transmitting timing mismatch information, either alone or in combination with one or more of the first to seventh aspects, includes transmitting timing mismatch information in at least one of UCI communication, MAC-CE communication, or RRC communication (for example, using the controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, memory 282, transmit component 1004, etc.). In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the process 800 includes determining updated timing mismatch information about updated timing mismatches between uplink and downlink timelines associated with a satellite (using, for example, a receiving processor 258, a transmitting processor 264, a controller / processor 280, a memory 282, a determination component 1008, etc.) and transmitting the updated timing mismatch information to the satellite (using, for example, a controller / processor 280, a transmitting processor 264, a TX MIMO processor 266, a MOD 254, an antenna 252, a memory 282, a transmission component 1004, etc.).
[0091] In the tenth aspect, transmitting timing mismatch information, either alone or in combination with one or more of the first to ninth aspects, includes transmitting timing mismatch information based at least in part on having received an instruction to transmit timing mismatch information in at least one of DCI communication, MAC-CE communication, or RRC communication (for example, using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, memory 282, transmit component 1004, etc.). In the eleventh aspect, transmitting timing mismatch information, either alone or in combination with one or more of the first to tenth aspects, includes transmitting timing mismatch information on periodic or semi-persistent uplink authorization (for example, using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, memory 282, transmit component 1004, etc.).
[0092] In the twelfth aspect, transmitting timing mismatch information, either alone or in combination with one or more of the first to eleventh aspects, includes transmitting timing mismatch information at least in part on an event (for example, using the controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, memory 282, transmit component 1004, etc.), wherein the event includes transmitting an event that is a specified event, or at least one of the changes between timing mismatch information that satisfies a threshold and previous timing mismatch information. In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the UE and the satellite communicate using NB-IoT communication and / or eMBB communication.
[0093] Figure 8 shows an exemplary block of process 800, but in some embodiments, process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the block shown in Figure 8. Additionally or alternatively, two or more blocks of process 800 may be executed in parallel.
[0094] Figure 9 shows an exemplary process 900 performed by, for example, a UE, as described in this disclosure. The exemplary process 900 is an example of an operation performed by a UE (e.g., UE120) in a non-terrestrial network that is associated with UE timing mismatch reporting.
[0095] As shown in Figure 9, in some embodiments, process 900 may include receiving instructions to transmit an uncompensated uplink signal to a satellite associated with a non-terrestrial cell (block 910). For example, a UE (e.g., using antenna 252, DEMOD 254, MIMO detector 256, receiving processor 258, controller / processor 280, memory 282, receiving component 1002, etc.) may receive instructions to transmit an uncompensated uplink signal to a satellite associated with a non-terrestrial cell, as described above.
[0096] As further shown in Figure 9, in some embodiments, process 900 may include transmitting an uncompensated uplink signal to the satellite, at least in part on the basis of having received instructions, such that the uncompensated uplink signal is not adjusted, at least in part on the basis of timing mismatches between the uplink timeline and downlink timeline associated with the non-terrestrial cell (block 920). For example, a UE (e.g., using a transmit processor 264, a TX MIMO processor 266, a MOD 254, an antenna 252, a controller / processor 280, a memory 282, a transmit component 1004, etc.) may transmit an uncompensated uplink signal to the satellite, at least in part on the basis of having received instructions, as described above. In some embodiments, the uncompensated uplink signal is not adjusted, at least in part on the basis of timing mismatches between the uplink timeline and downlink timeline associated with the non-terrestrial cell.
[0097] Process 900 may include additional embodiments, such as any single embodiment or any combination of embodiments, as described below and / or elsewhere in this specification with respect to one or more other processes.
[0098] In the first aspect, receiving instructions includes receiving instructions in PDCCH communication (e.g., using antenna 252, DEMOD 254, MIMO detector 256, receiving processor 258, controller / processor 280, memory 282, receiving component 1002, etc.). In the second aspect, transmitting an uncompensated uplink signal, either alone or in combination with the first aspect, includes transmitting an uncompensated uplink signal as part of a Random Access Channel (RACH) procedure (e.g., using controller / processor 280, transmitting processor 264, TX MIMO processor 266, MOD 254, antenna 252, memory 282, transmitting component 1004, etc.). In the third aspect, either alone or in combination with one or more of the first and second aspects, the uncompensated uplink signal includes a Random Access Channel preamble transmission over PRACH. In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the UE and the satellite communicate using NB-IoT communication and / or eMBB communication.
[0099] Figure 9 shows an exemplary block of process 900, but in some embodiments, process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the block shown in Figure 9. Additionally or alternatively, two or more blocks of process 900 may be executed in parallel.
[0100] Figure 10 is a block diagram of an exemplary device 1000 for wireless communication. Device 1000 may be a UE (e.g., UE120), or a UE may include device 1000. In some embodiments, device 1000 includes a receiving component 1002 and a transmitting component 1004, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1000 may use the receiving component 1002 and the transmitting component 1004 to communicate with another device 1006 (such as UE120, base station 110, satellite 110, satellite 420, or another wireless communication device). As further shown, device 1000 may include a determining component 1008.
[0101] In some embodiments, the device 1000 may be configured to perform one or more operations described herein with respect to Figure 6 and / or Figure 7. Additionally or alternatively, the device 1000 may be configured to perform one or more processes described herein, such as process 800 in Figure 8, process 900 in Figure 9, or a combination thereof. In some embodiments, one or more components shown in the device 1000 and / or Figure 10 may include one or more components of the UE described above with respect to Figure 2. Additionally or alternatively, one or more components shown in Figure 10 may be implemented within one or more components described above with respect to Figure 2. Additionally or alternatively, one or more components of a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code, stored on a non-temporary computer-readable medium, that can be executed by a controller or processor to perform the function or operation of the component.
[0102] The receiving component 1002 may receive communications from the device 1006, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some embodiments, the receiving component 1002 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) and provide the processed signals to one or more other components of the device 1006. In some embodiments, the receiving component 1002 may include one or more antennas 252, DEMOD 254, MIMO detector 256, receiving processor 258, controller / processor 280, memory 282, or a combination thereof, of the UE 120 described above with respect to Figure 2.
[0103] The transmitting component 1004 may transmit communications such as reference signals, control information, data communications, or a combination thereof to the device 1006. In some embodiments, one or more other components of the device 1006 may generate communications and provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some embodiments, the transmitting component 1004 may perform signal processing on the generated communications (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 1006. In some embodiments, the transmitting component 1004 may include one or more antennas 252, MOD 254, transmitting processor 264, TX MIMO processor 266, controller / processor 280, memory 282, or a combination thereof of the UE 120 described above with respect to Figure 2. In some embodiments, the transmitting component 1004 may collate with the receiving component 1002 in the transceiver.
[0104] In some embodiments, the determination component 1008 determines timing mismatch information about timing mismatches between the uplink timeline and downlink timeline associated with the non-terrestrial cell. In some embodiments, the transmission component 1004 may transmit the timing mismatch information to the device 1006 associated with the non-terrestrial cell. In some embodiments, the reception component 1002 may receive instructions to transmit an uncompensated uplink signal to the device 1006 associated with the non-terrestrial cell. In some embodiments, the transmission component 1004 may transmit an uncompensated uplink signal to the device 1006, at least in part, based on having received the instructions.
[0105] The determination component 1008 may include memory. In some embodiments, the determination component 1008 may include the receive processor 258, transmit processor 264, controller / processor 280, memory 282, or a combination thereof of the UE 120 as described above with respect to Figure 2. The determination component 1008 may include one or more instructions that cause the UE to determine timing mismatch information regarding timing mismatches between uplink timelines and downlink timelines associated with a non-terrestrial cell when executed by one or more processors of the UE. The determination component 1008 may include means for determining timing mismatch information regarding timing mismatches between uplink timelines and downlink timelines associated with a non-terrestrial cell.
[0106] The number and arrangement of components shown in Figure 10 are provided as an example. In practice, there may be additional components, fewer components, different components, or components arranged differently compared to the components shown in Figure 10. Furthermore, two or more components shown in Figure 10 may be implemented within a single component, or a single component shown in Figure 10 may be implemented as multiple distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 10 may perform one or more functions that are described as being performed by another set of components shown in Figure 10.
[0107] The following provides an overview of some aspects of this disclosure.
[0108] Embodiment 1: A method for wireless communication performed by a user device (UE), comprising the steps of determining timing mismatch information about a timing mismatch between an uplink timeline and a downlink timeline associated with a non-terrestrial cell, and transmitting the timing mismatch information to a satellite associated with the non-terrestrial cell.
[0109] Embodiment 2: The method of Embodiment 1, wherein the timing mismatch information includes at least one of a timing mismatch instruction or a geolocation instruction for the UE. Embodiment 3: The method of Embodiment 1 or 2, wherein the timing mismatch information includes a timing mismatch instruction, and the instruction in the timing mismatch information includes an instruction for an offset between the uplink timeline and the downlink timeline.
[0110] Embodiment 4: The method of Embodiment 3, wherein the offset is expressed as at least one of the following: the amount of a slot between the uplink timeline and the downlink timeline, the amount of a subframe between the uplink timeline and the downlink timeline, the amount of a radio frame between the uplink timeline and the downlink timeline, or the amount of time between the uplink timeline and the downlink timeline. Embodiment 5: The method of Embodiment 3 or 4, wherein the offset instruction is provided from among a plurality of candidate offsets configured for the UE.
[0111] Embodiment 6: The method of Embodiment 5, further comprising the steps of determining a measured offset and selecting a candidate offset from a plurality of candidate offsets closest to the measured offset as an offset for timing mismatch.
[0112] Embodiment 7: Any method of Embodiments 3 to 6, wherein the offset is expressed as a duration range from a plurality of duration ranges or as a time domain resource range from a plurality of time domain resource ranges. Embodiment 8: Any method of Embodiments 1 to 7, further comprising the steps of identifying a collision between the transmission of an uplink transmission containing timing mismatch information and the reception of a downlink transmission, and deciding to transmit the timing mismatch information on at least in part the fact that the priority associated with the uplink transmission is higher than the priority associated with the downlink transmission.
[0113] Embodiment 9: Any method of Embodiments 1 to 8, wherein the step of transmitting timing mismatch information includes transmitting timing mismatch information in at least one of uplink control information (UCI) communication, medium access control element (MAC-CE) communication, or radio resource control (RRC) communication. Embodiment 10: Any method of Embodiments 1 to 9, further comprising the steps of determining updated timing mismatch information for an updated timing mismatch between an uplink timeline and a downlink timeline associated with a satellite, and transmitting the updated timing mismatch information to the satellite.
[0114] Embodiment 11: Any method of Embodiments 1 to 10, wherein the step of transmitting timing mismatch information includes transmitting timing mismatch information at least in part on having received an instruction to transmit timing mismatch information in at least one of downlink control information (DCI) communication, media access control element (MAC-CE) communication, or radio resource control (RRC) communication. Embodiment 12: Any method of Embodiments 1 to 11, wherein the step of transmitting timing mismatch information includes transmitting timing mismatch information on periodic or semi-persistent uplink authorization.
[0115] Embodiment 13: Any method from Embodiments 1 to 12, wherein the step of transmitting timing mismatch information includes transmitting timing mismatch information at least in part based on an event, wherein the event includes at least one of a specified event or a change between timing mismatch information that satisfies a threshold and previous timing mismatch information.
[0116] Embodiment 14: A method of wireless communication performed by a user device (UE), comprising: receiving an instruction to transmit an uncompensated uplink signal to a satellite associated with a non-terrestrial cell; and transmitting an uncompensated uplink signal to the satellite, at least in part on having received the instruction, wherein the uncompensated uplink signal is not adjusted, at least in part on a timing mismatch between an uplink timeline and a downlink timeline associated with a non-terrestrial cell.
[0117] Embodiment 15: The method of Embodiment 14, wherein the step of receiving instructions includes the step of receiving instructions in physical downlink control channel (PDCCH) communication. Embodiment 16: The method of Embodiment 14 or 15, wherein the step of transmitting uncompensated uplink signals includes the step of transmitting uncompensated uplink signals as part of a random access channel (RACH) procedure.
[0118] Embodiment 17: The method of Embodiment 16, wherein the uncompensated uplink signal includes a RACH preamble transmission over a physical random access channel (PRACH). Embodiment 18: Any method of Embodiments 14 to 18, wherein the UE and the satellite communicate using narrowband Internet of Things (NB-IoT) communication and / or enhanced mobile broadband (eMBB) communication.
[0119] Embodiment 19: A device for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the device to perform one or more methods from Embodiments 1 to 13. Embodiment 20: A device for wireless communication, comprising a memory, and one or more processors coupled to the memory, wherein one or more processors are configured to perform one or more methods from Embodiments 1 to 13. Embodiment 21: A device for wireless communication, comprising at least one means for performing one or more methods from Embodiments 1 to 13.
[0120] Embodiment 22: A non-temporary computer-readable medium for storing code for wireless communication, wherein the code includes instructions that can be executed by a processor to perform one or more of the methods of Embodiments 1 to 13. Embodiment 23: A non-temporary computer-readable medium for storing a set of instructions for wireless communication, wherein the set of instructions includes one or more instructions that, when executed by one or more processors of the device, cause the device to perform one or more of the methods of Embodiments 1 to 13.
[0121] Embodiment 24: A device for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the device to perform one or more methods from Embodiments 14 to 18. Embodiment 25: A device for wireless communication, comprising a memory, and one or more processors coupled to the memory, wherein one or more processors are configured to perform one or more methods from Embodiments 14 to 18. Embodiment 26: A device for wireless communication, comprising at least one means for performing one or more methods from Embodiments 14 to 18.
[0122] Embodiment 27: A non-temporary computer-readable medium for storing code for wireless communication, wherein the code includes instructions that can be executed by a processor to perform one or more of the methods of Embodiments 14 to 18. Embodiment 28: A non-temporary computer-readable medium for storing a set of instructions for wireless communication, wherein the set of instructions includes one or more instructions that, when executed by one or more processors of the device, cause the device to perform one or more of the methods of Embodiments 14 to 18.
[0123] The foregoing disclosures are illustrative and explanatory, but are not intended to be exhaustive or to limit the embodiments to the exact forms disclosed. Modifications and variations may be made in light of the foregoing disclosures or derived from the practice of the embodiments.
[0124] As used herein, the term “Components” is broadly interpreted as hardware and / or combinations of hardware and software. “Software” is broadly interpreted as meaning, among other things, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The processors used herein are implemented in hardware and / or combinations of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited to their embodiments. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It should be understood that software and hardware may be designed to implement the systems and / or methods based at least in part on the descriptions herein.
[0125] As used herein, "meeting a threshold" may mean, depending on the context, that a value is greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold.
[0126] Where particular combinations of features are enumerated in the claims and / or disclosed herein, these combinations do not limit the disclosure of various embodiments. In practice, many of these features may be combined in ways not specifically enumerated in the claims and / or disclosed herein. Each dependent claim described below may depend directly on only one claim, but the disclosure of various embodiments includes each dependent claim combined with any other claims in the claim set. The phrase “at least one of” the list of items used herein refers to any combination of those items, including a single member. For example, “at least one of a, b, or c” shall cover a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, and c).
[0127] None of the elements, actions, or commands used herein should be construed as important or essential unless expressly stated otherwise. Furthermore, the articles “a” and “an” as used herein include one or more items and may be used interchangeably with “one or more.” Additionally, the article “the” as used herein includes one or more items referred to with the article “the” and may be used interchangeably with “one or more.” Furthermore, the terms “set” and “group” as used herein include one or more items (for example, related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with “one or more.” When only one item is intended, the phrase “only one” or similar words should be used. Also, terms such as “has,” “have,” and “having” as used herein are open-ended terms. Furthermore, the phrase “based on” means “at least partially based on” unless otherwise specified. Furthermore, as used herein, the term "or" is inclusive when used consecutively and may be used interchangeably with "and / or" unless otherwise specified (for example, when used in combination with "either" or "only one of"). [Explanation of symbols]
[0128] 100 Wireless Networks 102a Macrocell 102b picocell 102c femtocell 110 base stations, satellites, ground-based BS, satellite BS 110a BS, Macro BS 110b BS 110c BS 110d BS, Relay BS 110f BS, non-terrestrial BS, satellite 120 UE 120-1 UE 120-2 UE 120a UE 120b UE 120c UE 120d UE 120e UE 130 Network Controllers 200 cases 212 data sources 220 Transmitting Processors 230 Transmit (TX) Multiple Input Multiple Output (MIMO) Processor, TX MIMO Processor 232 Modulators, Demodulators, MOD / DEMOD, MOD 234 Antenna 236 MIMO detector 238 receiving processors 239 Data Sync 240 Controllers / Processors 242 memory 244 Communication Unit 246 Scheduler 252 Antenna 254 Demodulator, Modulator, MOD / DEMOD, MOD, DEMOD 256 MIMO detector 258 receiving processors 260 Data Sync 262 data sources 264 Transmitting Processors 266 TX MIMO processor 280 Controllers / Processors 282 memory 284 Housing 290 Controllers / Processors 292 memory 294 Communication Unit 300 cases 400 cases 410 examples 430 Service Link 430-D Downlink 430-U Uplink 440 satellite 450 Gateways 460 Feeder Link 460-D Downlink 460-U Uplink 500 cases 512 Uplink Timeline 514 Downlink Timeline 522 Uplink Timeline 524 Downlink Timeline 526 Timing mismatch 528 Uplink transmission 532 Uplink Timeline 534 Downlink Timeline 536 Timing mismatch 538 Uplink transmission 600 cases 700 cases 800 processes 900 processes 1000 devices 1002 Receiving components 1004 Transmitting Components 1006 Equipment 1008 Determination Components
Claims
1. User equipment (UE) for wireless communication, Memory and The system comprises one or more processors coupled to the memory, and the one or more processors To determine timing mismatch information regarding timing mismatches between the uplink timeline and downlink timeline associated with a non-terrestrial cell, Transmitting the aforementioned timing mismatch information to the satellite associated with the non-terrestrial cell. A UE configured to perform the following actions.
2. The aforementioned timing mismatch information, Instructions for the aforementioned timing mismatch, or Instructions for the geolocation of the aforementioned UE The UE according to claim 1, comprising at least one of the following.
3. The timing mismatch information includes an instruction for the timing mismatch, The instruction for the timing mismatch information includes an instruction for an offset between the uplink timeline and the downlink timeline. The UE according to claim 1.
4. The aforementioned offset is, The amount of slot between the uplink timeline and the downlink timeline, The amount of subframes between the uplink timeline and the downlink timeline, The amount of wireless frames between the uplink timeline and the downlink timeline, or The amount of time between the uplink timeline and the downlink timeline The UE according to claim 3, as shown as at least one of the following.
5. The UE according to claim 3, wherein the instruction for the offset is provided from among a plurality of candidate offsets configured for the UE.
6. The one or more processors described above Determining the measured offset, As the offset for the timing mismatch, a candidate offset is selected from among the multiple candidate offsets that are closest to the measured offset. The UE according to claim 5, further configured to perform the following.
7. The UE according to claim 3, wherein the offset is indicated as a duration range from a plurality of duration ranges or as a time domain resource range from a plurality of time domain resource ranges.
8. The one or more processors described above Identifying a collision between the transmission of an uplink transmission containing the aforementioned timing mismatch information and the reception of a downlink transmission, The decision to transmit the timing mismatch information is made, at least in part, based on the fact that the priority associated with the uplink transmission is higher than the priority associated with the downlink transmission. The UE according to claim 1, further configured to perform the following:
9. The one or more processors described above To determine updated timing mismatch information regarding the updated timing mismatch between the uplink timeline and the downlink timeline associated with the satellite, Transmit the updated timing mismatch information to the satellite. The UE according to claim 1, further configured to perform the following:
10. The one or more processors transmit the timing mismatch information, Transmitting the timing mismatch information on periodic or semi-permanent uplink authorizations. The UE according to claim 1, configured as follows.
11. The one or more processors transmit the timing mismatch information, Transmitting the timing mismatch information based at least partially on the event, The aforementioned event, A specified event, or The amount of change between the timing mismatch information that satisfies the threshold and the previous timing mismatch information. Sending at least one of the following The UE according to claim 1, configured to perform the following:
12. A UE for wireless communications, Memory and The system comprises one or more processors coupled to the memory, and the one or more processors Receiving instructions to transmit uncompensated uplink signals to satellites associated with non-terrestrial cells, Transmitting the uncompensated uplink signal to the satellite, at least in part, based on having received the aforementioned instructions. The uncompensated uplink signal is transmitted without being adjusted at least partially based on timing mismatches between the uplink timeline and downlink timeline associated with the non-terrestrial cell. A UE configured to perform the following actions.
13. The one or more processors, in order to receive the instruction, Receiving the instruction in physical downlink control channel (PDCCH) communication The UE according to claim 12, configured as follows.
14. The one or more processors transmit the uncompensated uplink signal, Transmitting the uncompensated uplink signal as part of the Random Access Channel (RACH) procedure The UE according to claim 12, configured as follows.
15. The UE according to claim 14, wherein the uncompensated uplink signal includes a RACH preamble transmission on a physical random access channel (PRACH).
16. A method of wireless communication performed by a user device (UE), A step of determining timing mismatch information regarding timing mismatches between uplink timelines and downlink timelines associated with a non-terrestrial cell, The steps include: transmitting the timing mismatch information to the satellite associated with the non-terrestrial cell; Methods that include...
17. The aforementioned timing mismatch information, Instructions for the aforementioned timing mismatch, or Instructions for the geolocation of the aforementioned UE The method according to claim 16, comprising at least one of the following.
18. The timing mismatch information includes an instruction for the timing mismatch, The instruction for the timing mismatch information includes an instruction for an offset between the uplink timeline and the downlink timeline. The method according to claim 16.
19. The aforementioned offset is, The amount of slot between the uplink timeline and the downlink timeline, The amount of subframes between the uplink timeline and the downlink timeline, The amount of wireless frames between the uplink timeline and the downlink timeline, or The amount of time between the uplink timeline and the downlink timeline The method according to claim 18, as shown as at least one of the following.
20. The method according to claim 18, wherein the instruction for the offset is provided from among a plurality of candidate offsets configured for the UE.
21. The steps include determining the measured offset, The steps include selecting a candidate offset from among the plurality of candidate offsets that is closest to the measured offset as the offset for the timing mismatch, The method according to claim 20, further comprising:
22. The method according to claim 18, wherein the offset is indicated as a duration range from a plurality of duration ranges or as a time domain resource range from a plurality of time domain resource ranges.
23. The steps include identifying a collision between the transmission of an uplink transmission and the reception of a downlink transmission that includes the aforementioned timing mismatch information, A step of deciding to transmit the timing mismatch information, at least in part, based on the fact that the priority associated with the uplink transmission is higher than the priority associated with the downlink transmission. The method according to claim 16, further comprising:
24. The steps include determining updated timing mismatch information for an updated timing mismatch between the uplink timeline and the downlink timeline associated with the satellite, The steps include transmitting the updated timing mismatch information to the satellite. The method according to claim 16, further comprising:
25. The step of transmitting the aforementioned timing mismatch information is: Steps to transmit the timing mismatch information on a periodic or semi-permanent uplink authorization. The method according to claim 16, including the method described in claim 16.
26. The step of transmitting the aforementioned timing mismatch information is: A step of transmitting the timing mismatch information based at least partially on the event, The aforementioned event, A specified event, or The amount of change between the timing mismatch information that satisfies the threshold and the previous timing mismatch information. Steps including at least one of the following The method according to claim 16, including the method described in claim 16.
27. A method of wireless communication performed by a user device (UE), The steps include receiving instructions to transmit an uncompensated uplink signal to a satellite associated with a non-terrestrial cell, A step of transmitting the uncompensated uplink signal to the satellite, at least in part, based on having received the aforementioned instructions, The uncompensated uplink signal is not adjusted, at least in part, based on timing mismatches between the uplink timeline and downlink timeline associated with the non-terrestrial cell, and Methods that include...
28. The step of receiving the instruction is, The step of receiving the instruction in physical downlink control channel (PDCCH) communication. The method according to claim 27, including the method described in claim 27.
29. The step of transmitting the uncompensated uplink signal is The step of transmitting the uncompensated uplink signal as part of a Random Access Channel (RACH) procedure. The method according to claim 27, including the method described in claim 27.
30. The method according to claim 29, wherein the uncompensated uplink signal includes a RACH preamble transmission on a physical random access channel (PRACH).