Configurable timing advance command granularity

Abstract

A user equipment (UE) may transmit a first message including a first indication associated with a timing advance command (TAC) granularity. The network node may receive the first message. The network node may send a second message including a TAC configuration associated with the TAC granularity based on the first indication. The network node may send the second message in response to receiving the first message. The UE may receive the second message. The network node may transmit the TAC. The UE may receive the TAC. The UE may transmit a third message based on the TAC configuration. The UE may transmit the third message in response to receiving the TAC. The network node may receive the third message. The network node may be a non-terrestrial network node, such as a satellite or near-earth orbit device.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 18 / 170,486, filed on February 16, 2023, entitled “CONFIGURABLE TIMING ADVANCE COMMAND GRANULARITY,” which is expressly incorporated herein by reference in its entirety. Background Art

[0003] The present disclosure relates generally to communication systems and, more particularly, to a system for configuring timing for transmissions between wireless devices.

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Non-limiting 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, national, regional, and even global level. A non-limiting example telecommunication standard is 5G New Radio (NR). 5G NR is part of the ongoing mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects. This summary does not identify key or critical elements of all aspects, nor does it delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that will be presented later.

[0007] In one aspect of the present disclosure, a method for wireless communication at a user equipment (UE) is provided. The method may include sending a first message including a first indication associated with a timing advance command (TAC) granularity. The method may include receiving a second message including a TAC configuration associated with the TAC granularity. The method may include sending a third message based on the TAC configuration.

[0008] In another aspect of the present disclosure, an apparatus for wireless communication is provided. The apparatus may be a UE, comprising a memory and at least one processor coupled to the memory. The at least one processor may be configured to send a first message including a first indication associated with a TAC granularity. The at least one processor may also be configured to receive a second message including a TAC configuration associated with the TAC granularity. The at least one processor may also be configured to send a third message based on the TAC configuration.

[0009] In another aspect of the present disclosure, an apparatus for wireless communication at a UE is provided. The apparatus may include means for sending a first message including a first indication associated with a TAC granularity. The apparatus may include means for receiving a second message including a TAC configuration associated with the TAC granularity. The apparatus may include means for sending a third message based on the TAC configuration.

[0010] In another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer-executable code for wireless communication at a UE is provided. When executed, the code may cause a processor to send a first message including a first indication associated with a TAC granularity. When executed, the code may cause the processor to receive a second message including a TAC configuration associated with the TAC granularity. When executed, the code may cause the processor to send a third message based on the TAC configuration.

[0011] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include a UE. The apparatus may send a first message including a first indication associated with a TAC granularity. The apparatus may receive a second message including a TAC configuration associated with the TAC granularity. The apparatus may send a third message based on the TAC configuration.

[0012] In one aspect of the present disclosure, a method for wireless communication at a network node is provided. The method may include receiving a first message including a first indication associated with a TAC granularity. The method may include sending a second message including a TAC configuration associated with the TAC granularity based on the first indication. The method may include sending a TAC. The method may include receiving a third message based on the TAC configuration in response to receiving the TAC.

[0013] In another aspect of the present disclosure, an apparatus for wireless communication is provided. The apparatus may be a network node comprising a memory and at least one processor coupled to the memory. The at least one processor may be configured to receive a first message comprising a first indication associated with a TAC granularity. The at least one processor may also be configured to send a second message comprising a TAC configuration associated with the TAC granularity based on the first indication. The at least one processor may also be configured to send a TAC. The at least one processor may also be configured to receive a third message based on the TAC configuration in response to receiving the TAC.

[0014] In another aspect of the present disclosure, an apparatus for wireless communication at a network node is provided. The apparatus may include means for receiving a first message including a first indication associated with a TAC granularity. The apparatus may include means for sending a second message including a TAC configuration associated with the TAC granularity based on the first indication. The apparatus may include means for sending a TAC. The apparatus may include means for receiving a third message based on the TAC configuration in response to receiving the TAC.

[0015] In another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer-executable code for wireless communication at a UE is provided. When executed, the code may cause a processor to receive a first message including a first indication associated with a TAC granularity. When executed, the code may cause the processor to send a second message including a TAC configuration associated with the TAC granularity based on the first indication. When executed, the code may cause the processor to send a TAC. When executed, the code may cause the processor to receive a third message based on the TAC configuration in response to receiving the TAC.

[0016] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus are provided. The network node may be a base station communicating with a UE via an NTN node. The apparatus may receive a first message including a first indication associated with a TAC granularity. The apparatus may, based on the first indication, send a second message including a TAC configuration associated with the TAC granularity. The apparatus may send a TAC. In response to receiving the TAC, the apparatus may receive a third message based on the TAC configuration.

[0017] To achieve the foregoing and related ends, one or more aspects may include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a diagram illustrating a non-limiting example of a wireless communication system and an access network (NW).

[0019] Figure 2 is a diagram illustrating a non-limiting example of a wireless communication system and an access network.

[0020] Figure 3A is a diagram illustrating a non-limiting example of a first frame according to various aspects of the present disclosure.

[0021] Figure 3B is a diagram illustrating a non-limiting example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0022] Figure 3C is a diagram illustrating a non-limiting example of a second frame according to various aspects of the present disclosure.

[0023] Figure 3D is a diagram illustrating a non-limiting example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0024] Figure 4 is a diagram illustrating a non-limiting example of a base station and a user equipment (UE) in an access network.

[0025] Figure 5A 、 Figure 5B and Figure 5C Non-limiting example aspects of a network architecture supporting communications via NTN devices according to various aspects of the present disclosure are illustrated.

[0026] Figure 6 Non-limiting examples of NTN configurations according to various aspects of the present disclosure are illustrated.

[0027] Figure 7A A non-limiting example of a UE sending a signal to an NTN device according to various aspects of the present disclosure is illustrated.

[0028] Figure 7B A non-limiting example is illustrated in which a UE sends a signal to an NTN device after moving in a direction relative to the NTN device, thereby triggering a timing advance command (TAC) according to various aspects of the present disclosure.

[0029] Figure 7C A non-limiting example of a UE sending a signal to an NTN device after updating its timing advance (TA) offset according to various aspects of the present disclosure is illustrated.

[0030] Figure 8 Illustrated are timing diagrams illustrating non-limiting example aspects of timing advance calculations in accordance with various aspects presented herein.

[0031] Figure 9 Another timing diagram showing differential UE-specific timing error values ​​for TAs for communications between a UE and an NTN node is illustrated.

[0032] Figure 10 A connection flow diagram is shown, wherein a UE is configured to send uplink transmissions to a network entity via an NTN device.

[0033] Figure 11A An uplink transmission format that a UE may use to indicate TAC granularity capabilities to a network node according to various aspects of the present disclosure is illustrated.

[0034] Figure 11B A set of physical random access channel (PRACH) formats or sequences that a UE may use to indicate TAC granularity capability to a network node according to various aspects of the present disclosure is illustrated.

[0035] Figure 11C Illustrated are a set of random access channel (RACH) opportunities that a UE may use to indicate TAC granularity capabilities to a network node in accordance with various aspects of the present disclosure.

[0036] Figure 11D A set of demodulation reference signal (DMRS) or physical uplink shared channel (PUSCH) functions that a UE may use to indicate TAC granularity capabilities to a network node according to various aspects of the present disclosure is illustrated.

[0037] Figure 11E A message having a set of bits that a wireless device may use to indicate TAC granularity capability or TAC granularity is illustrated in accordance with various aspects of the present disclosure.

[0038] Figure 12is a flow chart of a method of wireless communication.

[0039] Figure 13 is a flow chart of a method of wireless communication.

[0040] Figure 14 is a flow chart of a method of wireless communication.

[0041] Figure 15 is a flow chart of a method of wireless communication.

[0042] Figure 16 are diagrams illustrating non-limiting examples of hardware implementations for non-limiting example apparatuses and / or network entities.

[0043] Figure 17 is a diagram illustrating a non-limiting example of a hardware implementation for a non-limiting example network entity.

[0044] Figure 18 is a diagram illustrating a non-limiting example of a hardware implementation for a non-limiting example network entity. DETAILED DESCRIPTION

[0045] Some wireless communications may occur between a terrestrial device (e.g., a device at or near ground level) and another device at a greater altitude, such as a non-terrestrial network node (NTN). As a non-limiting example, a UE may exchange communications with a network node at a greater altitude (e.g., greater than 20 meters) relative to the UE, such as a geostationary orbit (GEO) device, a medium Earth orbit (MEO) device, a low Earth orbit (LEO) device, an aircraft device, a balloon device, or an unmanned aerial vehicle (UAV) device. Some aspects relate more specifically to satellite-based communications with the UE, which, as a non-limiting example, may occur via an NTN node.

[0046] In some aspects, a UE communicating with another wireless device via a network node with a large altitude (such as an NTN node) may send an uplink (UL) transmission to the wireless device with a timing error. A timing error may be the difference between the time at which the UE transmission is received by the transmitting wireless device (e.g., a symbol or frame) and the time at which the UE transmission is scheduled to be received by the wireless device. Such a timing error may cause a UE-to-wireless device transmission to interfere with another transmission to the same wireless device if the actual start of the time period for the wireless device to receive the UE transmission is later than the scheduled start of the time period for the wireless device to receive the UE transmission (interfering with the later transmission to the wireless device) or if the actual start of the time period for the wireless device to receive the UE transmission is earlier than the scheduled start of the time period for the wireless device to receive the UE transmission (interfering with the earlier transmission to the wireless device). Such a timing error may occur when a UE or network node is traveling in an unexpected direction or at an unexpected differential speed, causing a transmission from the UE to the wireless device to be received within a shorter time period (i.e., earlier) or a longer time period (i.e., later) than expected at the wireless device.

[0047] As timing error increases, the chance that an UL transmission from a UE may interfere with other transmissions from other wireless devices (e.g., other UEs, other network nodes) to the same network node also increases. The network node may use a timing error threshold to detect the UE's timing error. The timing error threshold may be a timing error value that the network node uses to determine whether to request the UE to adjust its TA offset for transmissions to the network node. When the UE adjusts its TA offset, the UE reduces the timing error to zero by ensuring that the UE's transmission to the wireless device is received when the UE's transmission is scheduled to be received by the wireless device. In response to the UE's timing error meeting or exceeding the timing error threshold, the network node may send a timing advance command (TAC) to the UE. In response to receiving the TAC, the UE may use a timing advance (TA) offset (also referred to as TA) to adjust the timing of its UL transmissions. The UE may use the TA to align its transmissions with the reception schedule at the network node and prevent interference with other transmissions to network nodes that may share the same frequency band. While a small TA may be used when the UE is at a first distance from the network node, a larger TA may be used when the UE is at a second distance from the network node, where the first distance is smaller than the second distance.

[0048] In one aspect, a network node may be associated with a timing error limit, which may represent a maximum error range that the network node can tolerate before an uplink transmission from a UE interferes with other transmissions to the network node. In other words, if the timing error exceeds the timing error limit in either direction (e.g., if a UE transmission is received earlier or later than it was intended to be received), the uplink transmission from the UE may interfere with other transmissions to the network node. The network node may use a timing error threshold to minimize the likelihood that the timing error between the UE and the network node will meet or exceed the timing error limit. As a non-limiting example, in response to the timing error exceeding the timing error threshold, the network node may send a timing advance command (TAC) to the UE. In response to receiving the TAC, the UE may adjust its TA to reduce the timing error between the UE and the network node to zero. The TAC may include an integer that the UE can use to calculate a new TA value. As a non-limiting example, the integer may indicate the difference between the time the network node expects to receive a transmission from the UE and the time the network node receives the transmission from the UE. The UE may multiply the integer included in the TAC by the TAC granularity value to calculate the time difference. Since the UE can calculate the time period indicated in the TAC based on an integer multiplied by the TAC granularity value, the TAC granularity value can be considered to represent the minimum time difference that the network node can use to indicate the timing error to the UE. In other words, the smaller the TAC granularity value, the more accurately the network node can indicate the length of the time period to the UE via the integer indicated in the TAC.

[0049] In some aspects, the size of the timing error threshold may be associated with the TAC granularity value. As a non-limiting example, in some aspects, the network node may set the value of its timing error threshold to be equal to the TAC granularity value. Thus, a large TAC granularity value may represent a large timing error threshold, and a small TAC granularity value may represent a small timing error threshold. If the timing error threshold is too high, the timing error between the network node and the UE may easily exceed the timing error limit, causing some UL transmissions from the UE to interfere with other transmissions to the network node. As a non-limiting example, if the timing error threshold is greater than the timing error limit, the network node may send a TAC to the UE after the timing error has exceeded the timing error limit. Even if the timing error threshold is greater than half the timing error limit, the network node may not send a TAC to the UE early enough for the UE to correct the timing error before the timing error exceeds the timing error limit. In addition, since the TAC granularity value may represent the minimum time difference that the network node can use to indicate the timing error to the UE, the size of the TAC granularity value may be associated with the accuracy with which the network node indicates the timing error to the UE. Given a selection, the network node may select a TAC granularity value that is less than half the timing error limit to allow for a larger error margin when indicating the timing error to the UE. However, not all network nodes or UEs may be able to select more than one TAC granularity value for calculating the timing error or calculating the TA. Some UEs and network nodes may be configured to use one TAC granularity value - the default TAC granularity value. Other UEs and network nodes may be configured to use multiple TAC granularity values. If both the UE and the network node are configured to use any of the multiple TAC granularity values, the network node may select the best TAC granularity value from the multiple TAC granularity values ​​for use by the UE and the network node. In some aspects, the UE may request the network node to use a finer TAC granularity value, which may convey the UE's preference for the network node to select a TAC granularity value that is smaller than the default TAC granularity value.

[0050] Various aspects presented herein enable a network node and a UE to use different TAC granularity values ​​based on the support and / or conditions experienced by the UE. If the TAC granularity value is too large or too small, the TAC granularity value may negatively impact the performance of transmissions from the UE to the network node. In one aspect, a network node and a UE using a first TAC granularity may cause a timing error between the UE and the network node to exceed a timing error limit of the network node. As a non-limiting example, the TAC granularity value may exceed the timing error limit of the network node, and because the timing error threshold may be equal to the TAC granularity, the network node may not send a TAC until after the timing error exceeds the timing error limit. On the other hand, a network node and a UE using a second TAC granularity may waste resources at the UE, causing the UE to readjust its transmission timing more frequently than is optimal. As a non-limiting example, a third TAC granularity value that is greater than the second TAC granularity value may be small enough to ensure that the timing error between the UE and the network node does not exceed the timing error limit of the network node. However, in the case where the TAC granularity value is equal to the timing error threshold, the network node will send TACs more frequently using the third TAC granularity value than using the second TAC granularity value. Therefore, selecting the third TAC granularity value may be more optimal than selecting the second TAC granularity value because selecting the third TAC granularity value ensures that the timing error between the UE and the network node does not exceed the timing error limit of the network node without requiring the network node / UE to send TACs as frequently to the UE as if the second TAC granularity value were selected. The ability to select between different TAC granularities (e.g., as presented herein) improves communication between the UE and the network by allowing for more dynamic TAC granularity to handle individual requests from the UE.

[0051] A network node that has the capability to use multiple TAC granularity values ​​may be configured to indicate to the UE that the network has the capability to use multiple TAC granularity values. The UE may indicate to the network node its request and / or capability to support one or more TAC granularity values ​​in addition to a single TAC granularity value. As a non-limiting example, the UE may indicate to the network node a request for a subset of TAC granularity values ​​from a set of TAC granularity values ​​that the network node may have the capability to support. In another non-limiting example, the UE may indicate to the network node that the UE is capable of supporting more than one TAC granularity value. In response to the indication, the network node may configure the TAC granularity for the UE to ensure that the timing error between the UE and the network node does not meet or exceed the timing error limit of the network node without wasting too many UE resources. The UE may then use the new TAC granularity configuration to calculate its TA.

[0052] In some aspects, a UE may send a first message including a first indication associated with a TAC granularity. A network node may receive the first message. The network node may, based on the first indication, send a second message including a TAC configuration associated with the TAC granularity. The network node may send the second message in response to receiving the first message. The UE may receive the second message. The network node may send a TAC. The UE may receive the TAC. The UE may send a third message based on the TAC configuration. The UE may send the third message in response to receiving the TAC. The network node may receive the third message.

[0053] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. The various aspects disclosed herein facilitate UEs and network nodes to use smaller or larger TAC granularity based on the requests and / or capabilities of the UE and network node, while ensuring that such wireless devices are also backward compatible. This flexibility may be useful for UEs communicating with NTN nodes because if the UE is closer to the NTN node, it may be optimal for the UE to use a larger TAC granularity, while if the UE is further away from the NTN node, it may be optimal for the UE to use a smaller TAC granularity. By optimizing the size of the TAC granularity, the network can maintain low timing error between the UE and the network node, which can reduce the number of times the UE readjusts the timing of its TA offset (e.g., by performing Global Navigation Satellite System (GNSS) positioning). Readjusting the timing of a UE's TA offset can consume a lot of energy, so reducing the number of times the UE readjusts the timing of its TA offset can reduce power consumption—particularly for low-power devices (e.g., Internet of Things (IoT) devices).

[0054] Although the following description provides non-limiting examples involving 5G NR, the concepts described herein may be applicable to other similar areas such as 6G, 5G-advanced, LTE, LTE-A, CDMA, GSM, and / or other wireless technologies.

[0055] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0056] Several aspects of telecommunications systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0057] As a non-limiting example, an element, or any part of an element, or any combination of elements, may be implemented as a "processing system" comprising one or more processors. Non-limiting examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, functions, or any combination thereof.

[0058] Thus, in one or more non-limiting example aspects, implementations, and / or use cases, the functionality described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. A storage medium can be any available medium that can be accessed by a computer. As non-limiting examples, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0059] While aspects, implementations, and / or use cases are described herein by way of illustration of certain non-limiting examples, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. As non-limiting examples, the aspects, implementations, and / or use cases may arise via integrated chip implementations and other non-module component-based devices (e.g., end-user devices, vehicles, communications equipment, computing devices, industrial equipment, retail / purchase equipment, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some non-limiting examples may or may not be specifically targeted at use cases or applications, the broad applicability of the described non-limiting examples may exist. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the techniques described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. As a non-limiting example, the transmission and reception of wireless signals necessarily include several components for both analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, and the like.

[0060] The deployment of a communication system, such as a 5G NR system, can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a radio access network (RAN) node, a core network node, a network element, or network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functionality can be implemented in a converged or disaggregated architecture. As non-limiting examples, a base station (such as a node B (NB), an evolved NB (eNB), a NR base station, a 5G NB, an access point (AP), a transmit / receive point (TRP), or a cell) can be implemented as a converged base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

[0061] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0062] Base station operation or network design may take into account the aggregated nature of base station functionality. As non-limiting examples, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as that promoted by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as virtually distributing the functionality of at least one unit, which can enable flexibility in network design. The various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0063] Figure 1 1 is a diagram illustrating a non-limiting example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (e.g., EPC 160), and another core network 190 (e.g., a 5G core (5GC)). Base stations 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femto cells, pico cells, and micro cells.

[0064] A base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can perform one or more of the following: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. Base stations 102 can communicate with each other directly or indirectly (eg, via EPC 160 or core network 190) via third backhaul link 134 (eg, X2 interface). First backhaul link 132, second backhaul link 184, and third backhaul link 134 can be wired or wireless.

[0065] In some aspects, a base station (e.g., one of base stations 102 or one of base stations 180) may be referred to as a RAN and may include converged or disaggregated components. As a non-limiting example of a disaggregated RAN, a base station may include a central unit (CU) (e.g., CU 106), one or more distributed units (DUs) (e.g., DU 105), and / or one or more remote units (RUs) (e.g., RU 109), as shown in FIG. Figure 1 As illustrated. The RAN can be decomposed by splitting between the RU 109 and the converged CU / DU. The RAN can be decomposed by splitting between the CU 106, DU 105, and RU 109. The RAN can be decomposed by splitting between the CU 106 and the converged DU / RU. The CU 106 and one or more DUs can be connected via an F1 interface. The DU 105 and RU 109 can be connected via a fronthaul interface. The connection between the CU 106 and the DU 105 can be referred to as midhaul, and the connection between the DU 105 and the RU 109 can be referred to as fronthaul. The connection between the CU 106 and the core network 190 can be referred to as backhaul.

[0066] The RAN may be based on a functional split between various RAN components (e.g., between the CU 106, DU 105, or RU 109). The CU 106 may be configured to perform one or more aspects of a wireless communication protocol, e.g., handling one or more layers of a protocol stack, and one or more DUs may be configured to handle other aspects of the wireless communication protocol, e.g., other layers of the protocol stack. In various implementations, the split between the layers handled by the CU and the layers handled by the DU may occur at different layers of the protocol stack. As a non-limiting example, the DU 105 may provide a logical node that hosts the radio link control (RLC) layer, the medium access control (MAC) layer, and at least a portion of the physical (PHY) layer based on the functional split. The RU may provide a logical node configured to host at least a portion of the PHY layer and radio frequency (RF) processing. The CU 106 may host, for example, higher-layer functions above the RLC layer, such as the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, and / or upper layers. In other implementations, the split between the layer functions provided by the CU, DU, or RU may vary.

[0067] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas may exist. As a non-limiting example, small cell 103 can have a coverage area 111 that overlaps with the corresponding geographic coverage area 110 of one or more base stations (e.g., one or more macro base stations, such as base station 102). A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a Home evolved Node B (eNB) (HeNB), which can provide service to a restricted group known as a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as a reverse link) transmissions from the UE to the base station and / or downlink (DL) (also known as a forward link) transmissions from the base station to the UE. Communication link 120 may utilize multiple-input, multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. This communication link may be over one or more carriers. Base station 102 / UE 104 may use spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) for each carrier allocated in the carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carriers may be referred to as secondary cells (SCells).

[0068] Certain UEs may communicate with each other using device-to-device (D2D) communication links, such as D2D communication link 158. D2D communication link 158 may use DL / UL WWAN spectrum. D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be performed via various wireless D2D communication systems, such as, by way of non-limiting example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 902.11 standard, LTE, or NR.

[0069] The wireless communication system may also include a Wi-Fi access point (AP), such as AP 150, that communicates with a Wi-Fi station (STA), such as STA 152, via a communication link 154, e.g., in the 5 GHz unlicensed spectrum, etc. When communicating in the unlicensed spectrum, STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available prior to communicating.

[0070] Small cell 103 can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 103 can adopt NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as that used by Wi-Fi AP 150. Small cell 103 adopting NR in unlicensed spectrum can improve access network coverage and / or increase access network capacity.

[0071] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, despite being distinct from the extremely high frequency (EHF) band (30 GHz–300 GHz), which is identified as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0072] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. As non-limiting examples, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz–71 GHz), FR4 (71 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0073] With the above in mind, unless otherwise specified, if the term "sub-6 GHz" or the like is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise specified, if the term "millimeter wave" or the like is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0074] A base station (whether a small cell 103 or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNBs, may operate in the traditional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When a gNB operates in millimeter wave frequencies or near-millimeter wave frequencies, base station 180 may be referred to as a millimeter wave base station. A millimeter wave base station may utilize beamforming 181 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0075] Base station 180 may transmit beamformed signals in one or more transmit directions 182 to UE 104. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 183. UE 104 may also transmit beamformed signals in one or more transmit directions to base station 180. Base station 180 may receive beamformed signals in one or more receive directions from UE 104. Base station 180 and UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 and UE 104. The transmit and receive directions of base station 180 may or may not be the same. The transmit and receive directions of UE 104 may or may not be the same.

[0076] EPC 160 may include a mobility management entity (e.g., MME 162), other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway (e.g., PDN gateway 172). MME 162 may communicate with a home subscriber server (HSS) (e.g., HSS 174). MME 162 is a control node that handles signaling between UE 104 and EPC 160. Generally speaking, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets pass through serving gateway 166, which itself is connected to PDN gateway 172. PDN gateway 172 provides UE IP address allocation and other functions. PDN gateway 172 and BM-SC 170 are connected to IP services 176. IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 provides functionality for the provisioning and delivery of MBMS user services. It serves as the entry point for content providers' MBMS transmissions, authorizes and initiates MBMS bearer services within the public land mobile network (PLMN), and schedules MBMS transmissions. The MBMS gateway 168 distributes MBMS services to base stations 102 within a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts specific services. It is also responsible for session management (start / stop) and for collecting eMBMS-related billing information.

[0077] The core network 190 may include an access and mobility management function (AMF) (e.g., AMF 192), other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) (e.g., UPF 195). The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is the control node that handles signaling between the UE 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets pass through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 connects to IP services 197. IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), packet-switched (PS) streaming (PSS) services, and / or other IP services.

[0078] Base station 102 may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver functionality, basic service set (BSS), extended service set (ESS), transmit reception point (TRP), network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a converged (monolithic) base station having a baseband unit (BBU) (including a CU and DU) and a RU, or as a disaggregated base station including one or more of a CU, DU, and / or RU. A collection of base stations that may include disaggregated base stations and / or converged base stations may be referred to as a next generation (NG) RAN (NG-RAN). Base station 102 provides a UE 104 with access to EPC 160 or core network 190.

[0079] Non-limiting examples of UEs include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional device. Some of these UEs may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart rate monitors, etc.). IoT devices can be devices connected to a network, capable of wirelessly connecting to other wireless devices such as routers, base stations, and other RF communication devices. A UE may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0080] Reference again Figure 1In certain aspects, a device communicating with a network entity, such as one of the UEs 104 communicating with one of the base stations 102 or a component of the base station (e.g., the CU 106, the DU 105, and / or the RU 109), can be configured to manage one or more aspects of wireless communications. As a non-limiting example, the UE 104 can have a timing advance (TA) transmitting component 198 that can be configured to transmit a first message including a first indication associated with a timing advance command (TAC) granularity. The TA transmitting component 198 can be configured to receive a second message including a TAC configuration associated with the TAC granularity. The TA transmitting component 198 can be configured to transmit a third message based on the TAC configuration.

[0081] In another configuration, a network entity, such as a satellite 107, one of the base stations 102, or a component of the base station (e.g., CU 106, DU 105, and / or RU 109), may be configured to manage one or more aspects of wireless communications. As a non-limiting example, one of the base stations 102 or the satellite 107 may have a TAC configuration component 199 that may be configured to receive a first message including a first indication associated with a TAC granularity. The TAC configuration component 199 may be configured to send a second message including a TAC configuration associated with the TAC granularity based on the first indication. The TAC configuration component 199 may be configured to send a TAC. The TAC configuration component 199 may be configured to receive a third message based on the TAC configuration in response to receiving the TAC.

[0082] It should be understood that Figure 1 The altitude of satellite 107 relative to base station 102 and UE 104 is not conveyed. Satellite 107 may be located at Figure 1 Above both UE 104 and UE 102.

[0083] Various aspects disclosed herein facilitate a network node selecting a TAC granularity for a UE and the network node for transmission from the UE to the network node. The UE may indicate a request for a subset of TAC granularity values ​​that the network node may support. The TA sending component 198 may indicate to the TAC configuring component 199 what type of TAC granularity the UE 204 may be capable of using, which may be different from a default TAC granularity associated with the UE 204. The TAC configuring component 199 may then configure a TAC configuration for the UE 204 based on the TAC granularity associated with the UE 204. When the UE 204 receives a TAC from the base station 202, the UE 204 may then use the new TAC granularity to calculate its TA for transmission to the base station 202. This may maintain low timing error at the UE 204 by utilizing the TAC granularity that the UE 204 may be capable of using.

[0084] The deployment of a communication system, such as a 5G NR system, can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a radio access network (RAN) node, a core network node, a network element, or network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functionality can be implemented in a converged or disaggregated architecture. As non-limiting examples, a base station (such as a node B (NB), an evolved NB (eNB), a NR base station, a 5G NB, an access point (AP), a Transmission Control Point (TRP), or a cell) can be implemented as a converged base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

[0085] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0086] Base station operation or network design may take into account the aggregated nature of base station functionality. As non-limiting examples, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as that promoted by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as virtually distributing the functionality of at least one unit, which can enable flexibility in network design. The various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0087] As a non-limiting example, Figure 2Diagram 200 illustrates a non-limiting example of a wireless communication system and access network with a decomposable base station. The illustrated wireless communication system includes a decomposable base station architecture. The decomposable base station architecture may include one or more CUs within a CU 210, which may communicate directly with a core network 220 via a backhaul link or indirectly with the core network 220 through one or more decomposable base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. A CU 210 may communicate with one or more DUs 230 via corresponding midhaul links, such as an F1 interface. A DU 230 may communicate with one or more RUs 240 via corresponding fronthaul links. A RU 240 may communicate with a corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 may be served simultaneously by multiple RUs 240.

[0088] Each of the units (i.e., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interfaces of these units, may be configured to communicate with one or more of the other units via the transmission medium. As a non-limiting example, these units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or transmit signals to one or more of the other units via a wireless transmission medium.

[0089] In some aspects, the CU 210 may host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 210 may be implemented to communicate with the DU 230 for network control and signaling.

[0090] The DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, the DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), based at least in part on a functional split (such as those defined by 3GPP). In some aspects, the DU 230 may also host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 230 or with control functions hosted by the CU 210.

[0091] Lower layer functionality may be implemented by one or more RUs 240. In some deployments, a RU 240 controlled by a DU 230 may correspond to a logical node that hosts RF processing functionality or low-PHY layer functionality (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, both real-time and non-real-time aspects of control and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the implementation of the DU 230 and CU 210 in a cloud-based RAN architecture, such as a vRAN architecture.

[0092] The SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 210, DU 230, RU 240, and near-RT RIC 225. In some implementations, the SMO framework 205 can communicate with hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

[0093] The non-RT RIC 215 can be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or in communication with the near-RT RIC 225 (e.g., via an A1 interface). The near-RT RIC 225 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions via an interface (e.g., via an E2 interface) that connects one or more CUs in the CU 210, one or more DUs 230, or both, and the O-eNB with the near-RT RIC 225.

[0094] In some implementations, the non-RT RIC 215 may receive parameters or external enrichment information from an external server to generate the AI / ML model to be deployed in the near-RT RIC 225. This information may be utilized by the near-RT RIC 225 and may be received from non-network data sources or from network functions at the SMO framework 205 or the non-RT RIC 215. In some non-limiting examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. As non-limiting examples, the non-RT RIC 215 may monitor long-term trends and patterns in performance and employ AI / ML models to execute corrective actions through the SMO framework 205 (e.g., via reconfiguration of O1) or through the creation of RAN management policies (e.g., A1 policies).

[0095] At least one of the CU 210, DU 230, and RU 240 may be referred to as a base station 202. Thus, the base station 202 may include one or more of the CU 210, DU 230, and RU 240 (each component is indicated by a dashed line to indicate that each component may or may not be included in the base station 202). The base station 202 provides an access point to the core network 220 for the UE 204. The base station 202 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group known as a closed subscriber group (CSG). The communication link between RU 240 and UE 204 may include uplink (UL) (also known as reverse link) transmissions from UE 204 to RU 240 and / or downlink (DL) (also known as forward link) transmissions from RU 240 to UE 204. The communication link may utilize multiple-input, multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. Base station 202 / UE 204 may utilize spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 200 MHz, 500 MHz, etc.) for each carrier allocated in a carrier aggregation for transmission in each direction, totaling up to Yx MHz (x component carriers). These carriers may or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0096] Certain UEs 204 may communicate with each other using device-to-device (D2D) communication links 258. D2D communication links 258 may utilize DL / UL wireless wide area network (WWAN) spectrum. D2D communication links 258 may utilize one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be accomplished via various wireless D2D communication systems, such as, by way of non-limiting example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 902.11 standard, LTE, or NR.

[0097] The wireless communication system may also include a Wi-Fi AP 250 that communicates with a UE 204 (also referred to as a Wi-Fi station (STA)) via a communication link 254, for example, in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE 204 / AP 250 may perform a clear channel assessment (CCA) to determine whether the channel is available before communicating.

[0098] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (510 MHz-7.225 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 extends beyond 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes arises with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, despite being distinct from the extremely high frequency (EHF) band (30 GHz–400 GHz), which is designated as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0099] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.225 GHz–24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. As non-limiting examples, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz–71 GHz), FR4 (71 GHz–214.25 GHz), and FR5 (214.25 GHz–400 GHz). Each of these higher frequency bands falls within the EHF band.

[0100] With the above in mind, unless otherwise specified, if the term "sub-6 GHz" or the like is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise specified, if the term "millimeter wave" or the like is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0101] Base station 202 and UE 204 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 202 may transmit beamformed signals 282 to UE 204 in one or more transmit directions. UE 204 may receive beamformed signals from base station 202 in one or more receive directions. UE 204 may also transmit beamformed signals 284 to base station 202 in one or more transmit directions. Base station 202 may receive beamformed signals from UE 204 in one or more receive directions. Base station 202 and UE 204 may perform beam training to determine the optimal receive and transmit directions for each of base station 202 and UE 204. The transmit and receive directions of base station 202 may or may not be the same. The transmit and receive directions of UE 204 may or may not be the same.

[0102] Base station 202 may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 202 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a converged (monolithic) base station having a baseband unit (BBU) (including a CU and DU) and a RU, or as a disaggregated base station including one or more of a CU, DU, and / or RU. A collection of base stations that may include disaggregated base stations and / or converged base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0103] The core network 220 may include an access and mobility management function (AMF) 261, a session management function (SMF) 262, a user plane function (UPF) 263, a unified data management (UDM) 264, one or more location servers 268, and other functional entities. The AMF 261 is a control node that handles signaling between the UE 204 and the core network 220. The AMF 261 supports registration management, connection management, mobility management, and other functions. The SMF 262 supports session management and other functions. The UPF 263 supports packet routing, packet forwarding, and other functions. The UDM 264 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. The one or more location servers 268 are exemplified as including a gateway mobile location center (GMLC) 265 and a location management function (LMF) 266. However, in general, the one or more location servers 268 may include one or more location / positioning servers, which may include one or more of the GMLC 265, LMF 266, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Positioning Center (MPC), and the like. The GMLC 265 and LMF 266 support UE location services. The GMLC 265 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 266 receives measurements and assistance information from the NG-RAN and UE 204 via the AMF 261 to calculate the location of the UE 204. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 204. Positioning the UE 204 may involve signal measurements, position estimation, and optional rate calculation based on these measurements. Signal measurements may be performed by the UE 204 and / or the base station 202 serving the UE 204. The measured signals may be based on one or more of a satellite positioning system (SPS) 270 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0104] Non-limiting examples of UE 204 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 204 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart rate monitor, etc.). UE 204 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0105] Reference again Figure 2 In certain aspects, the UE 204 may include a TA transmitting component 198 that may be configured to transmit a first message including a first indication associated with TAC granularity. The TA transmitting component 198 may be configured to receive a second message including a TAC configuration associated with the TAC granularity. The TA transmitting component 198 may be configured to transmit a third message based on the TAC configuration. In certain aspects, the base station 202 may include a TAC configuring component 199 that may be configured to receive the first message including the first indication associated with TAC granularity. The TAC configuring component 199 may be configured to transmit a second message including a TAC configuration associated with the TAC granularity based on the first indication. The TAC configuring component 199 may be configured to transmit a TAC. The TAC configuring component 199 may be configured to receive a third message based on the TAC configuration in response to receiving the TAC. The TA transmitting component 198 may indicate to the TAC configuring component 199 what type of TAC granularity the UE 204 may be capable of using, which may be different from a default TAC granularity associated with the UE 204. TAC configuring component 199 can then configure a TAC configuration for UE 204 based on the TAC granularity associated with UE 204. When UE 204 receives a TAC from base station 202, UE 204 can then use the new TAC granularity to calculate its TA for transmission to base station 202. This can maintain low timing error at UE 204 by utilizing a TAC granularity that UE 204 may be capable of using.

[0106] Figure 3A is a diagram 300 illustrating a non-limiting example of a first subframe within a 5G NR frame structure. Figure 3B is a diagram 330 illustrating a non-limiting example of DL channels within a 5G NR subframe. Figure 3C is a diagram 350 illustrating a non-limiting example of a second subframe within a 5G NR frame structure. Figure 3D FIG380 is a diagram illustrating a non-limiting example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), a subframe within that subcarrier set is dedicated to either DL or UL), or may be time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), a subframe within that subcarrier set is dedicated to both DL and UL). Figure 3A 、 Figure 2 In the non-limiting example provided in C, the 5G NR frame structure is assumed to be TDD, with subframe 4 configured with slot format 28 (mostly DL), where D stands for DL, U stands for UL, and F stands for flexible use between DL / UL, and subframe 3 configured with slot format 1 (all UL). While subframes 3 and 4 are shown with slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. The other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format via a received slot format indicator (SFI), either dynamically via DL control information (DCI) or semi-statically / statically via radio resource control (RRC) signaling. Note that the following description also applies to the 5G NR frame structure as TDD.

[0107] Figures 3A to 3DThis example illustrates a frame structure, and aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each slot may include 14 symbols, and for an extended CP, each slot may include 12 symbols. Symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) symbols (CP-OFDM). Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power-limited scenarios; limited to single-stream transmission). The number of slots within a subframe depends on the CP and the parameter set. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration is scalable with 1 / SCS.

[0108]

[0109] For normal CP (14 symbols / slot), different parameter sets µ 0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set µ, there are 14 symbols per slot and 2 per subframe. µ time slots. The subcarrier spacing can be equal to ,in For parameter sets 0 to 4. Therefore, the subcarrier spacing for parameter set µ=0 is 15 kHz, and the subcarrier spacing for parameter set µ=4 is 340 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 3A to 3D A non-limiting example of a parameter set µ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbol duration is approximately 16.67µs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 3B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0110] A resource grid can be used to represent the frame structure. Each slot consists of a resource block (RB) (also known as a physical RB (PRB)) that extends over 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0111] like Figure 3A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RSs may include a demodulation RS (DM-RS) (indicated as R for one specific configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) used for channel estimation at the UE. The RSs may also include a beamforming RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0112] Figure 3B Non-limiting examples of various downlink channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs). Each CCE consists of six resource element groups (REGs), with each REG comprising 12 contiguous REs within an OFDM symbol of a RB. The PDCCH within a BWP is referred to as a control resource set (CORESET). During PDCCH monitoring opportunities on a CORESET, a UE is configured to monitor PDCCH search spaces (e.g., common search space, UE-specific search space) for PDCCH candidates with different DCI formats and aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of specific subframes of a frame. The PSS is used by UE 204 to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of specific subframes of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH), which carries the master information block (MIB), can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as the system information block (SIB)), and paging messages.

[0113] like Figure 3CAs illustrated, some of the REs carry DM-RSs (indicated as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and the specific PUCCH format used. The UE can transmit a sounding reference signal (SRS). The SRS can be transmitted in the last symbol of the subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb structures within the comb structure. The SRS can be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0114] Figure 3D Non-limiting examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0115] Figure 44 is a block diagram of a base station 410 communicating with a UE 450 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 475. The controller / processor 475 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 475 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0116] The transmit (TX) processor 416 and receive (RX) processor 470 implement Layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 416 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-order phase-shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols are then separated into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying the time-domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 474 may be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimates may be derived based on a reference signal and / or channel condition feedback transmitted by the UE 450. Each spatial stream may then be provided to a different antenna 420 via a separate transmitter 418Tx. Each transmitter 418Tx may modulate a radio frequency (RF) carrier using a corresponding spatial stream for transmission.

[0117] At the UE 450, each receiver 454Rx receives a signal via its corresponding antenna 452. Each receiver 454Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 456. The TX processor 468 and the RX processor 456 implement Layer 1 functionality associated with various signal processing functions. The RX processor 456 performs spatial processing on the information to recover any spatial streams destined for the UE 450. If multiple spatial streams are destined for the UE 450, they may be combined into a single OFDM symbol stream by the RX processor 456. The RX processor 456 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 410. These soft decisions may be based on channel estimates calculated by the channel estimator 458. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 410. The data and control signals are then provided to a controller / processor 459, which implements layer 3 and layer 2 functionality.

[0118] The controller / processor 459 may be associated with a memory 460 that stores program codes and data. The memory 460 may be referred to as a computer-readable medium. In the UL, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 459 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0119] Similar to the functionality described in conjunction with DL transmissions performed by the base station 410, the controller / processor 459 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0120] Channel estimates derived by the channel estimator 458 based on a reference signal or feedback transmitted by the base station 410 may be used by the TX processor 468 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 468 may be provided to different antennas 452 via separate transmitters 454Tx. Each transmitter 454Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0121] UL transmissions are processed at the base station 410 in a manner similar to that described in conjunction with the receiver functionality at the UE 450. Each receiver 418Rx receives a signal through its corresponding antenna 420. Each receiver 418Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 470.

[0122] The controller / processor 475 may be associated with a memory 476 that stores program codes and data. The memory 476 may be referred to as a computer-readable medium. In the UL, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 475 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0123] At least one of the TX processor 468, the RX processor 456, and the controller / processor 459 may be configured to combine Figure 2 The TA sends component 198 to perform various aspects.

[0124] At least one of the TX processor 416, the RX processor 470, and the controller / processor 475 may be configured to perform operations related to Figure 2 The TAC configuration component 199 combines various aspects.

[0125] Figure 5A A non-limiting example network architecture 500 is illustrated that may have the ability to support NTN access using, for example, 5G NR, as presented herein. Although various aspects are described using the non-limiting example of 5G NR, the concepts presented herein may also be applied to other types of core networks. Figure 5A The network architecture with transparent payload is illustrated. Figure 5A Various aspects of the present invention illustrate a 5G-based network, but similar network implementations and configurations can be used for other communication technologies such as 3G, 5G LTE, etc.

[0126] Figure 5A Network architecture 500 includes a UE 505, NTN equipment 502, an NTN gateway 504 (sometimes referred to as a "gateway," "earth station," or "ground station"), and a base station 506 capable of communicating with the UE 505 via the NTN equipment 502. The NTN equipment 502, NTN gateway 504, and base station 506 may be part of a RAN 512 (e.g., an NG RAN). An NTN gateway may connect a public data network to a non-terrestrial network. The NTN gateway may support the functionality of forwarding signals from the NTN equipment to a Uu interface (such as an NR-Uu interface). The NTN gateway may provide a transport network layer node and may support transport protocols, such as acting as an IP router. In some aspects, a base station may include an NTN gateway. As a non-limiting example, the base station 102 may include an NTN gateway for communicating with the satellite 107, or the satellite 107 may include an NTN gateway for communicating with the base station 102. In some aspects, both the base station 102 and the satellite 107 may include components of an NTN gateway.

[0127] The base station 506 may be Figure 2 The network architecture 500 is illustrated as also including a network device 510. In some aspects, the network device 510 may include several fifth generation (5G) networks (including a 5G core network (5GCN)) and may correspond to a network node in conjunction with the base station 202. Figure 2The core network 220 is depicted. The network device 510 may be a public land mobile network (PLMN). In some aspects, the core network may be a 5G CN.

[0128] Figure 5A The permitted connections in the network architecture 500 with transparent payload illustrated in FIG. 5 allow a base station 506 to access an NTN gateway 504 and network devices 510. In some non-limiting examples, the base station 506 may be shared by multiple PLMNs. Similarly, the NTN gateway 504 may be shared by more than one base station.

[0129] Figure 5A A generalized illustration of each component is provided, wherein any or all of the components may be utilized as appropriate, and each of the components may be repeated or omitted as desired. Specifically, although Figure 5A The non-limiting example includes a single UE 505, but it should be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize network architecture 500. As a non-limiting example, multiple UEs may be connected to NTN device 502 via multiple service links similar to service link 520. Similarly, network architecture 500 may include a greater (or lesser) number of NTN devices, NTN gateways, base stations, RANs, core networks, and / or other components. The illustrated connections connecting the various components in network architecture 500 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, various components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0130] UE 505 is configured to communicate with network device 510 via NTN device 502, NTN gateway 504, and base station 506. As illustrated by RAN 512, one or more RANs associated with network device 510 may include one or more base stations. UE 505 may be provided with access to the network via wireless communications between UE 505 and base station 506 (e.g., a serving base station), via NTN device 502 and NTN gateway 504. Base station 506 may provide wireless communication access to network device 510 on behalf of UE 505, for example, using 5G NR.

[0131] Base station 506 may be referred to by other names, such as a network entity, gNB, "satellite node," satellite Node B (sNB), "satellite access node," etc. Base station 506 may be distinct from terrestrial network gNBs, but may be based on terrestrial network gNBs with additional capabilities. By way of non-limiting example, base station 506 may terminate the radio interface and associated radio interface protocol to UE 505, and may transmit downlink signals to and receive uplink signals from UE 505 via NTN device 502 and NTN gateway 504. Base station 506 may also support signaling connections and voice and data bearers to UE 505, and may support handover of UE 505 between different radio cells of NTN device 502, between different NTN devices, and / or between different base stations. Base station 506 may be configured to manage mobile radio beams (e.g., for airborne vehicles and / or non-geostationary (non-GEO) devices) and the associated mobility of UE 505. The base station 506 can assist in the handover (or transfer) of the NTN device 502 between different NTN gateways or different base stations. In some non-limiting examples, the base station 506 can be separated from the NTN gateway 504, for example, Figure 5A In other non-limiting examples, the base station 506 may include one or more NTN gateways, or may be combined with one or more NTN gateways, for example, using a split architecture. As a non-limiting example, using a split architecture, the base station 506 may include a central unit (CU), such as Figure 2 The non-limiting example of CU 210 and NTN gateway 504 may include or act as a distributed unit (DU), such as Figure 2 The non-limiting example of DU 230. The base station 506 can be fixed on the ground with transparent payload operation. In one embodiment, the base station 506 can be physically combined or physically connected to the NTN gateway 504 to reduce complexity and cost.

[0132] The NTN gateway 504 may be shared by more than one base station and may communicate with the UE 505 via the NTN device 502. The NTN gateway 504 may be dedicated to one of the constellations associated with the NTN device. The NTN gateway 504 may be included within the base station 506, for example, as a base station-DU within the base station 506. The NTN gateway 504 may communicate with the NTN device 502 using control plane protocols and user plane protocols. The control plane protocols and user plane protocols between the NTN gateway 504 and the NTN device 502 may: (i) establish and release the communication link from the NTN gateway 504 to the NTN device 502, including authentication and encryption; (ii) update NTN device software and firmware; (iii) perform NTN device operations and maintenance (O&M); (iv) control radio beams (e.g., direction, power, on / off status) and the mapping between radio beams and NTN gateway UL and DL payloads; and / or (v) facilitate handover of the NTN device 502 or radio cell to another NTN gateway.

[0133] For use Figure 5A Support for transparent payloads in the network architecture 500 shown in FIGURE 5 may impact the communication system in the following ways. Network equipment 510 may treat satellite RATs as a new type of RAT with longer latency, reduced bandwidth, and / or higher error rates. This may impact PDU session establishment, as well as mobility management (MM) and connection management (CM) procedures. NTN equipment 502 can be shared with other services utilizing 5G NR mobile access (e.g., satellite TV, fixed internet access) by transparently adding UEs. This enables the use of legacy NTN equipment and avoids the need to deploy new types of NTN equipment. Base stations 506 facilitate the assignment and transfer of NTN equipment 502 and radio cells between base stations 506 and NTN gateways 504, and support handovers for UEs 505 between radio cells, NTN equipment, and other base stations. Therefore, base stations 506 may differ from terrestrial network gNBs. Furthermore, the coverage area of ​​base stations 506 may be significantly larger than that of terrestrial network base stations.

[0134] exist Figure 5A In the illustrated non-limiting example, service link 520 may facilitate communication between UE 505 and NTN device 502, feeder link 522 may facilitate communication between NTN device 502 and NTN gateway 504, and interface 524 may facilitate communication between base station 506 and network device 510. Service link 520 and feeder link 522 may be implemented by the same radio interface (e.g., NR-Uu interface). Interface 524 may be implemented by an NG interface.

[0135] Figure 5BA diagram illustrating a network architecture 525 that may have the ability to support NTN access, for example, using 5G NR, as presented herein. Figure 5B The network architecture 525 shown in FIG is similar to Figure 5A The network architecture shown in FIG is similar or identical to the specified components. However, Figure 5A In contrast to the transparent payload shown in Figure 5B A network architecture with a regenerative payload is illustrated. Unlike a transparent payload, a regenerative payload includes an onboard base station (eg, includes the functional capabilities of a base station) and is referred to herein as an NTN device 502 / base station. The onboard base station may be a Figure 2 505. RAN 512 is illustrated as including NTN equipment 502 / base station. Reference to NTN equipment 502 / base station may refer to functionality related to communication with UE 505 and network equipment 510 and / or functionality related to communication with NTN gateway 504 and UE 505 at the physical radio frequency level.

[0136] The onboard base station can perform many of the same functions as the base station 506, as previously described. As a non-limiting example, the NTN device 502 / base station can terminate the radio interface and associated radio interface protocol to the UE 505, and can transmit downlink signals to the UE 505 and receive uplink signals from the UE 505, which can include encoding and modulating the transmitted signals and demodulating and decoding the received signals. The NTN device 502 / base station can also support signaling connections and voice and data bearers to the UE 505, and can support handover of the UE 505 between different radio cells of the NTN device 502 / base station and between different NTN devices / base stations. The NTN device 502 / base station can facilitate handover (or transfer) of the UE 505 between different NTN gateways and different control networks. The NTN device 502 / base station can hide or obscure certain aspects of the NTN device 502 / base station from the network device 510, for example by interfacing with the network device 510 in the same or similar manner as a terrestrial network base station. The NTN device 502 / base station can also facilitate sharing of NTN devices 502 / base stations. The NTN device 502 / base station can communicate with one or more NTN gateways and, via the NTN gateway 504, with one or more core networks. In some aspects, the NTN device 502 / base station can communicate directly with other NTN devices / base stations using an inter-satellite link (ISL), which can support an Xn interface between any pair of NTN devices / base stations.

[0137] Using NTN equipment or satellites, NTN equipment 502 / base station can manage mobile radio cells with coverage at different times. NTN gateway 504 can be directly connected to network equipment 510, as illustrated. As a non-limiting example, if NTN gateways are limited, NTN gateway 504 can be shared by multiple core networks. In some non-limiting examples, network equipment 510 can know the coverage area of ​​NTN equipment 502 / base station in order to page UE 505 and manage handover. Therefore, it can be seen that, compared with the example Figure 5A The network architecture 525 with regenerated payload may have greater impact and complexity for both the NTN devices 502 / base stations and the network devices 510 compared to the network architecture 500 including transparent payload shown in FIG.

[0138] For use Figure 5B Support for regenerative payloads in the network architecture 525 shown in FIGURE 5 may impact the network architecture 525 as follows. In scenarios where fixed tracking areas and fixed cells are not supported, network device 510 may be impacted because core components of mobility management and regulatory services based on fixed cells and fixed tracking areas for terrestrial PLMNs may be replaced by a new system (e.g., based on the location of UE 505). In scenarios where fixed tracking areas and fixed cells are supported, when paging a UE 505 located in that fixed tracking area, network device 510 may map any fixed tracking area to one or more NTN devices / base stations with current radio coverage for that fixed tracking area. This may include configuring long-term orbit data for NTN device 502 / base station (e.g., obtained from the operator of the NTN device 502 / base station) in network device 510 and may add significant new impact to network device 510.

[0139] exist Figure 5B In the illustrated non-limiting example, service link 520 may facilitate communication between UE 505 and NTN device 502 / base station, feeder link 522 may facilitate communication between NTN device 502 / base station and NTN gateway 504, and interface 524 may facilitate communication between NTN gateway 504 and network device 510. Service link 520 may be implemented by an NR-Uu interface. Feeder link 522 may be implemented by an NG interface over SRI. Interface 524 may be implemented by an NG interface.

[0140] Figure 5C A diagram illustrating a network architecture 550 that may have the capability to support NTN access, for example, using 5G NR, as presented herein. Figure 5C The network architecture shown in is similar to Figure 5A and Figure 5B The network architecture shown in FIG is similar or identical to the specified components. However, Figure 5A In contrast to the transparent payload shown in Figure 5C The network architecture with regenerative payload is illustrated, and with a split architecture for base stations. As a non-limiting example, a base station may be located in a central unit (CU) such as Figure 2 CU 210) and Distributed Units (DU) (such as Figure 2 DU 230). Figure 5C In the illustrated non-limiting example, the network architecture 550 includes an NTN-CU 516, which may be a ground-based base station or terrestrial base station. The regenerative payload includes an onboard base station DU and is referred to herein as an NTN-DU 514. The NTN-CU 516 and the NTN-DU 514 may collectively or individually correspond to Figure 2 A network node associated with the base station 202 in .

[0141] The NTN-DU 514 communicates with the NTN-CU 516 via the NTN gateway 504. The NTN-CU 516 performs functions together with the NTN-DU 514 and may use an internal communication protocol similar to or identical to that of a gNB with a split architecture. In a non-limiting example, the NTN-DU 514 may correspond to and perform functions similar to or identical to a gNB distributed unit (gNB-DU), while the NTN-CU 516 may correspond to and perform functions similar to or identical to a gNB central unit (gNB-DU). However, the NTN-CU 516 and NTN-DU 514 may each include additional capabilities to support access by UE 505 using NTN equipment.

[0142] The NTN-DU 514 and the NTN-CU 516 can communicate with each other using the F1 Application Protocol (F1AP) and can perform operations together and in combination with each other. Figure 5B and Figure 5C Some or all of the same functionality as described for base station 506 or NTN device 502 / base station.

[0143] The NTN-DU 514 may terminate the radio interface and associated low-level radio interface protocols to the UE 505, and may transmit DL signals to the UE 505 and receive UL signals from the UE 505, which may include encoding and modulation of transmitted signals and demodulation and decoding of received signals. The operation of the NTN-DU 514 may be controlled in part by the NTN-CU 516. The NTN-DU 514 may support one or more NR radio cells of the UE 505. The NTN-CU 516 may also be split into separate control plane (CP) (NTN-CU-CP) and user plane (UP) (NTN-CU-UP) portions. The NTN-DU 514 and the NTN-CU 516 may communicate over the F1 interface to: (a) support control plane signaling for the UE 505 using IP, Stream Control Transmission Protocol (SCTP), and F1 Application Protocol (F1AP) protocols, and (b) support user plane data delivery for the UE using IP, User Datagram Protocol (UDP), PDCP, SDAP, GTP-U, and NR User Plane Protocol (NRUPP) protocols.

[0144] The NTN-CU 516 may communicate with one or more other NTN-CUs and / or with one or more other terrestrial base stations using terrestrial links to support an Xn interface between any pair of NTN-CUs and / or between the NTN-CU 516 and any terrestrial base station.

[0145] The NTN-DU 514 and the NTN-CU 516 together can: (i) support signaling connections and voice and data bearers to the UE 505; (ii) support handover of the UE 505 between different radio cells of the NTN-DU 514 and between different NTN-DUs; and (iii) assist in the handover (or transfer) of NTN equipment between different NTN gateways or different core networks. The NTN-CU 516 can hide or obscure certain aspects of the NTN equipment from the network equipment 510, for example, by interfacing with the network equipment 510 in the same or similar manner as a terrestrial network base station.

[0146] exist Figure 5C In the network architecture 550, the NTN-DU 514 communicating with and accessible from the NTN-CU may change over time with LEO devices. With a split-base station architecture, the network device 510 may connect to a fixed NTN-CU that does not change over time, which may reduce the difficulty of paging the UE 505. As a non-limiting example, the network device 510 may not know which NTN-DU to use to page the UE 505. With a split-base station architecture, the network architecture with regenerative payload may thus reduce the impact on the network device 510 at the expense of additional impact on the NTN-CU 516.

[0147] For the use of Figure 5C The support of regenerative payloads for the split base station architecture shown in [ 5 ] may affect the network architecture 550 as follows. The impact on the network device 510 may be limited as discussed above for transparent payloads (e.g., NTN device 502). As a non-limiting example, the network device 510 may treat the satellite RAT in the network architecture 550 as a new type of RAT with longer latency, reduced bandwidth, and / or higher error rate. As discussed above with reference to [ 5 ], the network device 510 may treat the satellite RAT in the network architecture 550 as a new type of RAT with longer latency, reduced bandwidth, and / or higher error rate. Figure 5B As discussed, the impact on the NTN-DU 514 can be less than the impact on an NTN device / base station (e.g., NTN device 502 / base station with a non-split architecture). The NTN-DU 514 can manage changing associations with different (fixed) NTN-CUs. Furthermore, the NTN-DU 514 can manage radio beams and radio cells. The impact on the NTN-CU 516 can be similar to the impact of the base station 506 on a network architecture with transparent payloads, as discussed above, except for the additional impact of managing changing associations with different NTN-DUs and the reduced impact on supporting radio cells and radio beams (which can be communicated to the NTN-DU 514). In some aspects, the NTN device can correspond to a high-altitude platform system (HAPS) serving one or more UEs on the ground.

[0148] One or more satellites may be integrated with the ground infrastructure of a wireless communication system. Satellites may refer to low Earth orbit (LEO), medium Earth orbit (MEO), geostationary Earth orbit (GEO), and / or highly elliptical orbit (HEO). Non-terrestrial networks (NTNs) may refer to networks or network segments that utilize airborne or spaceborne vehicles for transmission. Airborne vehicles may include high altitude platforms (HAPs), including unmanned aerial systems (UASs).

[0149] NTN can be configured to facilitate wireless communications in unserved or underserved areas, thereby improving the performance of terrestrial networks. As a non-limiting example, communication satellites can provide coverage over larger geographic areas compared to TN base stations. NTN can also enhance service reliability by providing service continuity for UEs or mobile platforms (e.g., passenger vehicles—aircraft, ships, high-speed trains, buses). NTN can also increase service availability, including for critical communications. NTN can also achieve network scalability by providing efficient multicast / broadcast resources for data delivery to the network edge or even directly to user equipment.

[0150] Figure 6Non-limiting examples of configurations for NTN 600 are illustrated. NTN can refer to a network or network segment that utilizes RF resources on an NTN platform. An NTN platform can refer to either spaceborne or airborne vehicles. Spaceborne vehicles include communication satellites, which can be categorized by their orbits. As a non-limiting example, a communication satellite can include a GEO device that appears stationary relative to the Earth. Thus, a single GEO device can provide coverage for a geographic coverage area. In other non-limiting examples, a communication satellite can include a non-GEO device, such as a LEO device, a MEO device, or a HEO device. Non-GEO devices do not appear stationary relative to the Earth. Therefore, a satellite constellation (e.g., one or more satellites) can be configured to provide coverage for a geographic coverage area. Airborne vehicles can refer to systems including tethered UAS (TUAs), lighter-than-air UAS (LTAs), and heavier-than-air UAS (HTAs), for example, at altitudes typically between 8 km and 50 km, including high altitude platforms (HAPs).

[0151] In some aspects, NTN 600 may comprise a NR-NTN. Figure 6 The non-limiting example of NTN 600 may include NTN device 602, NTN device 604, NTN device 606, NTN gateway 608, data network 610, and UE 630 within the cell coverage of NTN device 602. In some aspects, UE 630 may include an IoT device, and the UE may be connected to NTN 600 for wireless communication. Data network 610 may be any network capable of transmitting data with the device, such as a public data network, Figure 1 Access network 100, Figure 1 Core network 190, Figure 2 Core network 220 or Figure 2 Wireless communication systems in .

[0152] NTN gateway 608 may be one of one or more NTN gateways that can connect NTN 600 to a public data network (data network 610, as a non-limiting example). In some non-limiting examples, NTN gateway 608 may support the functionality of forwarding signals from NTN devices to a Uu interface (such as an NR-Uu interface). In other non-limiting examples, NTN gateway 608 may provide a transport network layer node and support transport protocols, such as acting as an IP router. A satellite radio interface (SRI) may provide an IP trunk connection between NTN gateway 608 and NTN devices to transport NG or F1 interfaces, respectively. One or more NTN devices (e.g., these may be referred to herein as NTN device 602, NTN device 604, or NTN device 606) may be fed by NTN gateway 608 and deployed within a satellite target coverage area, which may correspond to regional coverage or even continental coverage. NTN devices may include GEO devices or non-GEO devices that may be successively served by one or more NTN gateways at a time, and NTN 600 may be configured to provide service and feeder link continuity between these successively served NTN gateways over time to perform mobility anchoring and handover.

[0153] The NTN device 602 (including a satellite-based tool or an airborne tool) can communicate with the data network 610 via a feeder link 612 established between the NTN device 602 and the NTN gateway 608 to provide services to the UE 630 within the cell coverage or field of view of the NTN cell 620 of the NTN device 602 via a service link 614. The feeder link 612 may include a wireless link between the NTN gateway and the NTN device. The service link 614 may refer to a radio link between the NTN device (e.g., the NTN device 602) and the UE 630. Figure 2 As depicted, the NTN device 602 may use one or more directional beams (eg, beamforming) to exchange communications with the UE 630. A beam may refer to a wireless communication beam generated by an antenna on the NTN device.

[0154] In some non-limiting examples, UE 630 can communicate with NTN device 602 via service link 614. NTN device 604 can relay communications for NTN device 602 via inter-satellite link (ISL) 616, and NTN device 604 can communicate with data network 610 via feeder link 612 established between NTN device 604 and NTN gateway 608. ISL links can be provided between satellite constellations and can involve the use of transparent payloads on NTN devices. ISLs can operate in RF frequencies or optical bands.

[0155] exist Figure 6In the illustrated non-limiting example, NTN device 602 may provide a first physical cell ID (PCI) ("PCI1") to NTN cell 620. In one aspect, NTN device 602 may be a GEO device that appears stationary relative to the Earth. In this non-limiting example, NTN device 602 may not move relative to an object located on the Earth's surface (such as UE 630) in direction 642. In other aspects, a satellite constellation may provide coverage for NTN cell 620. As a non-limiting example, NTN device 602 may comprise a non-GEO device that appears non-stationary relative to the Earth. In this non-limiting example, NTN device 602 may move relative to an object located on the Earth's surface (such as UE 630) in direction 642, or UE 630 may move relative to NTN device 602 in direction 644. Thus, a satellite constellation (e.g., one or more satellites) may be configured to provide coverage for NTN cell 620. As a non-limiting example, NTN device 602 and NTN device 606 may be part of a satellite constellation that provides coverage for NTN cell 620 .

[0156] In some non-limiting examples, an NTN deployment may provide different services based on the type of payload on the NTN device. The type of payload may determine whether the NTN device acts as a relay node or a base station. As a non-limiting example, a transmission payload may implement frequency conversion and RF amplifiers in both the UL and DL directions and may correspond to an analog RF repeater. As a non-limiting example, a transparent payload may receive UL signals from all served UEs and DL redirect the combined signals to an earth station without demodulating or decoding the signals. Similarly, a transparent payload may receive UL signals from an earth station and DL redirect the signals to a served UE without demodulating or decoding the signals. However, the transparent payload may perform frequency conversion on the received signals and may amplify and / or filter the received signals before transmitting them.

[0157] Wireless communications between a UE and a base station may experience propagation delay between the time the UE sends an uplink transmission and the time the uplink transmission is expected to be received at the base station. This time difference may be referred to as a timing error. In other words, the timing error can be the difference between the time a UE transmission is received by the transmitting wireless device (e.g., a symbol or frame) and the time the UE transmission is scheduled to be received by the wireless device. If a UE transmission is received later than its scheduled time (interfering with a later transmission to the wireless device) or if a UE transmission is received earlier than its scheduled time (interfering with an earlier transmission to the wireless device), such a timing error may cause a UE-to-wireless device transmission to interfere with another transmission to the same wireless device. Such timing errors may occur when a UE or network node is traveling in an unintended direction or at an unexpectedly different speed, causing a transmission from the UE to the wireless device to occur within a shorter or longer time period than expected. In some aspects, different UEs may experience different propagation delays, which may result in a misalignment of the times of uplink transmissions from different UEs at the base station. If this misalignment is large enough, it may cause interference between uplink transmissions (e.g., OFDM-based transmissions). The base station can provide the UE with a TAC, which instructs the UE to adjust the timing of uplink transmission to compensate for propagation delay. Therefore, the network can use the TAC to control the uplink signal transmission timing.

[0158] As a non-limiting example, UE 630 may be located closer to NTN device 602 than UE 635. Since UE 635 is located farther from NTN device 602 than UE 630, UE 635 may use a larger TA than UE 630 to transmit signals to NTN device 602. UE 630 may also use a smaller TA than UE 635 to transmit signals to NTN device 602. In other words, when UE 630 transmits signal 646 to NTN device 602, UE 630 may use a first TA, and when UE 635 transmits signal 648 to NTN device 602, UE 635 may use a second TA that is larger than the first TA. Since signal 646 takes less time to travel to NTN device 602 than signal 648, UE 630 may use the first TA that is smaller than the second TA when transmitting signal 646 to ensure that signal 646 does not interfere with signal 648. Since signal 648 takes more time to travel to NTN device 602 than signal 646 , UE 635 may use a second TA that is larger than the first TA when transmitting signal 648 to ensure that signal 648 does not interfere with signal 646 .

[0159] Figure 7AFIG700 illustrates a UE 704 transmitting a signal Tx1 to an NTN device 702. As non-limiting examples, the NTN device 702 may be a GEO device, a MEO device, a LEO device, an aircraft device, a balloon device, or a UAV device. The UE 704 may communicate with another wireless device (such as a base station or another UE) via the NTN device 702. The UE 704 may use a TA 708 (also known as a TA offset) to transmit the signal Tx1 to the NTN device 702. By using the TA 708 to transmit the signal Tx1 to the NTN device 702, the UE 704 ensures that the signal Tx1 is received at the NTN device 702 as the signal Rx1 at the expected time 706.

[0160] Figure 7B This is an example Figure 7A FIG710 shows a diagram of a UE 704 and an NTN device 702, wherein the UE 704 may have moved relative to the NTN device 702 in a direction 705. From the perspective of the NTN device 702, the movement in the direction 705 may be an unexpected movement. As non-limiting examples, the UE 704 may have accelerated to a higher speed on a highway without first notifying the NTN device 702, or the UE 704 may have moved from a parked state to a moving state without first notifying the NTN device 702. Due to the movement of the UE 704 relative to the NTN device 702 in the direction 705, Figure 7B The distance between the UE 704 and the NTN device 702 may be greater than Figure 7A The distance between the UE 704 and the NTN device 702 in FIG.

[0161] UE 704 may use TA 708 to send signal Tx2 to NTN device 702. However, due to Figure 7B The distance between UE 704 and NTN device 702 is greater than Figure 7A 706 , the TA 708 may not be large enough to ensure that the signal Tx2 is received at the NTN device 702 as the signal Rx2 at the expected time 706. Therefore, the NTN device 702 may receive the signal Rx2 after the expected time 706. The NTN device 702 may determine that the time between the time when the NTN device 702 received the signal Rx2 and the expected time 706 is greater than the timing error threshold, and in response, may send a TAC to the UE 704, the TAC indicating the difference between the time when the NTN device 702 received the signal Rx2 and the expected time 706. The TAC may include an integer, which the UE 704 may multiply by the TAC granularity to determine the value of the time period indicated by the NTN device 702.

[0162] Figure 7CThis is an example of the UE 704 receiving the TAC from the NTN device 702. Figure 7B FIG7 shows a diagram 720 of a UE 704 and an NTN device 702. The UE 704 may update its TA using the TAC received from the NTN device 702. After receiving the TAC from the NTN device 702, the UE 704 may use the TA 709 to send a signal to the NTN device 702 instead of the UE 704.

[0163] UE 704 may transmit signal Tx3 to NTN device 702. UE 704 may transmit signal Tx3 to NTN device 702 using TA 709 calculated based on the TAC received from NTN device 702. By transmitting signal Tx3 to NTN device 702 using TA 709, UE 704 may ensure that signal Tx3 is received as signal Rx3 at NTN device 702 at expected time 706.

[0164] Figure 7B The NTN device 702 in the embodiment may measure the time difference between the uplink reception of the signal Rx2 and the expected time 706, and may transmit the TAC to the UE 704 to change the Figure 7C The timing of the uplink transmission of UE 704 in the NTN device 702 is improved, thereby providing reception at the NTN device 702 that is better aligned with the timing at the network side. As a non-limiting example, because signal Rx2 arrives at the NTN device 702 too late (i.e., after the expected time 706 that is greater than the timing error threshold), the NTN device 702 can instruct the UE 704 to transmit its signal earlier by an indicated amount. In contrast, if signal Rx2 arrives at the NTN device 702 too early (i.e., before the expected time 706 that is greater than the timing error threshold), the NTN device 702 can instruct the UE 704 to transmit its signal earlier by an indicated amount.

[0165] Figure 7A Signal Tx1, Figure 7B Signal Tx2 in and Figure 7C Each of the signals Tx3 in may be transmitted according to scheduling. As non-limiting examples, the signals may include PUSCH, PUCCH, or SRS transmissions.

[0166] By such as 7A to 7C The NTN device 702 in the NTN communicates with the UE (such as 7A to 7C The total timing advance (T TA or send timing advance) can be based on:

[0167] T TA = (N TA + N TA,UE-specific + NTA,common + N TA,offset ) x T C .

[0168] When referring to a TA used by a UE to transmit a signal (such as the TA used by UE 704 to transmit signal Tx1), Figure 7A TA708 in the UE 704 or used by the UE 704 to send signal Tx3 Figure 7C TA 709) in the text, TA refers to T TA , which can be calculated as (N TA +N TA,UE-specific + N TA,common + N TA,offset ) x T C In some respects, + N TA,UE-specific Can be called In some embodiments, N TA,common Can be called

[0169] N TA The accumulated timing advance value based on the accumulation of TA commands from the network may be included. For PRACH transmissions, N TA The timing advance provided by the network may be referred to as closed-loop timing advance. The network entity may provide N to the UE via the NTN equipment. TA Values ​​such as Figure 1 The BS 102 provides the UE 104 via the satellite 107, or the base station 506 provides the UE 630 via the NTN gateway 608.

[0170] N TA,UE-specific This may include pre-compensation for service link delays (e.g. Figure 7B The timing advance estimated by the UE based on the propagation delay between the UE 704 and the NTN device 702. Figure 6 A non-limiting example serving link 614 is illustrated in FIG. The UE may estimate this TA based on its position relative to the NTN equipment (e.g., satellites) of the NTN (e.g., obtained using a global navigation satellite system (GNSS)). In other words, the UE may estimate this TA based on an estimate of the serving link distance and an estimate of the feeder link distance. Satellite positioning may be provided by ephemeris. Such a TA calculated by the UE may be referred to as open-loop timing advance. The UE may calculate its NTN without first performing a GNSS position fix. TA,UE-specific This may result in N being estimated based on the UE's last known location rather than the UE's current location. TA,UE-specific The value has a timing error.

[0171] As a non-limiting example, regarding Figure 7B In some aspects, the NTN device 702 may determine that the time between the time when the NTN device 702 received the signal Rx2 and the expected time 706 is less than the timing error threshold. In such aspects, the NTN device 702 may not send a TAC to the UE 704, and thus the UE 704 may not know the difference between the time when the NTN device 702 received the signal Rx2 and the expected time 706. However, the UE 704 may perform GNSS positioning to determine that its position has moved since the time when the UE 704 last received a TAC from the NTN device 702. The UE 704 may then calculate N TA,UE-specific to compensate for its new position, thereby increasing TA to Figure 7A The TA 708 was used for a longer period of time.

[0172] N TA,common A common TA controlled by the network may be included and may include a timing offset deemed necessary by the network. The common TA may be based on, for example, the delay at the feeder link between the satellite and the base station. Figure 6 A non-limiting example of a feeder link 612 is illustrated. In some aspects, the common TA may be 0. N TA,common The value can also be compared with N TA,UE-specific The network entity can provide N to the UE via the NTN equipment. TA,common Values ​​such as Figure 1 The base station 102 provides N to the UE 104 via the satellite 107, or the NTN gateway 608 provides N to the UE 630 via the NTN gateway 608. In some aspects, the UE may calculate N based on the model. TA,common The model is constructed by the UE using one or more parameters (eg, coefficients in a Taylor series) signaled by the network. In some aspects, these parameters may be signaled via system information.

[0173] N TA,offset A fixed offset may be included for calculating timing advance. In some aspects, N TA,offset It can be used to ensure coexistence with LTE. The network entity can provide NTN to UE via NTN equipment. TA,offset Values ​​such as Figure 1 The base station 102 provides the UE 104 via the satellite 107, or the NTN gateway 608 provides the UE 630 via the NTN gateway 608.

[0174] Tc may be equal to 1 / (480000 x 4096) seconds.

[0175] The UE may apply TA in an idle RRC state (e.g., the "RRC_IDLE" state), an inactive RRC state (e.g., the "RRC_INACTIVE" state), or an RRC connected state (e.g., the "RRC_CONNECTED" state). When the UE has established an RRC connection with a base station, the UE may be in a connected state (e.g., the "RRC_CONNECTED" state) or an inactive state (e.g., the "RRC_INACTIVE" state). If an RRC connection has not yet been established, the UE is in an idle state (e.g., the "RRC_IDLE" state). While in the idle state, the UE and the base station may establish an RRC connection, and the UE may transition to a connected state. While in the connected state, the UE and / or the base station may release the RRC connection, and the UE may transition to an idle state. In other non-limiting examples, while in the connected state, the UE and / or the base station may release and suspend the RRC connection, and the UE may transition to an inactive state. While in the inactive state, the UE and / or the base station may resume the RRC connection, and the UE may transition to a connected state. In other non-limiting examples, when in the inactive state, the UE and / or the base station may release the RRC connection, and the UE may transition to the idle state.

[0176] In some aspects, the TAC from the network may be out of date, for example, based on the amount of time since the UE received the TAC command. In other words, the open-loop component of the calculated TA may be calculated by the UE at a frequency, but the closed-loop component of the calculated TA may be calculated when the network sends the TAC. In some aspects, the timing advance calculation may result in a double adaptation, where the propagation delay is determined by the network-controlled TA (e.g., the accumulated TA based on the TA command from the network, N TA ) process, the network controlled TA attempts to reduce the UE's use of the previous GNSS positioning, when the UE performs a new GNSS positioning and updates the self-estimated timing advance value N TA,UE-specific When , the previous GNSS position becomes duplicated. Double adaptation can also be called double correction.

[0177] Figure 8 A time diagram 800 is illustrated showing a non-limiting example of dual adaptation for timing advance. The UE may be configured to perform GNSS positioning 802 and use the GNSS position readings generated by the GNSS positioning and GNSS satellite positioning to determine N TA,UE-specific The UE is based at least in part on the GNSS positioning 802 of the N TA,UE-specific An uplink transmission 804 is sent at time t1, and an uplink transmission 806 is sent at time t1'. The uplink transmission 804 and the uplink transmission 806 may also have a timing based on the accumulated timing advance command (eg, N TA )、NTA,Common and / or N TA,Offset The network provides a timing advance command 808 and a timing advance command 812 based on the UE's previous transmissions. As a non-limiting example, the timing advance command 808 and / or the timing advance command 812 can be based on the propagation delay observed for the uplink transmission 804, 806, or 810 based on the GNSS position 802. Thus, the timing advance command 808 or the timing advance command 812 can account for the movement of the UE relative to the satellite after the GNSS position 802. When sending an uplink transmission, the UE applies the accumulation of the timing advance command 808, the timing advance command 812, etc. As a non-limiting example, the uplink transmission 804 and the uplink transmission 806 can have a first value N TA1 , and the uplink transmission 810 may have a cumulative value N TA1 +Timing Advance Command 808. Uplink Transmission 816 may have a cumulative value N TA1 + Timing Advance Command 808 + Timing Advance Command 812. The closed-loop timing advance based on the accumulated timing advance commands from the network provides a timing advance that accounts for the UE's movement relative to the satellites between GNSS fixes. The UE performs another GNSS fix 814 and updates the self-estimated timing advance (e.g., the open-loop timing advance value) based on the UE's position relative to the satellites based on the GNSS fix 814. TA,UE-specific Therefore, the self-estimated timing advance N TA,UE-specific The movement of the UE between the GNSS position 802 and the GNSS position 814 is also processed. TA + N TA,UE-specific ) provides a double adaptation (also referred to as a double correction) based on the movement of the UE relative to the satellite. Since the time t2 at which the uplink transmission 816 was sent is close to the time t1′ at which the uplink transmission 810 was sent and the GNSS position, in addition to the timing advance commands 808, 812 from the network to process the position change, the self-estimated timing advance (N) based on the GNSS position 814 is also used. TA,UE-specific ) will also capture the position change between t1 and t1'.

[0178] Relative to terrestrial networks, NTN deployments may be associated with long delays (e.g., long latency and / or long RTT), due at least in part to the longer distance between the UE and the NTN nodes. Furthermore, delays in transparent satellite deployments (e.g., satellites using transparent repeaters that redirect signals from the UE to a wireless receiver without demodulating the signals) may exceed delays in regenerative satellite deployments (e.g., satellites using regenerative repeaters that demodulate signals from the UE to the wireless receiver and remodulate the signals for transmission to the wireless receiver). This is because any communication between a UE and a base station or gateway may travel from the UE to the NTN node via a serving link, and then from the NTN node to the base station or gateway via a feeder link, both of which may be associated with longer delays than in terrestrial networks. Therefore, in an NTN, a UE may typically apply a TA to uplink transmissions performed in an RRC idle or inactive state and / or uplink transmissions performed in an RRC connected state. As a non-limiting example, the TA applied by a UE may have a value corresponding to the length of time it takes for a signal to travel from a base station to the UE and back to the base station (which may be included in an NTN node in a regenerative satellite deployment or a gateway in a transparent satellite deployment). As a non-limiting example, the TA applied by a UE may correspond to the round-trip time (RTT) between the base station and the UE (the time between the time a transmission is transmitted from the base station to the UE and the time a response is received from the UE to the base station in response, or the time between the time a transmission is transmitted from the UE to the base station and the time a response is received from the base station in response to the UE). This is because the TA is relative to a downlink frame at the UE, which is already a single-trip delay relative to the same downlink frame at the base station. In this way, the TA applied by the UE can be aligned with the uplink reception timing achieved at the base station, enabling communication with different UEs that may be located at different distances from the base station.

[0179] In some cases, the UE may self-estimate the open-loop N based at least in part on the UE's location and satellite locations (eg, the locations of NTN equipment). TA,UE-specific Value, where the UE's position may be estimated based at least in part on the current or most recent GNSS position fix, which the UE may update every few seconds (e.g., every 10 seconds). In contrast to closed-loop calculations, open-loop N TA,UE-specific The value may be a TA calculation that is not based on feedback. Therefore, during the intervals between GNSS position fixes, the UE position used by the UE to calculate the UE-specific TA may not be accurate (e.g., when the UE is in motion and has not yet performed a GNSS position fix). In some aspects, the UE position used to calculate N TA,UE-specificThe inaccuracy of the UE position of the value can be corrected in the closed-loop timing offset (for example, the base station can measure the uplink receive timing error and send a TA value of the TA command, the N TA The value indicates the closed-loop timing offset to be used to calculate the total TA that the UE will apply for uplink transmissions). Therefore, when the UE calculates a new open-loop N after an updated GNSS position fix, TA,UE-specific When the new T TA The value can be corrected twice for changes in UE location - once at N TA value, and another time in N TA,UE-specific This may lead to a double correction problem whereby the UE applies the TA (e.g. T TA ) is based at least in part on closed-loop values ​​(e.g., N TA ) to be calculated, and the open-loop value (for example, N TA,UE-specific ) can double correct for errors in UE position. The double correction problem can cause the UE-specific timing error to increase at an ever-increasing rate until the network sends a TAC to the UE, allowing the UE to correct the closed-loop timing offset for the UE-specific TA.

[0180] Figure 9 A timing diagram 900 is illustrated showing differential UE-specific timing error values ​​for TAs used for communications between a UE and a network node. The network node may be a satellite located at an altitude of 600 km moving north, and the UE may be a land-based UE moving north at 30 m / s. The UE may be configured to update its position via GNSS positioning every 5 seconds.

[0181] At time 0, the UE may have processed the TAC, thereby synchronizing the calculated TA variables at both the closed-loop component of the calculated TA (calculated at the network node) and the open-loop component of the calculated TA (calculated at the UE). At time 0, the calculated timing error at the UE may be zero.

[0182] Every 5 seconds, the UE may perform a GNSS position fix to correct the open-loop component of the calculated TA. As a non-limiting example, at time 15 seconds, the calculated timing error at the UE may be zero at point 902 because the UE may have performed a GNSS position fix to correct the open-loop component of the calculated TA. From time 15 seconds to time 20 seconds, the timing error may grow to approximately 0.05µs at point 904. At time 20 seconds, the UE may perform a GNSS position fix to correct the open-loop component of the calculated TA, thereby reducing the timing error to zero at point 906. Over time, the timing error at the UE may grow at a faster rate because the UE calculates the open-loop component of the calculated TA every 5 seconds but does not synchronize the calculated TA variables at both the closed-loop component of the calculated TA and the open-loop component of the calculated TA until the UE receives a TAC from the network node.

[0183] As a non-limiting example, at time 40 seconds, the calculated timing error at the UE may be zero at point 908 because the UE may have performed a GNSS position fix to correct the open-loop component of the calculated TA. From time 40 seconds to time 45 seconds, the timing error may increase to approximately 0.35 μs at point 910. At time 45 seconds, the UE may perform a GNSS position fix to correct the open-loop component of the calculated TA, thereby reducing the timing error to zero at point 912.

[0184] Between time 15 seconds and time 20 seconds, the timing error grows to approximately 0.5µs at point 904, whereas between time 40 seconds and time 45 seconds, the timing error grows to approximately 0.35µs at point 910. The timing error may continue to grow at a faster rate until the timing error reaches a timing error threshold line 920, which may be 0.52µs. When the timing error meets or exceeds the timing error threshold line 920, the network node may send a TAC to the UE, which may then synchronize the calculated TA variables at both the closed-loop component of the calculated TA and the open-loop component of the calculated TA, thereby ensuring that the timing error does not grow as rapidly as before the UE received the TAC command.

[0185] The TAC may include an indication of the delay at the closed-loop component of the calculated TA at the network node. The indication may be an integer that, when multiplied by the TAC granularity, is equal to the delay at the closed-loop component (e.g., N TA,common ). The TAC granularity may be calculated based on the subcarrier spacing (SCS) of the frame. As a non-limiting example, the TAC granularity may be calculated as 16T s / 2 µ , where T s= 1 / (15000×2048) seconds, and for SCS 15kHz, µ=0; for SCS 30kHz, µ=1; for SCS 60kHz, µ=2; and so on (see Table 1). In other words, for SCS 15kHz, the granularity can be calculated as 0.52µs. However, in some aspects, the timing error limit for a frame with SCS 15kHz can be 29T for both SSB and UL signals. s = 0.94µs. If the TAC granularity is 0.52µs and the timing error limit is 0.94µs, the TAC must be accurate to an integer to prevent the timing error from exceeding the timing error threshold. If the TAC is not accurate to two or more integers, the timing error may easily exceed the timing error threshold because twice the TAC granularity is 1.04µs, which is greater than 0.94µs. Therefore, such coarse granularity regarding the timing error limit may prevent the network from activating closed-loop timing control.

[0186] exist Figure 10 1000 has a UE 1002 configured to use a calculated TA value to send an uplink transmission to a network node 1006. The calculated TA value may compensate for the propagation delay between the UE 1002 and the network node 1006. The network node 1006 may include an NTN node, as a non-limiting example, Figure 2 The base station 506, NTN device 502, NTN-DU 514, NTN-CU 516 or base station 202 in.

[0187] The network node 1006 may be configured to send a TAC granularity indication message 1008 to the UE 1002. The UE 1002 may be configured to receive the TAC granularity indication message 1008. The TAC granularity indication message 1008 may be a system information block (SIB) that includes an indication of the availability of one or more granularities of TAC that the network node 1006 can support. The SIB may include one or more of: an indication that the network node 1006 can support multiple TAC granularities (i.e., additional TAC granularity values ​​beyond the default TAC granularity value); an indication of what TAC granularities the network node 1006 can support (e.g., a set of TAC granularities); several ways for the UE 1002 to indicate its request for a particular TAC granularity and / or its ability to support additional TAC granularities; and / or how to interpret the TAC configuration message 1014 from the network node 1006.

[0188] The TAC granularity indication message 1008 may indicate a set of TAC granularities that the network node 1006 may support. In some aspects, the TAC granularity indication message 1008 may provide a bitmap indicator of the network node's 1006 support for the set of TAC granularities. In some aspects, the network node 1006 may support two TAC granularities, as non-limiting examples, a default TAC granularity and a TAC granularity that is half the size of the default TAC granularity. In such aspects, the TAC granularity indication message 1008 may include a binary indication. As non-limiting examples, a 0 may indicate that the network node 1006 supports a single TAC granularity value, and a 1 may indicate that the network node 1006 supports multiple predefined TAC granularity values. In some aspects, the network node may support more than two TAC granularities. A multi-bit bitmap indicator may indicate the network node's 1006 support for the set of TAC granularities. As non-limiting examples, 00 may indicate that the network node 1006 supports a single default TAC granularity value, 01 may indicate that the network node 1006 supports a first plurality of predefined TAC granularity values, 10 may indicate that the network node 1006 supports a second plurality of predefined TAC granularity values ​​that are different from the first plurality of predefined TAC granularity values, and 11 may indicate that the network node 1006 supports a third plurality of predefined TAC granularity values.

[0189] In some aspects, the network node 1006 may be configured to use a default TAC value associated with the SCS, which, as a non-limiting example, is calculated as 16T. s / 2 µ The TAC granularity indication message 1008 may indicate a TAC granularity value other than a default TAC value because, as a non-limiting example, the UE 1002 may have considered the default TAC value to be predefined in a specification shared by the network node 1006 and the UE 1002. In some aspects, the network node 1006 may indicate each TAC granularity in the set of TAC granularities according to a scaling factor with respect to the default granularity. As a non-limiting example, if the default TAC value is 0.52µs and the set of TAC granularities includes [0.13µs, 0.26µs, 0.39µs], the TAC granularity indication message 1008 may indicate scaling factors [0.25, 0.5, 0.75] as the set of scaling factors that may be multiplied by the default TAC value to produce the set of TAC granularities, or may indicate scaling factors [1, 2, 3] as the set of scaling factors divided by four that may be multiplied by the default TAC value to produce the set of TAC granularities. In other aspects, the TAC granularity indication message 1008 may directly include the set of TAC granularity values ​​listed in µs.

[0190] In some aspects, the TAC granularity indication message 1008 may indicate to the UE 1002 one or more transmission formats that the UE 1002 may use to indicate its request for and / or ability to support one or more TAC granularities that the network node 1006 may support. In other words, the TAC granularity indication message 1008 may indicate to the UE 1002 one or more transmission formats that the UE 1002 may use to send the TAC capability indication message 1010. As a non-limiting example, the indication may be a binary indication that the UE 1002 may or may not support one or more TAC granularities other than a default TAC granularity value. The indication may include an indication of which TAC granularity the UE 1002 may wish to use. The UE 1002 may select a TAC granularity from the set of TAC granularities provided by the network node 1006 in the TAC granularity indication message 1008.

[0191] In some aspects, the transmission format may indicate the type of message that the UE 1002 may send to the network node 1006, the message containing the indication of the UE's TAC capabilities / request. In one aspect, the TAC granularity indication message 1008 may indicate to the UE 1002 that the UE 1002 may send the TAC capability indication message 1010 in an uplink (UL) medium access control (MAC) control element (MAC-CE) format. In other words, the UE 1002 may send the TAC granularity indication message 1008 as a UL MAC-CE including an indication of the UE's TAC capabilities. In one aspect, the TAC granularity indication message 1008 may indicate to the UE 1002 that the UE 1002 may send the TAC capability indication message 1010 in a UL radio resource control (RRC) format. As a non-limiting example, the UE 1002 may send the TAC capability indication message 1010 as a UE capability report. The UL RRC (e.g., the UE capability report) may include the indication of the UE's TAC capabilities. In one aspect, the TAC granularity indication message 1008 may indicate to the UE 1002 that the UE 1002 may send the TAC capability indication message 1010 in an uplink control information (UCI) format. In other words, the UE 1002 may send the TAC granularity indication message 1008 as a UL MAC-CE including an indication of the UE's TAC capability.

[0192] In some aspects, the UE 1002 may be configured to indicate the UE's TAC capability / request during a random access event (as a non-limiting example, in a message 1 (Msg1) transmission (e.g., a physical random access channel (PRACH) message). The attributes transmitted in Msg1 may indicate the UE 902's TAC capability / request to the network node 1006. In one aspect, a TAC granularity indication message 1008 may indicate to the UE 1002 that the UE 1002 may transmit the TAC capability indication message 1010 in a physical random access channel (PRACH) format. The network node 1006 may indicate a specific PRACH format that indicates to the network node 1006 that the UE 1002 requests a specific TAC granularity. As a non-limiting example, the network node 1006 may indicate to the UE 1002 that the TAC granularity indication message 1008 is sent using format 1A if the UE 1002 requests a TAC granularity value smaller than the default TAC granularity value, and that the TAC granularity indication message 1008 is sent using format 1B if the UE 1002 requests the use of the default TAC granularity value. The network node 1006 may indicate to the UE 1002 a set of PRACH formats that the UE 1002 can use, wherein at least a first subset of the set of PRACH formats corresponds to a first TAC granularity value and a second subset of the set of PRACH formats corresponds to a second TAC granularity value that is different from the first TAC granularity value. In one aspect, the TAC granularity indication message 1008 may indicate to the UE 1002 that the UE 1002 can send a TAC capability indication message 1010 in a subset of physical random access channel (PRACH) sequences. As a non-limiting example, the network node 1006 may indicate to the UE 1002 that a first subset of PRACH sequences is used to send a TAC granularity indication message 1008 if the UE 1002 requests a TAC granularity value smaller than the default TAC granularity value, and that a second subset of PRACH sequences is used to send the TAC granularity indication message 1008 if the UE 1002 requests the default TAC granularity value. The network node 1006 may indicate to the UE 1002 a plurality of subsets of PRACH sequences that the UE 1002 may use for Msg1 transmission, wherein a first subset of the plurality of subsets of PRACH sequences corresponds to a first TAC granularity value and a second subset of the plurality of subsets of PRACH sequences corresponds to a second TAC granularity value different from the first TAC granularity value. In one aspect, the TAC granularity indication message 1008 may indicate to the UE 1002 that the UE 1002 may send a TAC capability indication message 1010 in a subset of random access channel (RACH) opportunities.As a non-limiting example, the network node 1006 may indicate to the UE 1002 that a first subset of RACH opportunities is used to send the TAC granularity indication message 1008 if the UE 1002 requests to use a TAC granularity value smaller than the default TAC granularity value, and that a second subset of RACH opportunities is used to send the TAC granularity indication message 1008 if the UE 1002 requests to use the default TAC granularity value. The network node 1006 may indicate to the UE 1002 a plurality of subsets of RACH opportunities that the UE 1002 may use for Msg1 transmission, wherein a first subset of the plurality of subsets of RACH opportunities corresponds to a first TAC granularity value, and a second subset of the plurality of subsets of RACH opportunities corresponds to a second TAC granularity value different from the first TAC granularity value.

[0193] In some aspects, UE 1002 may be configured to indicate the UE's TAC capability request in a Message 3 (Msg3) transmission (e.g., an RRC Setup Request). Characteristics of the Msg3 transmission may indicate the UE's TAC capability request to network node 1006, or the values ​​of one or more fields of the Msg3 transmission may indicate the UE's TAC capability request to network node 1006. In one aspect, TAC granularity indication message 1008 may indicate a set of demodulation reference signal (DMRS) port numbers for the Msg3 message, at least some of which may be associated with an indication of the UE's TAC capability request. As a non-limiting example, DMRS port number 0 may be used to indicate DMRS. Another port number, such as DMRS port number 1, may be used to indicate that UE 1002 requests use of a TAC granularity value smaller than the default TAC granularity value. Another port number, such as DMRS port number 2, may be used to indicate that UE 1002 requests use of the default TAC granularity value. In some aspects, each DMRS port number in the set of DMRS port numbers indicated in the TAC granularity indication message 1008 may correspond to a TAC granularity value, where at least two TAC granularity values ​​are different. In another non-limiting example, the TAC granularity indication message 1008 may indicate that the manner in which the DMRS sequence of the Msg3 message is generated may be used to indicate the TAC capability request of the UE. As a non-limiting example, if the UE 1002 uses a default random seed to initialize the DMRS sequence, the UE 1002 may indicate to the network node 1006 that the UE 1002 wishes to use the default TAC granularity value. On the other hand, if the UE 1002 uses a different random seed to initialize the DMRS sequence, the UE 1002 may indicate to the network node 1006 that the UE 1002 wishes to use a TAC granularity value other than the default TAC granularity value. The network node 1006 may provide a set of random seeds that the UE 1002 may use to initialize the DMRS sequence, where each random seed may correspond to a TAC granularity value. In some aspects, the manner of generating the DMRS sequence may use different initialization values ​​for the random seed, while in other aspects, the manner of generating the DMRS sequence may use different cyclic shifts. The TAC granularity indication message 1008 may include a set of DMRS generation functions, each of which may correspond to a TAC granularity value. In other words, the DMRS generation function may be used to indicate a TAC granularity capability / request. In another non-limiting example, the TAC granularity indication message 1008 may indicate that the manner of performing PUSCH scrambling for the Msg3 message may be used to indicate the TAC capability request of the UE. One manner may indicate to the network node 1006 that the UE 1002 requests to use a TAC granularity value that is smaller than the default TAC granularity value, while another manner may indicate to the network node 1006 that the UE 1002 requests to use the default TAC granularity value.In some aspects, the TAC granularity indication message 1008 may indicate a set of PUSCH scrambling functions that may be used by the UE 1002, where each PUSCH scrambling function in the set of PUSCH scrambling functions may correspond to a TAC granularity value. In other words, the TAC granularity indication message 1008 may include one or more PUSCH scrambling functions that indicate a TAC granularity capability / request.

[0194] In some aspects, the value of a field in the Msg3 message may indicate the UE's TAC capability request to the network node 1006. As a non-limiting example, one value may indicate that the UE 1002 desires to use a smaller TAC granularity value, while another value may indicate that the UE 1002 desires to use a default TAC granularity value. In some aspects, the value may indicate which TAC granularity value from a set of TAC granularity values ​​the UE 1002 requests to use. As a non-limiting example, the TAC granularity indication message 1008 may indicate a set of reserved logical channel identifier (LCID) codepoints for UL common control channel (CCCH) data of the Msg3 message. The UE 1002 may use the set of LCID codepoints to indicate the UE's TAC capability request to the network node 1006. In some aspects, the UE 1002 may define a new set of LCID codepoints for UL CCCH data of the Msg3 message. The UE 1002 may use the new set of LCID codepoints to indicate the UE's TAC capability request to the network node 1006. In another non-limiting example, the TAC granularity indication message 1008 may indicate a set of reserved fields in the MAC subheader for UL CCCH data of the Msg3 message. The UE 1002 may use the set of reserved fields to indicate the UE's TAC capability request to the network node 1006.

[0195] In some aspects, the TAC granularity indication message 1008 may indicate to the UE 1002 how to interpret the bits configured for TAC granularity. As a non-limiting example, the TAC granularity indication message 1008 may include a TAC configuration table for interpreting the TAC configuration message 1014. The TAC configuration table may include a bitmap that may be used to associate bit configurations with TAC granularity values. As a non-limiting example, the TAC configuration table may associate 01 with 0.13µs, 10 with 0.26µs, 11 with 0.39µs, and 00 with 0.52µs (default value).

[0196] UE 1002 may send a TAC capability indication message 1010 to network node 1006. Network node 1006 may receive TAC capability indication message 1010 from UE 1002. TAC capability indication message 1010 may be sent using the transmission format indicated by TAC granularity indication message 1008 to indicate the capabilities / requests of UE 1002 to network node 1006.

[0197] At 1012, the network node 1006 may configure a TAC granularity value for the UE 1002 based on the indication of the TAC capability indication message 1010. As a non-limiting example, the network node 1006 may select a default value for the TAC granularity value, or may select a TAC granularity value for the UE 1002 based on the indication of the TAC capability indication message 1010. In another non-limiting example, the network node 1006 may select a TAC granularity value from a set of TAC granularity values ​​based on the indication of the TAC capability indication message 1010.

[0198] The network node 1006 may send a TAC configuration message 1014 to the UE 1002. The UE 1002 may receive the TAC configuration message 1014 from the network node 1006. The TAC configuration message 1014 may be sent in a variety of ways. In one aspect, the TAC configuration message 1014 may include a downlink (DL) medium access control (MAC) control element (MAC-CE). The DL MAC-CE may include the TAC configuration configured at 1012. In one aspect, the TAC configuration message 1014 may include a DL radio resource control (RRC) message. The DL RRC message may include the TAC configuration configured at 1012. In one aspect, the TAC configuration message 1014 may include downlink control information (DCI). The DCI may include the TAC configuration configured at 1012. In one aspect, the network node 1006 may redefine the use of a set of bits in the DCI to indicate the TAC configuration. In one aspect, the network node 1006 may use a set of reserved bits in the DCI to indicate the TAC configuration. As a non-limiting example, the network node 1006 may indicate the TAC configuration using the set of bits reserved for the Downlink Assignment Index (DAI) for Scheduling Message 4 (Msg4) transmission. The Msg4 transmission may include DCI format 1_0 with a cyclic redundancy check (CRC) scrambled by a Temporary Cell (TC) Radio Network Temporary Identifier (TC-RNTI). In another non-limiting example, the network node 1006 may indicate the TAC configuration using the set of bits reserved for Scheduling Message 2 (Msg2) transmission. The Msg2 transmission may include DCI format 1_0 with a cyclic redundancy check (CRC) scrambled by a Random Access (RA) Radio Network Temporary Identifier (RA-RNTI). In one aspect, the TAC configuration message 1014 may be sent as a Random Access Response (RAR) uplink (UL) grant. The RAR UL grant may include the TAC configuration configured at 1012. The Channel State Information (CSI) request bit in the RAR UL grant may be used to indicate whether the UE 1002 should use a smaller TAC granularity to calculate its TA.

[0199] At 1016, the UE 1002 may configure its TAC granularity based on the TAC configuration message 1014. As a non-limiting example, the UE 1002 may set its TAC granularity to one of a plurality of TAC granularities supported by the network node 1006, as indicated by the TAC configuration message 1014.

[0200] Later, the UE 1002 may calculate its TA using the new TAC granularity. The network node 1006 may send a TAC message 1018 to the UE 1002. The UE 1002 may receive the TAC message 1018 from the network node 1006. The TAC message 1018 may include an indication of the delay at the closed-loop component of the calculated TA at the network node. The indication may be an integer that, when multiplied by the TAC granularity, is equal to the delay at the closed-loop component (e.g., N TA,common ). The UE 1002 may multiply the integer by the new TAC granularity. In response to receiving the TAC message 1018, at 1020, the UE 1002 may calculate its TA based on the TAC integer and the new TAC granularity. In other words, the UE 1002 may synchronize the calculated TA variables at both the closed-loop component of the calculated TA and the open-loop component of the calculated TA, thereby reducing the timing error at the UE 1002 when the closed-loop component has been readjusted. As a non-limiting example, the UE 1002 may calculate the closed-loop component of the calculated TA by multiplying the TAC integer by the new TAC granularity, and may then calculate the open-loop component of the calculated TA by performing GNSS positioning using the closed-loop component of the calculated TA.

[0201] The network node 1006 can send TACs more frequently using the new TAC granularity because the TAC granularity can be set to the timing error threshold used to trigger the sending of the TAC message 1018 at the network node 1006. Maintaining a low timing error can reduce the number of times the UE 1002 can perform GNSS positioning because the network node 1006 sends TACs more frequently with a smaller TAC granularity. This can not only ensure that the TA timing error does not increase to exceed the timing error limit associated with the network node 1006, but it can also reduce the amount of energy used by the UE 1002 to perform GNSS positioning—particularly for lower-power devices (e.g., IoT devices).

[0202] UE 1002 may use the newly calculated TA to send an UL transmission 1022 to network node 1006. Network node 1006 may receive the UL transmission 1022.

[0203] Figure 11A UE (such as Figure 10 UE 1002 in the Figure 10 The network node 1006 in FIG. 100 indicates an uplink transmission format 1100 of TAC granularity capability / preference. As a non-limiting example, Figure 10The network node 1006 in FIG. 1002 may send a TAC granularity indication message 1008 as a downlink transmission to the UE 1002 including an indication of an uplink transmission format 1100. The UE 1002 may use the uplink transmission format to send a TAC capability indication message 1010 as an uplink transmission including an indication of TAC granularity capability / preference to the network node 1006. As non-limiting examples, the uplink transmission format 1100 may be a UL MAC-CE, a UL RRC (e.g., a UE capability report), or UCI sent by the UE to the network node. The uplink transmission may include an indication 1102 of a TAC capability request for the UE, including, as non-limiting examples, whether the UE requests a TAC granularity value smaller than a default TAC granularity value or which TAC granularity value the UE has selected from a set of TAC granularity values ​​sent by the network node to the UE. The indication 1102 may include a bitmap representation of the TAC granularity request made by the UE.

[0204] Figure 11B Is UE (such as Figure 10 UE 1002 in the Figure 10 FIG110 shows a diagram of a set of PRACH formats or sequences indicating TAC granularity capability / preference of a network node 1006 in FIG110 . As a non-limiting example, Figure 10In the embodiment of the present invention, the network node 1006 may send a TAC granularity indication message 1008 to the UE 1002 as a downlink transmission including an indication of a set of PRACH formats or sequences (PRACH format / sequence 1112, PRACH format / sequence 1114, and PRACH format / sequence 1116). The UE 1002 may use the set of PRACH formats or sequences to send a TAC capability indication message 1010 to the network node 1006 as a PRACH uplink transmission indicating TAC granularity capability / preference. The network node may indicate the PRACH format / sequence 1112, PRACH format / sequence 1114, and PRACH format / sequence 1116 to the UE. As a non-limiting example, the PRACH format / sequence 1112 may be format 1A, the PRACH format / sequence 1114 may be format 1B, and the PRACH format / sequence 1116 may be format 2A. In another non-limiting example, PRACH format / sequence 1112 may be a first Zadoff-Chu sequence, PRACH format / sequence 1114 may be a second Zadoff-Chu sequence different from the first Zadoff-Chu sequence, and PRACH format / sequence 1116 may be a third Zadoff-Chu sequence different from the first and second Zadoff-Chu sequences. The network node may indicate that using PRACH format / sequence 1112 or PRACH format / sequence 1114 may indicate to the network node that the UE requests a TAC granularity value smaller than the default TAC granularity value, and using PRACH format / sequence 1116 may indicate to the network node that the UE does not request a TAC granularity value smaller than the default TAC granularity value (i.e., the UE requests use of the default TAC granularity value). In some aspects, the network node may indicate that a first fine TAC granularity value may be selected using PRACH format / sequence 1112, and a second TAC granularity value different from the first TAC granularity value may be selected using PRACH format / sequence 1114. The network node may indicate more or fewer formats or sequences to the UE. As a non-limiting example, the network node may indicate a first set of PRACH formats or sequences to the UE, and this first set of PRACH formats or sequences may indicate that the UE requests a smaller TAC granularity than a default value, meaning that any other PRACH formats or sequences used by the UE indicate that the UE does not request a smaller TAC granularity than the default value. In another non-limiting example, the network node may indicate a set of PRACH formats or sequences to the UE for each TAC granularity supported by the network node.

[0205] Figure 11C Is UE (such as Figure 10 UE 1002 in the Figure 10As a non-limiting example, a network node 1006 in FIG. 1006 indicates a set of RACH opportunities for which TAC granularity capability / preference is indicated. Figure 10 In the embodiment of the present invention, the network node 1006 may send a TAC granularity indication message 1008 to the UE 1002 as a downlink transmission including an indication of RACH opportunities (a subset of RACH opportunities 1122, a subset of RACH opportunities 1124, and a subset of RACH opportunities 1126). The UE 1002 may use the RACH opportunities to send a TAC capability indication message 1010 to the network node 1006 as an uplink transmission indicating TAC granularity capability / preference. The network node may indicate the subset of RACH opportunities 1122, the subset of RACH opportunities 1124, and the subset of RACH opportunities 1126 to the UE. Each subset is shown as a subset selected from a set of six RACH opportunities, but the network node may indicate more or fewer subsets of RACH opportunities. The network node may indicate that using RACH opportunity 1122 or RACH opportunity 1124 may indicate to the network node that the UE requests a TAC granularity value smaller than the default TAC granularity value, and using RACH opportunity 1126 may indicate to the network node that the UE does not request a TAC granularity value smaller than the default TAC granularity value (i.e., the UE requests use of the default TAC granularity value). In some aspects, the network node may indicate that using RACH opportunity 1122 may select a first TAC granularity value, and using RACH opportunity 1124 may select a second TAC granularity value different from the first TAC granularity value. The network node may indicate to the UE more or fewer subsets of RACH opportunities. As a non-limiting example, the network node may indicate to the UE a subset of RACH opportunities that may indicate that the UE requests a TAC granularity smaller than the default value, meaning that any other subset of RACH opportunities used by the UE indicates that the UE does not request a TAC granularity smaller than the default value. In another non-limiting example, the network node may indicate to the UE a subset of RACH occasions for each TAC granularity supported by the network node.

[0206] Figure 11D Is UE (such as Figure 10 UE 1002 in the Figure 10 FIG1130 shows a diagram of a network node 1006 in FIG1130 indicating a set of DMRS or PUSCH functions of a TAC granularity capability / preference. As a non-limiting example, Figure 10The network node 1006 in FIG. 1006 may send a TAC granularity indication message 1008 to the UE 1002 as a downlink transmission including an indication of a set of DMRS or PUSCH capabilities (DMRS or PUSCH capability 1132, DMRS or PUSCH capability 1134, and DMRS or PUSCH capability 1136), which the UE 1002 may use to generate a DMRS or scrambled PUSCH for a TAC capability indication message 1010, which is sent as an uplink transmission indicating TAC granularity capability / preference to the network node 1006. The network node may indicate the DMRS or PUSCH capability 1132, the DMRS or PUSCH capability 1134, and the DMRS or PUSCH capability 1136 to the UE. As a non-limiting example, the DMRS or PUSCH function 1132 may be a way to generate a DMRS sequence using a first initialization of a random seed, the DMRS or PUSCH function 1134 may be a way to generate a DMRS sequence using a second initialization of a random seed, and the DMRS or PUSCH function 1136 may be a way to generate a DMRS sequence using a third initialization of a random seed. In another non-limiting example, the DMRS or PUSCH function 1132 may be a PUSCH scrambling function using a first scrambling identity, the DMRS or PUSCH function 1134 may be a PUSCH scrambling function using a second scrambling identity, and the DMRS or PUSCH function 1136 may be a PUSCH scrambling function using a third scrambling identity. The network node may indicate that using DMRS or PUSCH functionality 1132 or DMRS or PUSCH functionality 1134 may indicate to the network node that the UE requests a TAC granularity value smaller than the default TAC granularity value, and using DMRS or PUSCH functionality 1136 may indicate to the network node that the UE does not request a TAC granularity value smaller than the default TAC granularity value (i.e., the UE requests use of the default TAC granularity value). In some aspects, the network node may indicate that using DMRS or PUSCH functionality 1132 may select a first TAC granularity value, and using DMRS or PUSCH functionality 1134 may select a second TAC granularity value different from the first TAC granularity value. The network node may indicate more or fewer DMRS or PUSCH functionality to the UE. As a non-limiting example, the network node may indicate to the UE a set of DMRS or PUSCH functionality that indicates that the UE requests a TAC granularity smaller than the default value, meaning that any other set of DMRS or PUSCH functionality used by the UE indicates that the UE does not request a TAC granularity smaller than the default value. In another non-limiting example, the network node may indicate to the UE a set of DMRS or PUSCH capabilities for each TAC granularity supported by the network node.

[0207] Figure 11E Message 1140 is illustrated with a set of bits 1142 that the wireless device may use to indicate TAC granularity capability / preference or TAC granularity. Figure 11E 1142, but the set of bits 1142 may be more or fewer bits depending on the configuration used by the network node. As a non-limiting example, the network node may instruct the UE to use a binary indication of its ability to use multiple TAC granularity values, in which case the set of bits 1142 may be one bit (e.g., 0 indicates that the UE does not have the capability, and 1 indicates that the UE has the capability). In another non-limiting example, the network node may instruct the UE to use a bitmap indication to select from a set of six TAC granularity values, in which case the set of bits 1142 may be three bits (e.g., 000, 001, 010, 011, 100, and 101 to indicate which of the six TAC granularity values ​​is to be requested).

[0208] In one aspect, message 1140 may be Msg3 sent by a UE (such as Figure 10 The UE 1002 in the embodiment may use this Msg3 transmission to send a TAC capability indication message 1010 to a network node such as a Figure 10 The network node 1006 in the UE indicates TAC granularity capability. The set of bits 1142 may indicate the DMRS port number in the Msg3 transmission. If the specification (e.g., wireless standard, network node configuration) uses DMRS port 0 and no other DMRS ports, the UE may use a DMRS port number other than 0 to indicate whether the UE requests a TAC granularity value smaller than the default TAC granularity value. The DMRS port number may indicate which TAC granularity value the UE requests from a set of TAC granularity values ​​supported by the network node. The set of bits 1142 may be a set of reserved LCID codepoints for UL CCH data. The UE may use the set of reserved LCID codepoints to indicate its TAC granularity capability, for example, by using a bitmap indicator. The set of bits 1142 may be a set of new extended LCID (eLCID) codepoints defined by the new specification. The UE may use the set of new eLCID codepoints to indicate its TAC granularity capability, for example, by using a bitmap indicator. The set of bits 1142 may be a set of reserved fields (i.e., "R" fields) in the MAC subheader for UL CCH data. A UE may use a set of reserved fields to indicate its TAC granularity capability, for example by using a bitmap indicator.

[0209] On the other hand, message 1140 may be Msg2 or Msg4 sent by a network node such as Figure 10The network node 1006 in the embodiment may use the Msg2 or Msg4 transmission to send a TAC granularity indication message 1008 to the UE in a downlink transmission such as the TAC granularity indication message 1008. Figure 10 1002 in the message 1140) indicates the TAC granularity. The set of bits 1142 may be a set of repurposed bits in the DCI. The set of bits 1142 may be a set of new bits in the DCI. The set of bits 1142 may be a set of reserved bits in the DCI, such as the DAI bits in the DCI sent by scheduling Msg4 (e.g., in DCI format 1_0 with a CRC scrambled by TC-RNTI) or the set of reserved bits in the DCI sent by scheduling Msg2 (e.g., in DCI format 1_0 with a CRC scrambled by RA-RNTI). The set of bits 1142 may be the CSI request bits in the RAR UL grant. The network node may use the set of bits 1142 in the message 1140 to indicate the TAC granularity, for example by using a bitmap indicator. The network node may indicate to the UE how to interpret the set of bits 1142 in a previous transmission, for example Figure 10 The TAC granularity indication message 1008 in.

[0210] Figure 12 1200 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 204, UE 450, UE 505, UE 630, UE 1002, UE; device 1604). At 1202, the UE may send a first message including a first indication associated with a TAC granularity. As a non-limiting example, 1202 may be performed by Figure 10 The UE 1002 in the embodiment may send a TAC capability indication message 1010 to the network node 1006 via the network node 1006. The TAC capability indication message 1010 may include a first indication associated with the TAC granularity of the UE 1002. Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0211] At 1204, the UE may receive a second message including a TAC configuration associated with a TAC granularity. As a non-limiting example, 1204 may be performed by Figure 10 The UE 1002 in the embodiment may receive a TAC configuration message 1014 from the network node 1006 via the network node 1006. The TAC configuration message 1014 may include a TAC configuration associated with the TAC granularity of the UE 1002. Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0212] At 1206, the UE may send a third message based on the TAC configuration. As a non-limiting example, 1206 may be Figure 10 1002 in the UE, which may send an UL transmission 1022 to the network node 1006 via the network node 1006 based on the TAC configuration of the TAC configuration message 1014. In addition, 1206 may be performed by Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0213] Figure 13 1300 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 204, UE 450, UE 505, UE 630, UE 1002, UE; device 1604). At 1301, the UE may receive a fourth message including a second indication of a set of TAC granularities. As a non-limiting example, 1301 may be performed by Figure 10 The UE 1002 in the embodiment may receive a TAC granularity indication message 1008 including an indication of a set of TAC granularities. Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0214] At 1302, the UE may send a first message including a first indication associated with TAC granularity in response to receiving the fourth message. As a non-limiting example, 1302 may be Figure 10 The UE 1002 may send a TAC capability indication message 1010 to the network node 1006 via the network node 1006. The TAC capability indication message 1010 may include a first indication associated with the TAC granularity of the UE 1002. The UE 1002 may send the TAC capability indication message 1010 in response to receiving the TAC granularity indication message 1008. In addition, 1302 may be performed by Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0215] At 1304, the UE may receive a second message including a TAC configuration associated with a TAC granularity. As a non-limiting example, 1304 may be performed by Figure 10The UE 1002 in the embodiment may receive a TAC configuration message 1014 from the network node 1006 via the network node 1006. The TAC configuration message 1014 may include a TAC configuration associated with the TAC granularity of the UE 1002. Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0216] At 1306, the UE may send a third message based on the TAC configuration. As a non-limiting example, 1306 may be performed by Figure 10 1002 in the UE, which may send an UL transmission 1022 to the network node 1006 via the network node 1006 based on the TAC configuration of the TAC configuration message 1014. In addition, 1306 may be performed by Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0217] At 1308, the UE may select a TAC granularity from a set of TAC granularities. As a non-limiting example, 1308 may be performed by Figure 10 The UE 1002 in the embodiment may select a TAC granularity from the set of TAC granularities indicated by the TAC granularity indication message 1008. In addition, 1308 may be performed by Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0218] At 1310, the UE may select a transmission format from a set of transmission formats of the first message, wherein the fourth message may include a third indication of the set of transmission formats. As a non-limiting example, 1310 may be Figure 10 The UE 1002 in the TAC capability indication message 1010 may select a transmission format from the set of transmission formats. The TAC granularity indication message 1008 may indicate the set of transmission formats. In addition, 1310 may be performed by Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0219] At 1312, the UE may send the first message using the selected transmission format. As a non-limiting example, 1312 may be performed by Figure 10 1002 in the UE, the UE may use the selected transmission format to send the TAC capability indication message 1010. In addition, 1312 may be performed by Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0220] At 1314, the UE may calculate the TA based on the TAC configuration and the TAC configuration table associated with the TAC configuration. The fourth message may include the TAC configuration table. As a non-limiting example, 1314 may be Figure 10 The UE 1002 in the embodiment may calculate the TA based on the TAC configuration and the TAC configuration table associated with the TAC configuration. The TAC granularity indication message 1008 may include the TAC configuration table. In addition, 1314 may be performed by Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0221] At 1316, the UE may send a third message based on the calculated TA. As a non-limiting example, 1316 may be Figure 10 The UE 1002 in the embodiment may send an UL transmission 1022 based on the calculated TA. In addition, 1316 may be performed by Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0222] At 1318, the UE may send a third message to the NTN node. As a non-limiting example, 1318 may be Figure 10 1002 in the UE, the UE may send UL transmission 1022 to the NTN node. In addition, 1318 may be performed by Figure 1 、 Figure 2 、 Figure 4 or Figure 16 Component 198 in is used for execution.

[0223] Figure 14 1400 is a flow chart of a method of wireless communication. The method may be performed by a network node (e.g., base station 202, base station 410, base station 506, network node 1006; NTN device 502, NTN device 602, NTN device 604, NTN device 606; NTN gateway 504, NTN gateway 608; network device 510; RAN 512; data network 610; network node 1006; network entity 1602, network entity 1702, network entity 1860). At 1402, the network node may receive a first message including a first indication associated with a TAC granularity. As a non-limiting example, 1402 may be performed by Figure 10The network node 1006 in the embodiment may receive a TAC capability indication message 1010 from the UE 1002 via the network node 1006. The TAC capability indication message 1010 may include a first indication associated with the TAC granularity of the UE 1002. Figure 1 、 Figure 2 、 Figure 4 、 Figure 17 or Figure 18 Component 199 in is executed.

[0224] At 1404, the network node may send a second message including a TAC configuration associated with the TAC granularity based on the first indication. As a non-limiting example, 1404 may be performed by Figure 10 The network node 1006 in the embodiment may send a TAC configuration message 1014 to the UE 1002 via the network node 1006. The TAC configuration message 1014 may include a TAC configuration associated with a TAC granularity based on the first indication received in the TAC capability indication message 1010. In addition, 1404 may be performed by Figure 1 、 Figure 2 、 Figure 4 、 Figure 17 or Figure 18 Component 199 in is executed.

[0225] At 1406, the network node may send a TAC. As a non-limiting example, 1406 may be performed by Figure 10 The network node 1006 in the embodiment may send a TAC message 1018 to the UE 1002 via the network node 1006. In addition, 1406 may be performed by Figure 1 、 Figure 2 、 Figure 4 、 Figure 17 or Figure 18 Component 199 in is executed.

[0226] At 1408, the network node may receive a third message based on the TAC configuration in response to receiving the TAC. As a non-limiting example, 1408 may be performed by Figure 10 The network node 1006 in the embodiment may receive an UL transmission 1022 from the UE 1002 via the network node 1006 based on the TAC configuration in response to receiving the TAC message 1018. In addition, 1408 may be performed by Figure 1 、 Figure 2 、 Figure 4 、 Figure 17 or Figure 18 Component 199 in is executed.

[0227] Figure 151500 is a flow chart of a method of wireless communication. The method may be performed by a network node (e.g., base station 202, base station 410, base station 506, network node 1006; NTN device 502, NTN device 602, NTN device 604, NTN device 606; NTN gateway 504, NTN gateway 608; network device 510; RAN 512; data network 610; network node 1006; network entity 1602, network entity 1702, network entity 1860). At 1501, the network node may send a fourth message including a second indication of a set of TAC granularities. As a non-limiting example, 1501 may be performed by Figure 10 The network node 1006 in the embodiment may send a TAC granularity indication message 1008 including an indication of a set of TAC granularities. Figure 1 、 Figure 2 、 Figure 4 、 Figure 17 or Figure 18 Component 199 in is executed.

[0228] At 1502, a network node may receive a first message including a first indication associated with a TAC granularity. The set of TAC granularities may include the TAC granularity. As a non-limiting example, 1502 may be performed by Figure 10 The network node 1006 in the embodiment may receive a TAC capability indication message 1010 from the UE 1002 via the network node 1006. The TAC capability indication message 1010 may include a first indication associated with a TAC granularity of the UE 1002. The set of TAC granularities from the TAC granularity indication message 1008 may include the TAC granularity from the TAC capability indication message 1010. In addition, 1502 may be performed by Figure 1 、 Figure 2 、 Figure 4 、 Figure 17 or Figure 18 Component 199 in is executed.

[0229] At 1504, the network node may send a second message including a TAC configuration associated with the TAC granularity based on the first indication. As a non-limiting example, 1504 may be performed by Figure 10 The network node 1006 in the embodiment may send a TAC configuration message 1014 to the UE 1002 via the network node 1006. The TAC configuration message 1014 may include a TAC configuration associated with a TAC granularity based on the first indication received in the TAC capability indication message 1010. In addition, 1504 may be performed by Figure 1 、 Figure 2 、 Figure 4 、 Figure 17 or Figure 18Component 199 in is executed.

[0230] At 1506, the network node may send a TAC. As a non-limiting example, 1506 may be performed by Figure 10 The network node 1006 in the embodiment may send a TAC message 1018 to the UE 1002 via the network node 1006. In addition, 1506 may be performed by Figure 1 、 Figure 2 、 Figure 4 、 Figure 17 or Figure 18 Component 199 in is executed.

[0231] At 1508, the network node may receive a third message based on the TAC configuration in response to receiving the TAC. As a non-limiting example, 1508 may be performed by Figure 10 The network node 1006 in the embodiment may receive an UL transmission 1022 from the UE 1002 via the network node 1006 based on the TAC configuration in response to receiving the TAC message 1018. In addition, 1508 may be performed by Figure 1 、 Figure 2 、 Figure 4 、 Figure 17 or Figure 18 Component 199 in is executed.

[0232] Figure 1616 is a diagram illustrating a non-limiting example of a hardware implementation for an apparatus 1604. The apparatus 1604 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1604 may include a cellular baseband processor 1624 (also referred to as a modem) coupled to one or more transceivers 1622 (e.g., a cellular RF transceiver). The cellular baseband processor 1624 may include on-chip memory 1624′. In some aspects, the apparatus 1604 may also include one or more subscriber identity module (SIM) cards 1620 and an application processor 1606 coupled to a secure digital (SD) card 1608 and a screen 1610. The application processor 1606 may include on-chip memory 1606′. In some aspects, device 1604 may also include a Bluetooth module 1612, a WLAN module 1614, an SPS module 1616 (e.g., a GNSS module), one or more sensor modules 1618 (e.g., a barometric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), memory 1626, a power supply 1630, and / or a camera 1632. The Bluetooth module 1612, the WLAN module 1614, and the SPS module 1616 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 1612, the WLAN module 1614, and the SPS module 1616 may include their own dedicated antennas and / or utilize antenna 1680 for communication. The cellular baseband processor 1624 communicates with the UE 204 and / or RUs associated with the network entity 1602 via the transceiver 1622 via one or more antennas 1680. The cellular baseband processor 1624 and the application processor 1606 may each include computer-readable media / memory 1624′, 1606′, respectively. Memory 1626 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1624′, 1606′, 1626 may be non-transitory. The cellular baseband processor 1624 and the application processor 1606 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the cellular baseband processor 1624 / application processor 1606, the software enables the cellular baseband processor 1624 / application processor 1606 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1624 / application processor 1606 when executing the software.The cellular baseband processor 1624 / application processor 1606 may be a component of the UE 450 and may include the memory 460 and / or at least one of the following: the TX processor 468, the RX processor 456, and the controller / processor 459. In one configuration, the device 1604 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1624 and / or the application processor 1606, while in another configuration, the device 1604 may be the entire UE (e.g., see. Figure 4 UE 450 ) and includes additional modules of device 1604.

[0233] As discussed above, component 198 may be configured to send a first message including a first indication associated with TAC granularity. Component 198 may be configured to receive a second message including a TAC configuration associated with TAC granularity. Component 198 may be configured to send a third message based on the TAC configuration. Component 198 may be within the cellular baseband processor 1624, the application processor 1606, or both. Component 198 may be one or more hardware components specifically configured to perform the recited processes / algorithms, implemented by one or more processors configured to perform the recited processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, device 1604 may include various components configured for various functions. In one configuration, device 1604 (and in particular, cellular baseband processor 1624 and / or application processor 1606) may include means for sending a first message including a first indication associated with TAC granularity. Apparatus 1604 may include means for receiving a second message including a TAC configuration associated with a TAC granularity. Apparatus 1604 may include means for sending a third message based on the TAC configuration. Apparatus 1604 may include means for receiving a fourth message including a second indication of a set of TAC granularities. Apparatus 1604 may include means for sending the first message in response to receiving the fourth message. Apparatus 1604 may include means for receiving the fourth message by receiving a SIB including the fourth message. Apparatus 1604 may include means for selecting a TAC granularity from the set of TAC granularities. The fourth message may include a scaling factor associated with a second TAC granularity. The TAC granularity may be based on the second TAC granularity and the scaling factor. The fourth message may include a third indication of a set of transmission formats for the first message. The set of transmission formats may include a UL MAC-CE format. The UL MAC-CE format may include a first field for the first indication. The set of transmission formats may include a UL RRC format. The UL RRC format may include a second field for the first indication. The set of transmission formats may include a UCI format. The UCI format may include a third field for a first indication. The set of transmission formats may include a PRACH format. The PRACH format may be associated with the first indication. The set of transmission formats may include a fourth indication for a first subset of PRACH sequences. The first subset of PRACH sequences may be associated with the first indication. The set of transmission formats may include a fifth indication for a second subset of RACH opportunities. The second subset of RACH indications may be associated with the first indication. The set of transmission formats may include a sixth indication for a DMRS. A DMRS port number may be associated with the first indication. The set of transmission formats may include a seventh indication for a DMRS generation function. The DMRS generation function may be associated with the first indication.The set of transmission formats may include an eighth indication of a PUSCH scrambling function associated with the first indication. The PUSCH scrambling function may be associated with the first indication. The set of transmission formats may include a first format comprising a set of reserved LCID codepoints for the first indication. The set of transmission formats may include a second format comprising a set of reserved fields in the MAC subheader for the first indication. The first message may include at least one of: (a) a PRACH format associated with the first indication; (b) a first subset of PRACH sequences associated with the first indication; (c) a second subset of RACH opportunities associated with the first indication; (d) a DMRS port number associated with the first indication; (e) a DMRS sequence; or (f) a PUSCH message. Apparatus 1604 may include means for generating a DMRS sequence based on the DMRS generation function associated with the first indication. Apparatus 1604 may include means for scrambling the PUSCH message based on the PUSCH scrambling function associated with the first indication. The fourth message may include the set of transmission formats for the first message. The set of transmission formats may include a UL MAC-CE format. The set of transmission formats may include a UL RRC format. The set of transmission formats may include a UCI format. The set of transmission formats may include a PRACH format. The set of transmission formats may include a third indication of a first subset of PRACH sequences. The set of transmission formats may include a fourth indication of a second subset of RACH opportunities. The set of transmission formats may include an Msg3 format. Apparatus 1604 may include means for generating a first indication by selecting a first value for the Msg3 format from a set of Msg3 DMRS port numbers. The fourth message may include a set of Msg3 DMRS port numbers. Apparatus 1604 may include means for generating the first indication by calculating a second value for the Msg3 format using a DMRS generation function. The fourth message may include a DMRS generation function. Apparatus 1604 may include means for generating the first indication by calculating a third value for the Msg3 format using a PUSCH scrambling function. The fourth message may include a PUSCH scrambling function. The apparatus 1604 may include means for generating a first indication by setting a fourth value for a set of reserved LCID code points for UL CCCH data in Msg3 format. The fourth message may include a fifth indication of the set of LCID code points. The apparatus 1604 may include means for generating a first indication by setting a fifth value for a set of reserved fields in a MAC subheader for UL CCCH data in Msg3 format. The fourth message may include a sixth indication of the set of reserved fields. The apparatus 1604 may include means for selecting a transmission format from a set of transmission formats. The apparatus 1604 may include means for transmitting the first message by transmitting the first message using the selected transmission format. The fourth message may include a TAC configuration table associated with the TAC configuration.Apparatus 1604 may include means for sending a third message based on the TAC configuration by calculating a TA based on the TAC configuration and a TAC configuration table. Apparatus 1604 may include means for sending a third message based on the calculated TA based on the TAC configuration. A fourth message may include a TAC configuration table for interpreting the TAC configuration. Apparatus 1604 may include means for sending a third message based on the TAC configuration by calculating a TA based on the TAC configuration table. Apparatus 1604 may include means for sending a third message based on the calculated TA based on the TAC configuration. Apparatus 1604 may include means for sending the third message based on the TAC configuration by sending the third message based on the calculated TA. Apparatus 1604 may include means for sending the third message to the NTN node. Apparatus 1604 may include means for receiving the TAC configuration by receiving a DL MAC-CE message including the TAC configuration. Apparatus 1604 may include means for receiving the TAC configuration by receiving a DL RRC message including the TAC configuration. Apparatus 1604 may include means for receiving the TAC configuration by receiving a DCI message including the TAC configuration. Apparatus 1604 may include means for receiving a TAC configuration by receiving a RA RUL grant including the TAC configuration. The DCI may include at least one of: a set of repurposed bits including the TAC configuration or a set of reserved bits. The set of reserved bits may include a first set of bits reserved for scheduling a DAI for a first transmission. The set of reserved bits may include a second set of bits reserved for scheduling a second transmission. The DCI may include DCI format 1_0 with a CRC scrambled by a TC-RNTI. The DCI may include a first set of bits. The set of reserved bits may include a first set of bits. The DCI may include DCI format 1_0 with a CRC scrambled by a RA-RNTI. The DCI may include a second set of bits. The set of reserved bits may include a second set of bits. The set of reserved bits may include a first set of bits reserved for scheduling a DAI for a Msg4 transmission. The set of reserved bits may include a second set of bits reserved for scheduling a Msg2 transmission. The Msg4 transmission may include DCI format 1_0 with a CRC scrambled by a TC-RNTI. The Msg2 transmission may include a DCI format 1_0 with a CRC scrambled by the RA-RNTI. The RAR UL grant may include a set of CSI request bits, which includes a TAC configuration. The means may be a component 198 of the apparatus 1604 configured to perform the functions recited by the means. As described above, the apparatus 1604 may include the TX processor 468, the RX processor 456, and the controller / processor 459. Thus, in one configuration, the means may be the TX processor 468, the RX processor 456, and / or the controller / processor 459 configured to perform the functions recited by the means.

[0234] Figure 17Diagram 1700 illustrates a non-limiting example of a hardware implementation for a network entity 1702. Network entity 1702 may be a base station (BS), a component of a BS, or may implement BS functionality. Network entity 1702 may include at least one of a CU 1710, a DU 1730, or a RU 1740. As non-limiting examples, depending on the layer functionality handled by component 199, network entity 1702 may include a CU 1710; both the CU 1710 and the DU 1730; each of the CU 1710, the DU 1730, and the RU 1740; the DU 1730; both the DU 1730 and the RU 1740; or the RU 1740. CU 1710 may include a CU processor 1712. CU processor 1712 may include on-chip memory 1712′. In some aspects, CU 1710 may also include an additional memory module 1714 and a communication interface 1718. The CU 1710 communicates with the DU 1730 via a midhaul link, such as an F1 interface. The DU 1730 may include a DU processor 1732. The DU processor 1732 may include on-chip memory 1732′. In some aspects, the DU 1730 may also include an additional memory module 1734 and a communication interface 1738. The DU 1730 communicates with the RU 1740 via a fronthaul link. The RU 1740 may include a RU processor 1742. The RU processor 1742 may include on-chip memory 1742′. In some aspects, the RU 1740 may also include an additional memory module 1744, one or more transceivers 1746, an antenna 1780, and a communication interface 1748. The RU 1740 communicates with the UE 204. On-chip memories 1712', 1732', 1742' and additional memory modules 1714, 1734, 1744 can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1712, 1732, 1742 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0235] As discussed above, component 199 may be configured to receive a first message including a first indication associated with TAC granularity. Component 199 may be configured to send a second message including a TAC configuration associated with TAC granularity based on the first indication. Component 199 may be configured to send a TAC. Component 199 may be configured to receive a third message based on the TAC configuration in response to receiving the TAC. Component 199 may be within one or more processors of one or more of CU 1710, DU 1730, and RU 1740. Component 199 may be one or more hardware components specifically configured to perform the recited processes / algorithms, implemented by one or more processors configured to perform the recited processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1702 may include a variety of components configured for various functions. In one configuration, network entity 1702 may include means for receiving a first message including a first indication associated with TAC granularity. Network entity 1702 may include means for sending a second message including a TAC configuration associated with a TAC granularity based on the first indication. Network entity 1702 may include means for sending a TAC. Network entity 1702 may include means for receiving a third message based on the TAC configuration in response to receiving the TAC. Network entity 1702 may include means for sending a fourth message including a second indication of a set of TAC granularities. The set of TAC granularities may include the TAC granularity. Network entity 1702 may include means for sending a fourth message by sending an SIB including the fourth message. The fourth message may include a scaling factor associated with the second TAC granularity. The TAC granularity may be based on the second TAC granularity and the scaling factor. The fourth message may include a third indication of a set of transmission formats for the first message. The set of transmission formats may include a UL MAC-CE format. The UL MAC-CE format may include a first field for the first indication. The set of transmission formats may include a UL RRC format. The UL RRC format may include a second field for the first indication. The set of transmission formats may include a UCI format. The UCI format may include a third field for a first indication. The set of transmission formats may include a PRACH format. The PRACH format may be associated with the first indication. The set of transmission formats may include a fourth indication for a first subset of PRACH sequences. The first subset of PRACH sequences may be associated with the first indication. The set of transmission formats may include a fifth indication for a second subset of RACH opportunities. The second subset of RACH indications may be associated with the first indication. The set of transmission formats may include a sixth indication for a DMRS. A DMRS port number may be associated with the first indication. The set of transmission formats may include a seventh indication for a DMRS generation function. The DMRS generation function may be associated with the first indication.The set of transmission formats may include an eighth indication of a PUSCH scrambling function associated with the first indication. The PUSCH scrambling function may be associated with the first indication. The set of transmission formats may include a first format comprising a set of reserved LCID codepoints for the first indication. The set of transmission formats may include a second format comprising a set of reserved fields in a MAC subheader for the first indication. The first message may include at least one of: (a) a PRACH format associated with the first indication; (b) a first subset of PRACH sequences associated with the first indication; (c) a second subset of RACH opportunities associated with the first indication; (d) a DMRS port number associated with the first indication; (e) a DMRS sequence; or (f) a PUSCH message. Network entity 1702 may include means for generating a DMRS sequence based on the DMRS generation function associated with the first indication. Network entity 1702 may include means for scrambling the PUSCH message based on the PUSCH scrambling function associated with the first indication. The set of transmission formats may include a transmission format of the first message. The fourth message may include a TAC configuration table associated with the TAC configuration. The fourth message may include a set of transmission formats for the first message. The set of transmission formats may include a UL MAC-CE format. The set of transmission formats may include a UL RRC format. The set of transmission formats may include a UCI format. The set of transmission formats may include a PRACH format. The set of transmission formats may include a third indication of a subset of PRACH sequences. The set of transmission formats may include a fourth indication of a subset of RACH opportunities. The set of transmission formats may include an Msg3 format. The fourth message may include a set of Msg3 DMRS port numbers, each corresponding to one TAC granularity in a set of TAC granularities. The fourth message may include a DMRS generation function for generating a DMRS sequence in Msg3 format based on one TAC granularity in the set of TAC granularities. The fourth message may include a PUSCH scrambling function for scrambling a PUSCH message in Msg3 format based on one TAC granularity in the set of TAC granularities. The fourth message may include a fifth indication of a set of LCID codepoints for UL CCCH data in Msg3 format. The set of LCID code points may indicate TAC granularity. The fourth message may include a sixth indication of a set of reserved fields of the Msg3 format. The set of reserved fields may indicate TAC granularity. The set of transmission formats may include the transmission format of the first message. The fourth message may include a TAC configuration table for interpreting the TAC configuration. The network node may include an NTN node or a base station communicating with the UE via the NTN node. The network entity 1702 may include a component for transmitting the TAC configuration by transmitting a DL MAC-CE including the TAC configuration. The network entity 1702 may include a component for transmitting the TAC configuration by transmitting a DL RRC message including the TAC configuration.Network entity 1702 may include means for transmitting the TAC configuration by transmitting DCI including the TAC configuration. Network entity 1702 may include means for transmitting the TAC configuration by transmitting an RAR UL grant including the TAC configuration. The DCI may include at least one of: a set of repurposed bits including the TAC configuration or a set of reserved bits. The set of reserved bits may include a first set of bits reserved for scheduling the DAI for the first transmission. The set of reserved bits may include a second set of bits reserved for scheduling the second transmission. The DCI may include DCI format 1_0 with a CRC scrambled by the TC-RNTI. The DCI may include the first set of bits. The set of reserved bits may include the first set of bits. The DCI may include DCI format 1_0 with a CRC scrambled by the RA-RNTI. The DCI may include the second set of bits. The set of reserved bits may include the second set of bits. The set of reserved bits may include the first set of bits reserved for scheduling the DAI for Msg4 transmission. The set of reserved bits may include the second set of bits reserved for scheduling Msg2 transmission. The Msg4 transmission may include a DCI format 1_0 with a CRC scrambled by the TC-RNTI. The Msg2 transmission may include a DCI format 1_0 with a CRC scrambled by the RA-RNTI. The RAR UL grant may include a set of CSI request bits, which includes a TAC configuration. The means may be a component 199 of the network entity 1702 configured to perform the functions recited by the means. As described above, the network entity 1702 may include the TX processor 416, the RX processor 470, and the controller / processor 475. Thus, in one configuration, the means may be the TX processor 416, the RX processor 470, and / or the controller / processor 475 configured to perform the functions recited by the means.

[0236] Figure 18Diagram 1800 illustrates a non-limiting example of a hardware implementation for a network entity 1860. In one example, network entity 1860 may be located within core network 220. Network entity 1860 may include a network processor 1812. Network processor 1812 may include on-chip memory 1812′. In some aspects, network entity 1860 may also include an additional memory module 1814. Network entity 1860 communicates with CU 1802 via a network interface 1880, either directly (e.g., a backhaul link) or indirectly (e.g., via a RIC). On-chip memory 1812′ and additional memory module 1814 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Processor 1812 is responsible for general processing, including executing software stored on the computer-readable medium / memory. This software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0237] As discussed above, component 199 may be configured to receive a first message including a first indication associated with TAC granularity. Component 199 may be configured to send a second message including a TAC configuration associated with the TAC granularity based on the first indication. Component 199 may be configured to send a TAC. Component 199 may be configured to receive a third message based on the TAC configuration in response to receiving the TAC. Component 199 may be within processor 1812. Component 199 may be one or more hardware components specifically configured to perform the recited processes / algorithms, implemented by one or more processors configured to perform the recited processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 1860 may include various components configured for various functions. In one configuration, network entity 1860 may include means for receiving a first message including a first indication associated with TAC granularity. Network entity 1860 may include means for sending a second message including a TAC configuration associated with the TAC granularity based on the first indication. Network entity 1860 may include means for sending a TAC. Network entity 1860 may include means for receiving a third message based on the TAC configuration in response to receiving the TAC. Network entity 1860 may include means for sending a fourth message including a second indication of a set of TAC granularities. The set of TAC granularities may include the TAC granularity. Network entity 1860 may include means for sending a fourth message by sending an SIB including the fourth message. The fourth message may include a scaling factor associated with the second TAC granularity. The TAC granularity may be based on the second TAC granularity and the scaling factor. The fourth message may include a set of transmission formats of the first message. The set of transmission formats may include a UL MAC-CE format. The set of transmission formats may include a UL RRC format. The set of transmission formats may include a UCI format. The set of transmission formats may include a PRACH format. The set of transmission formats may include a third indication of a subset of PRACH sequences. The set of transmission formats may include a fourth indication of a subset of RACH opportunities. The set of transmission formats may include an Msg3 format. The fourth message may include a set of Msg3 DMRS port numbers, each corresponding to one TAC granularity in the set of TAC granularities. The fourth message may include a DMRS generation function for generating a DMRS sequence in Msg3 format based on one TAC granularity in the set of TAC granularities. The fourth message may include a PUSCH scrambling function for scrambling a PUSCH message in Msg3 format based on one TAC granularity in the set of TAC granularities. The fourth message may include a fifth indication of a set of LCID code points for UL CCCH data in Msg3 format. The set of LCID code points may indicate the TAC granularity. The fourth message may include a sixth indication of a set of reserved fields in Msg3 format.The set of reserved fields may indicate TAC granularity. The set of transmission formats may include the transmission format of the first message. The fourth message may include a TAC configuration table for interpreting the TAC configuration. The network node may include an NTN node or a base station communicating with the UE via the NTN node. The network entity 1860 may include means for transmitting the TAC configuration by transmitting a DL MAC-CE including the TAC configuration. The network entity 1860 may include means for transmitting the TAC configuration by transmitting a DL RRC message including the TAC configuration. The network entity 1860 may include means for transmitting the TAC configuration by transmitting a DCI including the TAC configuration. The network entity 1860 may include means for transmitting the TAC configuration by transmitting a RAR UL grant including the TAC configuration. The DCI may include at least one of the following: a set of bits for repurposing the TAC configuration or a set of reserved bits. The set of reserved bits may include a first set of bits reserved for the DAI used to schedule Msg4 transmission. The set of reserved bits may include a second set of bits reserved for scheduling Msg2 transmission. The Msg4 transmission may include a DCI format 1_0 with a CRC scrambled by the TC-RNTI. The Msg2 transmission may include a DCI format 1_0 with a CRC scrambled by the RA-RNTI. The RAR UL grant may include a set of CSI request bits that include a TAC configuration. The means may be a component 199 of the network entity 1860 configured to perform the functions recited by the means. The means may be a component 199 of the network entity 1860 configured to perform the functions recited by the means.

[0238] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is merely illustrative of an exemplary method. It should be understood that the specific order or hierarchy of blocks in the process / flowchart may be rearranged based on design preferences. In addition, some blocks may be combined or omitted. The accompanying method claims provide elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0239] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be given the full scope consistent with the language of the claims. Unless otherwise specified, references to elements in the singular do not mean "one and only one," but rather "one or more." Terms such as "if," "when," and "while" do not imply a direct temporal relationship or reaction. That is, these phrases, such as "when...", do not imply immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the action to occur. The word "exemplary" is used herein to mean "serving as a non-limiting example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be interpreted as preferred or having an advantage over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, which may include multiple As, multiple Bs, or multiple Cs. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A, B, and C, where any such combination may include one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from or sends data to a second device, the data may be received / sent directly between the first and second devices, or indirectly between the first and second devices through a collection of devices. A device configured to "output" data (such as a transmission, signal, or message) may, for example, transmit the data using a transceiver, or may transmit the data to the device that transmitted the data. A device configured to "obtain" data (such as a transmission, signal, or message) may, for example, receive the data using a transceiver, or may obtain the data from the device that received the data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims.Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," and "device" are not intended to replace the word "component." Thus, no claim element is to be construed as part-plus-function unless the element is explicitly recited using the phrase "component for..."

[0240] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0241] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0242] Aspect 1 is a method of wireless communication at a UE, wherein the method may include: sending a first message including a first indication associated with a TAC granularity; receiving a second message including a TAC configuration associated with the TAC granularity; and sending a third message based on the TAC configuration.

[0243] Aspect 2 is a method according to aspect 1, wherein the method may include receiving a fourth message including a second indication of a set of TAC granularities. Sending the first message may be in response to receiving the fourth message.

[0244] Aspect 3 is a method according to aspect 2, wherein receiving the fourth message can include: receiving a SIB including the fourth message.

[0245] Aspect 4 is a method according to any one of aspects 2 or 3, wherein the method may include: selecting the TAC granularity from the set of TAC granularities.

[0246] Aspect 5 is a method according to any one of aspects 2 to 4, wherein the fourth message can include a scaling factor associated with the second TAC granularity.

[0247] Aspect 6 is a method according to aspect 5, wherein the TAC granularity can be based on the second TAC granularity and the scaling factor.

[0248] Aspect 7 is a method according to any one of aspects 2 to 6, wherein the fourth message can include a third indication of a set of transmission formats of the first message.

[0249] Aspect 8 is a method according to aspect 7, wherein the set of transmission formats may include a UL MAC-CE format. The UL MAC-CE format may include a first field for the first indication. The set of transmission formats may include a UL RRC format. The UL RRC format may include a second field for the first indication. The set of transmission formats may include a UCI format. The UCI format may include a third field for the first indication. The set of transmission formats may include a PRACH format. The PRACH format may be associated with the first indication. The set of transmission formats may include a fourth indication of a first subset of PRACH sequences. The first subset of PRACH sequences may be associated with the first indication. The set of transmission formats may include a fifth indication of a second subset of RACH opportunities. The second subset of RACH indications may be associated with the first indication. The set of transmission formats may include a sixth indication of a DMRS. The DMRS port number may be associated with the first indication. The set of transmission formats may include a seventh indication of a DMRS generation function. The DMRS generation function may be associated with the first indication. The set of transmission formats can include an eighth indication of a PUSCH scrambling function associated with the first indication. The PUSCH scrambling function can be associated with the first indication. The set of transmission formats can include a first format comprising a set of reserved LCID code points for the first indication. The set of transmission formats can include a second format comprising a set of reserved fields in a MAC subheader for the first indication.

[0250] Aspect 9 is a method according to any one of aspects 1 to 8, wherein the first message may include at least one of the following: (a) the PRACH format associated with the first indication; (b) the first subset of PRACH sequences associated with the first indication; (c) the second subset of RACH opportunities associated with the first indication; (d) the DMRS port number associated with the first indication; (e) a DMRS sequence; or (f) a PUSCH message. The method may include generating the DMRS sequence based on the DMRS generation function associated with the first indication. The method may include scrambling the PUSCH message based on the PUSCH scrambling function associated with the first indication.

[0251] Aspect 10 is a method according to any one of aspects 7 to 9, wherein the method may include: selecting the transmission format from the set of transmission formats. Sending the first message may include: sending the first message using the selected transmission format.

[0252] Aspect 11 is a method according to any one of aspects 2 to 10, wherein the fourth message may include a TAC configuration table associated with the TAC configuration. Sending the third message based on the TAC configuration may include calculating a TA based on the TAC configuration and the TAC configuration table. Sending the third message based on the TAC configuration may include sending the third message based on the calculated TA.

[0253] Aspect 12 is a method according to any one of aspects 1 to 11, wherein sending the third message can include: sending the third message to an NTN node.

[0254] Aspect 13 is a method according to any one of aspects 1 to 12, wherein receiving the TAC configuration may include: receiving a DL MAC-CE including the TAC configuration. Receiving the TAC configuration may include: receiving a DL RRC message including the TAC configuration. Receiving the TAC configuration may include: receiving a DCI including the TAC configuration. Receiving the TAC configuration may include: receiving a RAR UL grant including the TAC configuration.

[0255] Aspect 14 is a method according to aspect 13, wherein the DCI can include at least one of: a set of repurposed bits or a set of reserved bits including the TAC configuration.

[0256] Aspect 15 is a method according to aspect 14, wherein the set of reserved bits can include a first set of bits reserved for DAI for scheduling a first transmission. The set of reserved bits can include a second set of bits reserved for scheduling a second transmission.

[0257] Aspect 16 is a method according to aspect 15, wherein the DCI can include DCI format 1_0 with a CRC scrambled by TC-RNTI. The DCI can include the first set of bits. The set of reserved bits can include the first set of bits.

[0258] Aspect 17 is a method according to any one of aspects 15 or 16, wherein the DCI can include DCI format 1_0 with a CRC scrambled by RA-RNTI. The DCI can include the second set of bits. The set of reserved bits can include the second set of bits.

[0259] Aspect 18 is a method according to any one of aspects 13 to 17, wherein the RAR UL grant can include a set of CSI request bits, the set of CSI request bits including the TAC configuration.

[0260] Aspect 19 is a method of wireless communication at a network node, wherein the method may include receiving a first message including a first indication associated with a TAC granularity. The method may include sending a second message including a TAC configuration associated with the TAC granularity based on the first indication. The method may include sending a TAC. The method may include receiving a third message based on the TAC configuration in response to receiving the TAC.

[0261] Aspect 20 is a method according to aspect 19, wherein the method may include sending a fourth message including a second indication of a set of TAC granularities. The set of TAC granularities may include the TAC granularity.

[0262] Aspect 21 is a method according to aspect 20, wherein sending the fourth message may include: sending a SIB including the fourth message.

[0263] Aspect 22 is a method according to any one of aspects 20 or 21, wherein the fourth message can include a scaling factor associated with the second TAC granularity.

[0264] Aspect 23 is a method according to aspect 22, wherein the TAC granularity can be based on the second TAC granularity and the scaling factor.

[0265] Aspect 24 is a method according to any one of aspects 20 to 23, wherein the fourth message can include a third indication of a set of transmission formats of the first message.

[0266] Aspect 25 is a method according to aspect 24, wherein the set of transmission formats can include a UL MAC-CE format. The UL MAC-CE format can include a first field for the first indication. The set of transmission formats can include a UL RRC format. The UL RRC format can include a second field for the first indication. The set of transmission formats can include a UCI format. The UCI format can include a third field for the first indication. The set of transmission formats can include a PRACH format. The PRACH format can be associated with the first indication. The set of transmission formats can include a fourth indication of a first subset of PRACH sequences. The first subset of PRACH sequences can be associated with the first indication. The set of transmission formats can include a fifth indication of a second subset of RACH opportunities. The second subset of RACH indications can be associated with the first indication. The set of transmission formats can include a sixth indication of a DMRS. The DMRS port number can be associated with the first indication. The set of transmission formats can include a seventh indication of a DMRS generation function. The DMRS generation function can be associated with the first indication. The set of transmission formats can include an eighth indication of a PUSCH scrambling function associated with the first indication. The PUSCH scrambling function can be associated with the first indication. The set of transmission formats can include a first format comprising a set of reserved LCID code points for the first indication. The set of transmission formats can include a second format comprising a set of reserved fields in a MAC subheader for the first indication.

[0267] Aspect 26 is a method according to Aspect 25, wherein the first message may include at least one of the following: (a) the PRACH format associated with the first indication; (b) the first subset of PRACH sequences associated with the first indication; (c) the second subset of RACH opportunities associated with the first indication; (d) the DMRS port number associated with the first indication; (e) a DMRS sequence generated based on the DMRS generation function associated with the first indication; or (f) a PUSCH message generated based on the PUSCH scrambling function associated with the first indication.

[0268] Aspect 27 is a method according to any one of aspects 24 to 26, wherein the set of transmission formats can include the transmission format of the first message.

[0269] Aspect 28 is a method according to any one of aspects 20 to 27, wherein the fourth message can include a TAC configuration table associated with the TAC configuration.

[0270] Aspect 29 is a method according to any one of aspects 19 to 28, wherein the network node can include an NTN node or a base station that communicates with the UE via the NTN node.

[0271] Aspect 30 is a method according to any one of aspects 19 to 29, wherein the second message includes at least one of the following: (a) DL MAC-CE, the DL MAC-CE includes the TAC configuration; (b) DL RRC message, the DL RRC message includes the TAC configuration, (c) DCI, the DCI includes the TAC configuration; or (d) RAR UL grant, the RAR UL grant includes the TAC configuration.

[0272] Aspect 31 is a method according to aspect 30, wherein the DCI can include at least one of: a set of repurposed bits or a set of reserved bits including the TAC configuration.

[0273] Aspect 32 is a method according to any one of Aspect 31, wherein the set of reserved bits can include a first set of bits reserved for DAI for scheduling a first transmission. The set of reserved bits can include a second set of bits reserved for scheduling a second transmission.

[0274] Aspect 33 is a method according to aspect 32, wherein the DCI can include DCI format 1_0 with a CRC scrambled by TC-RNTI. The DCI can include the first set of bits. The set of reserved bits can include the first set of bits.

[0275] Aspect 34 is a method according to any one of aspects 32 or 33, wherein the DCI can include DCI format 1_0 with a CRC scrambled by the RA-RNTI. The DCI can include the second set of bits. The set of reserved bits can include the second set of bits.

[0276] Aspect 35 is a method according to any one of aspects 30 to 34, wherein the RAR UL grant can include a set of CSI request bits, the set of CSI request bits including the TAC configuration.

[0277] Aspect 36 is an apparatus for wireless communication, the apparatus comprising: a memory; and at least one processor coupled to the memory, the at least one processor configured to implement any one of aspects 1 to 35.

[0278] Aspect 37 is the apparatus of aspect 36, further comprising: at least one of an antenna or a transceiver coupled to the at least one processor.

[0279] Aspect 38 is an apparatus for wireless communication, comprising: means for implementing any one of aspects 1 to 35.

[0280] Aspect 39 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 35.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, the at least one processor configured to: sending a first message including a first indication associated with a timing advance command (TAC) granularity; receiving a second message including a TAC configuration associated with the TAC granularity; and A third message is sent based on the TAC configuration.

2. The apparatus of claim 1 , wherein the at least one processor is further configured to: A fourth message is received that includes a second indication of a set of TAC granularities, wherein to send the first message, the at least one processor is configured to send the first message in response to receiving the fourth message. 3 . The apparatus of claim 2 , wherein the fourth message comprises a system information block (SIB), the system information block (SIB) comprising the second indication.

4. The apparatus of claim 2, wherein the at least one processor is further configured to: The TAC granularity is selected from the set of TAC granularities. 5 . The apparatus of claim 2 , wherein the fourth message comprises a scaling factor associated with a second TAC granularity. The apparatus of claim 5 , wherein the TAC granularity is based on the second TAC granularity and the scaling factor. The apparatus of claim 2 , wherein the fourth message comprises a third indication of a set of transmission formats for the first message.

8. The apparatus of claim 7, wherein the set of transmission formats comprises at least one of: an uplink (UL) medium access control (MAC) control element (MAC-CE) format, the uplink (UL) medium access control (MAC) control element (MAC-CE) format comprising a first field for the first indication; a UL radio resource control (RRC) format comprising a second field for the first indication; a UL control information (UCI) format, the UL control information (UCI) format comprising a third field for the first indication; a physical random access channel (PRACH) format, the physical random access channel (PRACH) format being associated with the first indication; a fourth indication of a first subset of physical random access channel (PRACH) sequences associated with the first indication; a fifth indication of a second subset of random access channel (RACH) opportunities associated with the first indication; a sixth indication of a demodulation reference signal (DMRS) port number associated with the first indication; a seventh indication of a DMRS generation function associated with the first indication; an eighth indication of a physical uplink shared channel (PUSCH) scrambling function associated with the first indication; a first format comprising a set of reserved Logical Channel Identifier (LCID) code points for the first indication; or A second format comprising a set of reserved fields in a MAC subheader for the first indication.

9. The apparatus of claim 8, wherein the first message comprises at least one of: the PRACH format associated with the first indication; the first subset of PRACH sequences associated with the first indication; the second subset of RACH opportunities associated with the first indication; the DMRS port number associated with the first indication; a DMRS sequence, wherein the at least one processor is configured to generate the DMRS sequence based on the DMRS generation function associated with the first indication; or A PUSCH message, wherein the at least one processor is configured to scramble the PUSCH message based on the PUSCH scrambling function associated with the first indication.

10. The apparatus of claim 7, wherein the at least one processor is further configured to: The transmission format is selected from the set of transmission formats, wherein for transmitting the first message, the at least one processor is configured to transmit the first message using the selected transmission format.

11. The apparatus of claim 2, wherein the fourth message comprises a TAC configuration table associated with the TAC configuration, wherein to send the third message based on the TAC configuration, the at least one processor is configured to: calculating a timing advance (TA) based on the TAC configuration and the TAC configuration table; and The third message is sent based on the calculated TA.

12. The apparatus of claim 1 , further comprising a transceiver coupled to the at least one processor, wherein to send the third message, the at least one processor is configured to: The third message is sent to a non-terrestrial network (NTN) node via the transceiver.

13. The apparatus of claim 1 , wherein the second message comprises at least one of: a downlink (DL) medium access control (MAC) control element (MAC-CE), the downlink (DL) medium access control (MAC) control element (MAC-CE) including the TAC configuration; a DL radio resource control (RRC) message including the TAC configuration; Downlink Control Information (DCI), the Downlink Control Information (DCI) including the TAC configuration; or A random access response (RAR) uplink (UL) grant including the TAC configuration. 14 . The apparatus of claim 13 , wherein the DCI comprises at least one of: a set of repurposed bits comprising the TAC configuration or a set of reserved bits.

15. The apparatus of claim 14, wherein the set of reserved bits comprises at least one of: a first set of bits reserved for a downlink assignment index (DAI) for scheduling a first transmission; or A second set of bits is reserved for scheduling a second transmission.

16. The apparatus of claim 15, wherein the DCI comprises DCI format 1_0 having a cyclic redundancy check (CRC) scrambled by a temporary cell (TC) radio network temporary identifier (TC-RNTI) comprising the first set of bits.

17. The apparatus of claim 15, wherein the DCI comprises DCI format 1_0 having a cyclic redundancy check (CRC) scrambled by a random access (RA) radio network temporary identifier (RA-RNTI) comprising the second set of bits.

18. The apparatus of claim 13, wherein the RAR UL grant comprises a set of channel state information (CSI) request bits, the set of channel state information (CSI) request bits comprising the TAC configuration.

19. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and at least one processor coupled to the memory, the at least one processor configured to: receiving a first message including a first indication associated with a timing advance command (TAC) granularity; sending, based on the first indication, a second message including a TAC configuration associated with the TAC granularity; Send TAC; as well as A third message is received based on the TAC configuration in response to receiving the TAC.

20. The apparatus of claim 19, wherein the at least one processor is further configured to: A fourth message is sent including a second indication of a set of TAC granularities, wherein the set of TAC granularities includes the TAC granularity.

21. The apparatus of claim 20, wherein the fourth message comprises a system information block (SIB), the system information block (SIB) comprising the fourth message.

22. The apparatus of claim 20, wherein the fourth message comprises a scaling factor associated with a second TAC granularity.

23. The apparatus of claim 22, wherein the TAC granularity is based on the second TAC granularity and the scaling factor.

24. The apparatus of claim 20, wherein the fourth message comprises a third indication of a set of transmission formats for the first message.

25. The apparatus of claim 24, wherein the set of transmission formats comprises at least one of: an uplink (UL) medium access control (MAC) control element (MAC-CE) format, the uplink (UL) medium access control (MAC) control element (MAC-CE) format including the first indication; a UL radio resource control (RRC) format, the UL radio resource control (RRC) format including the first indication; a UL control information (UCI) format, the UL control information (UCI) format including the first indication; a physical random access channel (PRACH) format, the physical random access channel (PRACH) format being associated with the first indication; a fourth indication of a first subset of physical random access channel (PRACH) sequences associated with the first indication; a fifth indication of a second subset of random access channel (RACH) opportunities associated with the first indication; a sixth indication of a demodulation reference signal (DMRS) port number associated with the first indication; a seventh indication of a DMRS generation function associated with the first indication; an eighth indication of a physical uplink shared channel (PUSCH) scrambling function associated with the first indication; a first format comprising a set of reserved logical channel identifier (LCID) code points for UL common control channel (CCCH) data comprising the first indication; or A second format comprising a set of reserved fields in a MAC subheader for UL CCCH data comprising the first indication.

26. The apparatus of claim 25, wherein the first message comprises at least one of: the PRACH format associated with the first indication; the first subset of PRACH sequences associated with the first indication; the second subset of RACH opportunities associated with the first indication; the DMRS port number associated with the first indication; a DMRS sequence generated based on the DMRS generation function associated with the first indication; or A PUSCH message is generated based on the PUSCH scrambling function associated with the first indication.

27. The apparatus of claim 24, wherein the set of transmission formats comprises a transmission format of the first message.

28. The apparatus of claim 20, wherein the fourth message comprises a TAC configuration table associated with the TAC configuration.

29. A method of wireless communication at a user equipment (UE), the method comprising: sending a first message including a first indication associated with a timing advance command (TAC) granularity; receiving a second message including a TAC configuration associated with the TAC granularity; as well as A third message is sent based on the TAC configuration.

30. A method of wireless communication at a network node, the method comprising: receiving a first message including a first indication associated with a timing advance command (TAC) granularity; sending, based on the first indication, a second message including a TAC configuration associated with the TAC granularity; Send TAC; as well as A third message is received based on the TAC configuration in response to receiving the TAC.

Images