Patent Description:
The subject matter disclosed herein relates generally to wireless communications and more particularly relates to ultra-wideband measurements for radio access technology-independent positioning. In particular, there is disclosed herein a user equipment, a processor, a method performed by a user equipment, and a location sever device apparatus.

In certain wireless communication systems, <NUM> Location Services ("LCS") are inherently part of the 3GPP Architecture and radio access network ("RAN") framework to enable the identification and standardized reporting of a UE's or a group of UEs location information based on the supported RAT-dependent and RAT-independent measurements. The current issue within the 3GPP framework is the lack of support for enabling high accuracy positioning and/or ranging using ultra-wideband ("UWB") signal measurements at the network-side (e.g., UE-assisted) and/or UE-side (e.g., UE-based) positioning.

Disclosed are procedures for ultra-wideband measurements for radio access technology-independent positioning. The procedures may be implemented by apparatus, systems, methods, or computer program products. Claim <NUM> defines a user equipment, claim <NUM> defines a processor, claim <NUM> defines a method performed by a user equipment, and claim <NUM> defines a location sever device apparatus.

In one embodiment, a user equipment (UE) for wireless communication comprises a processor arranged to cause the UE to transmit, to a location server of a mobile wireless communication network, a set of capabilities related to ultra-wideband ("UWB") positioning for the UE in response to a request from the location server for the set of capabilities, the set of capabilities used to determine at least one UWB positioning method for performing UWB positioning of the UE device. The UE receives, from the location server, UWB assistance data to perform UWB positioning in response to a request for the assistance information, the assistance information comprising the at least one UWB positioning method for performing UWB positioning. The UE transmits, to the location server, a UWB measurement and location information report for the UE device using the at least one UWB positioning method associated with at least one of a set of timing-based and a set of angular-based UWB measurements in response to a request from the location server for the UWB measurement and location information. The UE determines information for potential causes of error for one or more of a UWB configuration and a position estimate for the UE device. The UE transmits, to the location server, the determined information for the potential causes of error. The UE receives, from the location server, UWB-specific error information associated with one or more of the UWB configuration and the position estimate information for correcting the determined potential causes of error.

In one embodiment, a first method includes transmitting, to a location server of a mobile wireless communication network, a set of capabilities related to ultra-wideband ("UWB") positioning for the UE device in response to a request from the location server for the set of capabilities, the set of capabilities used to determine at least one UWB positioning method for performing UWB positioning of the UE device. The first method includes receiving, from the location server, UWB assistance data to perform UWB positioning in response to a request for the assistance information, the assistance information comprising the at least one UWB positioning method for performing UWB positioning. The first method includes transmitting, to the location server, a UWB measurement and location information report for the UE device using the at least one UWB positioning method associated with at least one of a set of timing-based and a set of angular-based UWB measurements in response to a request from the location server for the UWB measurement and location information. The first method includes determining information for potential causes of error for one or more of a UWB configuration and a position estimate for the UE device. The transceiver transmits, to the location server, the determined information for the potential causes of error. The first method includes receiving, from the location server, UWB-specific error information associated with one or more of the UWB configuration and the position estimate information for correcting the determined potential causes of error.

In one embodiment, a location server device apparatus for wireless communication receives, from a user equipment ("UE"), a set of capabilities related to ultra-wideband ("UWB") positioning for the UE device in response to a request for the set of capabilities, the set of capabilities used to determine at least one UWB positioning method for performing UWB positioning of the UE device. In one embodiment, the transceiver transmits, to the user equipment ("UE") device, UWB assistance data to perform UWB positioning in response to a request for the assistance information, the assistance information comprising the at least one UWB positioning method for performing UWB positioning. The location server device receives, from the UE device, a UWB measurement and location information report for the UE device using the at least one UWB positioning method associated with at least one of a set of timing-based and a set of angular-based UWB measurements in response to a request from the location server for the UWB measurement and location information. The location server device receives, from the UE device, information describing potential causes of error for one or more of a UWB configuration and a position estimate for the UE device. The location server device transmits, to the UE device, UWB-specific error information associated with one or more of the UWB configuration and the position estimate information for correcting the determined potential causes of error.

Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN"), wireless LAN ("WLAN"), or a wide area network ("WAN"), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider ("ISP")).

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.

Generally, the present disclosure describes systems, methods, and apparatuses for ultra-wideband measurements for radio access technology-independent positioning. In certain embodiments, the methods may be performed using computer code embedded on a computer-readable medium. In certain embodiments, an apparatus or system may include a computer-readable medium containing computer-readable code which, when executed by a processor, causes the apparatus or system to perform at least a portion of the below described solutions.

<NUM> LCS are inherently part of the 3GPP Architecture and RAN framework to enable the identification and standardized reporting of a UE's or a group of UEs location information based on the supported RAT-dependent and RAT-independent measurements. The current issue within the 3GPP framework is the lack of support for enabling high accuracy positioning and/or ranging using UWB signal measurements at the network-side (e.g., UE-assisted) and/or UE-side (e.g., UE-based) positioning.

UWB has been extensively studied and implemented in commercial products for several years, and it has always been regarded as a well-established wireless technology for high accuracy positioning and tracking for indoor/short range scenarios. UWB has the potential to impact several vertical use cases such as public safety, commercial, automotive, and IIoT scenarios. UWB technology has also been standardized in <NUM>. 4z (HRP-UWB and LRP-UWB) and IEEE <NUM>. <NUM> (wireless body area networks).

The current 3GPP (new radio ("NR") and long-term evolution ("LTE")) design lacks the necessary support for enabling and exploiting RAT-independent UWB-based measurements for enhanced 3GPP UE-assisted, UE-based, or SL-based positioning. This provides an additional degree of freedom for hybrid positioning methods involving RAT-independent and RAT-dependent positioning techniques. The present disclosure aims to address this key open issue by providing the necessary signaling support for the location management function ("LMF"), gNB, and UE nodes for performing the required UWB positioning procedures and location estimation along the Uu and SL (e.g., PC5) interface.

In this disclosure, solutions are presented for supporting UWB measurements to complement the RAT-independent positioning framework. The solution proposes the supported UWB positioning methods, UE positioning modes, and types of UWB measurements to be exchanged between the target-UE and the location server, e.g., LMF. This use of UWB RAT-independent positioning provides an additional degree of freedom for the use of hybrid positioning technologies within the 3GPP positioning framework. UWB RAT-independent positioning can also be flexibly performed along with other SL positioning methods.

<FIG> depicts a wireless communication system <NUM> for ultra-wideband measurements for radio access technology-independent positioning, according to embodiments of the disclosure. In one embodiment, the wireless communication system <NUM> includes at least one remote unit <NUM>, a radio access network ("RAN") <NUM>, and a mobile core network <NUM>. The RAN <NUM> and the mobile core network <NUM> form a mobile communication network. The RAN <NUM> may be composed of a base unit <NUM> with which the remote unit <NUM> communicates using wireless communication links <NUM>. Even though a specific number of remote units <NUM>, base units <NUM>, wireless communication links <NUM>, RANs <NUM>, and mobile core networks <NUM> are depicted in <FIG>, one of skill in the art will recognize that any number of remote units <NUM>, base units <NUM>, wireless communication links <NUM>, RANs <NUM>, and mobile core networks <NUM> may be included in the wireless communication system <NUM>.

In one implementation, the RAN <NUM> is compliant with the <NUM> system specified in the Third Generation Partnership Project ("3GPP") specifications. For example, the RAN <NUM> may be a Next Generation Radio Access Network ("NG-RAN"), implementing New Radio ("NR") Radio Access Technology ("RAT") and/or Long-Term Evolution ("LTE") RAT. In another example, the RAN <NUM> may include non-3GPP RAT (e.g., Wi-Fi® or Institute of Electrical and Electronics Engineers ("IEEE") <NUM>-family compliant WLAN). In another implementation, the RAN <NUM> is compliant with the LTE system specified in the 3GPP specifications. More generally, however, the wireless communication system <NUM> may implement some other open or proprietary communication network, for example Worldwide Interoperability for Microwave Access ("WiMAX") or IEEE <NUM>-family standards, among other networks.

In one embodiment, the remote units <NUM> may include computing devices, such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. Moreover, the remote units <NUM> may be referred to as the UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit ("WTRU"), a device, or by other terminology used in the art. In various embodiments, the remote unit <NUM> includes a subscriber identity and/or identification module ("SIM") and the mobile equipment ("ME") providing mobile termination functions (e.g., radio transmission, handover, speech encoding and decoding, error detection and correction, signaling and access to the SIM). In certain embodiments, the remote unit <NUM> may include a terminal equipment ("TE") and/or be embedded in an appliance or device (e.g., a computing device, as described above).

The remote units <NUM> may communicate directly with one or more of the base units <NUM> in the RAN <NUM> via uplink ("UL") and downlink ("DL") communication signals. Furthermore, the UL and DL communication signals may be carried over the wireless communication links <NUM>. Here, the RAN <NUM> is an intermediate network that provides the remote units <NUM> with access to the mobile core network <NUM>. As described in greater detail below, the base unit(s) <NUM> may provide a cell operating using a first frequency range and/or a cell operating using a second frequency range.

In some embodiments, the remote units <NUM> communicate with an application server <NUM> via a network connection with the mobile core network <NUM>. For example, an application <NUM> (e.g., web browser, media client, telephone and/or Voice-over-Internet-Protocol ("VoIP") application) in a remote unit <NUM> may trigger the remote unit <NUM> to establish a protocol data unit ("PDU") session (or other data connection) with the mobile core network <NUM> via the RAN <NUM>. The mobile core network <NUM> then relays traffic between the remote unit <NUM> and the application server <NUM> in the packet data network <NUM> using the PDU session. The PDU session represents a logical connection between the remote unit <NUM> and the User Plane Function ("UPF") <NUM>.

In order to establish the PDU session (or PDN connection), the remote unit <NUM> must be registered with the mobile core network <NUM> (also referred to as "attached to the mobile core network" in the context of a Fourth Generation ("<NUM>") system). Note that the remote unit <NUM> may establish one or more PDU sessions (or other data connections) with the mobile core network <NUM>. As such, the remote unit <NUM> may have at least one PDU session for communicating with the packet data network <NUM>. The remote unit <NUM> may establish additional PDU sessions for communicating with other data networks and/or other communication peers.

In the context of a <NUM> system ("5GS"), the term "PDU Session" refers to a data connection that provides end-to-end ("E2E") user plane ("UP") connectivity between the remote unit <NUM> and a specific Data Network ("DN") through the UPF <NUM>. A PDU Session supports one or more Quality of Service ("QoS") Flows. In certain embodiments, there may be a one-to-one mapping between a QoS Flow and a QoS profile, such that all packets belonging to a specific QoS Flow have the same <NUM> QoS Identifier ("5QI").

In the context of a <NUM>/LTE system, such as the Evolved Packet System ("EPS"), a Packet Data Network ("PDN") connection (also referred to as EPS session) provides E2E UP connectivity between the remote unit and a PDN. The PDN connectivity procedure establishes an EPS Bearer, e.g., a tunnel between the remote unit <NUM> and a Packet Gateway ("PGW", not shown) in the mobile core network <NUM>. In certain embodiments, there is a one-to-one mapping between an EPS Bearer and a QoS profile, such that all packets belonging to a specific EPS Bearer have the same QoS Class Identifier ("QCI").

The base units <NUM> may be distributed over a geographic region. In certain embodiments, a base unit <NUM> may also be referred to as an access terminal, an access point, a base, a base station, a Node-B ("NB"), an Evolved Node B (abbreviated as eNodeB or "eNB," also known as Evolved Universal Terrestrial Radio Access Network ("E-UTRAN") Node B), a <NUM>/NR Node B ("gNB"), a Home Node-B, a relay node, a RAN node, or by any other terminology used in the art. The base units <NUM> are generally part of a RAN, such as the RAN <NUM>, that may include one or more controllers communicably coupled to one or more corresponding base units <NUM>. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art. The base units <NUM> connect to the mobile core network <NUM> via the RAN <NUM>.

The base units <NUM> may serve a number of remote units <NUM> within a serving area, for example, a cell or a cell sector, via a wireless communication link <NUM>. The base units <NUM> may communicate directly with one or more of the remote units <NUM> via communication signals. Generally, the base units <NUM> transmit DL communication signals to serve the remote units <NUM> in the time, frequency, and/or spatial domain. Furthermore, the DL communication signals may be carried over the wireless communication links <NUM>. The wireless communication links <NUM> may be any suitable carrier in licensed or unlicensed radio spectrum. The wireless communication links <NUM> facilitate communication between one or more of the remote units <NUM> and/or one or more of the base units <NUM>. Note that during NR operation on unlicensed spectrum (referred to as "NR-U"), the base unit <NUM> and the remote unit <NUM> communicate over unlicensed (e.g., shared) radio spectrum.

In one embodiment, the mobile core network <NUM> is a 5GC or an Evolved Packet Core ("EPC"), which may be coupled to a packet data network <NUM>, like the Internet and private data networks, among other data networks. A remote unit <NUM> may have a subscription or other account with the mobile core network <NUM>. In various embodiments, each mobile core network <NUM> belongs to a single mobile network operator ("MNO").

The mobile core network <NUM> includes several network functions ("NFs"). As depicted, the mobile core network <NUM> includes at least one UPF <NUM>. The mobile core network <NUM> also includes multiple control plane ("CP") functions including, but not limited to, an Access and Mobility Management Function ("AMF") <NUM> that serves the RAN <NUM>, a Session Management Function ("SMF") <NUM>, a Location Management Function ("LMF") <NUM>, a Unified Data Management function ("UDM"") and a User Data Repository ("UDR"). Although specific numbers and types of network functions are depicted in <FIG>, one of skill in the art will recognize that any number and type of network functions may be included in the mobile core network <NUM>.

The UPF(s) <NUM> is/are responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU session for interconnecting Data Network (DN), in the <NUM> architecture. The AMF <NUM> is responsible for termination ofNAS signaling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The SMF <NUM> is responsible for session management (e.g., session establishment, modification, release), remote unit (e.g., UE) IP address allocation & management, DL data notification, and traffic steering configuration of the UPF <NUM> for proper traffic routing.

The LMF <NUM> receives positioning measurements or estimates from RAN <NUM> and the remote unit <NUM> (e.g., via the AMF <NUM>) and computes the position of the remote unit <NUM>. The UDM is responsible for generation of Authentication and Key Agreement ("AKA") credentials, user identification handling, access authorization, subscription management. The UDR is a repository of subscriber information and may be used to service a number of network functions. For example, the UDR may store subscription data, policy-related data, subscriber-related data that is permitted to be exposed to third party applications, and the like. In some embodiments, the UDM is co-located with the UDR, depicted as combined entity "UDM/UDR" <NUM>.

In various embodiments, the mobile core network <NUM> may also include a Policy Control Function ("PCF") (which provides policy rules to CP functions), a Network Repository Function ("NRF") (which provides Network Function ("NF") service registration and discovery, enabling NFs to identify appropriate services in one another and communicate with each other over Application Programming Interfaces ("APIs")), a Network Exposure Function ("NEF") (which is responsible for making network data and resources easily accessible to customers and network partners), an Authentication Server Function ("AUSF"), or other NFs defined for the 5GC. When present, the AUSF may act as an authentication server and/or authentication proxy, thereby allowing the AMF <NUM> to authenticate a remote unit <NUM>. In certain embodiments, the mobile core network <NUM> may include an authentication, authorization, and accounting ("AAA") server.

In various embodiments, the mobile core network <NUM> supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network <NUM> optimized for a certain traffic type or communication service. For example, one or more network slices may be optimized for enhanced mobile broadband ("eMBB") service. As another example, one or more network slices may be optimized for ultra-reliable low-latency communication ("URLLC") service. In other examples, a network slice may be optimized for machine-type communication ("MTC") service, massive MTC ("mMTC") service, Internet-of-Things ("IoT") service. In yet other examples, a network slice may be deployed for a specific application service, a vertical service, a specific use case, etc..

A network slice instance may be identified by a single-network slice selection assistance information ("S-NSSAI") while a set of network slices for which the remote unit <NUM> is authorized to use is identified by network slice selection assistance information ("NSSAI"). Here, "NSSAI" refers to a vector value including one or more S-NSSAI values. In certain embodiments, the various network slices may include separate instances of network functions, such as the SMF <NUM> and UPF <NUM>. In some embodiments, the different network slices may share some common network functions, such as the AMF <NUM>. The different network slices are not shown in <FIG> for ease of illustration, but their support is assumed.

As discussed in greater detail below, the remote unit <NUM> receives a positioning measurement configuration <NUM> from the network (e.g., from the LMF <NUM> via RAN <NUM>), including a positioning processing timeline for the remote unit <NUM> based on the remote unit's capabilities. The remote unit <NUM> performs positioning measurements, as described in greater detail below, and sends a positioning report <NUM> to the LMF <NUM>.

While <FIG> depicts components of a <NUM> RAN and a <NUM> core network, the described embodiments for ultra-wideband measurements for radio access technology-independent positioning apply to other types of communication networks and RATs, including IEEE <NUM> variants, Global System for Mobile Communications ("GSM", e.g., a <NUM> digital cellular network), General Packet Radio Service ("GPRS"), Universal Mobile Telecommunications System ("UMTS"), LTE variants, CDMA <NUM>, Bluetooth, ZigBee, Sigfox, and the like.

Moreover, in an LTE variant where the mobile core network <NUM> is an EPC, the depicted 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"), and the like. For example, the AMF <NUM> may be mapped to an MME, the SMF <NUM> may be mapped to a control plane portion of a PGW and/or to an MME, the UPF <NUM> may be mapped to an SGW and a user plane portion of the PGW, the UDM/UDR <NUM> may be mapped to an HSS, etc..

In the following descriptions, the term "RAN node" is used for the base station but it is replaceable by any other radio access node, e.g., gNB, ng-eNB, eNB, Base Station ("BS"), Access Point ("AP"), etc. Further, the operations are described mainly in the context of <NUM> NR. However, the proposed solutions/methods are also equally applicable to other mobile communication systems supporting ultra-wideband measurements for radio access technology-independent positioning.

<FIG> depicts a NR protocol stack <NUM>, according to embodiments of the disclosure. While <FIG> shows the UE <NUM>, the RAN node <NUM> and an AMF <NUM> in a <NUM> core network ("5GC"), these are representative of a set of remote units <NUM> interacting with a base unit <NUM> and a mobile core network <NUM>. As depicted, the protocol stack <NUM> comprises a User Plane protocol stack <NUM> and a Control Plane protocol stack <NUM>. The User Plane protocol stack <NUM> includes a physical ("PHY") layer <NUM>, a Medium Access Control ("MAC") sublayer <NUM>, the Radio Link Control ("RLC") sublayer <NUM>, a Packet Data Convergence Protocol ("PDCP") sublayer <NUM>, and Service Data Adaptation Protocol ("SDAP") layer <NUM>. The Control Plane protocol stack <NUM> includes a physical layer <NUM>, a MAC sublayer <NUM>, a RLC sublayer <NUM>, and a PDCP sublayer <NUM>. The Control Plane protocol stack <NUM> also includes a Radio Resource Control ("RRC") layer <NUM> and a Non-Access Stratum ("NAS") layer <NUM>.

The AS layer (also referred to as "AS protocol stack") for the User Plane protocol stack <NUM> consists of at least SDAP, PDCP, RLC and MAC sublayers, and the physical layer. The AS layer for the Control Plane protocol stack <NUM> consists of at least RRC, PDCP, RLC and MAC sublayers, and the physical layer. The Layer-<NUM> ("L2") is split into the SDAP, PDCP, RLC and MAC sublayers. The Layer-<NUM> ("L3") includes the RRC sublayer <NUM> and the NAS layer <NUM> for the control plane and includes, e.g., an Internet Protocol ("IP") layer and/or PDU Layer (not depicted) for the user plane. L1 and L2 are referred to as "lower layers," while L3 and above (e.g., transport layer, application layer) are referred to as "higher layers" or "upper layers.

The physical layer <NUM> offers transport channels to the MAC sublayer <NUM>. The physical layer <NUM> may perform a Clear Channel Assessment and/or Listen-Before-Talk ("CCA/LBT") procedure using energy detection thresholds, as described herein. In certain embodiments, the physical layer <NUM> may send a notification of UL Listen-Before-Talk ("LBT") failure to a MAC entity at the MAC sublayer <NUM>. The MAC sublayer <NUM> offers logical channels to the RLC sublayer <NUM>. The RLC sublayer <NUM> offers RLC channels to the PDCP sublayer <NUM>. The PDCP sublayer <NUM> offers radio bearers to the SDAP sublayer <NUM> and/or RRC layer <NUM>. The SDAP sublayer <NUM> offers QoS flows to the core network (e.g., 5GC). The RRC layer <NUM> provides for the addition, modification, and release of Carrier Aggregation and/or Dual Connectivity. The RRC layer <NUM> also manages the establishment, configuration, maintenance, and release of Signaling Radio Bearers ("SRBs") and Data Radio Bearers ("DRBs").

The NAS layer <NUM> is between the UE <NUM> and the 5GC <NUM>. NAS messages are passed transparently through the RAN. The NAS layer <NUM> is used to manage the establishment of communication sessions and for maintaining continuous communications with the UE <NUM> as it moves between different cells of the RAN. In contrast, the AS layer is between the UE <NUM> and the RAN (e.g., RAN node <NUM>) and carries information over the wireless portion of the network.

As background, for Release <NUM> ("Rel-<NUM>") of the 3GPP specification, the different positioning requirements are especially stringent with respect to accuracy, latency, and reliability. Table <NUM> shows positioning performance requirements for different scenarios in an Industrial IoT ("IIoT") or indoor factory setting.

Some UE positioning method supported in Rel-<NUM> are listed in Table <NUM>. The separate positioning techniques as indicated in Table <NUM> may be currently configured and performed based on the requirements of the LMF and/or UE capabilities. Note that Table <NUM> includes TBS positioning based on PRS signals, but only OTDOA based on LTE signals is supported. The E-CID includes Cell-ID for NR method. The Terrestrial Beacon System ("TBS") method refers to TBS positioning based on Metropolitan Beacon System ("MBS") signals.

Regarding the LCS architecture, to support positioning of a target UE and delivery of location assistance data to a UE with NG-RAN access in 5GS, location related functions are distributed as shown in the architecture in TS <NUM> and as clarified in greater detail in TS <NUM> and TS <NUM>. The overall sequence of events applicable to the UE, NG-RAN and LMF for any location service is shown in <FIG>.

Note that when the AMF <NUM> receives a Location Service Request in case of the UE <NUM> is in CM-IDLE state, the AMF <NUM> performs a network triggered service request as defined in TS <NUM> and TS <NUM> in order to establish a signaling connection with the UE <NUM> and assign a specific serving gNB or ng-eNB. The UE <NUM> is assumed to be in connected mode before the beginning of the flow shown in the <FIG>; that is, any signaling that might be required to bring the UE <NUM> to connected mode prior to step 1a is not shown. The signaling connection may, however, be later released (e.g., by the NG-RAN <NUM> node as a result of signaling and data inactivity) while positioning is still ongoing.

In step 1a, in one embodiment, some entity in the 5GC <NUM> (e.g., GMLC) requests (see messaging <NUM>) some location service (e.g., positioning) for a target UE <NUM> to the serving AMF <NUM>. In step 1b, in one embodiment, the serving AMF <NUM> for a target UE <NUM> determines (see block <NUM>) the need for some location service (e.g., to locate the UE <NUM> for an emergency call). In step 1c, in one embodiment, the UE <NUM> requests (see messaging <NUM>) some location service (e.g., positioning or delivery of assistance data) to the serving AMF <NUM> at the NAS level.

At step <NUM>, in one embodiment, the AMF <NUM> transfers (see messaging <NUM>) the location service request to an LMF <NUM>. In step 3a, in one embodiment, the LMF <NUM> instigates location procedures (see block <NUM>) with the serving and possibly neighboring ng-eNB or gNB in the NG-RAN <NUM>, e.g., to obtain positioning measurements or assistance data.

At step 3b, in one embodiment, in addition to step 3a or instead of step 3a, the LMF <NUM> instigates location procedures (see block <NUM>) with the UE <NUM>, e.g., to obtain a location estimate or positioning measurements or to transfer location assistance data to the UE <NUM>.

At step <NUM>, in one embodiment, the LMF <NUM> provides (see messaging <NUM>) a location service response to the AMF <NUM> and includes any needed results, e.g., success or failure indication and, if requested and obtained, a location estimate for the UE.

At step 5a, in one embodiment, if step 1a was performed, the AMF <NUM> returns a location service response (see messaging <NUM>) to the 5GC entity <NUM> in step 1a and includes any needed results, e.g., a location estimate for the UE <NUM>.

At step 5b, in one embodiment, if step 1b occurred, the AMF <NUM> uses the location service response (see block <NUM>) received in step <NUM> to assist the service that triggered this in step 1b (e.g., may provide a location estimate associated with an emergency call to a GMLC).

At step 5c, in one embodiment, if step 1c was performed, the AMF <NUM> returns (see messaging <NUM>) a location service response to the UE <NUM> and includes any needed results, e.g., a location estimate for the UE <NUM>.

Location procedures applicable to NG-RAN occur in steps 3a and 3b in <FIG> and are defined in greater detail in this specification. Other steps in <FIG> are applicable only to the 5GC and are described in greater detail and in TS <NUM> and TS <NUM>.

Steps 3a and 3b can involve the use of different position methods to obtain location related measurements for a target UE and from these compute a location estimate and possibly additional information like velocity. The case that the NG-RAN node functions as an LCS client is not supported in this version of the specification.

In one embodiment, the following RAT-dependent positioning techniques may be supported by the system <NUM>:.

DL-TDoA: The DL TDOA positioning method makes use of the DL RS Time Difference ("RSTD") (and optionally DL PRS RS Received Power ("RSRP") of DL PRS RS Received Quality ("RSRQ")) of downlink signals received from multiple TPs, at the UE (e.g., remote unit <NUM>). The UE measures the DL RSTD (and optionally DL PRS RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE in relation to the neighboring Transmission Points ("TPs").

DL-AoD: The DL Angle of Departure ("AoD") positioning method makes use of the measured DL PRS RSRP of downlink signals received from multiple TPs, at the UE. The UE measures the DL PRS RSRP of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to locate the UE in relation to the neighboring TPs.

Multi-RTT: The Multiple-Round Trip Time ("Multi-RTT") positioning method makes use of the UE Receive-Transmit ("Rx-Tx") measurements and DL PRS RSRP of downlink signals received from multiple TRPs, measured by the UE and the gNB Rx-Tx measurements (e.g., measured by RAN node) and UL SRS-RSRP at multiple TRPs of uplink signals transmitted from UE.

The UE measures the UE Rx-Tx measurements (and optionally DL PRS RSRP of the received signals) using assistance data received from the positioning server, and the TRPs measure the gNB Rx-Tx measurements (and optionally UL SRS-RSRP of the received signals) using assistance data received from the positioning server. The measurements are used to determine the Round Trip Time ("RTT") at the positioning server which are used to estimate the location of the UE.

E-CID/ NR E-CID: Enhanced Cell ID (CID) positioning method, the position of a UE is estimated with the knowledge of its serving ng-eNB, gNB and cell and is based on LTE signals. The information about the serving ng-eNB, gNB and cell may be obtained by paging, registration, or other methods. NR Enhanced Cell ID (NR E CID) positioning refers to techniques which use additional UE measurements and/or NR radio resource and other measurements to improve the UE location estimate using NR signals.

Although NR E-CID positioning may utilize some of the same measurements as the measurement control system in the RRC protocol, the UE generally is not expected to make additional measurements for the sole purpose of positioning; e.g., the positioning procedures do not supply a measurement configuration or measurement control message, and the UE reports the measurements that it has available rather than being required to take additional measurement actions.

UL-TDoA: The UL TDOA positioning method makes use of the UL TDOA (and optionally UL SRS-RSRP) at multiple RPs of uplink signals transmitted from the UE. The RPs measure the UL TDOA (and optionally UL SRS-RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the location of the UE.

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

<FIG> depicts a system <NUM> for NR beam-based positioning. According to Rel-<NUM>, the PRS can be transmitted by different base stations (serving and neighboring) using narrow beams over Frequency Range #<NUM> Between ("FR1", e.g., frequencies from <NUM> to <NUM>) and Frequency Range #<NUM> ("FR2", e.g., frequencies from <NUM> to <NUM>), which is relatively different when compared to LTE where the PRS was transmitted across the whole cell.

As illustrated in <FIG>, a UE <NUM> may receive PRS from a first gNB ("gNB <NUM>") <NUM>, which is a serving gNB, and also from a neighboring second gNB ("gNB <NUM>") <NUM>, and a neighboring third gNB ("gNB <NUM>") <NUM>. Here, the PRS can be locally associated with a set of PRS Resources grouped under a Resource Set ID for a base station (e.g., TRP). In the depicted embodiments, each gNB <NUM>, <NUM>, <NUM> is configured with a first Resource Set ID <NUM> and a second Resource Set ID <NUM>. As depicted, the UE <NUM> receives PRS on transmission beams; here, receiving PRS from the gNB <NUM><NUM> on a set of PRS Resources <NUM> from the second Resource Set ID <NUM>, receiving PRS from the gNB <NUM><NUM> on a set of PRS Resources <NUM> from the second Resource Set ID <NUM>, and receiving PRS from the gNB <NUM><NUM> on a set of PRS Resources <NUM> from the first Resource Set ID <NUM>.

Similarly, UE positioning measurements such as Reference Signal Time Difference ("RSTD") and PRS RSRP measurements are made between beams as opposed to different cells as was the case in LTE. In addition, there are additional UL positioning methods for the network to exploit to compute the target UE's location. Table <NUM> lists the RS-to-measurements mapping required for each of the supported RAT-dependent positioning techniques at the UE, and Table <NUM> lists the RS-to-measurements mapping required for each of the supported RAT-dependent positioning techniques at the gNB.

RAT-dependent positioning techniques involve the 3GPP RAT and core network entities to perform the position estimation of the UE, which are differentiated from RAT-independent positioning techniques which rely on Global Navigation Satellite System ("GNSS"), Inertial Measurement Unit ("IMU") sensor, WLAN and Bluetooth technologies for performing target device (e.g., UE) positioning.

Various RAT-Independent positioning techniques may be used. For instance, in network-assisted GNSS methods, these methods make use of UEs that are equipped with radio receivers capable of receiving GNSS signals. In 3GPP specifications the term GNSS encompasses both global and regional/augmentation navigation satellite systems.

Examples of global navigation satellite systems include GPS, Modernized GPS, Galileo, GLONASS, and BeiDou Navigation Satellite System ("BDS"). Regional navigation satellite systems include Quasi Zenith Satellite System ("QZSS") while the many augmentation systems, are classified under the generic term of Space Based Augmentation Systems ("SBAS") and provide regional augmentation services. In this concept, different GNSSs (e.g., GPS, Galileo, or the like) can be used separately or in combination to determine the location of a UE.

In barometric pressure sensor positioning, the barometric pressure sensor method makes use of barometric sensors to determine the vertical component of the position of the UE. The UE measures barometric pressure, optionally aided by assistance data, to calculate the vertical component of its location or to send measurements to the positioning server for position calculation. This method should be combined with other positioning methods to determine the 3D position of the UE.

The WLAN positioning method makes use of the WLAN measurements (AP identifiers and optionally other measurements) and databases to determine the location of the UE. The UE measures received signals from WLAN access points, optionally aided by assistance data, to send measurements to the positioning server for position calculation. Using the measurement results and a references database, the location of the UE is calculated. Alternatively, the UE makes use of WLAN measurements and optionally WLAN AP assistance data provided by the positioning server, to determine its location.

The Bluetooth positioning method makes use of Bluetooth measurements (beacon identifiers and optionally other measurements) to determine the location of the UE. The UE measures received signals from Bluetooth beacons. Using the measurement results and a references database, the location of the UE is calculated. The Bluetooth methods may be combined with other positioning methods (e.g., WLAN) to improve positioning accuracy of the UE.

A Terrestrial Beacon System ("TBS"), used for positioning, consists of a network of ground-based transmitters, broadcasting signals only for positioning purposes. The current type of TBS positioning signals are the Metropolitan Beacon System ("MBS") signals and Positioning Reference Signals ("PRS") (see TS <NUM>). The UE measures received TBS signals, optionally aided by assistance data, to calculate its location or to send measurements to the positioning server for position calculation.

The motion sensor method makes use of different sensors such as accelerometers, gyros, magnetometers, to calculate the displacement of UE. The UE estimates a relative displacement based upon a reference position and/or reference time. UE sends a report comprising 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.

In one embodiment, the high-level solution of the subject matter disclosed herein provides a detailed conceptual solution for the measurement assistance configuration, positioning procedures and report signaling for performing RAT-independent positioning using the UWB capability of a UE and/or group of UEs. The following overview of embodiments including corresponding advantages are described:.

Embodiment <NUM>: Details the supported positioning modes and measurements required to be reported for performing UWB ranging/positioning including timing-based and angular-based positioning methods.

Embodiment <NUM>: Defines the information that may need to be transferred between various network entities including UE, NG-RAN and gNB to enable UWB positioning as part of the 3GPP framework. These may include the type of ranging measurements required for relative position estimation.

Embodiment <NUM>: Describes the NR positioning procedures required for enabling UWB positioning including the necessary triggers, configuration and report signalling between UE and LMF.

In one embodiment, the benefits of the solutions herein include the addition of a high-accuracy RAT-independent positioning technology such as UWB within the 3GPP framework. This enables a further degree of freedom with respect to the available positioning technology choices for a UE of perform Hybrid positioning, e.g., using a combination of RAT-dependent and RAT-independent positioning techniques. In addition, the specification of exploiting UWB measurements for high-accuracy positioning can increase the existing accuracy for computing the location estimate using 3GPP entities (e.g., UE or LMF), especially in short range indoor environments.

The present embodiments describe the details to include UWB-based positioning in the current 3GPP positioning framework as well as corresponding enhancements. In addition, Embodiments <NUM>-<NUM> can be implemented in combination with each other to achieve an improved location accuracy estimate using UWB positioning techniques using the Uu and PC5 interface.

In the first embodiment, directed to supported NR Positioning modes based on UWB measurements and location information, the target-UE may also be supported and signaled with the following positioning modes in relation to UWB RAT-independent positioning/ranging using network assistance (Uu interface) and/or sidelink assistance (PC5 interface):.

The location server or base station equipped with a Location Measurement Unit ("LMU") may signal the positioning modes using LPP/RRC/MAC CE signaling. In another implementation, if the target-UE is the source of the location information trigger, the UE may indicate the employed or desired positioning mode via LPP/RRC to the location server or base station equipped with an LMU. It should be noted that the proposed UWB RAT-independent positioning method may be used in at least one or more combinations of either, RAT-dependent positioning methods as listed in Table <NUM> and Table <NUM>, or other RAT-independent positioning methods listed above, to improve the overall location and tracking accuracy of the target-UE as part of a hybrid positioning method. This hybrid positioning method may be triggered at the target-UE or location server and corresponding information regarding the employed positioning methods may be signaled to the corresponding node, e.g., location server, base station, or target-UE. This can be applicable to positioning methods along the Uu and SL interface.

The UWB ranging and localization components normally comprises of an anchor (fixed unit with a known location), tags (devices to be localized, may be stationary or mobile) and a location engine and/or server, which may be co-located or be based in the cloud. In addition, positioning may occur between two entities (tags or UEs) in a peer-to-peer fashion, without assistance from an anchor/access point/gNB. Table <NUM> indicates the exemplary supported positioning methods that enable ranging between a UWB transmitter ("TX") and receiver ("RX"). These type of positioning techniques can be signaled to the location server, e.g., LMF in addition to the computed UE's location using UWB or a hybrid positioning technique involving UWB localization.

The positioning capabilities include support for absolute and relative positioning. The UE UWB measurements that may be exchanged with the network may broadly relate to supporting the following positioning techniques:.

An anchor node may also refer to either a UWB access point, distributed gNB with UWB functionality or a UE. The above positioning methods may be applicable to the previously listed positioning modes. A combination of two or positioning techniques may also be applicable, e.g., TWR together with Phase difference of Arrival may be used to obtain a location estimate in 3D space.

The key measurements for UWB ranging are performed with respect to the transmitted and response frame. For example, the transmitted may include control message frame or data frame while the response frame may include an ACK/NACK frame or a measurement report frame. The aforementioned mentioned measurement report frame is referred to as the RFRAME.

Therefore, a crucial aspect to enhance the NR RAT-independent positioning framework is the accurate time stamps with respect to the transmitted and response frame. This will enable accurate ToA/ToF determination. Therefore, the TX and RX each capture timestamp report which can be shared within the NR positioning framework to entities such as the LMF or UE.

In one embodiment related to UWB exchange between 3GPP entities, the UE and LMF may exchange assistance data information related to UWB positioning depending on the capabilities at each of these entities. This is applicable for both UE-based and UE-assisted positioning. Exemplary assistance data that may be transferred from LMF to UE may include information related to the anchor nodes/beacons as seen in Table <NUM>.

The location server, e.g., LMF can provide a UWB Anchor/Beacon list, which consists of all available anchor nodes in the vicinity of the target-UE to be localized including any associated identifiers differentiating the anchor nodes and corresponding channel frequency assignments. In addition, the UWB Secure Service ("USS") ID can also be shared (if available) with the target-UE since it provides secure routing feature for higher layers. In order to enable the timing-based localization methods, the location information of anchor nodes/beacons can also be provided to the target-UE.

The information provided to the LMF for UWB RAT-independent target-UE positioning can be further divided into three cases based on the operating positioning mode employed by the target-UE with UWB capabilities: <NUM>) UE-assisted, <NUM>) UE-Based, and <NUM>) Standalone positioning. Table <NUM> is a breakdown of the information that may be signaled to the LMF from the target-UE via LPP/positioning-based protocol based on the supported aforementioned positioning modes and a required to UWB positioning as per the secure ranging standard. An alternate implementation may include support for SL-based positioning modes for UWB RAT-independent positioning, which can be further divided into SL UE-assisted and SL UE-based positioning modes as noted in Table <NUM>.

In Table <NUM>, the following are defined:.

It can also be noted that the above parameters can be measured with respect to STS-ranging (scrambled time sequence) ranging and can be also signaled to the location server, if supported (enhanced ranging device ("ERDEV") or simply ranging device ("RDEV"). In an alternative implementation, the parameters in Table <NUM> may be signaled to a serving base station equipped with an LMU (location management functionality) using RRC/MAC CE signaling.

In the case of UE-Based/Standalone RAT-independent UWB positioning, the location information comprising of the position estimate/velocity estimates may also be transmitted to the location server.

In one embodiment related to NR positioning Procedures enabling UWB positioning, the required procedures for enabling RAT-independent positioning using UWB measurements and can be summarized with the following <NUM> key signaling procedures:.

These messages can be signaled via LPP signaling in coordination with the location server. In an alternate implementation where the gNB has location computation and processing capabilities, the aforementioned procedures may be signaled using RRC/MAC CE signaling.

Regarding UWB Request and Provide Assistance Data, in <FIG>, the signaling message UWB-RequestAssistanceData is used by the target device (e.g., UE <NUM>) to request (see messaging <NUM>) UWB assistance data from a location server such as the LMF <NUM>, while the exemplary message, UWB-ProvideAssistanceData, may be used by the location server <NUM> to provide (see messaging <NUM>) UWB assistance data to enable UE-based or UE-assisted UWB positioning.

This would be referred to as UE-initiated UWB assistance data transfer, while in the case of LMF-initiated UWB assistance data transfer, only Step <NUM> of <FIG> would be applicable. The UE <NUM> may determine the type of UWB assistance data it may require and indicate this via the exemplary UWB-RequestAssistanceData message. It may also be used to provide specific error messages in the case of any misconfiguration related to the UWB positioning system.

The assistance data may be transferred to the UE <NUM> in a single message, while alternate implementations may allow the assistance data message to be segmented into several messages. This may occur if the message size exceeds the allowable limit for transfer in a single message.

In an alternate implementation, the UWB assistance data may be further broadcasted to target-UEs as part of positioning system information blocks (posSIBs) upon request (on-demand posSIB request) or triggered by the LMF <NUM> and gNB.

In addition, Step <NUM> of <FIG>, can also contain the supported channel frequency assignments where a particular UWB positioning method is supported depending on if HRP-UWB or LRP-UWB is configured. Table <NUM> shows an exemplary list of the different UWB channel assignments, which can be signaled to the UE:.

Furthermore, the UWB assistance data may include location information of the various anchor nodes/beacons in a given geographic area in which the target-UE is to be absolutely or relatively localized. The location information may include latitude and longitude points and corresponding uncertainty points, e.g., as defined in TS <NUM>.

In one embodiment regarding UWB Request and Provide Location Information, as shown in <FIG>, a message, e.g. UWB-RequestLocationlnformation is used by the location server <NUM> to request (see messaging <NUM>) UWB measurements/location estimate from a target-UE <NUM> or a set of target-UEs, while an exemplary signaling message such as UWB-ProvideLocationlnformation is used by the target device <NUM> to provide (see messaging <NUM>) measurements or location information for one or more UWB anchor nodes with the associated UWB channels to the location server.

Such location information may comprise absolute and relative location data, latitude points, longitude points, horizontal and vertical velocity estimates, positioning and velocity uncertainty values, positioning error, heading information, 3D location estimates including elevation information, integrity of positioning estimates and quality of positioning estimate metrics. It may also provide some relative location measurements with respect to other target-UEs <NUM>. Additionally, the utilized positioning methods may also be signaled to the LMF <NUM> together with the UWB measurements as indicated in Table <NUM>. The target-UE <NUM> may also provide the necessary accuracy and integrity information to the LMF <NUM>. It may also be used to provide error-specific messages in the case of any misconfiguration related to the UWB positioning system. The location server <NUM> may request the UWB-related measurements from the target-UE <NUM> as denoted in Table <NUM>.

In one embodiment regarding UWB Request and Provide Capability Information, shown in <FIG>, a message, such as UWB-RequestCapabilities is used by the location server <NUM> to request (see messaging <NUM>) UWB positioning capabilities information from a target-UE <NUM>, while an exemplary message such as UWB-ProvideCapabilites is used by the target-UE <NUM> to provide (see messaging <NUM>) its UWB positioning capabilities to the location server <NUM>.

In one embodiment regarding UWB Error Indications, shown in <FIG>, in the event of any misconfigurations, lack of any UWB assistance information, uncertainties in the ranging position estimate, and/or the like, an exemplary message such as a general UWB-Error message is used by the location server <NUM> or target device <NUM> to provide (see messaging <NUM>) an indication of such error causes to the corresponding node. The type of error in addition to the originating node (target-UE <NUM> or location server <NUM>) causing the error may also be indicated the via this message. In addition, the integrity of the UWB positioning estimate may also be signaled via a separate message (see messaging <NUM>) in alternate implementations.

Here, in one embodiment, the potential error causes are from the location server side <NUM> (UWB configuration) or from the UE-side <NUM> (internal error related to any UWB measurement processing or the positioning estimate provided from the UE).

For the misconfiguration from location server <NUM> side, examples could be the unavailability of a UWB configuration, availability of a partial configuration, or an expired configuration that could result in an UWB configuration error cause.

Uncertainty information can be determined by comparing the desired location uncertainty e.g., <NUM>%, <NUM>%, <NUM>% location certainty with the current calculated location estimate and see if it meets the provided uncertainty requirements. Uncertainty described herein may be different from the positioning estimate error in the sense that the positioning estimate error is determined when there is an issue with the positioning algorithm internal to the UE <NUM>, while uncertainty assumes that the position estimate has already been calculated within some confidence intervals.

<FIG> depicts a user equipment apparatus <NUM> that may be used for ultra-wideband measurements for radio access technology-independent positioning, according to embodiments of the disclosure. In various embodiments, the user equipment apparatus <NUM> is used to implement one or more of the solutions described above. The user equipment apparatus <NUM> may be one embodiment of the remote unit <NUM> and/or the UE <NUM>, described above. Furthermore, the user equipment apparatus <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, an output device <NUM>, and a transceiver <NUM>.

In some embodiments, the input device <NUM> and the output device <NUM> are combined into a single device, such as a touchscreen. In certain embodiments, the user equipment apparatus <NUM> may not include any input device <NUM> and/or output device <NUM>. In various embodiments, the user equipment apparatus <NUM> may include one or more of: the processor <NUM>, the memory <NUM>, and the transceiver <NUM>, and may not include the input device <NUM> and/or the output device <NUM>.

As depicted, the transceiver <NUM> includes at least one transmitter <NUM> and at least one receiver <NUM>. In some embodiments, the transceiver <NUM> communicates with one or more cells (or wireless coverage areas) supported by one or more base units <NUM>. In various embodiments, the transceiver <NUM> is operable on unlicensed spectrum. Moreover, the transceiver <NUM> may include multiple UE panels supporting one or more beams. Additionally, the transceiver <NUM> may support at least one network interface <NUM> and/or application interface <NUM>. The application interface(s) <NUM> may support one or more APIs. The network interface(s) <NUM> may support 3GPP reference points, such as Uu, N1, PC5, etc. Other network interfaces <NUM> may be supported, as understood by one of ordinary skill in the art.

In various embodiments, the processor <NUM> controls the user equipment apparatus <NUM> to implement the above described UE behaviors. In certain embodiments, the processor <NUM> may include an application processor (also known as "main processor") which manages application-domain and operating system ("OS") functions and a baseband processor (also known as "baseband radio processor") which manages radio functions.

In one embodiment, the transceiver <NUM> transmits, to a location server of a mobile wireless communication network, a set of capabilities related to ultra-wideband ("UWB") positioning for the UE device in response to a request from the location server for the set of capabilities, the set of capabilities used to determine at least one UWB positioning method for performing UWB positioning of the UE device.

In one embodiment, the transceiver <NUM> receives, from the location server, UWB assistance data to perform UWB positioning in response to a request for the assistance information, the assistance information comprising the at least one UWB positioning method for performing UWB positioning. In one embodiment, the transceiver <NUM> transmits, to the location server, a UWB measurement and location information report for the UE device using the at least one UWB positioning method associated with at least one of a set of timing-based and a set of angular-based UWB measurements in response to a request from the location server for the UWB measurement and location information.

In one embodiment, the processor <NUM> determines information for potential causes of error for one or more of a UWB configuration and a position estimate for the UE device. In one embodiment, the transceiver transmits, to the location server, the determined information for the potential causes of error. In one embodiment, the transceiver <NUM> receives, from the location server, UWB-specific error information associated with one or more of the UWB configuration and the position estimate information for correcting the determined potential causes of error.

In one embodiment, the location server is one or more of part of a core network and co-located with a base station of the mobile wireless communication network. In one embodiment, the transceiver <NUM> transmits the location information to the base station equipped with a location measurement unit ("LMU") using the at least one UWB positioning method in response to a request from the base station for the location information.

In one embodiment, the UWB assistance data is received at the UE device in a dedicated manner using long-term evolution positioning protocol ("LPP") signaling in response to a request from the UE device. In one embodiment, the UWB assistance data is received at the UE device in a broadcast signal as part of positioning system information blocks ("posSIBs") triggered by one or more of the location server and a base station.

In one embodiment, the UWB assistance data is received at the UE device in a broadcast signal as part of positioning system information blocks ("posSIBs") in response to an on-demand posSIB request by the UE device. In one embodiment, the UWB assistance information comprises UWB channel assignment information, anchor node identifiers, and anchor node location information.

In one embodiment, the transceiver <NUM> indicates a type of UWB positioning method utilized to compute the location information along with the transmission of the location information comprising at least one selected from the group of two-way ranging, phase difference of arrival, and time difference of arrival.

In one embodiment, the location information comprises at least one selected from the group of: absolute and relative location data, latitude points, longitude points, horizontal and vertical velocity estimates, positioning and velocity uncertainty values, positioning error, heading information, 3D location estimates, elevation information, integrity of positioning estimates, and quality of positioning estimate metrics.

In one embodiment, the transceiver <NUM> receives a positioning mode from the location service for UWB RAT-independent positioning, the positioning mode comprising at least one selected from the group of: standalone mode, UE-assisted mode, UE-based mode, and sidelink-based positioning mode.

In one embodiment, the transceiver <NUM> transmits ranging measurements according to the received positioning mode to the location server, the supported ranging measurements comprising at least one selected from the group of timestamp, ranging counter, ranging offset, angle-of-arrival support indication, angle-of-arrival azimuth, angle-of-arrival elevation, received signal strength indicator.

In one embodiment, the processor <NUM> determines one or more of absolute and relative positioning and velocity estimates for the UE device based on the UWB positioning method. In one embodiment, the processor <NUM> enhances location and tracking accuracy of the UE device by combining the UWB positioning method at least one or more combinations of RAT-dependent positioning methods and other RAT-independent positioning methods.

In one embodiment, the transceiver <NUM> transmits an error type indication depending on if the error cause originates at the UE or location server. In one embodiment, the processor <NUM> utilizes a Uu interface between the UE device and a base station and a sidelink interface between the UE device and a peer UE device for transmitting and receiving information related to the UWB positioning method.

In some embodiments, the memory <NUM> stores data related to ultra-wideband measurements for radio access technology-independent positioning. For example, the memory <NUM> may store various parameters, panel/beam configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory <NUM> also stores program code and related data, such as an operating system or other controller algorithms operating on the apparatus <NUM>.

For example, the output device <NUM> may include, but is not limited to, a Liquid Crystal Display ("LCD"), a Light-Emitting Diode ("LED") display, an Organic LED ("OLED") display, a projector, or similar display device capable of outputting images, text, or the like to a user.

In some embodiments, all, or portions of the output device <NUM> may be integrated with the input device <NUM>.

The transceiver <NUM> communicates with one or more network functions of a mobile communication network via one or more access networks. The transceiver <NUM> operates under the control of the processor <NUM> to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor <NUM> may selectively activate the transceiver <NUM> (or portions thereof) at particular times in order to send and receive messages.

The transceiver <NUM> includes at least transmitter <NUM> and at least one receiver <NUM>. One or more transmitters <NUM> may be used to provide UL communication signals to a base unit <NUM>, such as the UL transmissions described herein. Similarly, one or more receivers <NUM> may be used to receive DL communication signals from the base unit <NUM>, as described herein. Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the user equipment apparatus <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>. Further, the transmitter(s) <NUM> and the receiver(s) <NUM> may be any suitable type of transmitters and receivers. In one embodiment, the transceiver <NUM> includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.

In various embodiments, one or more transmitters <NUM> and/or one or more receivers <NUM> may be implemented and/or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an Application-Specific Integrated Circuit ("ASIC"), or other type of hardware component. In certain embodiments, one or more transmitters <NUM> and/or one or more receivers <NUM> may be implemented and/or integrated into a multi-chip module. In some embodiments, other components such as the network interface <NUM> or other hardware components/circuits may be integrated with any number of transmitters <NUM> and/or receivers <NUM> into a single chip. In such embodiment, the transmitters <NUM> and receivers <NUM> may be logically configured as a transceiver <NUM> that uses one more common control signals or as modular transmitters <NUM> and receivers <NUM> implemented in the same hardware chip or in a multi-chip module.

<FIG> depicts a network apparatus <NUM> that may be used for ultra-wideband measurements for radio access technology-independent positioning, according to embodiments of the disclosure. In one embodiment, network apparatus <NUM> may be one implementation of a RAN node, such as the base unit <NUM> and/or the RAN node <NUM>, as described above. Furthermore, the base network apparatus <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, an output device <NUM>, and a transceiver <NUM>.

In some embodiments, the input device <NUM> and the output device <NUM> are combined into a single device, such as a touchscreen. In certain embodiments, the network apparatus <NUM> may not include any input device <NUM> and/or output device <NUM>. In various embodiments, the network apparatus <NUM> may include one or more of: the processor <NUM>, the memory <NUM>, and the transceiver <NUM>, and may not include the input device <NUM> and/or the output device <NUM>.

As depicted, the transceiver <NUM> includes at least one transmitter <NUM> and at least one receiver <NUM>. Here, the transceiver <NUM> communicates with one or more remote units <NUM>. Additionally, the transceiver <NUM> may support at least one network interface <NUM> and/or application interface <NUM>. The application interface(s) <NUM> may support one or more APIs. The network interface(s) <NUM> may support 3GPP reference points, such as Uu, N1, N2 and N3. Other network interfaces <NUM> may be supported, as understood by one of ordinary skill in the art.

For example, the processor <NUM> may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller.

In various embodiments, the network apparatus <NUM> is a RAN node (e.g., gNB) that communicates with one or more UEs, as described herein. In such embodiments, the processor <NUM> controls the network apparatus <NUM> to perform the above described RAN behaviors. When operating as a RAN node, the processor <NUM> may include an application processor (also known as "main processor") which manages application-domain and operating system ("OS") functions and a baseband processor (also known as "baseband radio processor") which manages radio functions.

In various embodiments, the processor <NUM> and transceiver <NUM> control the network apparatus <NUM> to perform the above described LMF behaviors. In one embodiment, transceiver <NUM> receives, from a user equipment ("UE") device, a set of capabilities related to ultra-wideband ("UWB") positioning for the UE device in response to a request for the set of capabilities, the set of capabilities used to determine at least one UWB positioning method for performing UWB positioning of the UE device.

In one embodiment, the transceiver <NUM> transmits, to the user equipment ("UE") device, UWB assistance data to perform UWB positioning in response to a request for the assistance information, the assistance information comprising the at least one UWB positioning method for performing UWB positioning.

In one embodiment, the transceiver <NUM> receives, from the UE device, a UWB measurement and location information report for the UE device using the at least one UWB positioning method associated with at least one of a set of timing-based and a set of angular-based UWB measurements in response to a request from the location server for the UWB measurement and location information.

In one embodiment, the transceiver <NUM> receives, from the UE device, information describing potential causes of error for one or more of a UWB configuration and a position estimate for the UE device. In one embodiment, the transceiver <NUM> transmits, to the UE device, UWB-specific error information associated with one or more of the UWB configuration and the position estimate information for correcting the determined potential causes of error.

In some embodiments, the memory <NUM> stores data related to ultra-wideband measurements for radio access technology-independent positioning. For example, the memory <NUM> may store parameters, configurations, resource assignments, policies, and the like, as described above. In certain embodiments, the memory <NUM> also stores program code and related data, such as an operating system or other controller algorithms operating on the apparatus <NUM>.

As another, non-limiting, example, the output device <NUM> may include a wearable display separate from, but communicatively coupled to, the rest of the network apparatus <NUM>, such as a smart watch, smart glasses, a heads-up display, or the like.

The transceiver <NUM> includes at least transmitter <NUM> and at least one receiver <NUM>. One or more transmitters <NUM> may be used to communicate with the UE, as described herein. Similarly, one or more receivers <NUM> may be used to communicate with network functions in the PLMN and/or RAN, as described herein. Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the network apparatus <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>. Further, the transmitter(s) <NUM> and the receiver(s) <NUM> may be any suitable type of transmitters and receivers.

<FIG> depicts one embodiment of a method <NUM> for ultra-wideband measurements for radio access technology-independent positioning, according to embodiments of the disclosure. In various embodiments, the method <NUM> is performed by a user equipment device in a mobile communication network, such as the remote unit <NUM>, the UE <NUM>, and/or the user equipment apparatus <NUM>, described above. In some embodiments, the method <NUM> is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

In one embodiment, the method <NUM> begins and transmits <NUM>, to a location server of a mobile wireless communication network, a set of capabilities related to ultra-wideband ("UWB") positioning for the UE device in response to a request from the location server for the set of capabilities, the set of capabilities used to determine at least one UWB positioning method for performing UWB positioning of the UE device. The method <NUM> receives <NUM>, from the location server, UWB assistance data to perform UWB positioning in response to a request for the assistance information, the assistance information comprising the at least one UWB positioning method for performing UWB positioning.

The method <NUM> transmits <NUM>, to the location server, a UWB measurement and location information report for the UE device using the at least one UWB positioning method associated with at least one of a set of timing-based and a set of angular-based UWB measurements in response to a request from the location server for the UWB measurement and location information. The method <NUM> determines <NUM> information for potential causes of error for one or more of a UWB configuration and a position estimate for the UE device.

The method <NUM> transmits <NUM>, to the location server, the determined information for the potential causes of error. The method <NUM> receives <NUM>, from the location server, UWB-specific error information associated with one or more of the UWB configuration and the position estimate information for correcting the determined potential causes of error, and the method <NUM> ends.

<FIG> depicts one embodiment of a method <NUM> for ultra-wideband measurements for radio access technology-independent positioning, according to embodiments of the disclosure. In various embodiments, the method <NUM> is performed by a Location Management Function in a mobile communication network, such as the LMF <NUM>, and/or the network apparatus <NUM>, described above. In some embodiments, the method <NUM> is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> begins and receives <NUM>, from a user equipment ("UE") device, a set of capabilities related to ultra-wideband ("UWB") positioning for the UE device in response to a request for the set of capabilities, the set of capabilities used to determine at least one UWB positioning method for performing UWB positioning of the UE device.

The method <NUM> transmits <NUM>, to the user equipment ("UE") device, UWB assistance data to perform UWB positioning in response to a request for the assistance information, the assistance information comprising the at least one UWB positioning method for performing UWB positioning.

The method <NUM> receives <NUM>, from the UE device, a UWB measurement and location information report for the UE device using the at least one UWB positioning method associated with at least one of a set of timing-based and a set of angular-based UWB measurements in response to a request from the location server for the UWB measurement and location information.

The method <NUM> receives <NUM>, from the UE device, information describing potential causes of error for one or more of a UWB configuration and a position estimate for the UE device. The method <NUM> transmits <NUM>, to the UE device, UWB-specific error information associated with one or more of the UWB configuration and the position estimate information for correcting the determined potential causes of error, and the method <NUM> ends.

Claim 1:
A User Equipment, UE, (<NUM>) for wireless communication, the UE (<NUM>) comprising:
at least one memory (<NUM>); and
at least one processor (<NUM>) coupled with the at least one memory (<NUM>) and configured to cause the UE (<NUM>) to:
transmit, to a location server of a mobile wireless communication network, a set of capabilities related to ultra-wideband, UWB, positioning for the UE in response to a request from the location server for the set of capabilities, the set of capabilities used to determine at least one UWB positioning method for performing UWB positioning of the UE;
receive, from the location server, UWB assistance data to perform UWB positioning in response to a request for assistance information, the assistance information comprising the at least one UWB positioning method for performing UWB positioning; and
transmit, to the location server, a UWB measurement and location information report for the UE using the at least one UWB positioning method associated with at least one of a set of timing-based and a set of angular-based UWB measurements in response to a request from the location server for the UWB measurement and location information report; and the UE being characterized by the at least one processor being configured to cause the UE to:
determine information for potential causes of error for one or more of a UWB configuration and a position estimate for the UE,
transmit, to the location server, the determined information for the potential causes of error; and
receive, from the location server, UWB-specific error information associated with one or more of the UWB configuration and the position estimate for correcting the potential causes of error.