Non-terrestrial network-based user equipment location verification

Abstract

An apparatus, method, and system for NTN-based UE location verification are disclosed. The apparatus (1300) includes a transceiver (1325) and a processor (1305) coupled to the transceiver. The processor (1305) is configured to cause the apparatus to: transmit a RAT-independent location information request, the request including a location configuration for an NG-RAN node; receive RAT-independent location information for a target UE corresponding to the transmitted location information request, the RAT-independent location information including a location estimate for the target UE; trigger a location server to determine a location estimate for the target UE using a RAT-dependent positioning indication; receive the location estimate based on the RAT-dependent positioning indication; and perform verification of the received RAT-independent target UE location against the RAT-dependent UE location estimate.

Description

[Technical Field]

[0001] The subject matter disclosed herein relates generally to wireless communications, and more particularly to non-terrestrial based network ("NTN") based user equipment ("UE") location verification. [Background technology]

[0002] In wireless networks, UE positioning may refer to techniques used in wireless networks to determine the geographic location, position, and / or velocity of a UE. Due to the large coverage area represented by an NTN cell, traditional terrestrial-based network positioning verification mechanisms may not be applicable to NTN systems. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] SMM020220104-GR-NP (IDF-153116) Summary of the Invention [Means for solving the problem]

[0004] Solutions for NTN-based location verification are disclosed, which may be implemented by an apparatus, a system, a method, or a computer program product.

[0005] In one embodiment, a first apparatus includes a transceiver and a processor coupled to the transceiver. In one embodiment, the processor is configured to cause the apparatus to: transmit a RAT-independent location information request, the request including a location configuration for an NG-RAN node; receive a RAT-independent location information request for a target UE corresponding to the transmitted location information request, the RAT-independent location information including a location estimate for the target UE; trigger a location server to determine a location estimate for the target UE using a RAT-dependent positioning indication; receive the location estimate based on the RAT-dependent positioning indication; and perform validation of the received RAT-independent target UE location against the RAT-dependent UE location estimate.

[0006] In one embodiment, a first method includes the steps of: sending a RAT-independent location information request, the request including a location configuration for an NG-RAN node; receiving RAT-independent location information for a target UE corresponding to the sent location information request, the RAT-independent location information including a location estimate for the target UE; triggering a location server to determine a location estimate for the target UE using a RAT-dependent positioning indication; receiving the location estimate based on the RAT-dependent positioning indication; and performing validation of the received RAT-independent target UE location against the RAT-dependent UE location estimate.

[0007] In one embodiment, the second apparatus includes a transceiver and a processor coupled to the transceiver. In one embodiment, the processor is configured to cause the apparatus to receive an instruction from the AMF to determine a location estimate for the target UE using a RAT dependent positioning indication, estimate a location of the target UE using the RAT dependent positioning indication, and send a response message to the AMF including the estimated location of the target UE, a location service identifier, a positioning method used to estimate the location, and a timestamp of the location estimate.

[0008] In one embodiment, the second method includes receiving an instruction from the AMF to determine a location estimate for the target UE using a RAT dependent positioning instruction; estimating a location of the target UE using the RAT dependent positioning instruction; and sending a response message to the AMF including the estimated location of the target UE, a location service identifier, a positioning method used to estimate the location, and a timestamp of the location estimate.

[0009] The above briefly described embodiments will now be described in more detail by reference to specific embodiments illustrated in the accompanying drawings, in which: The embodiments will be described with greater specificity and detail through the use of the accompanying drawings, with the understanding that these drawings illustrate only some embodiments and therefore should not be considered limiting in scope. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a schematic block diagram illustrating an embodiment of a wireless communication system for NTN-based UE location verification. [Figure 2] FIG. 1 is a block diagram illustrating one embodiment of a 5G NR protocol stack. [Figure 3] FIG. 1 illustrates an embodiment of NR beam-based positioning. [Figure 4A]FIG. 1 illustrates one embodiment of Downlink Time Difference of Arrival ("DL-TDOA") assistance data. [Figure 4B] FIG. 1 illustrates one embodiment of a DL-TDOA measurement report. [Figure 5] FIG. 1 illustrates one embodiment of an overall architecture for UE positioning applicable to a new generation radio access network ("NG-RAN"). [Figure 6] FIG. 1 illustrates one embodiment of location services support by NG-RAN. [Figure 7] FIG. 1 illustrates an embodiment of an NG-RAN location reporting procedure. [Figure 8A] FIG. 1 illustrates an embodiment of a networked RAN architecture with transparent satellites. [Figure 8B] FIG. 1 illustrates an embodiment of a regenerative satellite without an inter-satellite link (“ISL”) and a gNB processed payload. [Figure 8C] FIG. 1 illustrates an embodiment of a regenerative satellite with ISL and gNB processed payloads. [Figure 9] FIG. 1 illustrates an embodiment of a procedure for NTN-based NG-RAN location reporting. [Figure 10] FIG. 1 illustrates one embodiment of a procedure for AMF initiation location verification. [Figure 11A] FIG. 1 illustrates an embodiment of multi-satellite connectivity using a transparent payload architecture. [Figure 11B] FIG. 1 illustrates an embodiment of multi-satellite connectivity using a regenerative payload architecture. [Figure 11C] FIG. 1 illustrates one embodiment of TN and NTN connectivity using a transparent payload architecture. [Figure 11D] FIG. 1 illustrates one embodiment of TN and NTN connectivity using a transparent payload architecture using different AMFs and LMFs. [Figure 12]FIG. 1 is a block diagram illustrating an embodiment of a user equipment device that may be used for NTN-based UE location verification. [Figure 13] FIG. 1 is a block diagram illustrating an embodiment of a network device that may be used for NTN-based UE location verification. [Figure 14] FIG. 1 is a flowchart illustrating one embodiment of a method for NTN-based UE location verification. [Figure 15] FIG. 10 is a flowchart illustrating an embodiment of another method for NTN-based UE location verification. DETAILED DESCRIPTION OF THE INVENTION

[0011] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.) or an embodiment combining software and hardware aspects.

[0012] For example, the disclosed embodiments may be implemented as hardware circuitry comprising custom very large scale integrated ("VLSI") circuits or gate arrays, comprising off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions.

[0013] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable devices storing machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage devices may be tangible, non-transitory, and / or opaque. The storage devices may not embody signals. In certain embodiments, the storage devices merely use signals to access the code.

[0014] Any combination of one or more computer-readable mediums may be utilized. The computer-readable medium may be a computer-readable storage medium. The computer-readable storage medium may be a storage device that stores code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the above.

[0015] More specific examples (a non-exhaustive list) of storage devices include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the context of this document, a computer-readable storage medium may be any tangible medium that is capable of containing or storing a program for use by, or in association with, an instruction execution system, apparatus, or device.

[0016] The code for performing operations for the embodiments may be any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and the like, and traditional procedural programming languages ​​such as the “C” programming language, and / or machine languages ​​such as assembly language. The code may run entirely on the user's computer, partially on the user's computer as a standalone software package and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), or wide area network (“WAN”), or may be connected to an external computer (via the Internet using an Internet Service Provider (“ISP”)).

[0017] Furthermore, the above-described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, and hardware chips, to enable a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

[0018] References throughout this specification to "one embodiment," "an embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment. Thus, throughout this specification, appearances of the phrases "in one embodiment," "in an embodiment," and similar language all refer, although not necessarily, to the same embodiment and mean "one or more, but not all, embodiments," unless expressly stated otherwise. The terms "including," "comprising," and "having," and variations thereof, mean "including but not limited to," unless expressly stated otherwise. Listed items do not imply that all of the items are mutually exclusive unless expressly stated otherwise. The terms "a," "an," and "the" refer to "one or more," unless expressly stated otherwise.

[0019] As used herein, a list using the conjunction "and / or" includes any single item in the list or combination of items in the list. For example, a list of A, B, and / or C includes A only, B only, C only, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C. As used herein, a list using the term "one or more" includes any single item in the list or combination of items in the list. For example, one or more of A, B, and C includes A only, B only, C only, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C. As used herein, a list using the term "one of" includes only one of any single item in the list. For example, "one of A, B, and C" includes A only, B only, or C only, and excludes the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C" includes only one of A, B, or C, and excludes the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C and combinations thereof" includes A only, B only, C only, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C.

[0020] Aspects of the embodiments are described below with reference to schematic flowchart illustrations and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowchart illustrations and / or schematic block diagrams, and combinations of blocks in the schematic flowchart illustrations and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce machine-generated instructions that, when executed by the processor of the computer or other programmable data processing apparatus, form means for performing the functions / acts specified in the flowchart illustrations and / or block diagrams.

[0021] Code may also be stored in a storage device that directs a computer, other programmable data processing apparatus, or other device to function in a particular manner, whereby the instructions stored on the storage device, including instructions that implement the functions / acts specified in the flowchart diagrams and / or block diagrams, create an article of manufacture.

[0022] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device and cause the computer, other programmable data processing apparatus, or other device to perform a series of operational steps to create a computer-implemented process, whereby the code when executed on the computer or other programmable apparatus results in a process for performing the functions / acts specified in the flowchart diagrams and / or block diagrams.

[0023] The flowchart diagrams and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart diagrams and / or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions of code for implementing the specified logical function(s).

[0024] It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more of the block diagrams of the illustrated figures, or portions thereof.

[0025] While various arrow and line types may be used in the flowchart and / or block diagrams, it is understood that they do not limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the illustrated embodiments. For example, arrows may indicate waiting periods or monitoring periods of unspecified duration between enumerated steps of the illustrated embodiments. It should also be noted that each block of the block and / or flowchart diagrams, and combinations of blocks in the block and / or flowchart diagrams, may be implemented by dedicated hardware-based systems that perform the specified functions or acts, or a combination of dedicated hardware and code.

[0026] The description of an element in each figure may refer to the element in the preceding figure. Like numbers refer to the same element in all figures, including alternative embodiments of the same element.

[0027] Generally, this disclosure describes systems, methods, and apparatus for NTN-based UE location verification. In some embodiments, the methods may be implemented using computer code embedded on a computer-readable medium. In some embodiments, the apparatus or system may include a computer-readable medium containing computer-readable code that, when executed by a processor, causes the apparatus or system to implement at least a portion of the solutions described below.

[0028] Conventional methods exist for verifying a UE's reported location in NTN network deployments. Due to the large coverage areas represented by NTN cells, conventional terrestrial network mechanisms may not be applicable to NTN systems. Furthermore, the conclusions of TR 38.882 confirm the need to define network-based solutions aimed at verifying reported UE location information due to unreliable or unavailable locations reported by UEs. Depending on the configured positioning method, network verification procedures need to be enhanced to account for satellite motion, wider ranges, and higher Doppler shifts, providing accurate, reliable, and low-latency UE location verification. This disclosure provides a set of procedural enhancements to enable support for radio access technology ("RAT")-dependent (network-based) network verification procedures over NTN networks.

[0029] Because existing NTN RAT-dependent positioning methods are designed with terrestrial networks in mind, there is no known mechanism for verifying the accuracy and reliability of a UE's location based on an NTN RAT-dependent positioning method. According to Solution #18 of TR 23.700-030, location verification is performed using a Network Data Analysis Function ("NWDAF") network entity, which enables an Access and Mobility Management Function ("AMF") to receive statistics and predictions about the UE's location, thus facilitating the determination of whether the UE's potentially inaccurate location is a reliable location. This solution primarily ignores the Location Management Function ("LMF") in the UE's network verification procedure and results in high signaling overhead. According to Solution #24 of TR 23.700-030, NG-RAN assistance information is used to verify the UE's location, but this solution does not consider the details of this NG-RAN assistance information and how the AMF triggers the LMF to initiate the NTN RAT-dependent location verification procedure.

[0030] The problem solved by the solution herein is support of procedures including triggering, service request, configuration and reporting procedures for location validation by the network after UE initial access and registration procedures. This disclosure describes apparatus, methods and systems. A set of solutions and procedural enhancements are detailed to enable support of NTN RAT dependent (network-based) network validation procedures over the network.

[0031] The proposed solution enables enhanced location reporting configuration by NTN NG-RAN nodes through suitable triggering and configuration by the AMF. This provides an enhanced UE location reporting mechanism to the AMF, which can be utilized to trigger the LMF to initiate an NTN RAT-dependent location procedure. Various implementation options are detailed, in which the AMF can verify the UE's location using a response from the LMF. In another embodiment, location reporting and network verification procedures are detailed for various NTN multi-connectivity options, including transparent networks, regenerative networks, and combinations of terrestrial and non-terrestrial networks.

[0032] In one embodiment, a method is disclosed for enabling NG-RAN location request and reporting triggered by an AMF to verify the location of a UE in an NTN deployment. This includes different RAT-independent location configurations for reporting the UE's location without the involvement of an LMF. This reported UE location is used as the basis for triggering an LMF network verification procedure using an NTN-compatible RAT-dependent positioning technique, which will now be described in accordance with a second embodiment. In another embodiment, a method for supporting NG-RAN location reporting and UE-reported network verification for NTN multi-connectivity scenarios is described with respect to three exemplary scenarios.

[0033] 1 illustrates a wireless communication system 100 for NTN-based UE location verification, in accordance with an embodiment of the present disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 form a mobile communication network. The RAN 120 is comprised of a base unit 121, and the remote unit 105 communicates with the base unit 121 via a satellite 129 using wireless communication links, e.g., a service link 125 and a feeder link 127. As shown, the mobile communication network includes a “terrestrial” base unit 121 and a non-terrestrial-based network (“NTN”) gateway 123 that serves the remote unit 105 via satellite access.

[0034] While FIG. 1 illustrates a particular number of remote units 105, base units 121, wireless communication links, RANs 120, satellites 129, NTN gateways 123 (e.g., satellite terrestrial / earth devices), and mobile core networks 140, those skilled in the art will recognize that the wireless communication system 100 may include any number of remote units 105, base units 121, wireless communication links, RANs 120, satellites 129, NTN gateways 123, and mobile core networks 140.

[0035] In one implementation, the RAN 120 complies with a 5G system specified in 3rd Generation Partnership Project ("3GPP") specifications. For example, the RAN 120 may be an NG-RAN and implement an NR RAT and / or a 3GPP Long Term Evolution ("LTE") RAT. In another example, the RAN 120 may include a non-3GPP RAT (e.g., Wi-Fi or an Institute of Electrical and Electronics Engineers ("IEEE") 802.11 family compliant WLAN). In another implementation, the RAN 120 complies with an LTE system specified in 3GPP specifications. However, more generally, the wireless communication system 100 may implement some other open or private communication network, e.g., Worldwide Interoperable Microwave Access ("WiMAX") or the IEEE 802.16 family of standards, among other networks. This disclosure is not intended to be limited to any particular wireless communication architecture or protocol implementation.

[0036] In one embodiment, the remote unit 105 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant ("PDA"), a tablet computer, a smartphone, a smart television (e.g., a television connected to the Internet), a smart appliance (e.g., an appliance connected to the Internet), a set-top box, a game console, a security system (including security cameras), a vehicle-mounted computer, a network device (e.g., a router, a switch, a modem), etc. In some embodiments, the remote unit 105 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. Furthermore, the remote unit 105 may be referred to as a UE, a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a user terminal, a wireless transmit / receive unit ("WTRU"), a device, or by other terms used in the art. In various embodiments, the remote unit 105 includes a subscriber identification and / or identification module ("SIM") and a mobile equipment ("ME") that provide mobile terminal functionality (e.g., radio transmission, handover, voice encoding and decoding, error detection and correction, signaling and access to the SIM). In some embodiments, the remote unit 105 may include terminal equipment (“TE”) and / or may be embedded in an appliance or device (eg, a computing device as described above).

[0037] The remote unit 105 may communicate directly with one or more of the base units 121 in the RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. In some embodiments, the remote unit 105 communicates between the remote unit 105 and a satellite 129 in a non-terrestrial-based network via UL and DL communication signals. In some embodiments, the satellite 129 may communicate with the RAN 120 through the NTN gateway 123 using UL and DL communication signals between the satellite 129 and the NTN gateway 123. The NTN gateway 123 may communicate directly with the base unit 121 in the RAN 120 to relay the UL and DL communication signals.

[0038] Additionally, UL and DL communication signals may be carried via wireless communication links during at least a portion of the signal path between the RAN 120 and the remote unit 105. In the illustrated embodiment, the wireless communication link between the remote unit 105 and the satellite 129 comprises a service link 125, while the wireless communication link between the satellite 129 and the base unit 121 comprises a feeder link 127. However, in other embodiments, satellite and NTN gateways may be deployed between the base unit 121 or the RAN 120 and the mobile core network 140, as well as, for example, a wireless backhaul link.

[0039] The RAN 120 is an intermediate network that enables the remote units 105 to access the mobile core network 140. In various embodiments, the UL communication signals may comprise one or more uplink channels, such as a Physical Uplink Control Channel (“PUCCH”) and / or a Physical Uplink Shared Channel (“PUSCH”), while the DL communication signals may comprise one or more downlink channels, such as a Physical Downlink Control Channel (“PDCCH”) and / or a Physical Downlink Shared Channel (“PDSCH”).

[0040] Additionally, satellites 129 provide a non-terrestrial based network that allows remote units 105 to access mobile core network 140 via satellite access. While Figure 1 shows a transparent NTN system in which satellites 129 repeat waveform signals to base units 121, in other embodiments, satellites 129 (for a regenerative NTN system) or NTN gateways 123 (for alternative implementations of a transparent NTN system) may also act as base stations depending on the deployed configuration.

[0041] In some embodiments, the remote unit 105 communicates with an application server via a network connection with the mobile core network 130. For example, an application 107 (e.g., a web browser, a media client, a telephone, and / or a Voice over Internet Protocol (“VoIP”)) on the remote unit 105 may trigger the remote unit 105 to establish a protocol data unit (“PDU”) session (or other database connection) with the mobile core network 130 via the RAN 120. The mobile core network 130 then relays traffic between the remote unit 105 and the application server (e.g., a content server 151 in the packet data network 150) using the PDU session. The PDU session represents a logical connection between the remote unit 105 and the user plane function (“UPF”) 131.

[0042] To establish a PDU session (or PDN connection), the remote unit 105 must register with the mobile core network 130 (also referred to as "attached to the mobile core network" in the context of fourth generation ("4G") systems). Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 130. Thus, the remote unit 105 may have at least one PDU session for communicating with the packet data network 150, which may represent, for example, the Internet. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and / or other communication peers.

[0043] In the context of 5G systems ("5GS"), the term "PDU session" refers to a data connection that provides end-to-end ("E2E") user plane ("UP") connectivity between a remote unit 105 and a particular data network ("DN") through the UPF 131. A PDU session supports one or more Quality of Service ("QoS") flows. In some embodiments, there may be a one-to-one mapping between QoS flows and QoS profiles, whereby all packets belonging to a particular QoS flow have the same 5G QoS identifier ("5QI").

[0044] In the context of a 4G / LTE system, such as an Evolved Packet System ("EPS"), a packet data network ("PDN") connection (also called an EPS session) provides E2E UP connectivity between a remote unit and the PDN. The PDN connectivity procedure establishes an EPS bearer, i.e., a tunnel between the remote unit 105 and a packet gateway ("PGW," not shown) in the mobile core network 130. In some embodiments, there is a one-to-one mapping between EPS bearers and QoS profiles, such that all packets belonging to a particular EPS bearer have the same QoS class identifier ("QCI").

[0045] The base units 121 may be distributed throughout a geographic region. In some embodiments, the base units 121 may be referred to as access terminals, access points, bases, base stations, Node Bs (“NBs”), evolved Node Bs (abbreviated as eNodeBs or “eNBs” and also referred to as evolved universal terrestrial-based radio access network (“E-UTRAN”) Node Bs), 5G / NR Node Bs (“gNBs”), home Node Bs, relay nodes, RAN nodes, or any other terminology used in the art. The base units 121 are generally part of a RAN, such as the RAN 120, and may include one or more controllers communicatively coupled to one or more corresponding base units 121. These and other elements of a radio access network are not shown but are generally known to those skilled in the art. The base units 121 connect to the mobile core network 130 via the RAN 120. Note that in an NTN scenario, certain RAN entities or functions may be incorporated into the satellites 129. For example, the satellites 129 may be embodiments of non-terrestrial-based base stations / base units.

[0046] The base unit 121 may serve several remote units 105 within a serving area, e.g., a cell or cell sector, via wireless communication link 123. The base unit 121 may communicate directly with one or more of the remote units 105 via communication signals. Generally, the base unit 121 transmits DL communication signals to serve the remote units 105 in the time, frequency, and / or spatial domains. Furthermore, the DL communication signals may be carried via wireless communication link 123. The wireless communication link 123 may be any suitable carrier in a licensed or unlicensed radio frequency band. The wireless communication link 123 facilitates communication between one or more of the remote units 105 and / or one or more of the base units 121. It should be noted that during NR-U operation, the base unit 121 and the remote units 105 communicate via unlicensed radio frequency bands.

[0047] In one embodiment, the mobile core network 130 is a 5GC or evolved packet core ("EPC") and may be coupled to a packet data network 150 such as the Internet and private data networks, among other data networks. The remote units 105 may have a subscription or other account with the mobile core network 130. Each mobile core network 130 belongs to a single public land mobile network ("PLMN"). This disclosure is not intended to be limited to any particular wireless communications system architecture or protocol implementation.

[0048] The mobile core network 130 includes several network functions ("NFs"). As shown, the mobile core network 130 includes at least one UPF 131. The mobile core network 130 also includes multiple control plane ("CP") functions, including, but not limited to, an AMF 133 that serves the RAN 120, a session management function ("SMF") 135, a network exposure function ("NEF"), a policy control function ("PCF") 137, a location management function ("LMF") 141, a unified data management function ("UDM"), and a user data repository ("UDR") 139.

[0049] The UPF 131 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU sessions for interconnecting with data networks ("DNs") in the 5G architecture. The AMF 133 is responsible for NAS signaling termination, NAS ciphering and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. The SMF 135 is responsible for session management (i.e., session establishment, modification, and teardown), remote unit (i.e., UE) IP address allocation and management, DL data notification, and traffic steering configuration of the UPF for proper traffic routing.

[0050] The NEF is responsible for providing easy access to network data and resources for customers and network partners. Service providers can activate new capabilities and expose them through APIs. These APIs allow third-party authorized applications to monitor and configure network behavior for several different subscribers (i.e., connected devices using different applications). The PCF 137 is responsible for the unified policy framework and provides policy rules for the CP function, access subscription information for policy decisions in the UDR.

[0051] The LMF 141, in one embodiment, receives positioning measurements or estimates from the RAN 120 and the remote unit 105 (e.g., via the AMF 133) and calculates the location of the remote unit 105. The UDM 139 is responsible for authentication and key agreement ("AKA") credentials, user identity handling, access authorization, and subscription management. The UDR is a repository of subscriber information and can be used to provide several network functions. For example, the UDR may store subscription data, policy-related data, subscriber-related data that is allowed to be exposed to third-party applications, etc. In some embodiments, the UDM is collocated with the UDR and is denoted as the combined entity "UDM / UDR" 139.

[0052] In various embodiments, the mobile core network 130 may also include an Authentication Server Function ("AUSF") (acting as an authentication server), a Network Repository Function ("NRF") (performing NF service registration and discovery, allowing NFs to identify appropriate services to each other and communicate with each other via application programming interfaces ("APIs"), or other NFs defined for 5GC. In some embodiments, the mobile core network 130 may include an Authentication, Authorization, and Accounting ("AAA") server.

[0053] In various embodiments, the mobile core network 130 supports different types of mobile data connections and different types of network slices, with each mobile data connection utilizing a particular network slice, where a "network slice" refers to a portion of the mobile core network 130 optimized for a particular traffic type or communication service. A network instance may be identified by a single network slice selection assistance information ("S-NSSAI"), while a set of network slices that the remote unit 105 is authorized to use is identified by the network slice selection assistance information ("NSSAI").

[0054] Here, "NSSAI" refers to a vector value that includes one or more S-NSSAI values. In some embodiments, various network slices may include separate instances of network functions, such as the SMF 135 and the UPF 131. In some embodiments, different network slices may share some common network functions, such as the AMF 133. In FIG. 1, for ease of illustration, different network slices are not shown, but their support is assumed. If different network slices are deployed, the mobile core network 130 may include a network slice selection function ("NSSF") that is responsible for selecting a network slice instance that serves the remote unit 105, determining the allowed NSSAIs, and determining the AMF set to be used to serve the remote unit 105.

[0055] 1 illustrates a particular number and types of network functions, those skilled in the art will recognize that any number and types of network functions may be included in the mobile core network 130. Furthermore, in LTE variants in which the mobile core network 130 comprises an EPC, the illustrated network functions may be replaced with appropriate EPC entities, such as a mobility management entity ("MME"), a serving gateway ("SGW"), a PGW, a home subscriber server ("HSS"), etc. For example, the AMF 133 may be mapped to the MME, the SMF 135 may be mapped to the control plane portion of the PGW and / or the MME, the UPF 131 may be mapped to the user plane portion of the SGW and PGW, the UDM / UDR 139 may be mapped to the HSS, etc.

[0056] While FIG. 1 shows components of a 5G RAN1 and a 5G core network, the described embodiments apply to other types of communication networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications (“GSM”, i.e., 2G digital cellular network), General Packet Radio Service (“GPRS”), UMTS, LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, etc.

[0057] In the following description, the term "gNB" is used for base station, but can be replaced by any other radio access node, e.g., RAN node, eNB, base station ("BS"), access point ("AP"), NR, etc. Furthermore, operation is primarily described in the context of 5G NR. However, the proposed solutions / methods are equally applicable to other mobile communication systems that support CSI enhancement for higher frequencies.

[0058] FIG. 2 illustrates an NR protocol stack 200 according to an embodiment of the present disclosure. FIG. 2 illustrates a UE 205, a RAN node 210, and an AMF 215 in a 5G core network ("5GC"), which are representative of a set of remote units 105 interfacing with a base unit 121 and a mobile core network 140. As illustrated, protocol stack 200 comprises a user plane protocol stack 202 and a control plane protocol stack 203. User plane protocol stack 201 includes a physical ("PHY") layer 220, a medium access control ("MAC") sublayer 225, a radio link control ("RLC") sublayer 230, a packet data convergence protocol ("PDCP") sublayer 235, and a service data adaptation protocol ("SDAP") sublayer 240. Control plane protocol stack 203 includes the physical layer 220, the MAC sublayer 225, the RLC sublayer 230, and the PDCP sublayer 235. The control plane protocol stack 203 also includes a radio resource control (“RRC”) sublayer 245 and a non-access stratum (“NAS”) sublayer 250 .

[0059] The AS layer (also referred to as the "AS protocol stack") of the user plane protocol stack 201 consists of at least the SDAP, PDCP, RLC, and MAC sublayers, and a physical layer. The AS layer of the control plane protocol stack 203 consists of at least the RRC, PDCP, RLC, and MAC sublayers, and a physical layer. Layer 2 ("L2") is divided into the SDAP, PDCP, RLC, and MAC sublayers. Layer 3 ("L3") includes the RRC sublayer 245 and the NAS layer 250 for the control plane, and includes, for example, an Internet Protocol ("IP") layer and / or a PDU layer (not shown) for the user plane. L1 and L2 are referred to as "lower layers," while layers above L3 (e.g., the transparency layer, the application layer) are referred to as "higher layers" or "upper layers."

[0060] The physical layer 220 provides transparent channels to the MAC sublayer 225. The physical layer 220 may perform clear channel assessment and / or listen-before-talk ("CCA / LBT") procedures using an energy detection threshold, as described herein. In some embodiments, the physical layer 220 may send a UL listen-before-talk ("LBT") failure notification to a MAC entity in the MAC sublayer 225. The MAC sublayer 225 provides logical channels to the RLC sublayer 230. The RLC sublayer 230 provides RLC channels to the PDCP sublayer 235. The PDCP sublayer 235 provides radio bearers to the SDAP sublayer 240 and / or RRC sublayer 245. The SDAP sublayer 240 provides QoS flows to the core network (e.g., 5GC). The RRC layer 245 enables the addition, modification, and release of carrier aggregation and / or dual connectivity. The RRC layer 245 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (“SRBs”) and data radio bearers (“DRBs”).

[0061] The NAS layer 250 resides between the UE 205 and the 5GC 215. NAS messages are routed transparently through the RAN. The NAS layer 250 manages the establishment of communication sessions and is used to maintain continuous communication with the UE 205 as the UE 205 moves between different cells of the RAN. In contrast, the AS layer resides between the UE 205 and the RAN (e.g., RAN node 210) and carries information over the wireless portion of the network.

[0062] By way of background, NR positioning based on NR Lu signals and standalone ("SA") architectures (e.g., beam-based transmissions) was specified for the first time in Rel-16. Target use cases included commercial and regulatory (e.g., emergency services) scenarios, similar to Rel-15. Performance requirements are as follows and are described, for example, in TR 38.855:

[0063] [Table 1]

[0064] 3GPP Rel-17 Positioning recently defined positioning performance requirements for commercial and IIoT use cases, for example as described in TR 38.857, such as:

[0065] [Table 2]

[0066] Several UE positioning techniques supported in Rel-16 are listed in Table 1 (Table 3). Separate positioning techniques shown in Table 2 (Table 4) may be configured and implemented based on LMF and / or UE performance requirements. Note that Table 1 (Table 3) includes Terrestrial Beacon System ("TBS") positioning based on PRS signals, but only Observed Time Difference of Arrival ("OTDOA") based on LTE signals is supported. E-CID includes the cell ID for NR methods. The TBS method refers to TBS positioning based on Metropolitan Beacon System ("MBS").

[0067] [Table 3]

[0068] The transmission of the PRS enables the UE to perform UE positioning-related measurements to calculate a location estimate for the UE and is configured per transmission / reception point (“TRP”), where the TRP may transmit one or more beams.

[0069] In one embodiment, the following RAT dependent positioning techniques may be supported by the system 100:

[0070] DL-TDoA: The Downlink Time Difference of Arrival ("DL-TDOA") positioning method uses the DL RS Time Difference ("RSTD") (and possibly the DL PRS RS Received Power ("RSRP") of the DL PRS RS Received Quality ("RSRQ")) of downlink signals received from multiple TPs at a UE (e.g., remote unit 105). The UE measures the DL RSTD (and possibly the DL PRS RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements, along with other configuration information, are used to determine the location of the UE relative to neighboring transmission points ("TPs").

[0071] DL-AoD: The DL Angle of Departure ("AoD") positioning method uses the measured DL PRS RSRP of downlink signals received at the UE from multiple TPs. The UE measures the DL PRS RSRP of the received signals using assistance data received from a positioning server, and the resulting measurements, along with other configuration information, are used to determine the location of the UE relative to neighboring TPs.

[0072] Multi-RTT: The multi-round trip time ("multi-RTT") positioning method uses UE receive-transmit ("Rx-Tx") measurements and DL PRS RSRPs of downlink signals received from multiple TRPs, as measured by the UE, and gNB Rx-Tx measurements (e.g., measured by a RAN node) and UL sounding reference signal ("SRS")-RSRPs of uplink signals transmitted from the UE at multiple TRPs.

[0073] The UE uses the assistance data received from the positioning server to measure UE Rx-Tx measurements (and possibly DL PRS RSRP of the received signal), and the TRP uses the assistance data received from the positioning server to measure gNB Rx-Tx measurements (and possibly UL SRS-RSRP of the received signal). The measurements are used to determine the round trip time ("RTT") at the positioning server, which is used to estimate the location of the UE. In one embodiment, multi-RTT is supported only for UE-assisted / NG-RAN-assisted positioning techniques, as shown in Table 1.

[0074] E-CID / NR E-CID: In the enhanced Cell ID ("CID") positioning method, the UE's location is estimated using knowledge of the UE's serving ng-eNB, gNB, and cells and is based on LTE signals. Information about the serving ng-eNB, gNB, and cells may be obtained by paging, registration, or other methods. NR enhanced Cell ID ("NR E-CID") positioning refers to techniques that use additional UE measurements and / or NR radio resources and other measurements to improve the UE location estimate using NR signals.

[0075] NR E-CID positioning utilizes some of the same measurements as the measurement control system in the RRC protocol, but the UE is generally not expected to perform additional measurements solely for positioning; e.g., the positioning procedure does not provide measurement configuration or measurement control messages, and the UE reports measurements that are available to the UE rather than having to perform additional measurement operations.

[0076] UL-TOoA: The UL TDOA positioning method uses UL TDOA (and possibly UL SRS-RSRP) at multiple reception points ("RPs") of uplink signals transmitted from the UE. The RPs measure the UL TDOA (and possibly UL SRS-RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements, along with other configuration information, are used to estimate the location of the UE.

[0077] UL-AoA: The UL Angle of Arrival ("AoA") positioning method uses measured azimuth angles and zenith angles of arrival at multiple RPs of uplink signals transmitted from the UE. The RPs measure the A-AoA and Z-AoA of the received signals using assistance data received from a positioning server, and the resulting measurements, along with other configuration information, are used to estimate the location of the UE.

[0078] In one embodiment, system 100 may support various RAT-independent techniques, such as those described in TS 38.305. In one embodiment, a network-aided Global Navigation Satellite System ("GNSS") method uses a UE equipped with a radio receiver capable of receiving GNSS signals. In 3GPP specifications, the term GNSS encompasses both global and regional augmented navigation satellite systems.

[0079] Examples of global navigation satellite systems include GPS, modernized GPS, Galileo, GLONASS, and the BeiDou Navigation Satellite System ("BDS"). Regional navigation satellite systems include the Quasi-Zenith Satellite System ("QZSS"), while a number of augmentation systems fall under the general category of Space-Based Augmentation Systems ("SBAS") and provide regional augmentation services. In this concept, different GNSS (e.g., GPS, Galileo, etc.) can be used separately or in combination to determine the location of a UE.

[0080] In one embodiment, the barometric pressure sensor method uses a barometric pressure sensor to determine the vertical component of the UE's position. The UE measures the barometric pressure and, possibly with the help of aiding data, calculates the vertical component of the UE's location or transmits the measurements to a positioning server for position calculation. This method can be combined with other positioning methods to determine the 3D position of the UE.

[0081] In one embodiment, a WLAN positioning method uses WLAN measurements (e.g., AP identifiers and possibly other measurements) and a database to determine the location of a UE. The UE measures received signals from WLAN access points and, possibly with the help of assistance data, sends the measurements to a positioning server for position calculation. Using the measurement results and a reference database, the UE's location is calculated. Alternatively, the UE uses WLAN measurements and possibly WLAN AP assistance data provided by the positioning server to determine the UE's location.

[0082] In one embodiment, the Bluetooth positioning method uses Bluetooth measurements (beacon identifiers and possibly other measurements) to determine the location of the UE. The UE measures the received signals from the Bluetooth beacons. Using the measurements and a reference database, the location of the UE is calculated. The Bluetooth method can be combined with other positioning methods (e.g., WLAN) to improve the accuracy of UE positioning.

[0083] In one embodiment, the TBS consists of a network of ground-based transmitters that broadcast signals solely for positioning purposes. Current types of TBS positioning signals are MBS signals and PRS. The UE measures the received TBS signals and, possibly with the help of assistance data, calculates the UE's location or transmits the measurements to a positioning server for position calculation.

[0084] In one embodiment, the motion sensor method calculates the displacement of the UE using different sensors, such as an accelerometer, gyroscope, and magnetometer. The UE estimates the relative displacement based on a reference position and / or a reference time. The UE transmits a report including the determined relative displacement, which can be used to determine the absolute position. This method should be used with other positioning methods for hybrid positioning.

[0085] 3 shows a system 300 for NR beam-based positioning. According to Rel-16, the PRS can be transmitted by different base stations (serving and neighboring) using narrow beams over frequency range #1 (“FR1”, e.g., frequencies between 410 MHz and 7125 MHz) and frequency range #2 (“FR2”, e.g., frequencies between 24.25 GHz and 52.6 GHz), which is relatively different compared to LTE, where the PRS is transmitted over the entire cell.

[0086] As shown in FIG. 3, the UE 305 may receive a PRS from a first gNB (“gNB3”), i.e., the serving gNB, and may also receive a PRS from a neighboring second gNB (“gNB1”) 315 and a neighboring third gNB (“gNB2”) 320. Here, the PRS may be locally associated with a set of PRS resources grouped based on a resource set ID for the base station (e.g., TRP). In the illustrated embodiment, each gNB 310, 315, 320 is configured with a first resource set ID 325 and a second resource set ID 330. As shown, the UE 305 receives the PRS on a transmit beam. Here, receive a PRS from gNB3 310 on a set of PRS resources 335 from the second resource set ID 330, receive a PRS from gNB1 315 on a set of PRS resources 335 from the second resource set ID 330, and receive a PRS from gNB2 320 on a set of PRS resources 335 from the first resource set ID 325.

[0087] Similarly, UE positioning measurements, such as reference signal time difference ("RSTD") and PRS RSRP measurements, are made between beams, rather than between different cells as in LTE. In addition, there are additional UL positioning methods that the network leverages to calculate the location of the target UE. Tables 2 (Table 4) and 3 (Table 5) show the mapping of reference signal measurements required for each of the RAT-dependent positioning techniques supported in the UE and gNB, respectively. RAT-dependent positioning techniques involve 3GPP RATs and core network entities to perform UE location estimation, and are distinguished from RAT-independent positioning techniques that rely on GNSS, IMU sensors, WLAN, and Bluetooth technologies to perform positioning of the target device (e.g., UE).

[0088] [Table 4]

[0089] [Table 5]

[0090] Regarding the measurement and reporting configuration according to TS38.215, UE measurements are defined and these measurements are applicable to DL-based positioning techniques, see section 2.4. For an overview of the current implementation concept in Rel-16, the auxiliary data configuration (see Figure 4A) and measurement information (see Figure 4B) are provided for each supported positioning technique.

[0091] 4A is used by the location server to provide assistance data to enable UE-assisted NR downlink TDOA and UE-based NR downlink TDOA. This information element can also be used to provide NR DL TDOA positioning-specific error causes.

[0092] The IE NR-DL-TDOA-SignalMeasurementlInformation 404 shown in FIG. 4B is used by the target device to provide NR-DL TDOA measurements to the location server. The measurements are provided as a list of TRPs, with the first TRP in the list being used as the reference TRP when reporting RSTD measurements. The first TRP in the list may or may not be the reference TRP indicated in the NR-DL-PRS-AssistanceData. Furthermore, the target device selects a reference resource for each TRP and compiles measurements for each TRP based on the selected reference resource.

[0093] Regarding RAT dependent positioning measurements, the different DL measurements including DL PRS-RSRP, DL RSTD, and UE Rx-Tx time difference required for supported RAT dependent positioning techniques are shown in Table 4. The following measurement configurations may be specified: Four pairs of DL RSTD measurements can be performed per cell pair, each with a single reference timing between different pairs of DL PRS resources / resource sets. Eight DL PRS RSRP measurements can be performed on different DL PRS resources from the same cell.

[0094] [Table 6]

[0095] 5 illustrates an architecture in 5GS applicable to positioning of a UE using NR or E-UTRA access. In one embodiment, as described in TS 23.502 and TS 23.273, the AMF 133 receives a request for some location services associated with a particular target UE from another entity (e.g., a Gateway Mobile Location Center (“GMLC”) or a UE), or the AMF 133 itself decides to initiate some location services for a particular target UE (e.g., for an IP Multimedia System (“IMS”) emergency call from the UE). The AMF 133 then sends a location service request to the LMF 141. The LMF 141 processes the location service request, which may include forwarding assistance data to the target UE to assist in UE-based positioning and / or UE-assisted positioning, and / or may include positioning of the target UE. The LMF 141 then returns the results of the location services (e.g., a position estimate for the UE) to the AMF 133. In the case of a location service requested by an entity other than the AMF 133 (e.g., a GMLC or a UE), the AMF 133 returns the location service result to this entity.

[0096] In one embodiment, the NG-RAN node may control several TRPs / TPs, such as resource radio heads, or DL-PRS-dedicated TPs to support PRS-based TBS. In one embodiment, the LMF 141 may have a dedicated signaling connection to an E-Serving Mobile Location Center ("SMLC"), which may enable the LMF 141 to access information from the E-UTRAN (e.g., to support the OTDOA of the E-UTRA positioning method using downlink measurements obtained by the target UE of signals from eNBs and / or PRS-dedicated TPs in the E-UTRAN). The LMF 141 may have a dedicated signaling connection to an SLP. The SLP is the SUPL entity responsible for positioning on the user plane. Further details of user plane positioning are described in TS38.305 Annex A.

[0097] In the case of a split gNB architecture, the gNB-DU may include a TRP function, which may support functionality for the TP, the RP, or both the TP and the RP. The gNB-DU that includes the TRP function does not need to provide cell service.

[0098] For RAN-UE positioning operations, to support positioning of target UEs and delivery of location assistance data to the UE using NG-RAN access in 5GS, the location related functions are distributed as shown in the architecture in Figure 5 and specified in further detail in TS 23.501 and TS 23.273. The overall sequence of events applicable to the UE, NG-RAN, and LMF for any location service is shown in Figure 6.

[0099] It should be noted that when the AMF receives a location service request when the UE is in CM-IDLE state, the AMF implements a network-triggered service request, e.g., as defined by TS 23.502 and TS 23.273, to establish a signaling connection with the UE and assign a specific serving gNB or NG-eNB. The UE is assumed to be in connected mode before starting the flow shown in Figure 6, i.e., signaling that may be necessary to place the UE in connected mode before step 1a is not shown. However, the signaling connection is later released (e.g., by the NG-RAN node as a result of signaling and data inactivity) while positioning is still taking place.

[0100] The procedure flow shown in FIG. 6 includes, in one embodiment, a UE 601, an NG-RAN node 603, an AMF 133, an LMF 141, and a 5GC Location Services (“LCS”) entity 605.

[0101] In step 1a, an entity in 5GC (e.g., GMLC) requests location services (e.g., positioning) for target UE 601 from serving AMF 133 (see messaging 602). In step 1b, serving AMF 133 for target UE 601 determines that some location services are needed (e.g., to determine the location of UE 601 for an emergency call) (see block 604). In step 1c, UE 601 requests some location services (e.g., positioning or delivery of assistance data) from serving AMF 133 at the NAS level (see messaging 606).

[0102] In one embodiment, in step 2, the AMF 133 forwards a location service request to the LMF 141 (see messaging 608). In step 3a, the LMF 141 facilitates location procedures with the serving ng-eNB or gNB and possibly neighboring ng-eNBs or gNBs in the NG-RAN 603 (see block 610), e.g., to obtain positioning measurements or assistance data. In one embodiment, in addition to or instead of step 3a, the LMF 141 facilitates location procedures with the UE 601 (see block 612), e.g., to obtain location estimates or positioning measurements or forward location assistance data to the UE 601, in step 3b.

[0103] In one embodiment, in step 4, the LMF 141 provides a location service response to the AMF 133 (see messaging 614), including any required results, e.g., an indication of success or failure, and, if requested and obtained, a location estimate for the UE 601. In one embodiment, in step 5a, if step 1a was performed, the AMF 133 returns a location service response to the 5GC entity 605 in step 1a, including any required results, e.g., a location estimate for the UE 601. In one embodiment, in step 5b, if step 1b occurred, the AMF 133 uses the location service response received in step 4 (see block 618) to assist the service that triggered it in step 1b (e.g., may provide a location estimate associated with the emergency call to the GMLC). In step 5c, in one embodiment, if step 1c was performed, the AMF 133 returns a location service response to the UE 601, including any required results, e.g., a location estimate for the UE 601.

[0104] In one embodiment, the location procedure applicable to NG-RAN occurs in steps 3a and 3b in Figure 6. Other steps in Figure 6 are applicable to 5GC and are described in more detail in TS 23.502 and TS 23.273. In one embodiment, steps 3a and 3b obtain location-related measurements for the target UE using different positioning methods and calculate a location estimate from these measurements, and possibly additional information such as velocity.

[0105] 7 illustrates a procedure flow for the NG-RAN location reporting procedure, as described, for example, in TS 23.502. In one embodiment, the illustrated procedure is used by the AMF 133 to request the NG-RAN 701 to report where the UE is currently located when the target UE is in the CN-CONNECTED state. The need for the NG-RAN 701 to continue reporting ends when the UE transitions to CM-IDLE or when the AMF 133 sends a revocation indication to the NG-RAN 701. This procedure can be used for services that require accurate cell identification (e.g., emergency services, lawful interception, charging) or for subscription to services by other NFs. When dual connectivity is activated, PSCell information is reported only if requested by the AMF 133.

[0106] In step 1, in one embodiment, the AMF 133 sends a location reporting control message to the NG-RAN 701 (see messaging 702). The location reporting control message shall identify the UE for which reporting is requested and shall include a reporting type and a location reporting level. The location reporting control message may also include an area of ​​interest and a request reference ID. The location reporting level may be TAI+cell identity. The reporting type indicates whether the message is intended to trigger a single standalone report on the current cell identity serving the UE, or to request the NG-RAN 701 to report whenever the UE changes cells, or whenever the UE enters or leaves the area of ​​interest. If the reporting type indicates to report whenever the UE changes cells, and PScell ​​reporting is requested and dual connectivity is used, the master RAN node shall also report to the AMF 133 whenever the PSCell changes. If the report type indicates that the NG-RAN 701 should report when the UE enters or leaves the area of ​​interest, the AMF 133 also provides the requested area of ​​interest information in a location reporting control message. The AMF 133 may include a request reference ID in the location reporting control message to identify the request for a report on the area of ​​interest. If the message includes multiple areas of interest, the request reference ID identifies each area of ​​interest.

[0107] Note that requiring reporting every time a UE changes cell may increase the signaling load for multiple interfaces. Requiring reporting for every change of PSCell ID may increase the signaling load even further. It is therefore recommended that any such reporting only apply to a limited number of subscribers.

[0108] In step 2, in one embodiment, the NG-RAN 701 sends a location report message (see messaging 704) informing the AMF 133 about the UE's location, which shall be expressed as a requested location reporting level. If PSCell reporting is requested and dual connectivity is activated, the master NG-RAN shall also include the PSCell ID. When using NR satellite access, the cell and TAI report by the NG-RAN refers to the fixed cell and fixed TA in which the UE is geographically located. As part of the user location information, the NG-RAN also reports one or more tracking area codes ("TACs") for the selected PLMN, for example, as described in TS 38.413, although it is not guaranteed that the UE will always be located in one of these TACs.

[0109] When the UE is in the RRC inactive state CM-CONNECTED, if the NG-RAN 701 receives a location report control message from the AMF 133 with the report type indicating a single standalone report, the NG-RAN 701 shall perform NG-RAN paging before reporting the location to the AMF 133. The NG-RAN 701 shall send the location report immediately and shall not wait to create a dual connectivity configuration. However, if a PSCell report is requested and the PSCell ID is known to the master RAN node, the PSCell report shall be included in the location report. If the RAN paging fails, the RAN shall report the last known location of the UE with a timestamp.

[0110] When the UE is in CM-CONNECTED in RRC inactive state, if NG-RAN 701 receives a location reporting control message from AMF 133 where the reporting type indicates continuous reporting whenever the UE changes cells, NG-RAN 701 shall send a location report message containing the last known location of the UE together with a timestamp to AMF 133. If the UE was using dual connectivity just before entering CM-CONNECTED in RRC inactive state and PSCell reporting is requested, the location report shall also include the PSCell ID.

[0111] When the UE is in CM-CONNECTED, if the NG-RAN 701 receives a location reporting control message from the AMF 133 with a reporting type of area of ​​interest based report, the NG-RAN 701 shall track the presence of the UE in the area of ​​interest and shall send a location report message to the AMF 133 containing the UE's presence in the area of ​​interest as described in Section D.2 (e.g., IN, OUT, or UNKNOWN) and the UE's current location when the UE is in an RRC connected state or when the UE is in an RRC inactive state (including the PSCell ID if a PSCell report is requested and dual connectivity is activated), and if the NG-RAN 701 recognizes that the UE's presence in the area of ​​interest is different from the last reported one, the last known location of the UE with a timestamp (including the PSCell ID if a PSCell report is requested and the UE was using dual connectivity immediately before entering CM-CONNECTED in an RRC inactive state) shall be included. When the NG-RAN 701 detects that the UE has entered or exited multiple regions of interest, it shall send multiple pairs of the UE's presence in the regions of interest and requested reference IDs in one location report message to the AMF 133. If the UE transitions from an RRC inactive state to an RRC connected state, the NG-RAN 701 shall check the UE's latest location (including the PSCell ID if PSCell reporting is requested and dual connectivity is activated) and shall follow the rules when the UE is in an RRC connected state.

[0112] The AMF 133 may receive location reports even if the presence of the UE in the area of ​​interest has not changed. The AMF 133 stores the most recently received PSCell ID along with its associated timestamp. The AMF 133 stores the most recently received PSCell ID along with its associated timestamp when the timestamp is available.

[0113] In one embodiment, in step 3, the AMF 133 may send a Location Report Cancellation message informing the NG-RAN 701 that it should terminate location reporting for the given UE corresponding to the reporting type or for the area of ​​interest indicated by the Request Reference ID. This message is necessary when the reporting type is requested for continuous reporting or the area of ​​interest. The AMF 133 may include the Request Reference ID indicating the requested location reporting control for the area of ​​interest, and therefore the NG-RAN 701 should terminate location reporting for the area of ​​interest. It should be noted that during an Xn handover, the location reporting related state of the source NG-RAN node is transferred to the target NG-RAN node.

[0114] FIG. 8A illustrates one embodiment of a transparent satellite-based NG-RAN architecture. In the illustrated embodiment, the satellite payload performs frequency conversion and radio frequency amplification in both the uplink and downlink directions. The satellite payload corresponds to an analog RF repeater. Thus, the satellite 802 repeats the NR-Uu 804 air interface from the feeder link (between the NTN gateway 806 and the satellite 802) to the service link (between the satellite 802 and the UE 810), and from the service link to the feeder link. The satellite air interface ("SRI") on the feeder link is the NR-Uu 804. In other words, the satellite does not terminate the NR-Uu 804. The NTN GW 806 supports all functions necessary to forward signals on the NR Uu 804 interface. Different transparent satellites can be connected to the same terrestrial gNB 808. It should be noted that several gNBs 808 may access a single satellite payload, but the description is simplified to a unique gNB 808 accessing a satellite payload without loss of generality.

[0115] Figure 8B shows an embodiment of a regenerative satellite-based NG-RAN architecture without ISL. In one embodiment, the NG-RAN logical architecture as described in TS 38.401 is used as a baseline for the NTN scenario. The satellite payload performs regeneration of signals received from the ground. The NR-Uu 804 air interface is the service link between the UE 810 on the feeder link between the NTN gateway 806 and the satellite 802, the satellite 802, and the SRI 812. The SRI 812 is the transport link between the NTN GW 806 and the satellite 802. Note that the satellite 802 may undertake additional traffic routing functions outside the RAN scope. The satellite payload also provides the ISL between the satellites. The ISL is the transport link between the satellites. The ISL may be a radio or optical interface, may or may not be defined by 3GPP, and is outside the scope of the study. The NTN GW 806 is a transport network layer node and supports all necessary transport protocols.

[0116] Figure 8C illustrates an embodiment of a regenerative satellite-based NG-RAN architecture with an ISL. Figure 8C shows that a UE 810 served by a gNB 808 onboard a satellite 802 can access a 5GCN 814 via the ISL. gNBs 808 onboard different satellites 802 can connect to the same terrestrial 5GCN 814. When a satellite 802 hosts multiple gNBs 808, the same SRI 812 transports all corresponding NG interface instances.

[0117] In general, the subject matter disclosed herein enables an enhanced solution for enabling network-verified location determination of a target UE. In one embodiment, a method is disclosed for enabling NG-RAN location request and reporting triggered by an AMF for verification of a UE's location in an NTN deployment. In one embodiment, a method is disclosed for triggering an LMF to initiate a network-verified location procedure using an NTN RAT-dependent positioning technique. In one embodiment, a method is disclosed for supporting NG-RAN location reporting and UE-reported network verification for NTN multi-connectivity scenarios. In one embodiment, various embodiments described below may be implemented in combination with each other to support NR positioning using supported NTN interfaces and network entities / nodes.

[0118] In one embodiment, for purposes of this disclosure, positioning-related reference signals may refer to reference signals used for positioning procedures / purposes to estimate the location of a target UE, e.g., reference signals based on existing reference signals such as PRS or SRS. The target UE may be referred to as a device / entity to be localized / located. In one embodiment, the target UE is referred to as a UE of interest whose location is calculated by the network or the target UE itself. Additionally, the subject matter disclosed in Lenovo Patent Application SMM020220104-GR-NP (IDF-153116) is incorporated herein by reference and may be implemented in combination with embodiments of the present disclosure.

[0119] In a first embodiment, a system for a RAT-independent location collection procedure between an AMF (via an NG-RAN node) and a UE is disclosed. According to the first embodiment, a location request is initiated by the AMF to request the NG-RAN node to provide location information regarding the current location of a target UE in a CM-CONNECTED state (including either an RRC CONNECTED state or an RRC INACTIVE state), where the location information consists of at least location information derived from a RAT-independent method (non-3GPP positioning method). The current behavior of requesting location information or network information based on cell identity may not be justified / accurate in NTN deployments for applicable services because cell sizes are very large (e.g., on the order of hundreds of kilometers) and may cover multiple areas of interest; for example, in the case of geodetic satellites, one cell may span an entire continent. In one embodiment, the main purpose of the procedure is to obtain initial location information for the target UE, which may be used to register the UE in a specific PLMN / RAN area and then verified to use services such as emergency services, lawful interception, charging, or subscription services in non-terrestrial networks.

[0120] 9 illustrates one embodiment of a procedure for NTN NG-RAN RAT independent location reporting. In one embodiment, in step 1, a location reporting control message (see messaging 902) is initiated by the AMF 133, and the location reporting control message includes a request for RAT independent location information including GNSS information, for example, GNSS time of day ("ToD") in ms (e.g., based on GPS, GLONASS, NavIC), Bluetooth positioning, WLAN positioning, IMU sensor information, altitude, direction / azimuth speed estimate, accuracy, or a combination thereof.

[0121] In one embodiment, in step 2, the NG-RAN node 903, e.g., a serving gNB, requests RAT-independent location information from the target UE 901 using RRC signaling such as intra / inter-RAT measurement reporting, RRC reconfiguration, etc., provided that the CommonLocationlinfo IE is configured (messaging 904). In this case, the trigger to the NG-RAN node 903 is derived by the AMF 133 from the request for RAT-independent target UE location information.

[0122] In one embodiment, in step 3, the target UE responds with RAT-independent location information contained in a CommonLocationInfo IE (see messaging 906). In one embodiment, in step 4, the NG-RAN node sends a Location Report Response message containing the RAT-independent location information to the AMF 133 (see messaging 908). In one embodiment, in step 5, the AMF 133 performs an Initiate Location Procedure (see block 910), which is verified by the network.

[0123] 9, the AMF 133 initiates a location reporting control message to the NG-RAN 903, which may include an identifier for the UE 901 for which reporting is requested. Additionally, in one embodiment, the following information may be required in the configuration: Location method type or location source may be indicated, including RAT dependent methods based on SL measurements, RAT independent methods (e.g. GNSS) and cell ID, SSB ID, beam ID, SSB measurements (e.g. RSRP) or CSL-RS measurements (e.g. RSRP). Location reporting types, including single, periodic, event-based, and / or aperiodic reporting. In one embodiment, a single report may be requested, while in other implementations, periodic reporting may be requested with a configured periodicity or reporting interval and / or several reports. For event-based reporting, the NG-RAN will perform a location report for the UE when the UE's area changes, e.g., when it moves from one NTN cell / beam to another NTN cell / beam, or when it moves from an NTN cell to a TN cell (or vice versa), or when a timer starts / expires. A timestamp with the overall location report (e.g., location timestamp and NG-RAN timestamp), or if the report contains multiple locations, a timestamp associated with each location The configuration may also include a certain quality measurement indicator / location estimate quality indicator associated with each location estimate, e.g., horizontal / vertical accuracy; and / or UE mobility parameters, including speed estimates, acceleration estimates, and / or trajectories

[0124] In the case of a transparent payload NTN architecture, the AMF, the NG-RAN node, and the UE may perform the procedure shown in Figure 9. In the case of a regenerative payload NTN architecture, the AMF may send a location reporting control message to multiple NTN-gNB satellites in advance based on the movement of different satellites and which satellites are in the coverage of the target UE at a given time. In another implementation, events can be defined such that a location reporting control message is sent to the AMF following each NTN-gNB handover.

[0125] In one embodiment, steps 2 and 3 of FIG. 9 may assist the NG-RAN node in determining the location of the target UE and may be in the form of NG-RAN assistance information.

[0126] In the extended information of step 4 of Figure 9, the NG-RAN node responds to the AMF with a location report message, in this case including the requested information in the configuration message of step 1 of Figure 9 regarding the target UE location information. The location information may be information based on the location method type indicated in the location report control message, for example, GNSS-based location information, cell / beam ID information, etc., as well as the following additional elements: Single / multiple location points with single / multiple timestamps an error message indicating the unavailability of the requested location information, e.g., no UE location; and / or Cell / SSB ID changes due to satellite mobility and / or UE mobility, including previous NTN cell ID / beam ID and current NTN cell ID / beam ID

[0127] In the case of a regenerative payload NTN architecture, the source NTN-gNB may forward the location report to the target NTN-gNB via an ISL for forwarding to the AMF. In an alternative implementation, during an NTN-gNB handover, the AMF may receive an error message from the source NTN-gNB (e.g., an NG-RAN node) or a handover indication that prompts the AMF to retrigger a location report control message with the target NTN-gNB.

[0128] In another enhanced implementation, the AMF may send a location report cancellation message requesting the NG-RAN node to stop / stop an already requested location report.

[0129] In an alternative implementation in which the NG-RAN node reports an error message regarding the location reported by the UE, the AMF may trigger a network-initiated location request procedure together with the LMF to directly determine the location of the target UE using a RAT-independent or RAT-dependent method or a combination thereof, which are further described below with reference to Figure 10.

[0130] 10 shows a location reporting and verification procedure initiated by the AMF. In a second embodiment, after UE registration is completed, the AMF initiates a location request procedure to verify the UE location in the NTN cell, where the first reported location may be based on a RAT-independent method (e.g., GNSS) or a cell ID as described in embodiment 1, while a separate RAT-dependent location procedure may be used to verify the location reported by the UE. The AMF may trigger a location request initiated by the network to perform location verification of the location reported by the UE.

[0131] In one implementation, the AMF that initiates the location reporting and verification procedure may be a serving AMF (e.g., based on a single PLMN) of the NTN NG-RAN node. In an alternative implementation, the AMF may initiate the location reporting and verification procedure.

[0132] In one embodiment, the AMF initiates an NG-RAN based location request procedure and simultaneously initiates a network initiated location service request to the serving LMF to initiate a network-based location procedure to determine the location of the target UE (see FIG. 10). In one embodiment, it may be advantageous to initiate the network-based location procedure as early as possible due to the long propagation delays of NTN systems. The network-based location procedure may include a RAT dependent positioning method using any one or more of the following positioning techniques: DL-TDoA DL-AoD Multi-RTT E-CID / NR E-CID UL-TDoA UL-AoA ·SL-TDoA SL-AoA / AoD SL-RTT (one-way and / or two-way) ·SL RSS measurement ·Direct AI / ML positioning AI / ML-assisted positioning techniques

[0133] In one embodiment, the aforementioned positioning techniques are also adapted for NTN scenarios to account for Doppler compensation as well as propagation delays experienced by NTN systems. The network-based verified UE position estimate may be derived based on PRS / SRS transmissions using an NTN network deployment and may be DL-based measurements, or UL-based measurements, or both DL-based and UL-based measurements, or SL-based measurements, or a combination thereof.

[0134] In one embodiment, the NG-RAN based location request may result in a GNSS-based location, or cell ID, or SSD ID, or beam ID. In one embodiment, both procedures are initiated in parallel, as shown in Figure 10. Figure 10 is an example diagram of the call flow required to perform verification of one or more UE locations retrieved from the NG-RAN and stored in the AMF.

[0135] In another implementation, the AMF initiates two location procedures sequentially, for example, when the NG-RAN performs a location report, the AMF initiates a network-initiated location service request to the LMF.

[0136] 10 , in one embodiment, after UE registration is completed in step 1.1 (see procedure 1002), the AMF 133 triggers a location request (see messaging 1004) to the NTN NG-RAN node 1003 for location information upon UE registration as described in embodiment 1. In one embodiment, in step 1.2, the AMF 133 may also initiate a network (guided) location request together with the LMF 141.

[0137] In one implementation, a location request verified by the NTN may be sent by invoking an Nlmf Location DetermineLocation service operation to the LMF 141 to request the current location of the UE 1001. In one embodiment, this service operation may include at least one of an LCS correlation identifier, a serving cell identity of the primary NTN cell at the master RAN node and, when a secondary RAN node is available based on a dual connectivity scenario, a primary NTN cell at the secondary RAN node, and an indication of the type of location request, e.g., restricted service client (e.g., emergency services). In one embodiment, the service operation may include an indication of whether the UE 1001 supports the LTE Positioning Protocol (“LPP”), the required QoS (e.g., required QoS for emergency and restricted services) and the shape of the supported Geographical Area Description (“GAD”), and the UE NTN positioning capabilities based on a previous signaling exchange with the LMF 141.

[0138] In another implementation, the AMF 133 may store the positioning capabilities of the UE 1001. In yet another implementation, the AMF 133 may indicate to use a RAT-dependent method for UE location estimation as part of the validation procedure. These methods may be indicated based on their suitability for single-satellite and multi-satellite scenarios. In a further indication, the AMF 133 may also indicate to the LMF 141 whether the NTN deployment is a single-satellite or multi-satellite case. This location request trigger may be applicable to the following scenarios (Note: this step may be performed in parallel with step 1.1 or after step 3 depending on the scenario): AMF133 performs validation of UE location with respect to configurable location granularity, e.g., a specific location accuracy (on the order of centimeters, meters, kilometers, etc.), country, or international region; The UE1001 must register with 5GC for emergency services, and / or · The UE 1001 requests establishment of a PDU session (e.g., emergency session initiation) related to the applicable restricted service via the LCS service for the UE 1001 that is registering or has been registered for NTN single-satellite access or multi-satellite access.

[0139] In one embodiment, in step 2, in case of the above trigger, the NG-RAN 1003 initiates a procedure (see block 1006) to the UE based on the location type requested by the AMF 133 (as detailed above with reference to embodiment 1).

[0140] In one embodiment, in step 3, the NG-RAN 1003 provides a UE location report to the AMF 133 based on information received by the UE 1001 (e.g., as detailed above with reference to embodiment 1) (see messaging 1008).

[0141] In one embodiment, the LMF 141 initiates a RAT-dependent location procedure with the NTN NG-RAN node 1003 and the UE 1001. In step 4.1, in one embodiment, the LMF 141 facilitates location procedures (see block 1010) with the serving NTN-gNB and possibly neighboring NTN-gNBs in the NG-RAN 1003, which may be applicable to both transparent and regenerative payload architectures, e.g., to perform PRS / SRS resource requests, obtain positioning measurements, etc., in which case the location procedure is RAT-dependent. This may also be applicable to single-satellite and multi-satellite cases. An example of this may include the use of a network-based positioning method that relies on the NR Positioning Protocol A (“NRPPa”) protocol, e.g., to exchange NTN-gNB measurements, etc.

[0142] In one embodiment, in step 4.2, the LMF 141 facilitates location procedures, e.g., via LPP with the UE 1001, for example, to exchange NTN capability information, provide NTN assistance data configurations, provide NTN location measurement configurations, provide NTN location information reports (location estimates or positioning measurements), provide error / abort messages, etc. (see block 1012). In one embodiment, the mode of location estimation may include a UE-assisted positioning procedure, although in other implementations, a UE-based positioning procedure for determining the UE 1001 location is not excluded.

[0143] In step 5, in one embodiment, the LMF 141 provides a location service response to the AMF 133 (see messaging 1014) including any required results, e.g., a location estimate for the UE 1001. This implementation uses an Nlmf_Location_DetermineLocation response to convey the location response to the AMF 133. This message may also include an LCS correlation identifier, information about the location estimate and its associated validity and accuracy, a positioning method including DL-based measurements, or UL-based measurements, or both DL-based and UL-based measurements, or SL-based measurements, or a combination thereof, and a service action including a timestamp of the location estimate. The foregoing may be mapped to one or more location estimates, each providing the information described above. For example, in the case of country determination, the service action from the LMF 141 may also return an indication of the country or international region determined in step 4 in addition to the location estimate.

[0144] In step 6, in one embodiment, the AMF 133 validates the reported location using configured criteria (see block 1016). The configured criteria may include time validity of the location estimate relative to the received location from the NG-RAN 1003, area validity with respect to the area over which both the RAT-independent and RAT-dependent location estimates are calculated, etc. If successful, in one embodiment, no further steps are required. If steps 1.1-3 are not supported, in one embodiment, for example, if the UE 1001 does not have RAT-independent positioning capability, step 1.2 may be initiated and then steps following step 4.1 may continue.

[0145] In one embodiment, if in step 7 it is determined that the UE location verification is successful (see procedure 1018), the UE 1001 continues to maintain connection with the network; otherwise, if it is determined that the UE location verification is unsuccessful, the UE 1001 is deregistered from the network.

[0146] After the location of the provided RAT-independent method is verified, in one embodiment, the network (e.g., AMF 133 and LMF 141) may grant a location certificate indicating that the reported location of the UE 1001 via the NG-RAN 1003 can be trusted for a certain period of time, which may include minutes, hours, days, or an absolute time base and date. In one embodiment, this avoids repeated and unnecessary network validation signaling on the network side. For example, if the location reported by the UE to be verified is GNSS and is successfully verified using the RAT-dependent method, the network may issue a location certificate attesting to the authenticity of the UE's reported GNSS position for a certain period of time, and upon expiration of the location certificate, the network validation procedure is re-triggered. In one embodiment, this enables low-latency NTN position determination, for example, for emergency services.

[0147] In a third embodiment directed to location reporting and verification using different multi-connectivity options, a solution is described for NG-RAN reporting and location verification of a target UE using dual connectivity between multiple satellites and TN and NTN connectivity.

[0148] 11A shows a first scenario of multi-satellite connectivity using a transparent payload architecture. According to Scenario 1, in one embodiment, the procedures described in Embodiments 1 and 2 may be used to determine and verify the location of a UE. A master cell group ("MCG") and a secondary cell group ("SCG") are established, and the UE establishes an initial access procedure with a gNB, i.e., part of the MCG, after which the AMF may initiate an NG-RAN location reporting procedure with the MCG gNB. In another alternative implementation, the AMF may initiate an NG-RAN location reporting procedure with the gNB part of the SCG upon successful initial access and registration.

[0149] 11B illustrates a second scenario of multi-satellite connectivity using a regenerative payload architecture. According to Scenario 2, in one embodiment, the procedures described in Embodiments 1 and 2 may be used to determine and verify the location of the UE. As in Scenario 1, the MCG and SCG are established, and the UE establishes an initial access procedure with an NTN gNB-DU, i.e., part of the MCG, after which the AMF may initiate an NG-RAN location reporting procedure with the MCG gNB-CU and MCG gNB-DU. In another alternative implementation, the AMF may initiate an NG-RAN location reporting procedure with the gNB-DU, i.e., part of the SCG, upon successful initial access and registration.

[0150] In this case, the gNB-CU that receives a location report request from the AMF may forward the same request to the NTN gNB-DU to collect RAT-independent location information. This response may also be reported from the NTN gNB-DU to the AMF via the NTN gateway (gNB-CU).

[0151] Figure 11C illustrates a third scenario of TN and NTN connectivity using a transparent payload architecture. According to Scenario 3, in one embodiment, an MCG can be established with a terrestrial gNB or an NTN gNB. However, due to propagation delays and ease of connectivity, the first priority is to assign a terrestrial gNB as part of the MCG, which can enable the initial access procedure and NG-RAN location reporting. In this case, the NTN and gateway form part of the SCG. Therefore, the AMF can initiate the NG-RAN location reporting procedure with the MCG terrestrial gNB using legacy reporting procedures that rely on cell ID coarse location identification and verification. Therefore, the UE's location can be easily verified via the connection with the terrestrial gNB.

[0152] Figure 11D shows a fourth scenario of TN and NTN connectivity using a transparent payload architecture with different AMFs and LMFs. According to Scenario 4, each gNB may also be connected to separate AMFs and LMFs belonging to different PLMN areas. This scenario serves as another variation of Scenario 3, and procedures related to location and reporting verification may be applicable using the MCG and SCG configurations described above.

[0153] 12 illustrates a user equipment device 1200 that may be used for NTN-based UE location verification, according to embodiments of the present disclosure. In various embodiments, the user equipment device 1200 is used to implement one or more of the solutions described above. The user equipment device 1200 may be an embodiment of a UE, such as the remote unit 105 and / or the UE 205 described above. Additionally, the user equipment device 1200 may include a processor 1205, a memory 1210, an input device 1215, an output device 1220, and a transceiver 1225. In some embodiments, the input device 1215 and the output device 1220 are combined into a single device, such as a touchscreen. In some embodiments, the user equipment device 1200 may not include the input device 1215 and / or the output device 1220. In various embodiments, user equipment device 1200 may include one or more of a processor 1205 , a memory 1210 , and a transceiver 1225 , and may not include an input device 1215 and / or an output device 1220 .

[0154] As shown, the transceiver 1225 includes at least one transmitter 1230 and at least one receiver 1235, where the transceiver 1225 communicates with one or more base units 121. Additionally, the transceiver 1225 may support at least one network interface 1240 and / or application interface 1245. The application interface 1245 may support one or more APIs. The network interface 1240 may support 3GPP reference points such as Uu and PC5. As will be appreciated by those skilled in the art, other network interfaces 1240 may be supported.

[0155] Processor 1205, in one embodiment, may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 1205 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field programmable gate array (“FPGA”), digital signal processor (“DSP”), coprocessor, application-specific processor, or similar programmable controller. In some embodiments, processor 1205 executes instructions stored in memory 1210 to implement the methods and routines described herein. Processor 1205 is communicatively coupled to memory 1210, input devices 1215, output devices 1220, and transceiver 1225. In some embodiments, processor 1205 may include an application processor (also referred to as a “main processor”) that manages application domain and operating system (“OS”) functions and a baseband processor (also referred to as a “baseband radio processor”) that manages radio functions.

[0156] Memory 1210, in one embodiment, is a computer-readable storage medium. In some embodiments, memory 1210 includes a volatile computer storage medium. For example, memory 1210 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 1210 includes a non-volatile computer storage medium. For example, memory 1210 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 1210 includes both volatile and non-volatile computer storage media.

[0157] In some embodiments, memory 1210 stores data related to CSI enhancement for higher frequencies. For example, memory 1210 may store parameters, configurations, resource allocations, policies, etc., as described above. In some embodiments, memory 1210 also stores program code and associated data, such as an operating system or other controller algorithms, and one or more software applications operating on user equipment device 1200.

[0158] The input device(s) 1215, in one embodiment, may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device(s) 1215 may be integrated with the output device(s) 1220, for example, as a touch screen or similar touch-sensitive display. In some embodiments, the input device(s) 1215 includes a touch screen, whereby text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device(s) 1215 includes two or more different devices, such as a keyboard and a touch panel.

[0159] Output device(s) 1220, in one embodiment, is designed to output visual, audio, and / or tactile signals. In one embodiment, output device(s) 1220 includes an electronically controllable display or display device capable of outputting video data to a user. For example, output device(s) 1220 may include, without limitation, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, output device(s) 1220 may include a wearable display that is separate from but communicatively coupled to the rest of user equipment device 1200, such as a smartwatch, smart glasses, or a head-up display. Furthermore, output device(s) 1220 may be a component of a smartphone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0160] In some embodiments, output device(s) 1220 include one or more speakers for generating sound. For example, output device(s) 1220 may generate audible alerts or notifications (e.g., beeps or chimes). In some embodiments, output device(s) 1220 include one or more haptic devices for generating vibrations, movement, or other haptic feedback. In some embodiments, all or a portion of output device(s) 1220 may be integrated with input device(s) 1215. For example, input device(s) 1215 and output device(s) 1220 may form a touchscreen or similar touch-sensitive display. In other embodiments, output device(s) 1220 may be located near input device(s) 1215.

[0161] The transceiver 1225 includes at least one transmitter 1230 and at least one receiver 1235. The transceiver 1225 may be used to provide UL communication signals to the base unit 121 and receive DL communication signals from the base unit 121, as described herein. Similarly, the transceiver 1225 may be used to transmit and receive SL signals (e.g., V2X communications), as described herein. Although only one transmitter 1230 and one receiver 1235 are shown, the user equipment device 1200 may have any suitable number of transmitters 1230 and receivers 1235. Furthermore, the transmitter 1230 and receiver 1235 may be any suitable type of transmitter and receiver. In one embodiment, the transceiver 1225 includes a first transmitter / receiver pair used to communicate with a mobile communications network over a licensed radio frequency band and a second transmitter / receiver pair used to communicate with a mobile communications network over an unlicensed radio frequency band.

[0162] In some embodiments, a first transmitter / receiver pair used to communicate with a mobile communications network over a licensed radio frequency band and a second transmitter / receiver pair used to communicate with a mobile communications network over an unlicensed radio frequency band may be combined into a single transceiver unit, e.g., a single chip that performs functions used with both licensed and unlicensed radio frequency bands. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, some transceivers 1225, transmitters 1230, and receivers 1235 may be implemented as physically separate components that access shared hardware and / or software resources, such as, for example, a network interface 1240.

[0163] In various embodiments, one or more transmitters 1230 and / or one or more receivers 1235 may be implemented and / or integrated as a single hardware component, such as a multi-transceiver chip, a system-on-chip, an ASIC, or other type of hardware component. In some embodiments, one or more transmitters 1230 and / or one or more receivers 1235 may be implemented and / or integrated as a multi-chip module. In some embodiments, other components, such as a network interface 1240 or other hardware components / circuits, may be integrated as a single chip with any number of transmitters 1230 and / or receivers 1235. In such embodiments, the transmitters 1230 and receivers 1235 may be logically configured as a transceiver 1225 using one or more common control signals, or may be logically configured as modular transmitters 1230 and receivers 1235 implemented on the same hardware chip or multi-chip module.

[0164] 13 illustrates one embodiment of a network device 1300 that may be used for NTN-based UE location verification, according to embodiments of the present disclosure. In some embodiments, the network device 1300 may be an embodiment of a RAN node and supporting hardware of a RAN node, such as the base unit 121 and / or gNB described above. Additionally, the network device 1300 may include a processor 1305, a memory 1310, an input device 1315, an output device 1320, and a transceiver 1325. In some embodiments, the network device 1300 does not include the input device 1315 and / or the output device 1320.

[0165] As shown, the transceiver 1325 includes at least one transmitter 1330 and at least one receiver 1335, where the transceiver 1325 communicates with one or more remote units 105. Additionally, the transceiver 1325 may support at least one network interface 1340 and / or application interface 1345. The application interface 1345 may support one or more APIs. The network interface 1340 may support 3GPP reference points such as the Uu, N1, N2, N3, N5, N6, and / or N7 interfaces. As will be appreciated by those skilled in the art, other network interfaces 1340 may be supported.

[0166] The processor 1305, in one embodiment, may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 1305 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field programmable gate array (“FPGA”), digital signal processor (“DSP”), coprocessor, application-specific processor, or similar programmable controller. In some embodiments, the processor 1305 executes instructions stored in the memory 1310 to implement the methods and routines described herein. The processor 1305 is communicatively coupled to the memory 1310, the input devices 1315, the output devices 1320, and the transceiver 1325. In some embodiments, the processor 1305 may include an application processor (also referred to as a “main processor”) that manages application domain and operating system (“OS”) functions and a baseband processor (also referred to as a “baseband radio processor”) that manages radio functions. In various embodiments, the processor 1305 controls the network device 1300 to implement the network entity behavior (e.g., of a gNB) described above for NTN-based UE location verification.

[0167] Memory, in one embodiment, is a computer-readable storage medium. In some embodiments, memory 1310 includes a volatile computer storage medium. For example, memory 1310 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 1310 includes a non-volatile computer storage medium. For example, memory 1310 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 1310 includes both volatile and non-volatile computer storage media.

[0168] In some embodiments, memory 1310 stores data related to CSI enhancement for higher frequencies. For example, memory 1310 may store parameters, configurations, resource allocations, policies, etc., as described above. In some embodiments, memory 1310 also stores program code and associated data, such as an operating system (“OS”) or other controller algorithms, and one or more software applications running on network device 1300.

[0169] The input device(s) 1315, in one embodiment, may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device(s) 1315 may be integrated with the output device(s) 1320, for example, as a touch screen or similar touch-sensitive display. In some embodiments, the input device(s) 1315 includes a touch screen, whereby text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device(s) 1315 includes two or more different devices, such as a keyboard and a touch panel.

[0170] Output device(s) 1320, in one embodiment, may include any known electronically controllable display or display device. Output device(s) 1320 may be designed to output visual, audio, and / or tactile signals. In some embodiments, output device(s) 1320 includes an electronic display capable of outputting video data to a user. Additionally, output device(s) 1320 may be a component of a smartphone, personal digital assistant, television, table computer, notebook (laptop) computer, personal computer, vehicle dashboard, etc.

[0171] In some embodiments, the output device(s) 1320 include one or more speakers for generating sound. For example, the output device(s) 1320 may generate audible alerts or notifications (e.g., beeps or chimes). In some embodiments, the output device(s) 1320 include one or more haptic devices for generating vibrations, movement, or other haptic feedback. In some embodiments, all or a portion of the output device(s) 1320 may be integrated with the input device(s) 1315. For example, the input device(s) 1315 and the output device(s) 1320 may form a touchscreen or similar touch-sensitive display. In other embodiments, all or a portion of the output device(s) 1320 may be located near the input device(s) 1315.

[0172] As discussed above, the transceiver 1325 may communicate with one or more interworking functions that provide access to one or more remote units and / or one or more PLMNs. The transceiver 1325 may also communicate with one or more network functions (e.g., in the mobile core network 80). The transceiver 1325 operates under the control of the processor 1305 to transmit messages, data, and other signals and to receive messages, data, and other signals. For example, the processor 1305 may selectively activate the transceiver (or a portion thereof) at a particular time to transmit and receive messages.

[0173] The transceiver 1325 may include one or more transmitters 1330 and one or more receivers 1335. In some embodiments, one or more transmitters 1330 and / or one or more receivers 1335 may share transceiver hardware and / or circuitry. For example, one or more transmitters 1330 and / or one or more receivers 1335 may share antennas, antenna tuners, amplifiers, filters, oscillators, mixers, modulators / demodulators, power supplies, etc. In one embodiment, the transceiver 1325 implements multiple logical transceivers using common physical hardware while using different communication protocols or protocol stacks.

[0174] In one embodiment, the processor 1305 is configured to: send a RAT-independent location information request via the transceiver 1325, the request including a location configuration for the NG-RAN node; receive RAT-independent location information of the target UE corresponding to the sent location information request via the transceiver 1325, the RAT-independent location information including a location estimate of the target UE; trigger a location server to determine a location estimate of the target UE using the RAT-dependent positioning indication; receive the location estimate based on the RAT-dependent positioning indication via the transceiver 1325; and perform validation of the received RAT-independent target UE location against the RAT-dependent UE location estimate.

[0175] In one embodiment, the processor 1305 initiates a location request to the NG-RAN node and a location request to the location server simultaneously or sequentially.

[0176] In one embodiment, the NG-RAN location configuration includes a request for the UE location based on the configured RAT independent positioning information.

[0177] In one embodiment, the RAT independent positioning information includes at least one selected from the group of GNSS positioning information, Bluetooth positioning information, WLAN positioning information, IMU sensor information, altitude information, direction or orientation information, speed estimate information, accuracy information, or a combination thereof.

[0178] In one embodiment, the processor 1305 triggers the NG-RAN node to report the target UE location information.

[0179] In one embodiment, location reporting by an NG-RAN node may be based on at least one selected from the group including single reporting, periodic reporting, event-based reporting, aperiodic reporting, or a combination thereof.

[0180] In one embodiment, a location report by an NG-RAN node includes multiple locations, each of the multiple locations associated with a timestamp and a location estimate quality indicator.

[0181] In one embodiment, the location report includes an error message in response to the UE's location being unavailable.

[0182] In one embodiment, verifying and reporting target UE location is supported for NTN multi-connectivity scenarios including transparent payload connectivity option, regenerative payload connectivity option, terrestrial-based connectivity option, and non-terrestrial-based connectivity option.

[0183] In one embodiment, the network entity comprises an AMF.

[0184] In one embodiment, the processor 1305 receives an instruction from the AMF via the transceiver 1325 to determine a location estimate for the target UE using the RAT dependent positioning instruction, estimates a location of the target UE using the RAT dependent positioning instruction, and sends a response message to the AMF via the transceiver 1325 including the estimated location of the target UE, a location service identifier, the positioning method used to estimate the location, and a timestamp of the location estimate.

[0185] 14 is a flowchart diagram of a method 1400 for NTN-based UE location verification. Method 1400 may be performed by a network entity as described herein, e.g., a gNB, a base station 121, a network function (e.g., an AMF or LMF), and / or a network equipment device 1300. In some embodiments, method 1400 may be performed by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0186] In one embodiment, method 1400 begins by transmitting 1405 a RAT-independent location information request. In one embodiment, method 1400 receives 1410 RAT-independent location information for the target UE corresponding to the transmitted location information request. In one embodiment, method 1400 triggers 1415 a location server to determine a location estimate for the target UE using the RAT-dependent positioning indication. In one embodiment, method 1400 receives 1420 a location estimate based on the RAT-dependent positioning indication. In one embodiment, method 1400 performs 1425 a validation of the received RAT-independent target UE location against the RAT-dependent UE location estimate, and method 1400 ends.

[0187] 15 is a flowchart diagram of a method 1500 for NTN-based UE location verification. Method 1500 may be performed by a network entity as described herein, e.g., a gNB, a base station 121, a network function (e.g., an AMF or LMF), and / or a network equipment device 1300. In some embodiments, method 1500 may be performed by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0188] In one embodiment, method 1500 begins by receiving an instruction from an AMF to determine a location estimate for a target UE using a RAT dependent positioning instruction (1505). In one embodiment, method 1500 estimates a location of the target UE using the RAT dependent positioning instruction (1510). In one embodiment, method 1500 sends a response message to the AMF that includes the estimated location of the target UE, a location service identifier, the positioning method used to estimate the location, and a timestamp of the location estimate (1515), and method 1500 ends.

[0189] A first apparatus for NTN-based UE location verification is disclosed. The first apparatus may include a network entity as described herein, e.g., a gNB, a base station 121, a network function (e.g., an AMF or an LMF), and / or a network equipment device 1300. In some embodiments, the first apparatus includes a processor that executes program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0190] In one embodiment, a first apparatus includes a transceiver and a processor coupled to the transceiver. In one embodiment, the processor is configured to cause the apparatus to: transmit a RAT-independent location information request, the request including a location configuration for an NG-RAN node; receive RAT-independent location information for a target UE corresponding to the transmitted location information request, the RAT-independent location information including a location estimate for the target UE; trigger a location server to determine a location estimate for the target UE using a RAT-dependent positioning indication; receive the location estimate based on the RAT-dependent positioning indication; and perform validation of the received RAT-independent target UE location against the RAT-dependent UE location estimate.

[0191] In one embodiment, the processor is configured to cause the device to initiate a location request to an NG-RAN node and a location request to a location server simultaneously or sequentially.

[0192] In one embodiment, the NG-RAN location configuration includes a request for the UE location based on the configured RAT independent positioning information.

[0193] In one embodiment, the RAT independent positioning information includes at least one selected from the group of GNSS positioning information, Bluetooth positioning information, WLAN positioning information, IMU sensor information, altitude information, direction or orientation information, speed estimate information, accuracy information, or a combination thereof.

[0194] In one embodiment, the processor is configured to cause the apparatus to trigger the NG-RAN node to report the target UE location information.

[0195] In one embodiment, location reporting by an NG-RAN node may be based on at least one selected from the group including single reporting, periodic reporting, event-based reporting, aperiodic reporting, or a combination thereof.

[0196] In one embodiment, a location report by an NG-RAN node includes multiple locations, each of the multiple locations associated with a timestamp and a location estimate quality indicator.

[0197] In one embodiment, the location report includes an error message in response to the UE's location being unavailable.

[0198] In one embodiment, verifying and reporting target UE location is supported for NTN multi-connectivity scenarios including transparent payload connectivity option, regenerative payload connectivity option, terrestrial-based connectivity option, and non-terrestrial-based connectivity option.

[0199] In one embodiment, the network entity comprises an AMF.

[0200] A first method for NTN-based UE location verification is disclosed. The first method may include a network entity as described herein, e.g., a gNB, a base station 121, a network function (e.g., an AMF or an LMF), and / or a network equipment device 1300. In some embodiments, the first method may be implemented by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0201] In one embodiment, the first method includes the steps of: sending a RAT-independent location information request, the request including a location configuration for an NG-RAN node; receiving RAT-independent location information of a target UE corresponding to the sent location information request, the RAT-independent location information including a location estimate of the target UE; triggering a location server to determine a location estimate of the target UE using a RAT-dependent positioning indication; receiving the location estimate based on the RAT-dependent positioning indication; and performing validation of the received RAT-independent target UE location against the RAT-dependent UE location estimate.

[0202] In one embodiment, the first method includes initiating a location request to an NG-RAN node and a location request to a location server simultaneously or sequentially.

[0203] In one embodiment, the NG-RAN location configuration includes a request for the UE location based on the configured RAT independent positioning information.

[0204] In one embodiment, the RAT independent positioning information includes at least one selected from the group of GNSS positioning information, Bluetooth positioning information, WLAN positioning information, IMU sensor information, altitude information, direction or orientation information, speed estimate information, accuracy information, or a combination thereof.

[0205] In one embodiment, the first method includes triggering an NG-RAN node to report target UE location information.

[0206] In one embodiment, location reporting by an NG-RAN node may be based on at least one selected from the group including single reporting, periodic reporting, event-based reporting, aperiodic reporting, or a combination thereof.

[0207] In one embodiment, a location report by an NG-RAN node includes multiple locations, each of the multiple locations associated with a timestamp and a location estimate quality indicator.

[0208] In one embodiment, the location report includes an error message in response to the UE's location being unavailable.

[0209] In one embodiment, verifying and reporting target UE location is supported for NTN multi-connectivity scenarios including transparent payload connectivity option, regenerative payload connectivity option, terrestrial-based connectivity option, and non-terrestrial-based connectivity option.

[0210] In one embodiment, the network entity comprises an AMF.

[0211] A second device for NTN-based UE location verification is disclosed. The second device may include a network entity as described herein, such as a gNB, a base station 121, a network function (e.g., an AMF or an LMF), and / or a network equipment device 1300. In some embodiments, the second device includes a processor that executes program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0212] In one embodiment, the second apparatus includes a transceiver and a processor coupled to the transceiver. In one embodiment, the processor is configured to cause the apparatus to receive an instruction from the AMF to determine a location estimate for the target UE using a RAT dependent positioning indication, estimate a location of the target UE using the RAT dependent positioning indication, and send a response message to the AMF including the estimated location of the target UE, a location service identifier, a positioning method used to estimate the location, and a timestamp of the location estimate.

[0213] A second method for NTN-based UE location verification is disclosed. The second method may include a network entity as described herein, e.g., a gNB, a base station 121, a network function (e.g., an AMF or an LMF), and / or a network equipment device 1300. In some embodiments, the second method may be implemented by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0214] In one embodiment, the second method includes receiving an instruction from the AMF to determine a location estimate for the target UE using a RAT dependent positioning instruction; estimating a location of the target UE using the RAT dependent positioning instruction; and sending a response message to the AMF including the estimated location of the target UE, a location service identifier, a positioning method used to estimate the location, and a timestamp of the location estimate.

[0215] The embodiments may be embodied in other specific forms. The described embodiments are to be considered in all respects as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope. [Explanation of symbols]

[0216] 100 Wireless Communication System 105 Remote Unit 107 Applications 120 Radio Access Network (“RAN”) 121 Base Unit 123 Non-Terrestrial Network ("NTN") 125 Service Link 127 Feeder Link 129 satellite 130 Mobile Core Network 131 User Plane Function ("UPF") 133 AMF 135 Session Management Facility ("SMF") 137 Policy Control Function ("SMF") 139 User Data Repository (“UDR”) 139 140 Mobile Core Network 141 Location Management Function (“LMF”) 150 Packet Data Network 151 Content Server 200 NR protocol stack 201 User Plane Protocol Stack 203 Control Plane Protocol Stack 205 UE 210 RAN nodes 215 AMF 220 Physical ("PHY") Layer 225 MAC Sublayer 230 Radio Link Control ("RLC") Sublayer 235 PDCP Sublayer 240 Service Data Adaptation Protocol ("SDAP") 245 Radio Resource Control ("RRC") Sublayer 250 Non-Access Stratum ("NAS") Sublayer 300 System 305 UE 310 First gNB 315 Second gNB 320 The third gNB 325 First Resource Set ID 330 Secondary Resource Set ID 335 PRS Resources 402 NR-DL-TDOA-ProvideAssistanceData 404 IE NR-DL-TDOA-SignalMeasurementlnformation 601 UE 603 NG-RAN nodes 605 5GC Entity 701 NG-RAN 802 satellite 804 NR-Uu 806 NTN Gateway 808 gNB 810 UE 812 SRI 814 5GCN 901 Target UE 903 NG-RAN nodes 1001UE 1003 NG-RAN 1200 User Equipment Device 1205 processor 1210 memory 1215 Input Devices 1220 output device 1225 transceiver 1230 Transmitter 1235 receiver 1240 network interface 1245 Application Interface 1300 Network Device 1305 processor 1310 memory 1315 Input Devices 1320 output device 1325 transceiver 1330 Transmitter 1335 receiver 1340 Network Interface 1345 Application Interface

Claims

1. A network entity device, A transceiver; a processor coupled to the transceiver, the processor causing the apparatus to: transmitting a radio access technology ("RAT") independent location information request, the request including location configuration for a new generation radio access network ("NG-RAN") node; receiving RAT-independent location information of a target user equipment (“UE”) corresponding to the transmitted location information request, the RAT-independent location information including a location estimate of the target UE; triggering a location server to determine a location estimate of the target UE using a RAT dependent positioning indication; receiving the location estimate based on the RAT dependent positioning indication; performing verification of the received RAT-independent target UE location against the RAT-dependent UE location estimate.

2. 10. The apparatus of claim 1, wherein the processor is configured to cause the apparatus to simultaneously or sequentially initiate a location request to the NG-RAN node and a location request to the location server.

3. 3. The apparatus of claim 1, wherein the NG-RAN location configuration includes a request for a UE location based on configured RAT-independent positioning information.

4. 4. The apparatus of claim 3, wherein the RAT-independent positioning information includes at least one selected from the group of Global Navigation Satellite System ("GNSS") positioning information, Bluetooth positioning information, Wireless Local Network ("WLAN") positioning information, Inertial Measurement Unit ("IMU") sensor information, altitude information, direction or orientation information, speed estimate information, accuracy information, or combinations thereof.

5. 5. The apparatus of claim 1, wherein the processor is configured to cause the apparatus to trigger the NG-RAN node to report the target UE location information.

6. 6. The apparatus of claim 5, wherein the location reporting by the NG-RAN node may be based on at least one selected from the group including a single report, a periodic report, an event-based report, an aperiodic report, or a combination thereof.

7. 7. The apparatus of claim 5 or 6, wherein the location report by the NG-RAN node includes a plurality of locations, each of the plurality of locations being associated with a timestamp and a location estimate quality indicator.

8. 8. The apparatus of claim 5, 6, or 7, wherein the location report includes an error message in response to the UE's location being unavailable.

9. 9. The apparatus of claim 5, wherein the verifying and reporting of the target UE location is supported for non-terrestrial ("NTN") multi-connectivity scenarios, including a transparent payload connectivity option, a regenerative payload connectivity option, a terrestrial connectivity option, and a non-terrestrial connectivity option.

10. The apparatus of claim 1 , wherein the network entity comprises an Access and Mobility Management Function (“AMF”).

11. A method for a network entity device, comprising: sending a radio access technology ("RAT") independent location information request, said request including location configuration for a new generation radio access network ("NG-RAN") node; receiving RAT-independent location information of a target user equipment (“UE”) corresponding to the transmitted location information request, the RAT-independent location information including a location estimate of the target UE; triggering a location server to determine a location estimate of the target UE using a RAT dependent positioning indication; receiving the location estimate based on the RAT dependent positioning indication; and performing a validation of the received RAT-independent target UE location against the RAT-dependent UE location estimate.

12. 12. The method of claim 11, further comprising initiating a location request to the NG-RAN node and a location request to the location server simultaneously or sequentially.

13. 13. The method of claim 11 or 12, wherein the NG-RAN location configuration includes a request for a UE location based on configured RAT-independent positioning information.

14. 14. The method of claim 13, wherein the RAT-independent positioning information includes at least one selected from the group of Global Navigation Satellite System ("GNSS") positioning information, Bluetooth positioning information, Wireless Local Network ("WLAN") positioning information, Inertial Measurement Unit ("IMU") sensor information, altitude information, direction or orientation information, speed estimate information, accuracy information, or combinations thereof.

15. A network entity device, A transceiver; a processor coupled to the transceiver, the processor causing the apparatus to: receiving instructions from an Access and Mobility Management Function (“AMF”) to determine a location estimate for a target user equipment (“UE”) using a Radio Access Technology (“RAT”) dependent positioning instruction; estimating a location of the target UE using the RAT dependent positioning indication; 4. The apparatus configured to cause the AMF to send a response message including the estimated location of the target UE, a location service identifier, a positioning method used to estimate the location, and a timestamp of the location estimate.

Images