Timing advance for positioning

Abstract

Aspects of the present disclosure relate to methods, apparatuses, and systems for supporting TA for positioning. For example, implementations provide a set of signaling and procedure enhancements to enable timing advance (TA) and / or TA assisted positioning procedures on a non-terrestrial support network to be supported. Further, application and configuration aspects for TA-based and / or TA-assisted positioning are provided for both single-satellite and multi-satellite systems.

Description

[0001] Related Applications

[0002] This application claims priority to U.S. Provisional Application Serial No. 63 / 418,450, filed on October 21, 2022, entitled “TIMING ADVANCE FOR POSITIONING”, the disclosure of which is incorporated herein by reference in its entirety. This application also claims priority to U.S. Provisional Application Serial No. 63 / 418,455, filed on October 21, 2022, entitled “TIMING ADVANCE FOR POSITIONING”, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates to wireless communications, and more particularly to positioning in wireless communications. Background Art

[0004] A wireless communication system may include one or more network communication devices, such as a base station, which may be referred to as an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as a user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers). Additionally, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0005] Some wireless communication systems provide methods for device (eg, UE) positioning. However, such systems may not provide support for certain procedures for device positioning, particularly procedures involving non-terrestrial networks. Summary of the invention

[0006] The present disclosure relates to methods, apparatus and systems for supporting timing advance (TA) for positioning. For example, implementations provide a set of signaling and process enhancements to enable support for TA-based positioning procedures on NTN-supported networks. In addition, application and configuration aspects for TA-based positioning are provided for both single-satellite systems and multi-satellite systems.

[0007] By utilizing the described techniques, accurate and efficient determination of device location may be achieved.

[0008] Some implementations of the methods and apparatus described herein may further include: receiving an auxiliary configuration message indicating that multiple TA measurements corresponding to multiple measurement time instances are performed, wherein: each measurement time instance is associated with at least one cell, and the auxiliary configuration message includes TA-related parameters and measurement reference signal configuration corresponding to the at least one cell; performing at least one TA measurement based at least in part on the received auxiliary configuration message, the at least one TA measurement corresponding to at least one measurement time instance in the multiple measurement time instances; and sending a TA positioning report including at least one TA measurement.

[0009] Some implementations of the methods and apparatus described herein may further include: wherein the TA-related parameters include at least one of the following items: satellite ephemeris information, epoch time, common TA parameters, or validity duration; multiple measurement time instances include time instances within the validity duration; the auxiliary configuration message includes measurement instance separation information, and the multiple measurement time instances are determined at least in part based on the measurement instance separation information; a first subset of the multiple measurement time instances includes time instances within a first validity duration, and a second subset of the multiple measurement time instances includes time instances within a second validity duration; the first validity duration is associated with a first set of one or more of the satellite ephemeris or common TA parameters, and the second validity duration is associated with a second set of one or more of the satellite ephemeris or common TA parameters.

[0010] Some implementations of the methods and apparatus described herein may also include: wherein a first subset of the plurality of measurement time instances is associated with a first cell in at least one cell, and a second subset of the plurality of measurement time instances is associated with a second cell in at least one cell; further including: receiving a TA parameter broadcast message for positioning, and wherein the TA parameter broadcast message includes information about at least one of the following items: satellite ephemeris information, epoch time, common TA parameters, validity duration, or reference point; further including: periodically receiving a TA parameter broadcast message, and wherein the TA parameter broadcast message is associated with at least one validity duration; receiving a capability information request related to TA-based positioning from a network; and sending one or more capability parameters based at least in part on the capability information request; the capability information request includes information about an indication of support for TA calculations for positioning; the capability information request includes information about support for user-specific TA position estimation methods; the one or more capability parameters include at least one of the following items: an indication of support for TA positioning calculations for positioning, a user-specific TA position estimation method, a number of satellite nodes in a coverage area, or polarization capability.

[0011] Some implementations of the methods and apparatus described herein may further include: sending an auxiliary configuration message indicating that multiple TA measurements corresponding to multiple measurement time instances are performed, wherein: each measurement time instance is associated with at least one cell, and the auxiliary configuration message includes TA-related parameters and measurement reference signal configuration corresponding to the at least one cell; and receiving a TA positioning report including at least one TA measurement based at least in part on the auxiliary configuration message.

[0012] Some implementations of the methods and apparatus described herein may also include: wherein the TA-related parameters include at least one of the following items: satellite ephemeris information, epoch time, common TA parameters, or validity duration; multiple measurement time instances include time instances within the validity duration; the auxiliary configuration message includes measurement instance separation information; a first subset of multiple measurement time instances includes time instances within a first validity duration, and a second subset of multiple measurement time instances includes time instances within a second validity duration; the first validity duration is associated with a first set of one or more of the satellite ephemeris or common TA parameters, and the second validity duration is associated with a second set of one or more of the satellite ephemeris or common TA parameters; and also includes: sending a capability information request from a network associated with TA-based positioning; and receiving one or more capability parameters based at least in part on the capability information request. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 An example of a wireless communication system supporting TA for positioning according to aspects of the present disclosure is illustrated.

[0014] Figure 2 Illustrated is a system in which positioning reference signals may be utilized to acquire positioning measurements.

[0015] Figure 3 An example of assistance data configuration implementation regarding UE measurement and reporting configuration signaling applicable to downlink based positioning techniques is illustrated.

[0016] Figure 4 An example of a positioning measurement report is illustrated.

[0017] Figure 5 An example architecture suitable for NG-RAN for UE positioning is illustrated.

[0018] Figure 6 The sequence of signaling events is illustrated.

[0019] Figure 7 Illustration of the transparent satellite-based NG-RAN architecture.

[0020] Figure 8An example of a transparent satellite-based NG-RAN architecture with mapping to Quality of Service (QoS) flows is illustrated.

[0021] Fig. 9 An example of a UE user plane protocol stack for a transparent satellite-based NG-RAN architecture is illustrated.

[0022] Fig.10 An example of a control plane protocol stack for a transparent satellite-based NG-RAN architecture is illustrated.

[0023] Fig.11 An NG-RAN architecture based on a regenerative satellite is illustrated, such as a regenerative satellite without inter-satellite links (ISLs) and with gNB-processed payloads.

[0024] Fig.12 Another example of a regenerative satellite based NG-RAN architecture, such as a regenerative satellite system with ISLs, is illustrated.

[0025] Fig.13 An example of a regenerative satellite-based NG-RAN architecture with onboard gNBs and QoS flows is illustrated.

[0026] Fig.14 An example of a UE user plane protocol stack for a PDU session is illustrated.

[0027] Fig.15 An example of a UE control plane protocol stack for a PDU session is illustrated.

[0028] Fig.16 An example of open-loop TA in NTN is illustrated.

[0029] Fig.17 An example is illustrated in which TA measurements at multiple time instances may be performed.

[0030] Fig.18 Depicted are example error IEs supporting TA for positioning according to aspects of the present disclosure.

[0031] Fig.19 Depicted are example error IEs supporting TA for positioning according to aspects of the present disclosure.

[0032] Fig. 20 An example TA measurement process is depicted that supports TA for positioning according to aspects of the present disclosure.

[0033] Fig.21 Depicted are example TA capability request IEs that support TAs for positioning according to aspects of the present disclosure.

[0034] Fig. 22Depicted are example TA capability response IEs that support a TA for positioning according to aspects of the present disclosure.

[0035] Fig.23 Depicted is an example information exchange process to support TA for positioning according to aspects of the present disclosure.

[0036] Fig.24 Depicted are example TA assistance data IEs supporting TA for positioning according to aspects of the present disclosure.

[0037] Fig.25a and Fig.25b An example scenario of supporting TA for positioning according to aspects of the present disclosure is illustrated.

[0038] Fig.26 and Fig. 27 An example block diagram of a device supporting TA for positioning according to aspects of the present disclosure is illustrated.

[0039] Figures 28 to 33 A flow chart of a method of supporting TA for positioning according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0040] In wireless communication systems, a concern is to enable configuration, measurement, processing and reporting of radio access technology (RAT) related positioning for a target UE connected to a non-terrestrial based network without significantly reducing positioning accuracy and latency. For example, depending on the configured positioning method, certain configuration signaling parameters from the network function need to be adapted to enable the target UE to report the required and accurate positioning measurements in a low-latency manner. Specifically, in a non-terrestrial network (NTN), the number of satellites providing coverage for the UE may be limited. This may mean that the positioning method may be applicable to only one satellite. In addition, regulatory and emergency requirements in NTNs may not specify sufficiently accurate positioning parameters. With regard to the use of the TA procedure in device positioning, current wireless communication systems do not provide support for such a procedure, particularly in the context of NTNs.

[0041] Therefore, the present disclosure provides technologies to support TA for positioning. For example, the implementation provides a set of signaling and process enhancements to enable support for TA-based positioning processes on NTN-supported networks. In addition, application and configuration aspects for TA-based positioning are provided for both single-satellite systems and multi-satellite systems.

[0042] For example, in an implementation, a location server (e.g., LMF) exchanges TA positioning capabilities with a target UE and a next generation radio access (NG-RAN) node (e.g., using LTE Positioning Protocol (LPP) and NR Positioning Protocol Additional (NRPPa) signaling), and based on the exchanged capability information, the location server configures parameters to the target UE to calculate TA estimates and / or position estimates with reference to a single satellite at different orbital coordinates. In this case, LLP can be used as an end-to-end protocol between the location server and the target UE to estimate the position of the target UE.

[0043] The implementation also provides signaling (e.g., LPP signaling) as an end-to-end protocol between a location server and a target UE to exchange capabilities for implementing a TA positioning process, wherein the location server may initiate a capability transfer process using a request and provide a capability message to enable capabilities related to supporting a TA-based positioning process to be transferred from the target UE to the location server.

[0044] In implementation, the NRPPa location information transfer procedure is used to handle the transfer of TA-based positioning related information between the NTN NG-RAN node and the location server (e.g., LMF). In addition, based on the capability exchange information (e.g., from the target UE and / or NG-RAN node), the location server can configure the target user with assistance that can be used to estimate the target UE position, and the location server can exchange request and provide assistance data (e.g., positioning configuration) messages for assistance data.

[0045] In an implementation, the location server configures TA parameters to the target UE, wherein the TA parameters are associated with multiple satellites and / or cell IDs that may serve one NG-RAN node or multiple NG-RAN nodes. For example, the configuration indicated by the TA parameters may be based on information received during a capability exchange between the location server and the target UE and / or between the location server and (multiple) NG-RAN nodes.

[0046] Thus, by utilizing the described techniques, accurate and efficient determination of device location may be achieved.

[0047] Aspects of the disclosure are described in the context of a wireless communication system.Aspects of the disclosure are also illustrated and described with reference to device diagrams and flow diagrams.

[0048] Figure 1An example of a wireless communication system 100 supporting TA for positioning according to aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0049] One or more network entities 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a RAN, a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. The network entity 102 and the UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, the network entity 102 and the UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0050] The network entity 102 may provide a geographic coverage area 112 for which the network entity 102 supports services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, the network entity 102 and the UE 104 may support wireless communications of signals associated with services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0051] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc. In some implementations, UE 104 may be stationary in the wireless communication system 100. In some other implementations, UE 104 may be mobile in the wireless communication system 100.

[0052] One or more UEs 104 may be devices in different forms or with different capabilities. Figure 1 Some examples of UE 104 are illustrated in FIG. Figure 1 As shown, the UE 104 is capable of communicating with various types of devices, such as a network entity 102, other UEs 104, or a network device (e.g., a core network 106, a packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network device). Additionally or alternatively, the UE 104 can support communication with other network entities 102 or UEs 104 that can act as relays in the wireless communication system 100.

[0053] The UE 104 may also be capable of supporting wireless communications directly with other UEs 104 via a communication link 114. For example, the UE 104 may support wireless communications directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, V2X deployments, or cellular V2X deployments, the communication link 114 may be referred to as a sidelink. For example, the UE 104 may support wireless communications directly with another UE 104 via a PC5 interface.

[0054] The network entity 102 may support communication with the core network 106 or with another network entity 102 or both. For example, the network entity 102 may be connected to the core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2 or another network interface). The network entities 102 may communicate with each other via the backhaul links 116 (e.g., via X2, Xn or another network interface). In some implementations, the network entities 102 may communicate directly with each other (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio heads, smart radio heads, or transport reception points (TRPs)).

[0055] In some implementations, the network entity 102 may be configured in a decomposed architecture that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 102 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC (near real-time (RT) RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof.

[0056] The RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). In a decomposed RAN architecture, one or more components of the network entity 102 may be collocated, or one or more components of the network entity 102 may be located at distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0057] The functional split between CU, DU and RU can be flexible, and different functions can be supported according to the functions performed at the CU, DU or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions and any combination thereof). For example, a functional split of the protocol stack can be adopted between the CU and the DU, so that the CU can support one or more layers of the protocol stack, and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and one or more DUs or RUs can host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, media access control (MAC) layer) functions and signaling, and each DU or RU can be at least partially controlled by the CU.

[0058] Additionally or alternatively, a functional split of the protocol stack may be employed between the DU and the RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and the DU or between the DU and the RU may be within the protocol layer (e.g., some functions for the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer may be performed by different items of the CU, DU, or RU).

[0059] The CU may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU may be connected to one or more DUs via a medium-range communication link (e.g., F1, F1-c, F1-u), and the DU may be connected to one or more RUs via a fronthaul communication link (e.g., an open fronthaul (FH) interface). In some implementations, the medium-range communication link or the fronthaul communication link may be implemented according to interfaces (e.g., channels) between layers of a protocol stack supported by a corresponding network entity 102 communicating via such a communication link.

[0060] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)), and user plane entities that route packets or interconnections to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0061] The core network 106 may communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UE 104 may establish a session (e.g., a PDU session, etc.) with the core network 106 via the network entity 102. The core network 106 may route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0062] In the wireless communication system 100, the network entity 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers) to perform various operations (e.g., wireless communication). In some implementations, the network entity 102 and the UE 104 may support different resource structures. For example, the network entity 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the network entity 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the network entity 102 and the UE 104 may support various frame structures (e.g., multiple frame structures). The network entity 102 and the UE 104 may support various frame structures based on one or more digital technologies.

[0063] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefixes. A first digital technology (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15kHz) and a conventional cyclic prefix. A first digital technology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15kHz) may utilize one slot per subframe. A second digital technology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a conventional cyclic prefix. A third digital technology (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60kHz) and a conventional cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120kHz) and a conventional cyclic prefix. A fifth digital technology (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a conventional cyclic prefix.

[0064] The time intervals of resources (e.g., communication resources) can be organized according to frames (also referred to as radio frames). Each frame can have a duration, for example, a duration of 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, a duration of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0065] Additionally or alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols). In some implementations, the number (e.g., quantity) of time slots for a subframe may depend on the digital technology. For a conventional cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60kHz subcarrier spacing), a time slot may include 12 symbols. For a conventional cyclic prefix and an extended cyclic prefix, the relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame may depend on the digital technology. It should be understood that references to a first digital technology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15kHz) may be used interchangeably between subframes and time slots.

[0066] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc. based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, the network entity 102 and the UE 104 can perform wireless communications on the one or more operating frequency bands. In some implementations, FR1 can be used by the network entity 102 and the UE 104 and other devices or apparatuses for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by the network entity 102 and the UE 104 and other devices or apparatuses for short-range, high data rate capabilities.

[0067] FR1 may be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 may be associated with a first digital technology (e.g., μ=0) including a subcarrier spacing of 15 kHz; a second digital technology (e.g., μ=1) including a subcarrier spacing of 30 kHz; and a third digital technology (e.g., μ=2) including a subcarrier spacing of 60 kHz. FR2 may be associated with one or more digital technologies (e.g., at least 2 digital technologies). For example, FR2 may be associated with a third digital technology (e.g., μ=2) including a subcarrier spacing of 60 kHz; and a fourth digital technology (e.g., μ=3) including a subcarrier spacing of 120 kHz.

[0068] According to the implementation of TA for positioning, the network entity 102 (e.g., LMF, location server, etc.) generates an auxiliary configuration message 120 and sends the auxiliary configuration message 120 to the UE 104. For example, the auxiliary configuration message 120 indicates that a plurality of TA measurements corresponding to a plurality of measurement time instances are performed, wherein each measurement time instance is associated with at least one cell, and the auxiliary configuration message 120 includes a TA-related parameter and a measurement reference signal configuration corresponding to the at least one cell.

[0069] The UE 104 receives the secondary configuration message 120 and performs TA measurements 122 based at least in part on information (e.g., timing information and TA-related parameters) from the secondary configuration message 120. The UE 104 generates a TA measurement report 124 including the TA measurements and sends the TA measurement report 124 to the network entity 102. The network entity 102 may estimate a position and / or location of the UE 104 using the TA measurements from the TA measurement report 124.

[0070] In some wireless communication systems, NR positioning based on NR Uu signals and standalone (SA) architecture (e.g., beam-based transmission) is specified. Target use cases include commercial and regulatory (emergency services) scenarios. Performance parameters include the following [Technical Report (TR) 38.855]:

[0071] Positioning error indoor outdoor Horizontal positioning For 80% of UEs < 3m For 80% of UEs < 10m Vertical positioning For 80% of UEs < 3m For 80% of UEs < 3m

[0072] Additionally, some systems specify positioning performance parameters for commercial and IIoT use cases as follows [TR 38.857]:

[0073]

[0074] At least some of the supported positioning technologies are listed in Table 1 below [TS38.305]:

[0075] Table 1

[0076]

[0077]

[0078] Currently, the individual positioning techniques shown in Table 1 can be configured and performed based on the requirements of LMF and UE capabilities. The transmission of positioning reference signals (PRS) enables the UE to perform UE positioning related measurements to enable the calculation of the UE's position estimate, and the positioning techniques are configured for each transmission reception point (TRP), where a TRP can transmit one or more beams.

[0079] The following RAT-related positioning technologies [TS38.305] can be supported:

[0080] The downlink time difference of arrival (DL-TDOA) positioning method utilizes the DL reference signal time difference (RSTD) (and optionally the DL PRS reference signal received power (RSRP)) of downlink signals received from multiple TPs at the UE. The UE measures the DL RSTD (and optionally the DL PRS RSRP) of the received signal using assistance data received from the positioning server, and the resulting measurements are used together with other configuration information to position the UE relative to neighboring TPs.

[0081] The DL AoD positioning method utilizes the measured DL PRS RSRP of downlink signals received from multiple TPs at the UE. The UE uses the assistance data received from the positioning server to measure the DL PRS RSRP of the received signal, and the resulting measurement is used together with other configuration information to position the UE relative to neighboring TPs.

[0082] The multiple round trip time (RTT) positioning method utilizes UE Rx-Tx measurements and DL PRS RSRP of downlink signals received from multiple TRPs measured by the UE, and gNB Rx-Tx measurements and uplink (UL) sounding reference signal (SRS)-RSRP measured at multiple TRPs of uplink signals sent from the UE. The UE measures the UE Rx-Tx measurements (and optionally the DL PRS RSRP of the received signal) using assistance data received from the positioning server, and the TRPs measure the gNB Rx-Tx measurements (and optionally the UL SRS-RSRP of the received signal) using assistance data received from the positioning server. The measurements are used to determine the RTT at the positioning server, which is used to estimate the UE's position.

[0083] In the enhanced cell identifier (E-CID) positioning method, the UE's position is estimated using knowledge of its serving ng-eNB, gNB, and cell, and is based on LTE signals. Information about the serving ng-eNB, gNB, and cell can be obtained through paging, registration, or other methods. NR enhanced cell ID (NR E-CID) positioning refers to a technique that uses NR signals to improve UE position estimates using additional UE measurements and / or NR radio resources and other measurements. Although NR E-CID positioning can utilize some of the same measurements as the measurement control system in the RRC protocol, it is generally not expected that the UE will make additional measurements solely for positioning purposes; for example, the positioning process does not provide measurement configuration or measurement control messages, and the UE reports measurements that it already has available without taking additional measurement actions.

[0084] The UL TDOA positioning method utilizes the UL TDOA (and optionally the UL SRS-RSRP) of an uplink signal sent from a UE at multiple reception points (RPs). The RP measures the UL TDOA (and optionally the UL SRS-RSRP) of the received signal using assistance data received from a positioning server, and the resulting measurements are used together with other configuration information to estimate the UE's position.

[0085] The UL AoA positioning method utilizes the measured azimuth and zenith of arrival of uplink signals sent from the UE at multiple RPs. The RP uses the assistance data received from the positioning server to measure the A-AoA and Z-AoA of the received signal, and the resulting measurements are used together with other configuration information to estimate the position of the UE.

[0086] RAT-independent positioning techniques can also be implemented, including [TS38.305]:

[0087] Network-assisted Global Navigation Satellite System (GNSS) methods: These methods utilize UEs equipped with radio receivers capable of receiving GNSS signals. In the 3GPP specifications, the term GNSS includes both global and regional / augmented navigation satellite systems. Examples of global navigation satellite systems include the Global Positioning System (GPS), modernized GPS, Galileo, GLONASS, and the BeiDou Navigation Satellite System (BDS). Regional navigation satellite systems include the Quasi-Zenith Satellite System (QZSS), while some augmentation systems are classified as a general term for Space-Based Augmentation Systems (SBAS) and provide regional augmentation services. In this concept, different GNSS (e.g., GPS, Galileo, etc.) can be used alone or in combination to determine the position of the UE.

[0088] Barometric pressure sensor positioning: The barometric pressure sensor method uses a barometric pressure sensor to determine the vertical component of the UE's position. The UE measures the air pressure (optionally with the help of assistance data) to calculate the vertical component of its position, or sends the measurement to a positioning server for position calculation. This method can be combined with other positioning methods to determine the 3D position of the UE.

[0089] Wireless Local Area Network (WLAN) Positioning: WLAN positioning methods use WLAN measurements (access point (AP) identifiers and optional other measurements) and a database to determine the location of the UE. The UE measures the signals received from the WLAN access points (optionally with the help of assistance data) to send the measurements to the positioning server for position calculation. Using the measurement results and the reference database, the position of the UE is calculated. Alternatively, the UE uses WLAN measurements and optional WLAN AP assistance data provided by the positioning server to determine its position.

[0090] Bluetooth positioning: The Bluetooth positioning method uses Bluetooth measurements (beacon identifiers and optional other measurements) to determine the location of the UE. The UE measures the signals received from the Bluetooth beacons. Using the measurement results and a reference database, the UE's position is calculated. The Bluetooth method can be combined with other positioning methods (e.g., WLAN) to improve the positioning accuracy of the UE.

[0091] TBS positioning: TBS consists of a network of ground-based transmitters that broadcast signals for positioning purposes only. The current types of TBS positioning signals are MBS (Metropolitan Beacon System) signals and PRS (Technical Specification (TS) 36.211 [4]). The UE measures the received TBS signals (optionally with the help of assistance data) to calculate its position, or sends the measurements to a positioning server for position calculation.

[0092] Motion sensor positioning: The motion sensor method uses different sensors such as accelerometers, gyroscopes, magnetometers, etc. to calculate the displacement of the UE. The UE estimates the relative displacement based on a reference position and / or a reference time. The UE sends a report including the determined relative displacement, which can be used to determine the absolute position. This method can be used for hybrid positioning with other positioning methods.

[0093] Figure 2 A system 200 is illustrated in which positioning reference signals may be utilized to obtain positioning measurements. For example, PRS may be transmitted by different base stations (serving base station and neighboring base stations) using narrow beams over FR1 and FR2, which is relatively different from LTE where PRS is transmitted throughout the cell. PRS may be locally associated with a PRS resource ID and resource set ID for a base station (TRP). Similarly, UE positioning measurements such as reference signal time difference (RSTD) and PRS RSRP measurements are performed between beams (e.g., between different DL PRS resource pairs or DL ​​PRS resource sets), rather than between different cells as is the case in LTE. In addition, there are additional UL positioning methods for the network to calculate the position of the target UE.

[0094] Tables 2 and 3 show the mapping of reference signals to measurements required for each of the supported RAT-dependent positioning techniques at the UE and gNB, respectively. RAT-dependent positioning techniques involve 3GPP RAT and core network entities to perform UE position estimation, which is different from RAT-independent positioning techniques that rely on GNSS, inertial measurement unit (IMU) sensors, WLAN, and Bluetooth technologies to perform target device (UE) positioning.

[0095] Table 2: UE measurements implementing RAT-related positioning techniques

[0096]

[0097] Table 3: gNB measurements implementing RAT-related positioning techniques

[0098]

[0099]

[0100] Figure 3 An example of an assistance data configuration 300 (implementing Rel-16 TS38.215) for UE measurement and reporting configuration signaling applicable to downlink-based positioning techniques is illustrated. In the DL-TDOA assistance data, the information element (IE) NR-DL-TDOA-ProvideAssistanceData 302 can be used by the location server to provide assistance data to achieve UE-assisted and UE-based NR DL-TDOA, and can also be used to provide NR DL-TDOA positioning specific error causes.

[0101] Figure 4 An example of a positioning measurement report 400 (currently implementing Rel-16) is illustrated. The UE measurement and reporting configuration includes signaling applicable to downlink based positioning techniques. In the DL-TDOA measurement report, NR DL-TDOA measurements are provided to the location server by the target UE using the IE NR-DL-TDOA-SignalMeasurementInformation 402. These measurements are provided as a list of TRPs, where the first TRP in the list is used as the reference TRP in the case of reporting RSTD measurements. The first TRP in the list may or may not be the reference TRP indicated in the NR-DL-PRS-AssistanceData. In addition, the target UE selects a reference resource for each TRP and compiles measurements for each TRP based on the selected reference resource.

[0102] The different downlink measurements required for the supported RAT-related positioning techniques, including downlink PRS RSRP, downlink RSTD, and UE Rx-Tx time difference, are shown in Table 4. The measurement configuration may include four (4) downlink RSTD measurement pairs performed for each cell pair, and each measurement is performed between a different downlink PRS resource pair or resource set with a single reference timing; and eight (8) downlink PRS reference signal received power (RSRP) measurements may be performed on different downlink PRS resources from the same cell.

[0103] Table 4: Downlink measurements for downlink based positioning techniques.

[0104]

[0105]

[0106]

[0107] To comply with regulatory requirements, the network may be configured to enforce that the selected public land mobile network (PLMN) is allowed to operate in the country where the UE is located by verifying the UE location during mobility management and session management procedures. In this case, the AMF may decide to verify the UE location when it receives a Next Generation Application Protocol (NGAP) message containing user location information for a UE using NR satellite access. If the AMF determines that it is not allowed to operate in the current UE location based on the selected PLMN ID and User Location Information (ULI) (including cell ID) received from the gNB, the AMF may reject the request and inform the UE of the country of the UE location.

[0108] If the AMF based on the ULI does not know the UE location accurately enough to make a final decision, the AMF continues with the mobility management or session management procedures and may initiate the UE location procedure as specified in clause 6.10.1 of TS 23.273

[87] to determine the UE location. In the case of a NAS procedure, the AMF may reject any NAS request for a PLMN that is not allowed to operate at the known UE location and indicate an appropriate cause value and, if known in the AMF, the country of the UE location, or accept the NAS procedure and then register the UE once the UE location is known.

[0109] In case of a handover procedure, the AMF rejects the handover if the (target) AMF determines that it is not allowed to operate at the current UE location, or accepts the handover and then de-registers the UE.

[0110] Network selection for NR satellite access: The network selection principles specified in clause 5.2.2 can also be used for NR satellite access. For NR satellite access, a UE with location capabilities can use its awareness of its location to select a PLMN that is allowed to operate in the country where the UE is located as specified in TS 23.122

[17] . To comply with regulatory requirements, the network can be configured to enforce this UE selection by verifying the UE location, as described in clause 5.4.11.4.

[0111] Support of Mobility Registration Update: A radio cell for NR satellite access may indicate support of one or more TACs per PLMN. A UE registered with a PLMN may access a radio cell and need not perform a Mobility Registration Update procedure as long as at least one supported Tracking Area Code (TAC) for the registered Public Land Mobile Network (RPLMN) or equivalent to the RPLMN is part of the UE registration area. A UE may perform a Mobility Registration Update procedure when accessing a radio cell where none of the supported TACs for the RPLMN or equivalent to the RPLMN is part of the UE registration area.

[0112] Figure 5 An example architecture 500 of an NG-RAN 502 suitable for UE positioning is illustrated. The NG-RAN 502 is capable of supporting two types of interfaces, LTE Uu and NR Uu, and the gNB 504 can be implemented in the NTN architecture. The gNB 504 and the LTE Next Generation Evolved NodeB (ng-eNB) 506 are connected via an Xn backhaul interface. The access and mobility management function (AMF) 508 can be transparent or bypassed in the NTN architecture, and the LMF 510 provides positioning technology and configuration for UE positioning.

[0113] The AMF 508 may receive a request for a certain location service associated with a specific target UE 104 from another entity (e.g., a Gateway Mobile Location Center (GMLC) or a UE), or the AMF itself may decide to initiate a certain location service on behalf of a specific target UE, such as an Internet Protocol (IP) Multimedia Subsystem (IMS) emergency call from a UE. The AMF 508 then sends a location service request to the LMF 510. The LMF 510 processes the location service request, which may include transmitting assistance data to the target UE 104 to assist in UE-based and / or UE-assisted positioning, and / or may include the positioning of the target UE. The LMF 510 then returns the result of the location service to the AMF 508 (e.g., a location estimate for the UE 104). In the case where the location service is requested by an entity other than the AMF (e.g., requested by a GMLC or a UE), the AMF 508 returns the location service result to that entity.

[0114] The NG-RAN node may control several TRPs and / or TPs, such as remote radio heads, or downlink PRS-only TPs for supporting a PRS-based terrestrial beacon system (TBS). The LMF 510 may have a dedicated signaling connection to an enhanced serving mobile location center (E-SMLC), which may enable the LMF 510 to access information from the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) (e.g., using downlink measurements of signals from the next generation evolved NodeB (ng-eNB) and / or PRS-only TPs in the E-UTRAN acquired by the target UE to support the observed time difference of arrival (OTDOA) for the Evolved Universal Terrestrial Radio Access (E-UTRA) positioning method). The LMF 510 may have a dedicated signaling connection to a SUPL Positioning Platform (SLP). The SLP is a secure user plane positioning (SUPL) entity responsible for positioning on the user plane. In the case of a split gNB architecture, the gNB distributed unit (DU) 512 may include TRP functionality, where the TRP functionality may support functionality for a transmission point (TP), RP, or both. The gNB-DU 512 including the TRP functionality is not required to provide cell services. To support positioning of target UEs and delivery of location assistance data to UEs with NG-RAN access in 5GS, location-related functionality is distributed as shown in the example architecture 500.

[0115] Figure 6 An overall sequence 600 of signaling events applicable to a UE 104, NG-RAN 502, AMF 508, and LMF 510 for any location service is illustrated. When the AMF 508 receives a location service request (LSR), and the UE 104 is in a connection management (CM) idle state (CM-IDLE) state, the AMF 508 performs a network-triggered service request to establish a signaling connection with the UE and allocate a specific serving gNB or next generation evolved NodeB (ng-eNB). It is assumed that the UE is in connected mode before the signaling shown in the figure begins (e.g., signaling that may be required to put the UE into connected mode before step 1a is not shown). However, the signaling connection may be released later, such as by the NG-RAN 502 node, due to signaling and data inactivity while positioning is still in progress. Additionally, the NG-RAN 502 node represents any combination of NTS in an NTN, including a network architecture with a terrestrial network (TN) and NTN gNBs, and / or a network architecture that is entirely an NTN with a NG-RAN architecture.

[0116] At step 1, step 1a, step 1b, or step 1c is performed. At step 1a, an entity in the 5GC (such as the GMLC) requests a location service for locating the target UE 104 from the serving AMF 508. Alternatively, at step 1b, the serving AMF 508 for the target UE 104 determines a need for location services (e.g., locating the UE for an emergency call). Alternatively, at step 1c, the UE 104 requests location services, such as for delivery of positioning or assistance data, from the serving AMF 508 at the non-access stratum (NAS) level.

[0117] At step 2, the AMF 508 transmits a location service request to the LMF 510. At step 3a, the LMF 510 starts a positioning procedure with the serving and possibly neighboring next generation evolved NodeBs (ng-eNBs) or gNBs in the ng-RAN 502, such as to obtain positioning measurements or assistance data. In addition to step 3a or alternatively (instead of step 3a), at step 3b, the LMF 510 starts a positioning procedure with the UE 104, such as to obtain a position estimate or positioning measurements, or to transmit location assistance data to the UE.

[0118] At step 4, the LMF 510 provides a location services response to the AMF 508, and includes any required results, such as a success or failure indication, and a location estimate for the UE 104 (if requested and obtained). At step 5a (if step 1a is performed), the AMF 508 returns a location services response to the 5GC entity in step 1a, and includes any required results, such as a location estimate for the UE 104. At step 5b (if step 1b occurs), the AMF 508 uses the location services response received in step 4 to assist the service that triggered the response in step 1b, such as to provide a location estimate associated with an emergency call to the GMLC. At step 5c (if step 1c is performed), the AMF 508 returns a location services response to the UE 104, and includes any required results, such as a location estimate for the UE.

[0119] In terms of positioning in NTN, the positioning process applicable to NG-RAN occurs in steps 3a and 3b, which supports configuration and reporting for communication between LMF 510 and UE 104 to achieve NTN system-level positioning. Steps 3a and 3b may involve using different positioning methods (also referred to herein as positioning techniques or positioning processes) to obtain location-related measurements for the target UE, and from these measurements, the UE calculates a position estimate and additional positioning assistance information.

[0120] Figure 7A transparent satellite-based NG-RAN architecture 700 is illustrated. The satellite payload implements frequency conversion and radio frequency amplifiers in both the uplink direction and the downlink direction, and it corresponds to an analog RF repeater. Therefore, the satellite (e.g., the network entity 102) repeats the NR-Uu radio interface from the feeder link between the NTN gateway 702 and the satellite to the service link between the satellite and the UE 104 (and vice versa). The satellite radio interface (SRI) on the feeder link is NR Uu, which means that the satellite does not terminate the NR Uu radio interface. The NTN gateway 702 can support all necessary functions to forward signals of the NR-Uu interface, and different transparent satellites can be connected to the same gNB 704 on the ground. Note that although several gNBs can access a single satellite payload, the illustration and description are simplified to one gNB 704 accessing the satellite payload without loss of generality.

[0121] Figure 8 An example 800 of a transparent satellite-based NG-RAN architecture with mapping to Quality of Service (QoS) flows is illustrated. A UE 104 has access to a 5G system via a 3GPP NR-based radio interface. Fig. 9 An example of a UE user plane protocol stack for a transparent satellite-based NG-RAN architecture is illustrated 900. User data is transmitted between the UE 104 and the 5GC via the NTN gateway. Fig.10 An example of a control plane protocol stack for a transparent satellite-based NG-RAN architecture is illustrated 1000. Non-access stratum (NAS) session management (NAS-SM) and NAS mobility management (MM) signaling from the UE 104 and NG-AP signaling from the gNB are transmitted to the 5GC and vice versa.

[0122] Fig.11 A regenerative satellite based NG-RAN architecture 1100 is illustrated, such as a regenerative satellite without inter-satellite links (ISLs) and with a gNB-processed payload. The NG-RAN logical architecture can be used as a baseline for NTN. The satellite payload implements the regeneration of signals received from ground-based network nodes. In this architecture 1100, the NR-Uu radio interface is implemented on a service link between the UE 104 and the satellite (e.g., the network entity 102), and the satellite radio interface (SRI) is implemented on a feeder link between the NTN gateway 1102 and the satellite. The satellite radio interface (SRI) is a transport link between the NTN gateway 1102 and the satellite.

[0123] Fig.12Another example of a regenerative satellite-based NG-RAN architecture 1200 is illustrated, such as a regenerative satellite system with ISLs. An ISL is a transport link between satellites (e.g., network entities 102), such as a radio interface or an optical interface. The NTN gateway 1202 is a transport network layer node and supports all necessary transport protocols. In this architecture 1200, a UE 104 served by an onboard gNB on a satellite can access the 5GCN via an ISL. In implementation, onboard gNBs on different satellites can be connected to the same 5GCN on the ground, and if the satellite hosts more than one gNB, the same satellite radio interface (SRI) can be used to transmit all corresponding NG interface instances. In this architecture, a protocol stack of the satellite radio interface (SRI) is used to transmit the UE user plane between the satellite and the NTN gateway 1202. User protocol data units (PDUs) are transmitted over a general packet radio service (GPRS) tunneling protocol (GTP) GTP-U tunnel between the 5GCN and the onboard gNB via the NTN gateway 1202. NG-AP is transmitted between 5GCN and onboard gNB via NTN gateway through Stream Control Transmission Protocol (SCTP). NAS protocol is also transmitted between 5GCN and onboard gNB via NTN gateway by NG-AP protocol.

[0124] Fig.13 An example 1300 of a regenerative satellite-based NG-RAN architecture with onboard gNBs and quality of service (QoS) flows is illustrated. Fig.14 An example 1400 of a UE user plane protocol stack for a PDU session for a regenerative satellite-based NG-RAN architecture with an onboard gNB is illustrated. The protocol stack of the satellite radio interface (SRI) is used to transmit the UE user plane between the satellite and the NTN gateway. The user protocol data unit (PDU) is transmitted over a GTP-U tunnel between the 5GC and the onboard gNB via the NTN gateway. Fig.15 An example 1500 of a UE control plane protocol stack for a PDU session for a regenerative satellite-based NG-RAN architecture with an onboard gNB is illustrated. The NG-AP is communicated between the 5GC and the onboard gNB via the NTN gateway over SCTP. The non-access stratum (NAS) protocol is also communicated between the 5GC and the onboard gNB by the NG-AP protocol via the NTN gateway.

[0125] Fig.16An example 1600 of open-loop TA in NTN is illustrated. For non-terrestrial networks with transparent payload architecture, an open-loop TA approach may be employed, where the TA may be divided into two parts, such as a common TA and a user-specific TA. The common TA may be defined as a network-controlled beam and / or a cell-specific common TA, and may include a timing offset utilized by the network, and this is common to users in one cell. The UE-specific TA is a TA estimated by the UE itself to pre-compensate for service link delay, as shown in example 1600.

[0126] Fig.17 An example 1700 is illustrated in which TA measurements at multiple (e.g., three) time instances may be performed. For example, if the one-way propagation delay from the satellite to the UE 104 at three points in space is known, the UE position estimate may be calculated by converting the delay to a distance, such as (d=τ / c, where c is the speed of light). In example 1600, TA measurements at three time instances may be performed, taking into account that a non-geosynchronous satellite orbit (NGSO) satellite is moving relative to the UE. In other implementations, more than three time instances may also be configured, which may improve the accuracy of the distance. The intersection of the three distances may correspond to the UE position. Therefore, a positioning method based on TA calculation in an NTN may be formulated that may be applied to a single satellite or based on TA calculations from multiple satellites.

[0127] In implementation, an auxiliary data configuration is provided for implementing a TA-based positioning method and a related capability exchange process for the TA positioning method from a location server (e.g., LMF) to a NG-RAN node and a target user. In addition, the present disclosure discusses a measurement configuration and reporting process for calculating a TA-based UE position for both single-satellite and multi-satellite scenarios. In implementation, the TA-based positioning method can be implemented by an NG-RAN node and / or directly by a location server. Therefore, the measurement configuration and reporting process can be applied to the LTE Positioning Protocol (LPP) and / or NRPPa protocol discussed in the present disclosure.

[0128] The present disclosure also provides signaling aspects for TA-based positioning procedures, such as positioning procedures for implementing TA positioning methods. For example, a capability exchange procedure from a location server to an NG-RAN node and a target user is provided. Parameter configuration aspects are also provided for performing TA measurements for single satellite cases and multi-satellite cases.

[0129] The implementations discussed in the present disclosure may be implemented individually or in combination with one another to support NR TA-based positioning using supported NTN interfaces and network entities / nodes. In addition, for the purposes of the present disclosure, positioning-related reference signals may be referred to as reference signals used for positioning processes and / or purposes to estimate the position of a target UE (e.g., PRS) and / or based on existing reference signals (such as channel state information reference signals (CSI-RS) or SRS). In addition, a target UE may be referred to as a device and / or entity to be located and / or positioned. In various implementations, the term "PRS" may refer to signals such as reference signals, which may or may not be used primarily for positioning. In addition, a target UE may be referred to as a UE, device, and / or entity of interest, whose position will be acquired by the network and / or by the UE itself.

[0130] In an implementation of the present disclosure, a TA positioning measurement and reporting process is provided. For example, the target UE is configured by a location server using LPP to perform TA positioning measurements, and the target UE can perform such measurements based on configured resources and report the measurements to the location server. For example, the measurements can correspond to a single satellite node or multiple satellite nodes. In addition, the TA-based measurement configuration may include parameters and associated behaviors for implementing a reporting mechanism specified by a positioning calculation entity (e.g., LMF).

[0131] In an implementation, the location server explicitly requests TA-based location measurement data and / or TA-based positioning estimates from the target UE using a request / provide location information message. For example, a location server (e.g., LMF) may send a RequestLocationInformation LPP message to the target UE, which indicates what types of measurements and location-related data may be included in the UE's location information report. Thus, a TA location information request IE may be formulated that contains information about the location information report. In at least one example, an IE (e.g., TA-RequestLocationInformation) may request the following information in its report:

[0132] Position estimation

[0133] The type of report, such as immediate report, one-time report, periodic report, event-based report, scheduled report in advance or for future time instances, etc.

[0134] Position report format

[0135] TA estimation, such as common TA and / or user-specific TA

[0136] Timestamp

[0137] Distance calculation

[0138] UE positioning method for user-specific TA calculation

[0139] In an implementation, the location server may request a report of the target UE's calculated TA measurements. In response to the location information request, the target UE may report the TA positioning location measurements and / or location estimates to the location server via LPP (e.g., via the exchange of ProvideLocationInformation LPP messages). The message may include the information requested by the location server in the RequestLocationInformation LPP message and / or additional information related to the target UE. In at least one example, the report may include the following parameters and / or fields:

[0140] Reference signal information: Information about the reference signal on which the measurement is performed. For example, if PRS is used, the DL-PRS resource may be identified using information about the PRS ID and PRS resource ID. If another RS ​​or signal type is used, the corresponding ID information identifying the measurement of the resource may be signaled.

[0141] Cell measurement elements: Parameters related to the cell may also be included in the report. For example, parameters such as physical cell ID, TRP ID and cell global ID may be part of the information in the report.

[0142] • Neighbor cell measurement elements: In the scenario where measurements are performed, information about neighbor cells, such as the physical cell ID, bandwidth part (BWP), and polarization information of the neighbor cell, may be included in the report.

[0143] TA measurements: The target UE may indicate TA measurements, which may include common TA measurements, user-specific TA measurements and / or differential TA measurements. In the case where multiple measurements are performed at different time instances, multiple measurements with corresponding timestamps may be included in the report. Information about the validity duration of the measurements may also be part of the report.

[0144] • Timestamp: A timestamp may be included indicating an association with a time instance at which a TA measurement was performed. One or more timestamps may be reported.

[0145] • Ephemeris information: Ephemeris information based on which the user-specific TA is calculated at one or more time instances may also be part of the report.

[0146] Distance calculation: The target UE may calculate the distance between its position and the satellite position at one or more time instances, e.g. according to the UE configuration. In this scenario, the distance calculated at one or more time instances may be included in the report, and

[0147] A corresponding timestamp may also be indicated.

[0148] · Location estimate: The target user may also report their location estimate in a configured format (e.g., latitude and longitude) and / or using one or more geographic shapes (such as an ellipsoid point, an ellipsoid point with an uncertainty circle, an ellipsoid point with an uncertainty ellipse, a high-accuracy ellipsoid point with an uncertainty ellipse, a polygon, an ellipsoid point with an altitude, an ellipsoid point with an altitude and an uncertainty ellipsoid, a high-accuracy ellipsoid point with an altitude and an uncertainty ellipsoid, an ellipsoid arc, or a combination thereof).

[0149] • UE positioning method used for user-specific TA calculation: The location information report may also include information about the type of RAT-independent method used for user-specific TA calculation.

[0150] In an implementation, the target UE transmits location measurement data and / or a location estimate to the location server even in the absence of a request. In an implementation, the location server may also configure a response time to the target UE in the request message, during which the location server expects a response message of a TA measurement report. In a scenario of TA-based location estimation for a single satellite node, the response time may include at least a configured measurement window (e.g., within which the target UE calculates TA estimates, distances, and / or locations for multiple time instances) and a propagation delay time between the target UE and the location server. In at least one implementation, if the target UE cannot perform the entire measurement group during the response time, the target UE may reduce the number of measurements in order to comply with the configured reporting time response.

[0151] In an implementation, the target UE is configured with resources on multiple satellite nodes and is configured to perform measurements on multiple satellite nodes. For example, the multi-satellite measurement configuration is indicated in the assistance data configuration and / or the measurement and reporting message (e.g., RequestLocationInformation message). In this scenario, the target UE can perform measurements on resources from different satellite nodes, and the target UE can be configured to send a separate measurement report for each satellite node measurement or a combined report indicating the measurements from each satellite node. In some scenarios, one satellite node can act as a serving reference cell, while other information from other satellite nodes can be considered as neighboring cells. In at least one implementation, when a single report contains information about measurements from different satellite nodes (e.g., TRP), the target device will explicitly indicate in its report which measurements are related to which satellite node (e.g., TRP). For example, an IE (e.g., TA-SignalMeasurementInformation) can be used, which contains measurements corresponding to the serving reference cell and the neighboring cell. In at least some implementations, when a resource is configured for TA measurements corresponding to a cell, the resource can be punctured in other (e.g., neighboring) cells.

[0152] In implementations, the location server may explicitly allow additional location information messages when measurements for each of the multiple satellite nodes are to be reported back in separate messages and / or measurement reports exceed a specified number of satellite nodes that can be allocated in one message. In this scenario, the target device may send additional ProvideLocationInformation messages to the server, where the last message may include an endTransaction IE set to "true" to indicate that this is the last message.

[0153] The implementation described in the present disclosure also provides for TA-based positioning error handling and abort procedures. For example, when the target UE and / or location server receives erroneous and / or unexpected data or detects that some data is missing in performing a task for TA positioning, it initiates an LPP error and / or abort message. For example, the target UE receives a RequestLocationInformation message from a location server, and after receiving it, the target UE checks whether the requested information is compatible with the target device capabilities and configurations, for example, the UE location estimation method for calculating a user-specific TA is no longer available. If the target UE does not support this capability, the target UE can generate an LPP error message. After receiving the error message, the location server can abort the ongoing process or provide specified information.

[0154] Fig.18An example error IE 1800 supporting TA for positioning according to aspects of the present disclosure is depicted. In at least one implementation, the error IE 1800 (eg, TA error) may be used by a location server and / or a target device to provide a TA error cause to a target UE and / or location server, respectively.

[0155] Fig.19 An example error IE 1900 supporting TA for positioning according to aspects of the present disclosure is depicted. In implementations, the TA-LocationServerErrorCauses IE (e.g., Error IE 1900) may be used by a location server to provide the cause of the TA error to a target UE, and the TA-TargetDeviceErrorCauses IE may be used by a target UE to explain the TA error cause to the location server.

[0156] In implementation, the target UE IE may also describe the cause for the error. For example, the following list of events and / or causes may generate an error message from the target UE:

[0157] Changes in satellite coverage areas

[0158] The location estimation method used for UE-specific TA calculation is not supported and / or is not available

[0159] The response time for the report is less than a threshold, for example, the threshold is the propagation time plus the processing time.

[0160] The implementations described herein also provide for TA positioning measurements and reporting using NRPPa. For example, the NRPPa location information transfer procedure is used to handle the transfer of TA positioning measurement reports between NTN NG-RAN nodes and a location server (e.g., LMF), such as in scenarios where an NG RAN-based TA positioning measurement and reporting procedure is implemented to estimate a TA-based target UE position estimate.

[0161] In an implementation, the location server may request a report of TA measurements (e.g., common TA and / or user-specific TA) from a NG-RAN node. The NG-RAN node may be implemented as a gNB, a gateway, a satellite, or a combination thereof. Based on the received TA measurements and the corresponding mapping parameters, the location server may calculate the target user location. In at least one implementation, measurements for TA positioning may be performed by the NG-RAN node, such as initiated by the location server, and the measurements may be reported to the location server by the NG-RAN node after receiving a request message from the location server.

[0162] Fig. 20An example TA measurement process 2000 is depicted that supports TA for positioning according to aspects of the present disclosure. For example, the TA measurement process 2000 is implemented using NRPPa.

[0163] In the TA measurement procedure 2000, the LMF 2002 (e.g., a location server) initiates the procedure by sending a TA measurement request message 2004 to a NG-RAN node 2006 (e.g., a gNB). The TA measurement request message 2004 may contain information about the type of TA measurement to be reported. The NG-RAN node 2006 receives the TA measurement request message 2004 and may respond to the LMF 2002 with a TA measurement response message 2008, for example, if the NG-RAN node is able to initiate the requested TA measurement.

[0164] In an implementation, information about the measurement report type (e.g., as requested by the location server) may be included in an IE (e.g., Report Characteristics IE). In at least one implementation, the location server may request a single measurement report, for example by setting a field in the Report Characteristics IE. In this scenario, and in at least one implementation, the NG-RAN node may initiate a TA Measurement Response message to indicate support for TA measurements, and then separately send a TA Measurement Report message containing the specific TA measurements. In at least one implementation, the NG-RAN node may return the TA measurement results in a TA Measurement Response message 2008. In addition to the TA calculation, the following information may be included in the report message to convert the TA measurement results into a positioning estimate:

[0165] Timestamp: The time when the UE calculates the TA measurement

[0166] Ephemeris information: satellite coordinates in single or multiple formats

[0167] Epoch time

[0168] Cell characteristics: cell-related parameters

[0169] In implementation, the location server may request that multiple TA measurements (e.g., the number of measurements may be indicated by a field) be reported in a single report (which may be indicated by a field). In this scenario, the time window for the measurement report may also be set by the location server, for example, and may be indicated in the request message. After receiving this type of information in the message, the NG-RAN node may initiate a TA response message to indicate to the location server that the measurement procedure has been initiated and that the TA calculation and corresponding parameters will be sent via the measurement report message.

[0170] After the TA measurement procedure is completed, the NG-RAN node may send the TA measurements along with additional information to the location server in a TA Measurement Report message. The additional information in the report message may include a timestamp calculated for each TA, ephemeris information at each TA measurement, epoch time, etc. In at least one implementation, the NG-RAN node may request additional time in the response message, such as if the configured time window is too small to perform the measurement. In at least one implementation, if the NG-RAN cannot perform the measurement in the indicated time window, the NG-RAN node may respond to the location server with a TA Measurement Failure message. The failure message may include an indication of the reason for the failure, such as the time window being too small.

[0171] In an implementation, the location server may request the NG-RAN node to perform periodic measurements and report back the measurement results. For example, such a request may be indicated by the location server in a configuration or reporting IE, such as in the ReportCharacteristics IE. For example, if the field in the Report Characteristics IE is set to "Periodic", the NG-RAN node may initiate the requested measurement and may answer with a first TA measurement in a TA Measurement Response message, or may indicate that a measurement report will be sent subsequently. The NG-RAN node may periodically initiate a TA measurement reporting procedure for measurements, such as with a requested reporting periodicity. In at least one implementation, the reporting periodicity period is set by the location server, and the NG-RAN node terminates the measurement reporting after the reporting periodicity period expires.

[0172] In at least one example, the location server explicitly instructs the NG-RAN node in a separate message to terminate the periodic TA measurement report. Such an implementation may be implemented by the LMF by generating a TA measurement termination command. In at least one implementation, each measurement report during a period of the period may correspond to one TA calculation at one satellite position and at one time instance. Information about the satellite position, epoch time, and TA calculation with a timestamp may be part of each report. In at least one implementation, each periodic report may correspond to TA results for multiple time instances, where the time window may be defined by the location server associated with each report. For example, each report may contain multiple TA measurement results calculated over a period of time (e.g., as defined by the time window) and repeated periodically.

[0173] In at least some implementations, the location server may request event-based reporting triggers and / or measurement reports at certain time instances in the future, which may be scheduled and / or defined based on specified time instances. One or more future time instances may also be requested to report TA-based measurements and / or location estimates. The NG-RAN node may respond with positioning measurements based on event-based and / or configured future time instance reports.

[0174] In at least one implementation, the target UE sends user-specific TA information and / or differential TA information (e.g., relative to previously sent TA information) to the NG-RAN node using one or more of the following: uplink control information (UCI), uplink medium access control element (MAC-CE), RRC, physical uplink shared channel (PUSCH), or a combination thereof, and such behavior may be explicitly requested by the NG-RAN node and / or any network entity. In at least one implementation, the target UE autonomously sends (e.g., independent of a request from the NG-RAN node and / or other network entities) user-specific TA information and / or differential TA information (e.g., relative to previously sent TA information) to the NG-RAN node.

[0175] The implementation also provides support for TA-assisted RAT-related positioning procedures. For example, in the implementation, RAT-related methods such as NR E-CID can utilize TA measurements as well as measurements of the RAT-related methods themselves to assist and / or enhance the accuracy of the deployed positioning methods, where the TA measurements can be included in the same and / or separate measurement reports. For example, in the NRE-CID method, TA measurements can be read together with RSRP measurements to improve the accuracy of the NR-CID method. This may be advantageous in NTNs, where the cell size can be large and therefore the accuracy of NR E-CID can be improved. TA measurement information can be requested by the location server to the NG-RAN node using NRPPa and / or by the location server to the target UE using LPP. In at least one implementation, the TA measurements are explicitly requested by the location server in a report configuration having a field indicating that the TA measurements will be included in the RAT-related method report. In at least one implementation, the NG-RAN node and / or the target UE implicitly includes TA measurements in the positioning method report, where the inclusion of TA measurements can be based on the type of positioning method adopted. For example, when NR E-CID method measurements are requested, the target UE and / or NG-RAN node may include TA measurements in its reports.

[0176] In implementations, assistance information (e.g., common TA parameters and user-specific TA parameters) that may transform and / or assist in TA measurements is also included in the report, where the information may or may not be explicitly requested by the location server. For example, the assistance information may include information about the satellite ephemeris when the measurement was made, the timestamp when the measurement was made, the type of reference signal on which the measurement was done, etc.

[0177] In at least one implementation, when the NG-RAN node is configured by the location server to report TA measurements as well as its own method-specific measurements (e.g., measurements for the NR E-CID method), the NG-RAN node may initiate new TA measurements in scenarios where previous TA measurements are not available and / or are considered outdated. In such scenarios, the NG-RAN node may indicate to the location server that previous TA measurements are not available or have been outdated, and that new measurements will be provided in subsequent reports. In at least one implementation, the location server may also associate a time window for which TA measurements are to be provided, where the time window may be specific to TA measurements. In at least one example, when the time window is associated with other measurements (e.g., RSRP measurements for E-CID), the same time window may also be valid for TA measurements.

[0178] The implementation described in the present disclosure also provides TA-based positioning configuration and capability exchange for a single satellite. For example, in the implementation, the location server exchanges TA positioning capabilities with the target UE and the NG-RAN node using LPP and NRPPa signaling. Based on the capability exchange information, the location server can configure parameters to the target UE to calculate TA estimates and / or position estimates with reference to a single satellite at different orbital coordinates. In this scenario, LPP can be used as an end-to-end protocol between the location server and the target UE to estimate the position of the target UE using TA-based location-related measurements acquired by one or more reference sources (e.g., GNSS and NG-RAN). The following set of message types can be used to facilitate the necessary NTN TA configuration and capability exchange processes:

[0179] Request capability;

[0180] Provide capabilities;

[0181] Request assistance data;

[0182] Provide auxiliary data.

[0183] The implementation described in the present disclosure also provides positioning preparation using capability exchange between the location server and the target UE. For example, LPP signaling is used as an end-to-end protocol between the location server and the target UE to exchange capabilities for implementing TA positioning. For example, the location server uses a request / provide capability message to initiate a capability transfer process to enable the transfer of capabilities related to supporting TA-based positioning from the target UE to the location server. The exchange of capability information for NTN devices and / or TN devices can be implemented. In at least one implementation, the location server can use an IE (e.g., nr-TA-RequestCapabilities) to request the target UE to support TA-based positioning capabilities, and request TA-based location capabilities from the target UE. The request may include one or more of the following items: support for TA-based positioning, support for TA measurement windows, user-specific TA location estimates (e.g., geodetic coordinates, longitude and latitude, distance (e.g., in meters, kilometers, etc.), user-specific TA location estimate sources (e.g., GNSS, Bluetooth, WiFi, etc.), satellite modes, satellite connectivity types, polarization capabilities, etc.

[0184] Fig.21 An example TA Capabilities Request IE 2100 supporting a TA for positioning according to aspects of the present disclosure is depicted. For example, the TA Capabilities Request IE 2100 represents an instance of the nr-TA-RequestCapabilities IE.

[0185] In an implementation, in response to the request capabilities message, the target UE indicates its ability to support the NR TA positioning method and provide its NR TA positioning capabilities to the location server by exchanging ProvideCapabilities messages. In one implementation, the target device may provide this information using an IE (e.g., nr-TA-ProvideCapabilities).

[0186] Fig. 22An example TA Capability Response IE 2200 for supporting TA for positioning according to aspects of the present disclosure is depicted. For example, the TA Capability Response IE 2200 represents an instance of the nr-TA-ProvideCapabilities IE. In an implementation, the IE may include information indicating whether the target UE supports TA-based positioning, which may be indicated by two bits, where 0 may indicate no support and 1 may indicate support. In addition, information about the type(s) of the position method(s) used to calculate its own position estimate (e.g., further used in the user-specific TA calculation) may be indicated. For example, the user-specific TA calculation may be based on the UE GNSS capability, and if the target UE does not have GNSS capability, the target UE may indicate that TA positioning is not supported. In at least one implementation, the user-specific TA calculation may be based on a position estimate using a RAT-independent positioning method, such as GNSS, Bluetooth, WLAN (such as Wi-Fi), etc. In such a scenario, the target UE may indicate these methods, which may also be used for user-specific calculations. In addition, other information about satellite coverage (e.g., single-satellite and / or multi-satellite TA methods) and target UE polarization capabilities may be part of the information exchange.

[0187] The implementation described in the present disclosure also provides for information exchange between the NG-RAN node and the location server. For example, in the implementation, the NRPPa location information transfer procedure is used to handle the transfer of TA-based positioning related information between the NTN NG-RAN node and the location server (e.g., LMF). The NRPPa procedure can be used for information exchange, and the location server can also use this information to facilitate TA-based positioning using LPP. For example, this enables the LMF to request the NG-RAN node to transmit TA positioning method information to the LMF. The NRPPa procedure can be based on a TA information request message from the LMF to the NG-RAN node, where such a message can request the following information:

[0188] Cell Information: This may include information about Physical Cell Identity (PCI), Cell ID, TAC, BWP Id, etc. In addition, information about the cell type employed may also be specified, e.g., geo-fixed, quasi-geo-fixed, or geo-mobile cells, in order to correctly implement the TA positioning method.

[0189] Reference signal information: The location server may request parameters regarding the type of reference signal to be used for the TA positioning method. For example, if PRS is to be used, information such as PRS bandwidth, PRS configuration index, PRS occasion group, and PRS frequency hopping configuration may be part of the request message. In at least one implementation, if PRS is to be used for TA measurements, the location server may initiate a PRS configuration exchange procedure to request the NG-RAN node to configure or update (e.g., turn off) PRS transmission.

[0190] Public TA parameters: TA public parameters with epoch time and validity duration may be requested by the location server. In at least one implementation, multiple public TA parameters for different time instances may be used by the LMF to implement a TA based positioning method. In such a scenario, a request may be included where a field may be used to indicate that the requested public TA parameters are used for different time instances. In at least one implementation, a time separation window between two public TA parameters may also be included in the request to enable the NG-RAN node to indicate that one or more sets of public TA parameters are to be used for TA based positioning.

[0191] Ephemeris information: Satellite ephemeris information may be used by the target UE to calculate user-specific TA and / or differential TA. The location server may request satellite ephemeris information for a single time instance and / or multiple time instances, where the format type of the ephemeris information may also be indicated to the NG-RAN node. In at least one implementation, the request may contain a single format, such as format 1 (e.g., satellite position and velocity state vectors) and / or format 2, such as orbital parameter ephemeris format. In at least one implementation, ephemeris information in multiple formats may be requested.

[0192] Reference point coordinates: Coordinates with respect to a reference point (e.g., where uplink and downlink signals are offset N TA，offset Information for frame alignment may also be requested and used for user-specific TA or differential TA calculations. Such information requests may include reference point coordinates, reference point coordinate accuracy, and reference point location.

[0193] Polarization information: The polarization capability of the TRP (eg, satellite) may also be used by the location server to avoid polarization mismatch errors during TA measurements.

[0194] Fig.23An example information exchange process 2300 for supporting TA for positioning according to aspects of the present disclosure is depicted. In the information exchange process 2300, the LMF 2302 sends a TA information request message 2304 to the NG-RAN node 2306, and the NG-RAN node 2306 returns a TA information response message 2308 to the LMF 2302. For example, the NG-RAN node 2306 includes available TA information in the TA information response message 2308. The TA information response message 2308 may include the requested information available to the NG-RAN node 2306 (e.g., as described above). In at least one implementation, the NG-RAN node 2306 may also send additional information in the TA information request message 2304 that is not requested by the LMF 2302 (e.g., location server) but may be relevant to the TA positioning method.

[0195] In implementation, the LMF 2302 may also request the NG-RAN node 2306 to provide detailed information for a TRP hosted by the NG-RAN node 2306, where for transparent payloads, the NG-RAN node 2306 may be a gNB on the ground and the TRP may correspond to a satellite connected to the gNB on the ground. For example, such a request may instruct the gNB to provide information about the number of satellites to which it is connected. In addition, information about satellite ephemeris may also be part of the request. This information may be used by the location server to configure resources, such as to avoid feeder link switching and / or to provide neighboring cell information for seamless connectivity and positioning calculations. In addition, information associated with each satellite, such as synchronization signal block (SSB) information, cell ID, number of cells, cell layout configuration (e.g., earth mobile cells and / or earth fixed cells), may also be requested. The requested information may be part of the TA information request message 2304, or a separate request message may be used for this purpose, such as a TRP and / or NTN cell request message. Upon receiving this message, the gNB may include the request information for the TRP / satellite hosted by the NG-RAN node 2306 in the TA Information Response message 2308 (e.g., if such information was requested in the TA Information Request message 2304) and / or in the TRP Information Response message, e.g., if such information was requested in the TRP Information Request message.

[0196] Implementations described in the present disclosure also provide positioning configuration using configuration exchange. For example, in an implementation, and based on capability exchange information (e.g., from a target UE and / or NG-RAN node), a location server configures a target UE with assistance that the target UE can use to estimate the location of the target UE. For example, for this purpose, the location server can exchange requests / provides for assistance data (e.g., positioning configuration) with the target UE. In at least one implementation, the target UE can send a RequestAssistanceData message (e.g., for UE-based positioning) to the location server, where an IE (e.g., nr-TA-RequestAssistanceData) can be used. The location server can provide assistance data (e.g., requested assistance data) in response to a request from the target UE, and / or provide assistance data (e.g., unrequested assistance information) without a request, such as by using a ProvideAssistanceData message, where an IE including configuration parameters can be defined. This can be applicable to UE-specific configuration of a TA-based positioning method.

[0197] Fig.24 An example TA Assistance Data IE 2400 supporting TA for positioning according to aspects of the present disclosure is depicted. For example, the TA Assistance Data IE 2400 represents an instance of a TA-RequestCapabilities IE. The TA Assistance Data IE 2400 may include a set of fields for enabling UE-assisted TA-based positioning methods. An example description of the fields is as follows:

[0198] The IE "TA-ReferenceCellInfo" may be used by the location server to provide reference cell information for TA assistance data. The target UE may be within the coverage of multiple satellites with different cell IDs, or within the coverage of a single satellite but with different beams corresponding to different cell IDs. Thus, the target UE may use the information of the cell ID and related parameters for the TA positioning method. For example, the IE may include information related to the cell ID, antenna port configuration, CP length, DL bandwidth, etc. In at least one implementation, TA-based measurements may be performed on a cell different from the serving cell, and thus a field may be included indicating that the related assistance data is different from the serving cell. In at least one implementation, the field may be used to indicate multiple measurements to be performed on the same cell in different situations (e.g., TA-based positioning for a single satellite), or multiple measurements corresponding to different cell IDs, such as multi-satellite or multi-beam TA-based positioning. In at least one implementation, if data associated with one cell ID is configured, it may be assumed that the target UE may perform multiple measurements corresponding to a single satellite, such as cell edge users and / or neighboring cell data for edge users. In at least one example, in addition to measurements corresponding to a single satellite, the target UE may also perform measurements corresponding to different satellites, cell IDs, and / or beams (e.g., on neighboring cells), such as when the UE is close to a cell edge.

[0199] In implementation, the target UE is indicated by a location server (e.g., LMF) of the reference signal for the TA measurement to be performed. For this purpose, various types of reference signals (e.g., SSB, PRS and / or CSI-RS) can be used. Information about the reference signal can be part of the IE "TA-ReferenceCellInfo" and / or a separate IE, for example, measurement-signal-info can be used to indicate the type of reference signal to be used. The location server may include a reference signal configuration. For example, if DL-PRS is used for TA calculation and / or TA-based distance calculation, the IE PRS can be reused for this purpose and can be indicated within the IE "TA-ReferenceCellInfo" and / or IE "measurement-signal-info". In addition, if SSB is to be used, information related to SSB can be configured.

[0200] Common and user-specific TA-related parameters may be configured via IE NTN-Config, which includes configuration for satellite ephemeris information (in the format of position and velocity state vectors and / or in the format of orbital parameters), an indication of the epoch time for the assistance information (e.g., indicated by a system frame number (SFN) and a subframe number), and common TA parameters, such as common TA, common TA offset, common TA offset change. In at least one implementation, the configuration is valid for one TA calculation (e.g., if configured), and the target UE calculates the distance in its report at one time instance (e.g., at Fig.17 In at least one implementation, the target UE may be instructed by the location server to perform multiple measurements at different time instances, wherein the TA parameters remain valid for the entire measurement duration. The validity of the parameters may be indicated by a "validity duration" field, wherein the field defines a maximum time during which the target UE may apply the satellite ephemeris and / or common TA parameters without acquiring new satellite ephemeris or common TA parameters.

[0201] In an implementation, the target UE is configured with a set of common TA and ephemeris parameters to perform TA measurements for position estimation at different time instances, where the measurement separation and / or time instance can be indicated using fields in the assistance data IE. For example, fields (e.g., sampling-window and / or measurement-instance-separation) can be used to define the minimum separation between two measurements. Additionally or alternatively, a field (e.g., measurement-instances) can be used to indicate the precise time instance related to the epoch time used for the measurement. In this scenario, the target UE can perform the indicated number of TA measurements at the configured time instances and at the TA measurements that meet the sampling window condition by adopting the same TA common parameters and ephemeris information.

[0202] Fig.25a An example scenario 2500a of supporting TA for positioning according to aspects of the present disclosure is illustrated. In scenario 2500a, a target UE receives TA parameters with a validity duration, a time instance of measurement and / or a separation gap of measurement (e.g., relative to epoch time), and a number of measurement instances. The target UE may perform measurements at indicated time instances (e.g., t1, t2, t3, etc.) using the same TA parameters (e.g., TA common parameters and ephemeris parameters used at t1) during the corresponding validity duration.

[0203] In at least one example, the target UE is configured with a set of TA parameters with the same validity duration during the validity duration. The target UE can be configured to perform measurements at multiple time instances, and the TA parameters used for position and / or distance estimation at different time instances can be different and are derived from the initial TA parameters using a prediction model. In this scenario, the UE can be additionally instructed to perform measurements based on the prediction.

[0204] In an implementation, different sets of TA parameters for different time instances (e.g., different TA common and ephemeris parameters for time instances t1, t2, t3, etc. in scenario 2500a) are configured by the location server in one configuration message, where these parameters are valid for a validity duration. For example, using the example in scenario 2500a, three sets of TA common parameters and ephemeris information are configured, each set corresponding to time instances t1, t2, and t3. In at least one implementation, a separate field may be used to indicate that different TA parameters are configured for multiple time instances. In at least one implementation, only the ephemeris information at the time instances is different, while the TA common parameters are the same.

[0205] In an implementation, the UE is configured with multiple sets of TA parameters (e.g., in one configuration message), where each set of parameters is valid for a validity duration. For example, using the example in scenario 2500a, the target UE may be configured with two sets of TA common and ephemeris information parameters indicated by respective validity durations, where the first set is valid for measurement instances t1, t2, and t3, and the second set is valid for measurements at t4, t5, and t6.

[0206] In addition to the above fields, the target UE may also be configured with the type of positioning method used to locate its position for a user-specific TA (e.g., RAT-independent), for example, using a field indicating the method type. In the absence of this field, the positioning method selection may be made by the target UE itself. In at least one implementation, the polarization type to be used for uplink and downlink reference signals may also be configured via the NTN IE.

[0207] In an implementation, TA parameters common to a set of target UEs are broadcast via a positioning system information block (posSIB) carried in an RRC system information (SI) message. In this scenario, common and general assistance data IEs related to the TA positioning method can be sent via the posSIB. In addition, TA parameters common to users in a cell are broadcast via the posSIB, and these parameters are defined in the NTN system information block (SIB)-19 (e.g., defined in the IE NTN-Config), where the posSIB type for the TA positioning method can be defined. In at least one implementation, the TA parameters are broadcast periodically, where each set of parameters is valid for a validity duration. Information such as the number of measurements and the reference signal type can be configured via the assistance data IE. The target UE can look up the TA parameters (e.g., common TA parameters and ephemeris information) in the broadcast message, and can perform TA measurements for the number of time instances configured via the assistance data. The number of measurements can fall within two or more validity durations. Therefore, two or more sets of TA parameters can be used for positioning related measurements.

[0208] Fig.25b An example scenario 2500b is illustrated that supports TA for positioning according to aspects of the present disclosure. In scenario 2500b, a target UE may be configured to perform measurements at t3, t4, and t5. In this example, the target UE may use a first set of TA parameters at t3, and a second set of TA parameters is used for the t4 and t5 time instances. In at least one example, a plurality of sets of TA parameters are mapped to a validity duration, where each set corresponds to one or more time instances within the validity duration, and the information is broadcast periodically.

[0209] In an implementation, a location server employs an Assistance Information Control procedure to signal positioning assistance information to a NG-RAN node for TA assistance information broadcast, wherein such a procedure may be initiated by a location server (e.g., LMF) sending an Assistance Information Control message to a NG-RAN node (e.g., gNB). Based on the signaled positioning assistance information received from an IE in the Assistance Information Control message, the NG-RAN node may implement the broadcast of the TA information. For example, if the IE contains new parameters for broadcast, the NG-RAN node may replace the previously stored information and use the received information to configure the assistance information broadcast. In at least one implementation, the IE may contain information about the broadcast priority of the assistance data, such as validity duration, ephemeris data, etc. In such a scenario, the NG-RAN node may consider the information when configuring the broadcast for the relevant information, wherein assistance information with the same broadcast priority value may receive the same treatment, such as being broadcast or not broadcast by the NG-RAM node. In at least one example, the start and stop fields are set in the Assistance Information Control message to indicate when to start and / or stop the broadcast. In such a scenario, the NG-RAN node may start or stop the TA parameter broadcast as indicated.

[0210] Implementations described in the present disclosure also support TA-based positioning configuration and capability exchange for multiple satellite systems. For example, in an implementation, a location server configures TA parameters to a target UE, where these parameters are related to multiple satellites (and / or cell IDs) that may be associated with one NG-RAN node or multiple NG-RAN nodes. The configuration may be based on information received during a capability exchange between the location server and the target device and / or between the location server and (multiple) NG-RAN nodes.

[0211] In an implementation, the location server exchanges information about the multi-satellite connectivity of the target UE with the target UE. For example, the target UE may obtain such information, such as from the number of cells to which it is connected. In at least one implementation, this information may be provided to the location server in a provide capabilities message. The location server may have information about the mapping of cell IDs to satellite ephemeris and NG-RAN nodes, and / or may request this information from the AMF and / or NG-RAM node.

[0212] Based on its determination of the number of satellite nodes (e.g., TRPs) connected to the target UE and the corresponding NG-RAN node, the location server may initiate an NRPPa location information transfer procedure with the relevant NG-RAM nodes. The NRPPa procedure may be applied to each NG-RAN node. In at least one example, when an NG-RAN node is served by multiple satellites, the TA parameters for each satellite node may be explicitly included in the TA response message by the NG-RAN node.

[0213] In an implementation, the location server may determine TA parameters for satellites connected to the NG-RAN node using a TRP information request message to the NG-RAN node, where a TRP may correspond to a satellite in the NTN transparent payload architecture. The information request message may include a list of satellites for which TA parameter related information is requested. The NG-RAN node may respond with a TRP information response message, where information such as ephemeris data, TA parameters, cell information, and reference points for the corresponding satellites may be included in the response message.

[0214] In implementation, the location server configures TA parameters for different satellites to the target UE, where each set of TA parameters can be associated with a cell ID. For example, the parameters listed in the TA-ProvideAssistanceData IE can be associated with the TA cell information, and the IE can divide the parameters into satellite common parameters and satellite specific parameters. Satellite common parameters are common parameters and can be applied to each node, such as a user-specific TA position estimation method. Satellite specific parameters can include ephemeris information, TA common parameters, etc.

[0215] In implementation, a parameter field is included in the IE, which indicates that the TA measurement will be carried for different satellite nodes and is not based on single satellite measurement. If it is indicated as multi-satellite measurement, the target UE can perform a single TA calculation for each satellite node, and if it is not indicated as multi-satellite measurement, multiple measurements are performed.

[0216] In implementation, for each satellite node, TA parameters common to users in a cell (and / or satellite) may be broadcast via posSIB.The target UE may be individually configured via assistance data IE regarding the initiation of TA measurements using TA parameters of different satellite nodes.

[0217] Fig.26An example of a block diagram 2600 of a device 2602 (e.g., an apparatus) supporting TA for positioning according to aspects of the present disclosure is illustrated. The device 2602 may be an example of a UE 104 as described herein. The device 2602 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 2602 may include components for bidirectional communication including components for sending and receiving communications (such as a processor 2604, a memory 2606, a transceiver 2608, and an I / O controller 2610). These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0218] The processor 2604, the memory 2606, the transceiver 2608, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 2604, the memory 2606, the transceiver 2608, or various combinations thereof, or components thereof may support methods for performing one or more of the operations described herein.

[0219] In some implementations, the processor 2604, the memory 2606, the transceiver 2608, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of components configured to or otherwise support the functions described in the present disclosure. In some implementations, the processor 2604 and the memory 2606 coupled to the processor 2604 may be configured to perform one or more functions described herein (e.g., the processor 2604 executes instructions stored in the memory 2606). For example, in the context of the UE 104, the transceiver 2608 and the processor 2604 coupled to the transceiver 2608 are configured to cause the UE 104 to perform various described operations and / or combinations thereof.

[0220] For example, according to an example as disclosed herein, the processor 2604 and / or the transceiver 2608 may support wireless communication at the device 2602. For example, the processor 2604 and / or the transceiver 2608 may be configured to and / or otherwise support components for: receiving an auxiliary configuration message indicating to perform a plurality of TA measurements corresponding to a plurality of measurement time instances, wherein: each measurement time instance is associated with at least one cell, and the auxiliary configuration message includes a TA-related parameter and a measurement reference signal configuration corresponding to the at least one cell; performing at least one TA measurement based at least in part on the received auxiliary configuration message, the at least one TA measurement corresponding to at least one measurement time instance of the plurality of measurement time instances; and sending a TA positioning report including the at least one TA measurement.

[0221] In addition, in some implementations, the TA-related parameters include at least one of the following items: satellite ephemeris information, epoch time, common TA parameters, or validity duration; multiple measurement time instances include time instances within the validity duration; the auxiliary configuration message includes measurement instance separation information, and the processor is configured to cause the device to determine multiple measurement time instances at least in part based on the measurement instance separation information; a first subset of the multiple measurement time instances includes time instances within a first validity duration, and a second subset of the multiple measurement time instances includes time instances within a second validity duration; the first validity duration is associated with a first set of one or more of the satellite ephemeris or the common TA parameters, and the second validity duration is associated with a second set of one or more of the satellite ephemeris or the common TA parameters.

[0222] In addition, in some implementations, a first subset of the multiple measurement time instances is associated with a first cell in at least one cell, and a second subset of the multiple measurement time instances is associated with a second cell in at least one cell; the processor is configured to cause the device to receive a TA parameter broadcast message for positioning, and the TA parameter broadcast message includes information about at least one of the following items: satellite ephemeris information, epoch time, common TA parameters, validity duration, or reference point; the processor is configured to cause the device to periodically receive the TA parameter broadcast message, and the TA parameter broadcast message is associated with at least one validity duration; the processor is configured to cause the device to: receive a capability information request related to TA-based positioning from the network; and send one or more capability parameters based at least in part on the capability information request; the capability information request includes information about an indication of support for TA calculations for positioning; the capability information request includes information about support for user-specific TA position estimation methods; the one or more capability parameters include at least one of the following items: an indication of support for TA positioning calculations for positioning, a user-specific TA position estimation method, the number of satellite nodes in the coverage area, or polarization capability.

[0223] According to an example as disclosed herein, a processor 2604 of a device 2602 (such as UE 104) may support wireless communication. The processor 2604 includes at least one controller coupled to at least one memory, and the processor 2604 is configured and / or operable to cause the processor to: receive an auxiliary configuration message indicating to perform a plurality of TA measurements corresponding to a plurality of measurement time instances, wherein: each measurement time instance is associated with at least one cell, and the auxiliary configuration message includes a TA-related parameter and a measurement reference signal configuration corresponding to the at least one cell; perform at least one TA measurement based at least in part on the received auxiliary configuration message, the at least one TA measurement corresponding to at least one measurement time instance in the plurality of measurement time instances; and send a TA positioning report including the at least one TA measurement. In addition, the processor 2604 and the at least one controller are configured and / or operable to cause the processor to perform any one or more operations discussed herein with reference to a UE (such as UE 104).

[0224] The processor 2604 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 2604 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 2604. The processor 2604 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 2606) to cause the device 2602 to perform various functions of the present disclosure.

[0225] The memory 2606 may include random access memory (RAM) and read-only memory (ROM). The memory 2606 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 2604, cause the device 2602 to perform various functions described herein. The code may be stored in a non-transient computer-readable medium such as a system memory or another type of memory. In some implementations, the code may not be directly executed by the processor 2604, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 2606 may also include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral device components or devices.

[0226] I / O controller 2610 can manage input and output signals for device 2602. I / O controller 2610 can also manage peripheral devices that are not integrated into device 2402. In some implementations, I / O controller 2610 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 2610 can utilize an operating system, such as

[0227] Or other known operating systems. In some implementations, I / O controller 2610 can be implemented as part of a processor such as processor M08. In some implementations, a user can interact with device 2602 via I / O controller 2610 or via hardware components controlled by I / O controller 2610.

[0228] In some implementations, the device 2602 may include a single antenna 2612. However, in some other implementations, the device 2602 may have more than one antenna 2612 (e.g., multiple antennas), including multiple antenna panels or antenna arrays, which are capable of concurrently sending or receiving multiple wireless transmissions. The transceiver 2608 can communicate bidirectionally via one or more antennas 2612, wired or wireless links, as described herein. For example, the transceiver 2608 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 2608 may also include a modem for modulating packets to provide modulated packets to one or more antennas 2612 for transmission, and demodulating packets received from one or more antennas 2612.

[0229] Fig. 27 An example of a block diagram 2700 of a device 2702 (e.g., an apparatus) supporting TA for positioning according to aspects of the present disclosure is illustrated. The device 2702 may be an example of a network entity 102 as described herein. The device 2702 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 2702 may include components for two-way communication including components for sending and receiving communications, such as a processor 2704, a memory 2706, a transceiver 2708, and an I / O controller 2710. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0230] The processor 2704, the memory 2706, the transceiver 2708, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 2704, the memory 2706, the transceiver 2708, or various combinations thereof, or components thereof may support methods for performing one or more of the operations described herein.

[0231] In some implementations, the processor 2704, the memory 2706, the transceiver 2708, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of components configured to or otherwise support the functions described in the present disclosure. In some implementations, the processor 2704 and the memory 2706 coupled to the processor 2704 may be configured to perform one or more functions described herein (e.g., the processor 2704 executes instructions stored in the memory 2706). For example, in the context of the network entity 102, the transceiver 2708 and the processor 2704 coupled to the transceiver 2708 are configured to cause the network entity 102 to perform various described operations and / or combinations thereof.

[0232] For example, according to an example as disclosed herein, the processor 2704 and / or the transceiver 2708 may support wireless communication at the device 2702. For example, the processor 2704 and / or the transceiver 2708 may be configured to or otherwise support components for: sending an auxiliary configuration message indicating that a plurality of TA measurements corresponding to a plurality of measurement time instances are performed, wherein: each measurement time instance is associated with at least one cell, and the auxiliary configuration message includes a TA-related parameter and a measurement reference signal configuration corresponding to the at least one cell; and receiving a TA positioning report including at least one TA measurement based at least in part on the auxiliary configuration message.

[0233] In addition, in some implementations, the TA-related parameters include at least one of the following items: satellite ephemeris information, epoch time, common TA parameters, or validity duration; multiple measurement time instances include time instances within the validity duration; the auxiliary configuration message includes measurement instance separation information; a first subset of multiple measurement time instances includes time instances within a first validity duration, and a second subset of multiple measurement time instances includes time instances within a second validity duration; the first validity duration is associated with a first set of one or more of the satellite ephemeris or common TA parameters, and the second validity duration is associated with a second set of one or more of the satellite ephemeris or common TA parameters; the processor is configured to cause the device to: send a capability information request from a network associated with TA-based positioning; and receive one or more capability parameters based at least in part on the capability information request.

[0234] The processor 2704 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 2704 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 2704. The processor 2704 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 2706) to cause the device 2702 to perform various functions of the present disclosure.

[0235] The memory 2706 may include random access memory (RAM) and read-only memory (ROM). The memory 2706 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 2704, cause the device 2702 to perform various functions described herein. The code may be stored in a non-transient computer-readable medium such as a system memory or another type of memory. In some implementations, the code may not be directly executed by the processor 2704, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 2706 may also include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral device components or devices.

[0236] I / O controller 2710 can manage input and output signals for device 2702. I / O controller 2710 can also manage peripheral devices that are not integrated into device 2402. In some implementations, I / O controller 2710 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 2710 can utilize an operating system, such as

[0237] Or other known operating systems. In some implementations, I / O controller 2710 can be implemented as part of a processor such as processor M06. In some implementations, a user can interact with device 2702 via I / O controller 2710 or via hardware components controlled by I / O controller 2710.

[0238] In some implementations, the device 2702 may include a single antenna 2712. However, in some other implementations, the device 2702 may have more than one antenna 2712 (e.g., multiple antennas), including multiple antenna panels or antenna arrays, which are capable of concurrently sending or receiving multiple wireless transmissions. The transceiver 2708 can communicate bidirectionally via one or more antennas 2712, wired or wireless links, as described herein. For example, the transceiver 2708 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 2708 may also include a modem for modulating packets to provide modulated packets to one or more antennas 2712 for transmission, and demodulating packets received from one or more antennas 2712.

[0239] Fig.28 2800 for supporting TA for positioning according to aspects of the present disclosure. The operations of the method 2800 may be implemented by a device or components thereof as described herein. For example, the operations of the method 2800 may be implemented by a device or components thereof as described herein. Figures 1 to 27 The UE 104 described herein may be used to perform the described functions. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0240] At 2802, the method may include receiving a reporting configuration to report TA measurements for location estimation, wherein the reporting configuration includes an indication of one or more TA measurement parameters, the one or more TA measurement parameters including at least one of the following: reporting frequency, reporting type, location reporting format, or time parameter. The operations of 2802 may be performed according to examples as described herein. In some implementations, aspects of the operations of 2802 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0241] At 2804, the method may include performing one or more TA measurements according to one or more TA measurement parameters. The operations of 2804 may be performed according to examples as described herein. In some implementations, aspects of the operations of 2804 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0242] At 2806, the method may include sending one or more TA positioning reports based at least in part on the one or more TA measurements. The operations of 2806 may be performed according to examples as described herein. In some implementations, aspects of the operations of 2806 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0243] Fig.292900 for supporting TA for positioning according to aspects of the present disclosure. The operations of the method 2900 may be implemented by a device or components thereof as described herein. For example, the operations of the method 2900 may be implemented by a device or components thereof as described herein. Figures 1 to 27 The network entity 102 is used to perform. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0244] At 2902, the method may include: receiving a TA measurement request from a location server to initiate a TA measurement process for a target device. The operations of 2902 may be performed according to examples as described herein. In some implementations, aspects of the operations of 2902 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0245] At 2904, the method may include sending a TA measurement response to a location server based at least in part on the indication of the TA measurement capability of the target device. The operations of 2904 may be performed according to examples as described herein. In some implementations, aspects of the operations of 2904 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0246] Fig.30 1 is a flowchart of a method 3000 for supporting TA for positioning according to aspects of the present disclosure. The operations of the method 3000 may be implemented by a device or components thereof as described herein. For example, the operations of the method 3000 may be implemented by a device or components thereof as described herein. Figures 1 to 27 The network entity 102 is used to perform. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0247] At 3002, the method may include sending a TA measurement request to initiate a TA measurement process, wherein the TA measurement request includes one or more TA measurement parameters. The operations of 3002 may be performed according to examples as described herein. In some implementations, aspects of the operations of 3002 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0248] At 3004, the method may include receiving a TA measurement response based at least in part on the TA measurement request. The operations of 3004 may be performed according to examples as described herein. In some implementations, aspects of the operations of 3004 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0249] At 3006, the method may include performing a position estimation based at least in part on the TA measurement information included in the TA measurement response. The operations of 3006 may be performed according to examples as described herein. In some implementations, aspects of the operations of 3006 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0250] Fig.31 3100 for supporting TA for positioning according to aspects of the present disclosure. The operations of the method 3100 may be implemented by a device or components thereof as described herein. For example, the operations of the method 3100 may be implemented by a device or components thereof as described herein. Figures 1 to 27 The UE 104 described herein may be used to perform the described functions. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0251] At 3102, the method may include: receiving an auxiliary configuration message indicating to perform multiple TA measurements corresponding to multiple measurement time instances, wherein: each measurement time instance is associated with at least one cell, and the auxiliary configuration message includes TA-related parameters and measurement reference signal configuration corresponding to the at least one cell. The operation of 3102 may be performed according to the examples described herein. In some implementations, aspects of the operation of 3102 may be performed by the example described in reference to Figure 1 The device is used to perform the above.

[0252] At 3104, the method may include: performing at least one TA measurement based at least in part on the received auxiliary configuration message, the at least one TA measurement corresponding to at least one measurement time instance of the plurality of measurement time instances. The operations of 3104 may be performed according to examples as described herein. In some implementations, aspects of the operations of 3104 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0253] At 3106, the method may include sending a TA positioning report including at least one TA measurement. The operations of 3106 may be performed according to examples as described herein. In some implementations, aspects of the operations of 3106 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0254] Fig.32 3200 for supporting TA for positioning according to aspects of the present disclosure. The operations of the method 3200 may be implemented by a device or components thereof as described herein. For example, the operations of the method 3200 may be implemented by a device or components thereof as described herein. Figures 1 to 27The network entity 102 is used to perform. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0255] At 3202, the method may include: sending an auxiliary configuration message indicating to perform multiple TA measurements corresponding to multiple measurement time instances, wherein: each measurement time instance is associated with at least one cell, and the auxiliary configuration message includes TA-related parameters and measurement reference signal configuration corresponding to the at least one cell. The operation of 3202 may be performed according to the examples described herein. In some implementations, aspects of the operation of 3202 may be performed by the example of reference 1. Figure 1 The device is used to perform the above.

[0256] At 3204, the method may include receiving a TA positioning report including at least one TA measurement based at least in part on the auxiliary configuration message. The operations of 3204 may be performed according to examples as described herein. In some implementations, aspects of the operations of 3204 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0257] Fig.33 3300 for supporting TA for positioning according to aspects of the present disclosure. The operations of the method 3300 may be implemented by a device or components thereof as described herein. For example, the operations of the method 3300 may be implemented by a device or components thereof as described herein. Figures 1 to 27 The network entity 102 is used to perform. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0258] At 3302, the method may include sending a reporting configuration to report TA measurements for location estimation, the reporting configuration including an indication of one or more TA measurement parameters, the one or more TA measurement parameters including at least one of the following: reporting frequency, reporting type, location reporting format, or time parameter. The operations of 3302 may be performed according to examples as described herein. In some implementations, aspects of the operations of 3302 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0259] At 3304, the method may include receiving one or more TA positioning reports based at least in part on one or more TA measurements, the one or more TA measurements based at least in part on one or more of: a common TA calculation or a UE-specific TA calculation. The operations of 3304 may be performed according to examples as described herein. In some implementations, aspects of the operations of 3304 may be performed as described in reference to Figure 1 The device is used to perform the above.

[0260] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0261] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0262] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination thereof. Features that implement the functions may also be physically located at various locations, including being distributed so that portions of the functions are implemented at different physical locations.

[0263] Computer readable medium includes both non-transient computer storage medium and communication medium, and communication medium includes any medium that promotes to transmit computer program from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.As an example and not limitation, non-transient computer readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage device, or can be used to carry or store desired program code parts in the form of instruction or data structure and can be accessed by general or special-purpose computer, or any other non-transient medium of general or special-purpose processor.

[0264] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, wherein disks typically reproduce data magnetically, and optical disks reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0265] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of..." or "one or more of..." or "one or both of...") represents an inclusive list, so that, for example, a list of at least one of A, B, or C represents A or B or C or AB or AC or BC or ABC (e.g., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a set of closed conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on." In addition, as used herein (including in the claims), a "set" may include one or more elements.

[0266] When referring to a network entity, the terms "send," "receive," or "transmit" may refer to any part of a network entity of a RAN (e.g., base station, CU, DU, RU) that communicates with another device (e.g., directly or via one or more other network entities).

[0267] The descriptions described herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "better than other examples." The detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid confusing the concepts of the described examples.

[0268] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be clear to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; as well as at least one processor, coupled to the at least one memory, and configured to cause the UE to: receiving an auxiliary configuration message, the auxiliary configuration message indicating to perform a plurality of timing advance (TA) measurements corresponding to a plurality of measurement time instances, wherein: each measurement time instance is associated with at least one cell, and the auxiliary configuration message includes a TA-related parameter and a measurement reference signal configuration corresponding to the at least one cell; performing at least one TA measurement based at least in part on the received secondary configuration message, the at least one TA measurement corresponding to at least one measurement time instance of the plurality of measurement time instances; and A TA positioning report is sent including the at least one TA measurement.

2. The UE according to claim 1, wherein the TA-related parameters include at least one of the following items: satellite ephemeris information, epoch time, common TA parameters or validity duration. 3 . The UE of claim 1 , wherein the plurality of measurement time instances comprises time instances within a validity duration.

4. The UE of claim 3, wherein the auxiliary configuration message comprises measurement instance separation information, and wherein the at least one processor is configured to cause the UE to: determine the plurality of measurement time instances based at least in part on the measurement instance separation information. 5 . The UE of claim 1 , wherein a first subset of the plurality of measurement time instances comprises time instances within a first validity duration, and a second subset of the plurality of measurement time instances comprises time instances within a second validity duration.

6. The UE of claim 5, wherein the first validity duration is associated with a first set of one or more of satellite ephemeris or common TA parameters, and the second validity duration is associated with a second set of one or more of satellite ephemeris or common TA parameters. 7 . The UE of claim 1 , wherein a first subset of the plurality of measurement time instances is associated with a first cell of the at least one cell, and a second subset of the plurality of measurement time instances is associated with a second cell of the at least one cell.

8. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to: receive a TA parameter broadcast message for positioning, and wherein the TA parameter broadcast message includes information about at least one of the following items: satellite ephemeris information, epoch time, common TA parameters, validity duration or reference point.

9. The UE of claim 8, wherein the at least one processor is configured to cause the UE to: periodically receive the TA parameter broadcast message, and wherein the TA parameter broadcast message is associated with at least one validity duration.

10. The UE of claim 1, wherein the at least one processor is configured to cause the UE to: receiving a capability information request related to TA-based positioning from a network; and One or more capability parameters are sent based at least in part on the capability information request. 11 . The UE according to claim 10 , wherein the capability information request includes information on an indication of support for TA calculation for positioning.

12. The UE according to claim 10, wherein the capability information request includes information on support for a user-specific TA location estimation method.

13. The UE of claim 10, wherein the one or more capability parameters include at least one of: an indication of support for TA location calculations for positioning, a user-specific TA position estimation method, a number of satellite nodes in a coverage area, or polarization capability.

14. A processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to cause the processor to: receiving an auxiliary configuration message, the auxiliary configuration message indicating to perform a plurality of timing advance (TA) measurements corresponding to a plurality of measurement time instances, wherein: each measurement time instance is associated with at least one cell, and the auxiliary configuration message includes a TA-related parameter and a measurement reference signal configuration corresponding to the at least one cell; performing at least one TA measurement based at least in part on the received secondary configuration message, the at least one TA measurement corresponding to at least one measurement time instance of the plurality of measurement time instances; and A TA positioning report is sent including the at least one TA measurement.

15. The processor of claim 14, wherein the TA-related parameters include at least one of: satellite ephemeris information, epoch time, common TA parameters, or validity duration.

16. The processor of claim 14, wherein the plurality of measured time instances comprises time instances within a validity duration.

17. The processor of claim 16, wherein the auxiliary configuration message includes measurement instance separation information, and wherein the at least one controller is configured to cause the processor to: determine the plurality of measurement time instances based at least in part on the measurement instance separation information.

18. The processor of claim 14, wherein a first subset of the plurality of measured time instances comprises time instances within a first validity duration, and a second subset of the plurality of measured time instances comprises time instances within a second validity duration.

19. A base station for wireless communication, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the base station to: Sending an auxiliary configuration message, the auxiliary configuration message indicating to perform a plurality of timing advance (TA) measurements corresponding to a plurality of measurement time instances, wherein: each measurement time instance is associated with at least one cell, and the auxiliary configuration message includes a TA-related parameter and a measurement reference signal configuration corresponding to the at least one cell; as well as A TA positioning report including at least one TA measurement is received based at least in part on the assistance configuration message.

20. A method comprising: receiving an auxiliary configuration message, the auxiliary configuration message indicating to perform a plurality of timing advance (TA) measurements corresponding to a plurality of measurement time instances, wherein: each measurement time instance is associated with at least one cell, and the auxiliary configuration message includes a TA-related parameter and a measurement reference signal configuration corresponding to the at least one cell; performing at least one TA measurement based at least in part on the received secondary configuration message, the at least one TA measurement corresponding to at least one measurement time instance of the plurality of measurement time instances; and A TA positioning report is sent including the at least one TA measurement.

Images