Data collection design for ai / ML based positioning using lpp
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-02-05
- Publication Date
- 2026-08-13
Smart Images

Figure CN2025075809_13082026_PF_FP_ABST
Abstract
Description
DATA COLLECTION DESIGN FOR AI / ML BASED POSITIONING USING LPPFIELD
[0001] This disclosure relates to wireless communication networks and mobile device capabilities.BACKGROUND
[0002] Wireless communication networks and wireless communication services are becoming increasingly dynamic, complex, and ubiquitous. For example, some wireless communication networks can be developed to implement fifth generation (5G) or new radio (NR) technology, sixth generation (6G) technology, and so on. Such technology can include solutions for enabling user equipment (UE) and network devices, such as base stations, to communicate with one another. Such communications can involve procedures for collecting and reporting certain types of information.BRIEF DESCRIPTION OF THE DRAWINGS
[0003] The present disclosure will be readily understood and enabled by the detailed description and accompanying figures of the drawings. Like reference numerals can designate like features and structural elements. Figures and corresponding descriptions are provided as non-limiting examples of aspects, implementations, etc., of the present disclosure, and references to "an" or “one” aspect, implementation, etc., may not necessarily refer to the same aspect, implementation, etc., and can mean at least one, one or more, etc.
[0004] Fig. 1 is a diagram of an example of an overview according to one or more implementations described herein.
[0005] Fig. 2 is a diagram of an example network according to one or more implementations described herein.
[0006] Fig. 3 is a diagram of an example of a network positioning architecture for long-term evolution (LTE) positioning protocol (LPP) according to one or more implementations described herein.
[0007] Fig. 4 is a diagram of an example of artificial intelligence / machine learning (AI / ML) functions according to one or more implementations described herein.
[0008] Fig. 5 is a diagram of an example of AI / ML model according to one or more implementations described herein.
[0009] Fig. 6 is a diagram of an example process for data collection using LPP for AI / ML positioning according to one or more implementations described herein.
[0010] Fig. 7 is a diagram of an example for monitoring and responding to a current memory buffer capacity and a current battery power according to one or more implementations described herein.
[0011] Fig. 8 is a diagram of an example of components of a device according to one or more implementations described herein.
[0012] Fig. 9 is a diagram of example interfaces of baseband circuitry according to one or more implementations described herein.
[0013] Fig. 10 is a block diagram illustrating components, according to one or more implementations described herein, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
[0014] Fig. 11 is a diagram of an example process for process for data collection using LPP for AI / ML positioning according to one or more implementations described herein.
[0015] Fig. 12 is a diagram of an example process for process for data collection using LPP for AI / ML positioning according to one or more implementations described herein.DETAILED DESCRIPTION
[0016] The following detailed description refers to the accompanying drawings. Like reference numbers in different drawings can identify the same or similar features, elements, operations, etc. Additionally, the present disclosure is not limited to the following description as other implementations can be utilized, and structural or logical changes made, without departing from the scope of the present disclosure.
[0017] Wireless communication networks can include user equipment (UE) capable of communicating with base stations, core network, and / or other network devices. The UE and base station can communicate with one another using time and frequency resources allocated for uplink and downlink communications. Examples of such communications can involve certain protocols, such as media access control (MAC) protocol, radio resource control (RRC) protocol, and more.
[0018] The fourth generation (4G) or long-term evolution (LTE) communication standards of the 3rd generation partnership project (3GPP) can use two positioning protocols via the radio network: LTE positioning protocol (LPP) and LPP Annex (LPPa) . LPP is a point-to-point protocol for communication between a location service (LCS) server and an LCS target device, and LPP can be used to determine the position of the LCS target device. LPP can be used both in the user plane and control plane, and multiple LPP procedures are allowed in series and / or in parallel, reducing latency. LPPa is a communication protocol between base station and an LCS server for control-plane positioning.
[0019] The firth generation (5G) or new radio (NR) communication standards of the 3GPP introduced several new capabilities and network entities that were not available in 4G LTE networks. Due to a new next generation (NG) interface between the NG radio access network (NG-RAN) and the core network, a new NR positioning protocol A (NRPPa) protocol was introduced to carry the positioning information between NG-RAN and location management function (LMF) of a core network over the next generation control plane interface (NG-C) . These additions in the 5G architecture provide the framework for positioning in 5G.
[0020] To enable more accurate positioning measurements than LTE, new reference signals were added to the NR specifications. These signals are the positioning reference signal (NR positioning reference signal (PRS) ) in the downlink and the sounding reference signal (SRS) for positioning in the uplink. The downlink PRS is the main reference signal supporting downlink-based positioning methods. Although other signals can be used, PRS is specifically designed to deliver the highest possible levels of accuracy, coverage, and interference avoidance and suppression.
[0021] Tools for enhancing the performance of wireless communication networks can include artificial intelligence (AI) , machine learning (ML) , deep learning (DL) , neural networks (NNs) , and similar technologies. For example, models can be developed and applied to one or more devices or aspects of a network to enhance performance by recognizing patterns, interpreting circumstances, generating inferences, and so on. An AI / ML model can be described as a logical framework of interrelated nodes developed to interpret or generate an inference about a corresponding set of inputs. A model can evaluate the inputs according to a combination of nodes that have been assigned different weights and relationships as the result of applying training data to improve and refine the AI / ML model. Conformance testing can include a technique used for developing an AI / ML model to be verified or validated for one or more scenarios, which can be characterized as conditions under which the AI / ML model can produce an inference output of suitable accuracy.
[0022] While AI / ML models can be helpful to enhance the capabilities of a network, the value and accuracy of inferences generated by AI / ML models can depend on the quantity, quality, and number of instances of training data available for refining and improving the models. Currently available wireless communication networks fail to provide adequate solutions for leveraging the ability, ubiquity, and availability of UEs to collect and report training data that can be used to enhance location and positioning capabilities of the network though the use of AI / ML models.
[0023] One or more of the techniques, described herein, include one or more solutions for data collection for AI / ML based positioning using LPP. A UE can provide a network (e.g., a location management function (LMF) of a core network) with capability information relating to LPP. The LMF can configure the UE to take measurements and generate positioning information according to a periodicity, schedule, and / or one or more trigger events. The UE can report measurements and positioning information on-demand and / or in response to one or more trigger events. Communications between the UE and LMF can involve new LPP signaling and repurposed LPP signaling so that LPP can be used effectively in network environments more advanced than 4G LTE networks. The measurement and positioning information collected can be used to develop, design, and train neural network models, in addition to validating neural network inputs data and neural network output inferences.
[0024] Fig. 2 is a diagram of an example 100 of an overview according to one or more implementations described herein. As shown, example 100 can include UE 110 and LMF 130. UE 210 can use LPP to provide LMF 120 with UE capability information (at 1.1) Examples of the UE capability information can include an ability of UE 110 to measure signaling, determine positioning information indicating a location of UE 110, determine an accuracy of the positioning information and label the information appropriately, store the positioning information, and / or report the positioning information to LMF 120. In response, LMF 120 can use LPP to provide UE 110 with positioning configuration information, which can cause the UE 110 to operate in certain ways and under certain conditions to measure signaling, generate and store positioning information, and reporting the positioning information to LMF 120.
[0025] UE 110 can generate positioning information according to the positioning configuration information from LMF 120 (at 1.2) . This can include measuring or monitoring one or more reference signals and determining one or more measurement metrics. This can also include creating records of the measurement metrics, which can also include a time stamp, quality indicator, label (e.g., a ground truth label) , and one or more additional record attributes or characteristics. In some implementations, UE 110 can generate the positioning information in response to one or more trigger events and / or according to a schedule or periodicity. UE 110 can store the positioning information in a local memory buffer.
[0026] UE 110 can use LPP to report the positioning information to LMF 120 (at 1.3) . UE 110 can report the positioning information on-demand (e.g., in response to a request form LMF 120) or in response to one or more trigger events. Examples of trigger events for generating positioning information (at 1.2) and / or reporting positioning information (at 1.3) can include UE 110 entering a target location area, positioning information being of a specified quality or receiving a particular label (e.g., a ground truth label) , the memory buffer of UE 110 having a minimum or a maximum amount of positioning information, and so on. LMF 120 can use the positioning information to train AI / ML models for positioning, validate model input information, validate output inferences, and so on. These and many other features and examples are described below with reference to the remaining Figures.
[0027] Fig. 2 is an example environment 200 in which one or more of the techniques described herein can be implemented. Example environment 200 can include UEs 210-1, 210-2, etc. (referred to collectively as “UEs 210” and individually as “UE 210” ) , a radio access network (RAN) 220, a core network (CN) 230, application servers 240, external networks 250.
[0028] The systems and devices of example environment 200 can operate in accordance with one or more communication standards, such as 2nd generation (2G) , 3rd generation (3G) , 4th generation (4G) (e.g., long-term evolution (LTE) ) , and / or 5th generation (5G) (e.g., new radio (NR) ) communication standards of the 3rd generation partnership project (3GPP) . Additionally, or alternatively, one or more of the systems and devices of example environment 200 can operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc. ) , institute of electrical and electronics engineers (IEEE) standards, and more.
[0029] As shown, UEs 210 can include smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more wireless communication networks) . Additionally, or alternatively, UEs 210 can include other types of mobile or non-mobile computing devices capable of wireless communications, such as personal data assistants (PDAs) , pagers, laptop computers, desktop computers, wireless handsets, etc. In some implementations, UEs 210 can include Internet of Things (IoT) devices (or IoT UEs) that can implement narrowband (NB) communications and that can comprise, for example, a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
[0030] Additionally, or alternatively, an IoT UE can utilize one or more types of technologies, such as machine-to-machine (M2M) communications or machine-type communications (MTC) (e.g., to exchanging data with an MTC server or other device via a public land mobile network (PLMN) ) , proximity-based service (ProSe) or device-to-device (D2D) communications, sensor networks, IoT networks, and more. Depending on the scenario, an M2M or MTC exchange of data can be a machine-initiated exchange, and an IoT network can include interconnecting IoT UEs (which can include uniquely identifiable embedded computing devices within an Internet infrastructure) with short-lived connections. In some scenarios, IoT UEs can execute background applications (e.g., keep-alive messages, status updates, etc. ) to facilitate the connections of the IoT network.
[0031] UEs 210 can communicate and establish a connection with one or more other UEs 210 via one or more wireless channels 212, each of which can comprise a physical communications interface / layer. The connection can include an M2M connection, MTC connection, D2D connection, SL connection, etc. The connection can involve a PC5 interface. In some implementations, UEs 210 can be configured to discover one another, negotiate wireless resources between one another, and establish connections between one another, without intervention or communications involving RAN node 222 or another type of network node. In some implementations, discovery, authentication, resource negotiation, registration, etc., can involve communications with RAN node 222 or another type of network node.
[0032] UEs 210 can communicate and establish a connection with RAN 220, which can involve one or more wireless channels 214-1 and 214-2, each of which can comprise a physical communications interface / layer. In some implementations, a UE can be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC) , where a multiple receive and transmit (Rx / Tx) capable UE can use resources provided by different network nodes (e.g., 222-1 and 222-2) that can be connected via non-ideal backhaul (e.g., where one network node provides NR access and the other network node provides either E-UTRA for LTE or NR access for 5G) . A network node can be referred to herein as a base station 222. In such a scenario, one network node can operate as a master node (MN) and the other as the secondary node (SN) . The MN and SN can be connected via a network interface, and at least the MN can be connected to the CN 230. In some implementations, a base station (as described herein) can be an example of network node 222. In some scenarios, RAN 220 can coordinate with core network 230 via interfaces 224, 226, and / or 228.
[0033] As shown, UE 210 can also, or alternatively, connect to access point (AP) 216 via connection interface 218, which can include an air interface enabling UE 210 to communicatively couple with AP 216. AP 216 can comprise a wireless local area network (WLAN) , WLAN node, WLAN termination point, etc. The connection 216 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, and AP 216 can comprise a wireless fidelity router or other access point device. While not explicitly depicted in Fig. 2, AP 216 can be connected to another network (e.g., the Internet) without connecting to RAN 220 or CN 230.
[0034] One or more of the techniques described herein include solutions for data collection design for AI / ML based positioning using LPP. UE 210 can provide LMF 320 with capability information relating to an ability of UE 210 to support LPP, collect positioning information, and report positioning information to LMF 320. LMF 320 can configure UE 210 to take measurements and to generate and store positioning information according to a periodicity, schedule, and / or one or more trigger events. UE 210 can report the positioning information on-demand and / or in response to one or more trigger events. Communications between UE 210 and LMF 320 can involve new and / or repurposed LPP signaling. These and many other features and examples are described herein.
[0035] RAN 220 can include one or more RAN nodes 222-1 and 222-2 (referred to collectively as RAN nodes 222, and individually as RAN node 222) that enable channels 214-1 and 214-2 to be established between UEs 210 and RAN 220. RAN nodes 222 can include network access points configured to provide radio baseband functions for data and / or voice connectivity between users and the network based on one or more of the communication technologies described herein (e.g., 1G, 3G, 4G, 5G, WiFi, etc. ) . As examples therefore, a RAN node can be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc. ) , a next generation base station (e.g., a 5G base station, NR base station, next generation eNBs (gNB) , etc. ) . RAN nodes 222 can include a roadside unit (RSU) , a transmission reception point (TRxP or TRP) , and one or more other types of ground stations (e.g., terrestrial access points) . In some scenarios, RAN node 222 can be a dedicated physical device, such as a macrocell base station, and / or a low power (LP) base station for providing femtocells, picocells or the like having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. A RAN node can generally be referred to herein as base station 222.
[0036] Some or all of RAN nodes 222, or portions thereof, can be implemented as one or more software entities running on server computers as part of a virtual network, which can be referred to as a centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP) . In these implementations, the CRAN or vBBUP can implement a RAN function split, such as a packet data convergence protocol (PDCP) split wherein radio resource control (RRC) and PDCP layers can be operated by the CRAN / vBBUP and other Layer 1 (L1) protocol entities can be operated by individual RAN nodes 222; a media access control (MAC) / physical (PHY) layer split wherein RRC, PDCP, radio link control (RLC) , and MAC layers can be operated by the CRAN / vBBUP and the PHY layer can be operated by individual RAN nodes 222; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer can be operated by the CRAN / vBBUP and lower portions of the PHY layer can be operated by individual RAN nodes 222. This virtualized framework can allow freed-up processor cores of RAN nodes 222 to perform or execute other virtualized applications.
[0037] In some implementations, an individual RAN node 222 can represent individual gNB-distributed units (DUs) connected to a gNB-control unit (CU) via individual F1 or other interfaces. In such implementations, the gNB-DUs can include one or more remote radio heads or radio frequency (RF) front end modules (RFEMs) , and the gNB-CU can be operated by a server (not shown) located in RAN 220 or by a server pool (e.g., a group of servers configured to share resources) in a similar manner as the CRAN / vBBUP. Additionally, or alternatively, one or more of RAN nodes 222 can be next generation eNBs (i.e., gNBs) that can provide evolved universal terrestrial radio access (E-UTRA) user plane and control plane protocol terminations toward UEs 210, and that can be connected to a 5G core network (5GC) 230 via an NG interface.
[0038] Any of the RAN nodes 222 can terminate an air interface protocol and can be the first point of contact for UEs 210. In some implementations, any of the RAN nodes 222 can fulfill various logical functions for the RAN 220 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. UEs 210 can be configured to communicate using orthogonal frequency-division multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 222 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a single carrier frequency-division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink (SL) communications) , although the scope of such implementations may not be limited in this regard. The OFDM signals can comprise a plurality of orthogonal subcarriers.
[0039] In some implementations, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 222 to UEs 210, and uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid (e.g., a resource grid or time-frequency resource grid) that represents the physical resource for downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises resource blocks, which describe the mapping of certain physical channels to resource elements (REs) . Each resource block can comprise a collection of resource elements; in the frequency domain, this can represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.
[0040] Further, RAN nodes 222 can be configured to wirelessly communicate with UEs 210, and / or one another, over a licensed medium (also referred to as the “licensed spectrum” and / or the “licensed band” ) , an unlicensed shared medium (also referred to as the “unlicensed spectrum” and / or the “unlicensed band” ) , or combination thereof. A licensed spectrum can correspond to channels or frequency bands selected, reserved, regulated, etc., for certain types of wireless activity (e.g., wireless telecommunication network activity) , whereas an unlicensed spectrum can correspond to one or more frequency bands that are not restricted for certain types of wireless activity.
[0041] The PDSCH can carry user data and higher layer signaling to UEs 210. The physical downlink control channel (PDCCH) can carry information about the transport format and resource allocations related to the PDSCH channel, among other things. The PDCCH can also inform UEs 210 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (e.g., assigning control and shared channel resource blocks to UE 210 within a cell) can be performed at any of the RAN nodes 222 based on channel quality information feedback from any of UEs 210. The downlink resource assignment information can be sent on the PDCCH used for (e.g., assigned to) each of UEs 210.
[0042] The RAN nodes 222 can be configured to communicate with one another via interface 223. In implementations where the system is an LTE system, interface 223 can be an X2 interface. In NR systems, interface 223 can be an Xn interface. The X2 interface can be defined between two or more RAN nodes 222 (e.g., two or more eNBs / gNBs or a combination thereof) that connect to evolved packet core (EPC) or CN 230, or between two eNBs connecting to an EPC. As shown, RAN 220 can be connected (e.g., communicatively coupled) to CN 230. CN 230 can comprise a plurality of network elements 232, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UEs 210) who are connected to the CN 230 via the RAN 220. In some implementations, CN 230 can include an evolved packet core (EPC) , a 5G CN (5GC) , and / or one or more additional or alternative types of CNs.
[0043] As shown, CN 230, application servers 240, and external networks 250 can be connected to one another via interfaces 234, 236, and 238, which can include IP network interfaces. Application servers 240 can include one or more server devices or network elements (e.g., virtual network functions (VNFs) offering applications that use IP bearer resources with CN 230 (e.g., universal mobile telecommunications system packet services (UMTS PS) domain, LTE PS data services, etc. ) . Application servers 240 can also, or alternatively, be configured to support one or more communication services (e.g., voice over IP (VoIP sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc. ) for UEs 210 via the CN 230. Similarly, external networks 250 can include one or more of a variety of networks, including the Internet, thereby providing the mobile communication network and UEs 210 of the network access to a variety of additional services, information, interconnectivity, and other network features.
[0044] Fig. 3 is a diagram of an example of a network positioning architecture 300 for long-term evolution positioning protocol (LPP) according to one or more implementations described herein. Network positioning architecture 300 can include UE 210, base stations 222, and CN 230 according to one or more implementations described herein. As shown, CN 230 can include access and mobility management function (AMF) 310, a location management function (LMF) 320, and / or one or more other types of functions or entities 330. Examples of such functions or entities can include a session management function (SMF) , unified data management (UDM) function, a gateway mobile location center (GMLC) , and more. AMF 310, LMF 320, etc., can be implemented by one or more servers in a centralized or distributed networking environment.
[0045] AMF 310 can communicate with base station 222 via an N2 interface and UE 210 via an N1 interface. AMF 310 can manage authentication, registration, and other functionalities relating to UEs 210 accessing a telecommunication mobile network. AMF 310 can also handle handovers, paging, and other functionality regarding the mobility and communications of UEs 210 with a telecommunication mobile network. AMF 310 can also provide security functionality for authenticating and authorizing UEs 210.
[0046] LMF 320 can provide positioning functionality to determine the geographic position of UE 210 based on downlink (DL) and uplink (UL) location measuring radio signals. LMF 320 can receive measurements and assistance information from base station 222 and UE 210 via AMF 310 and an NLs interface. LMF 320 can use the measurement and assistance information to compute the position of UE 210. A new NR positioning protocol A (NRPPa) protocol can be used to carry positioning information between base station 222 and LMF 320 over a next generation control plane interface (NG-C) . LMF 320 can also configure UE 210 using LTE positioning protocol (LPP) via AMF 310, and base station 222 can configure UE 210 using RRC protocol over an LTE-Uu interface and / or an NR-Uu interface.
[0047] LMF 320 can provide positioning assistance data to UE 210. Examples of such information can include information regarding signals to be measured (e.g., expected signal timing, signal coding, signal frequencies, signal Doppler, etc. ) , locations and identities of terrestrial transmitters (e.g., base stations 222, AP 216, etc. ) and / or signal, timing and orbital information for non-terrestrial transmitters, such as satellites and satellite systems. Doing so can improve signal acquisition and measurement accuracy of UE 210 and, in some cases, enable UE 210 to better determine a current geographic location based on the location measurements. LMF 320 can implement a protocol to transfer AI ML information describe herein. The protocol can be part of a new NR positioning protocol A (NRPPa) protocol, another type of positioning protocol, or a newly developed positioning protocol.
[0048] LMF 320 can provide UE 210 with information indicating locations and identities of terrestrial and / or non-terrestrial transmitters corresponding to a particular region and / or signaling information, such as transmission power, signal timing, etc. A UE 210 can obtain measurements of signal strengths (e.g., received signal strength indication (RSSI) ) for signals received from such transceivers and / or can obtain a signal to noise ratio (S / N) , a reference signal received power (RSRP) , a reference signal received quality (RSRQ) , a time of arrival (TOA) , or a round trip signal propagation time (RTT) between UE 210 and one or more transceivers (e.g., base station 222, AP 216, etc. ) .
[0049] UE 210 can transfer these measurements to LMF 320, to determine a location for UE 210, or in some implementations, can use these measurements together with assistance data (e.g., information indicating locations and identities of terrestrial and / or non-terrestrial transmitters) received from a location server (e.g., LMF 320) or broadcast by base station 222 to determine a location for UE 210. UE 210 can measure a reference signal time difference (RSTD) between signals such as a position reference signal (PRS) , cell specific reference signal (CRS) , or tracking reference signal (TRS) transmitted by nearby pairs of transceivers. An RSTD measurement can provide the time of arrival difference between signals (e.g., TRS, CRS or PRS) received at UE 210 from two different transceivers. The UE 210 can return the measured RSTDs to LMF 320, which can compute an estimated location for UE 210 based on known locations and known signal timing for the measured transceivers.
[0050] LMF 320 can support and provide functionality regarding model validity for AI-based UE positioning. In some implementations, some or all of the functionality described herein as being performed by LMF 320 can be performed by one or more other types of functions or entities, including base station 222, application servers 240, and / or another function or entity of CN 320.
[0051] An AI / ML based positioning procedure can be used to determine the location of UE 210 using an AI / ML model. Depending on the scenario, the AI / ML model can be implemented by one or more of UE 210, base station 222, and LMF 230. When the AI / ML model is implemented by UE 210, positioning can be determined using UE-based positioning with UE-side model and direct AI / ML positioning. Alternatively, when the AI / ML model is implemented by UE 210, positioning can be determined using UE-assisted / LMF-based positioning with UE-side model and AI / ML assisted positioning. When the AI / ML model is implemented by LMF 230, positioning can be determined using UE-assisted / LMF-based positioning with LMF-side model and direct AI / ML positioning. As described herein, LPP messages can be reused to configure UE 210 to collect and report UE data to LMF 230.
[0052] Fig. 4 is a diagram of an example of AI / ML functions 400 according to one or more implementations described herein. As shown, example 400 can include data collection function 410, model training function 420, model inference function 430, and actor function 440. In some implementations, AI / ML functions 400 can include one or more, fewer, alternative, or alternatively arranged functions than those depicted. Aspects of AI / ML functions 400 can be implemented by one or more devices, such as UE 210, base station 222, network elements of CN 230 (e.g., LMF 320) , application server 240, or a combination thereof. For example, application server 240 or LMF 320 can implement aspects of AI / ML functions 400 to generate, train, test, and evaluate AI / ML models. The AI / ML models can be distributed to UE 210, and UE can implement one or more aspects of AI / ML functions 400 for AI / ML model deployment, evaluation, and feedback generation. Application server 240 or LMF 320 can implement aspects of AI / ML model functionality to update AI / ML models, retrain AI / ML models, and send modified versions of AI / ML models to UE 210. The AI / ML models can be configured and trained to operate under specified conditions and generate certain types of inferences relating to UE 210, base station 222, and / or communications between UE 210 and base station 222.
[0053] Data collection function 410 can provide input data to model training function 420 and model inference function 430. Examples of input data can include measurements from UEs 210 or different network entities, feedback from actor function 440, output from an AI / ML model. As described herein, an AI / ML model can include a framework of functions, vectors, and / or other types of features that have been trained by applying training data to the AI / ML model. The AI / ML model can be capable of evaluating input data and producing output data interpreted as an inference derived from input data applied to the AI / ML model.
[0054] Training data can include input data for the AI / ML model training function 420. Model training function 420 can perform AI / ML model training, validation, and testing which can generate model performance metrics as part of a model testing procedure. Model training function 420 can also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on training data delivered by a data collection function 410. A model deployment / update can be used to initially deploy a trained, validated, and tested AI / ML model to model inference function 430 or to deliver an updated model to model inference function 430.
[0055] Model inference function 430 can implement an AI / ML model to produce an inference output based on input data provided to model inference function 430. The input data can be provided by a device executing data collection function, which can be the same or a different device performing model inference function 430. Model inference function 430 can also perform for data preparation procedures (e.g., data pre-processing, cleaning, formatting, and transformation) based on inference data provided by data collection function 410. Model inference function 430 can generate and provide model performance feedback to model training function 420 when applicable. The model performance feedback can be used evaluate the performance of an AI / ML model, which can lead to the AI / ML model being updated and / or retrained depending on an accuracy of the output inference.
[0056] Actor function 440 can receive an inference output from the model inference function 430 and perform one or more procedures using the inference output. Actor function 440 can include a function configured to use or evaluate the inference output of model inference function 430 in one or more ways. For example, input data provided to model inference function 430 can also be provided to a non-NN procedure. Model inference function 430 can produce an inference output intended to predict or anticipate the output produced by the non-NN procedure. Actor function 440 can perform the non-NN procedure, using the same input data used by model inference function 430, to produce output data of the non-NN procedures.
[0057] Actor function 440 can apply one or more data processing, evaluation, and analysis functions or tools to the inference output and / or the output of the non-NN procedure to determine an inference accuracy of the AI / ML model (e.g., whether the AI / ML model accurately predicted the output of the non-NN procedure) . Actor function 440 can also determine whether one or more additional inputs or conditions are appropriate for using the AI / ML model based on an inference accuracy of the interference output. Actor function 440 can produce results, feedback, and other information that can be used to derive training data, inference data, or monitor the performance of the AI / ML model and its impact on one or more device, such as UE 210, base station 222, etc.
[0058] Fig. 5 is a diagram of an example of AI / ML model 500 according to one or more implementations described herein. As shown, AI / ML model 500 can include nodes arranged in different layers, such as an input layer 510, multiple hidden or intermediary layers 520 of nodes, and an output layer 530 of nodes. In some implementations, AI / ML model 500 can be an example of, or a portion of, model training function 520, an AI / ML model, model inference function 530, and / or actor function 540. For example, AI / ML model 500 can be trained on training data from data collection function 510, deployed by model training function 520 as an AI / ML model, and used by model inference function 530 to produce feedback for model training function 520 and an inference output for actor function 540.
[0059] Example AI / ML model 500 can include a number N of inputs introduced to four input nodes [N, 4] of input layer 510. This can include processing or encoding input data into a form, shape, vector, or data structure, that is receivable by the AI / ML model. The four input nodes can process the inputs to produce a first weight (W1) that the four input nodes provide to the five nodes [4; 4] of a first hidden layer. The five nodes of the first hidden layer can use a first function (f1) to process the inputs to produce a second weight (W2) that the five nodes of the first hidden layer can provide to the five nodes [4; 4] of a second hidden layer. The five nodes of the second layer can use a second function (f2) to process the inputs to produce a third weight (W3) that the five nodes of the second hidden layer can provide to the three nodes [4; 3] of output layer 530. The nodes of output layer 530 can each process the inputs received and produce an output. This can include converting or unencoding output data from a form, shape, vector, or data structure, that can be used by a subsequent algorithm, process, or procedure.
[0060] One or more of the techniques described herein as using a NN, an AI / ML model, and the like, can be implemented using any type or combination of artificial intelligence (AI) . Generally, AI can involve a combination of computer science and datasets to enable problem-solving. AI can encompass machine learning (ML) and deep learning (DL) . These disciplines are comprised of AI algorithms that seek to create expert systems which make predictions or classifications based on input data. ML, DL, and neural networks (NNs) can be viewed as sub-fields of AI. However, NNs can actually be a sub-field of ML, and DL can be a sub-field of NNs. The way in which DL and ML differ can include in how each algorithm learns. Deep ML can use labeled datasets (also known as supervised learning) to inform its algorithm but may not necessarily involve a labeled dataset. DL can ingest unstructured data in a raw form (e.g., text or images) and can automatically or autonomously determine the set of features that distinguish different categories of data from one another. This can eliminate some of the human intervention otherwise involved and enable use of larger data sets. DL can be viewed, in a sense, as scalable ML.
[0061] NNs, or artificial NNs (ANNs) , can comprise logically interconnected nodes arranged in node layers. There can be an input layer, one or more hidden or intermediate layers, and an output layer. Each node, or artificial neuron, can connect to another and has an associated weight and threshold. If the output of any individual node is above the specified threshold value, that node is activated, sending data to the next layer of the network. Otherwise, no data can be passed along to the next layer of the network by that node. The “deep” in deep learning can refer to the number of layers in an NN. An AI / ML model with more than three layers-which would be inclusive of the input and the output-can be considered a deep learning algorithm or a deep NN.A NN model with only three layers can be viewed as a basic NN.
[0062] A NN can be a feed forward NN (FNN) or a recurrent NN (RNN) . Examples of a FFN can include linear functions, such as a convolutional NN (CNN) or a NN that uses a radial basis function network. A CNN can include a framework capable of discovering NN features using filter or kernel optimization and producing an output. These NNs can harness principles from linear algebra, particularly matrix multiplication, to identify patterns within an image. Linear regression analysis, for example, can be used to predict a value of a variable based on a value of another variable. This form of analysis can estimate coefficients of a linear equation, involving one or more independent variables that best predict the value of the dependent variable. Linear regression can fit a straight line or surface that minimizes discrepancies between a predicted value and an actual value. These learning algorithms can be leveraged when using time-series data to make predictions about future outcomes.
[0063] An NN using a radial basis function network can be a linear combination of radial basis functions of inputs and neuron parameters. Radial basis function networks can be used for function approximation, time series prediction, classification, and system control. An RNN can be a bi-directional (as opposed to a linear) NN. A RNN can allow the output from some nodes to affect a subsequent input to the same nodes, thus having feedback loops and the potential for infinite impulse response compared to the finite impulse response of the more linear CNN.
[0064] Fig. 6 is a diagram of an example process 600 for data collection using LPP for AI / ML positioning according to one or more implementations described herein. As shown, process 600 can be implemented by UE 210 and LMF 320. In some implementations, some or all of process 600 can be performed by one or more other systems or devices, including baseband circuitry of UE 210 and one or more of the devices of Fig. 2. For example, communications between UE 210 and LMF 320 can be enabled by one or more devices, such as base station 222. Additionally, process 600 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 6. In some implementations, some or all of the operations of process 600 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 600. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 6.
[0065] As shown, process 600 can include LMF 320 communicating an LPP message to UE 210 (block 610) . The LPP message can include a request for capability information. The capability information can be referred to herein as UE LPP capability information. The LPP message can include an indication of the type of capability information being requested by LMF 320. The LPP message can include a RequestCapabilities message of the LPP protocol with information, such as an indication that the capability information requested relates to the collection, logging, and reporting of LPP information.
[0066] As such, one or more of the techniques, described herein, include a repurposing legacy LPP capability signaling (e.g., LPP request capabilities message / LPP provide capabilities message) to indicate UE capabilities related to logged LPP. The LPP signaling to request capabilities can include new request indications on, for example, whether UE 210 can support logged LPP, whether UE 210 can support a minimum buffer size (e.g., 64 kilobytes) , an indication of an actual buffer size of UE 210, and more. The LPP signaling to provide capabilities can include indications of new UE LPP capabilities, such as whether UE 210 can support data collection, logging, and reporting of position information via LPP, an actual buffer size available to UE 210, whether UE 210 can support event trigger logging and / or reporting, whether UE 210 can support on-demand logging and / or reporting, and more. The capability of UE 210 to support event trigger logging and / or reporting can be one common indication for all types of trigger events or dedicated indication for each type of event. Similarly, the capability of UE 210 to support on-demand logging and / or reporting can be one common indication for all types of on-demand scenarios (e.g., UE-initiated, LFM-initiated, etc. ) or dedicated indication for each type of on-demand scenario.
[0067] Process 600 can include UE 210 an communicating an LPP message to LMF 320 (block 620) . The LPP message can include capability information for UE 210. The capability information can be referred to herein as UE LPP capability information. The LPP message can include device capability information for UE 210. The LPP message can include a ProvideCapabilities message of the LPP protocol with information, such as an indication of the capabilities of UE 210 to participate in the data collection and reporting for AI / ML-based positioning. Examples of UE capability information can include a variety of one or more types of information, such as whether UE 210 can collect location and positioning information, store or create logs of the information collect, perform certain types of measurements and generate certain types of information, communicate the information to LMF 320, engage in on-demand reporting, engage in event trigger reporting, and more.
[0068] Process 600 can include LMF 320 communicating an LPP message to UE 210 (block 630) . The LPP message can include configuration information for UE 210. The LPP message can include a ProvideAssistanceData message of the LPP protocol with information, such as configuration information for storing or logging LPP information. Examples of LPP information can include a logged metric, logging type, reporting type, availability indication, and more.
[0069] As such, one or more of the techniques, described herein, include a repurposing legacy LPP signaling to provide UE 210 with configuration information for data collection. In some implementations, the legacy LPP message ProvideAssistanceData can be repurposed to provide UE 210 with configuration information for data collection. In some implementations, the legacy LPP message RequestLocationInformation message can be repurposed to provide UE 210 with configuration information for data collection. In some implementations, a new LPP message to provide AI / ML assistance information can be used to provide UE 210 with configuration information for data collection.
[0070] The data collection configuration information can include an indication of one or more measurement resources (e.g., a Positioning Reference Signal (PRS) configuration, which can be for LTE, 5G, or 6G) . Other examples of information that can be included in the data collection configuration information provided to UE 210 can include: a validity area ID of the PRS to enable UE 210 to identify an appropriate cell and / or PRS to measure; and logging configuration information (e.g., a LoggingConfig information element (IE) ) that can include a measurement quantity (e.g., a MeasQuantity IE) and logging type (e.g., loggingType IE) .
[0071] A measurement quantity can indicate which metric to measure and a logging type can indicate, for example, whether UE 210 is to engage in periodic logging and / or trigger event logging. Other examples of information that can be included in the data collection configuration information provided to UE 210 can include report configuration information (e.g., a LoggingReportConfig IE) that can indicate a type or reporting or schedule (e.g., a reportType) . The type of reporting can include whether UE 210 is to report logged position information periodically and / or in repones to an event trigger. The configuration information can also, or alternatively, include one or more associated IDs that UE 210 can use to categorize different types of logs or datasets.
[0072] UE 210 can be configured to collect and store positioning data according to one or more formats or configurations. For instance, UE 210 can process one or more measurements of a channel or signal and create a record or dataset of the measurement metric, which includes characteristics according to the designated format or configuration. Examples of the characteristics can include the measurement, measurement type, a timestamp, ground truth label, quality indicator for the corresponding measurement, and / or a quality indicator for a ground truth label. A quality indicator for a measurement can include GNSS integrity. A quality indicator for a ground truth label can include the confidence level of the ground truth label.
[0073] Examples a measurement type can include a channel impulse response (CIR) , power delay profile (PDP) , or delay profile (DP) . reference signal received power (RSRP) , reference signal received quality (RSRQ) , received signal strength indicator (RSSI) , reference signal received path power (RSRPP) , reference signal time difference (RSTD) , relative time of arrival (RTOA) , and more. Ground truth, in AI / ML and as referred to herein, can indicate actual, correct output or label associated with a dataset, used as a reference for training and evaluating models. Ground truth is a foundational concept in machine learning, serving as the benchmark or reference against which the performance of models is evaluated.
[0074] Ground truth or a ground truth label can refer information or data being true and correct or outputs associated with a dataset. These labels are obtained from reliable sources or domain experts and represent the most accurate representation of the data. For labeling, ground truth can refer to the true and correct labels or outputs associated with a dataset. These labels can be obtained from reliable sources or domain experts and represent the most accurate representation of the data. As a training reference, ground truth labels can be used during model training to teach the algorithm how to make predictions. The model can learn to minimize the difference between its predictions and the ground truth labels.
[0075] With respect to the evaluation for benchmarks, ground truth can be useful in assessing the performance of machine learning models. After training, models can be evaluated using ground truth labels to measure their accuracy, precision, recall, and other performance metrics. For quality assurance purposes, ground truth information can serve as a quality assurance mechanism, ensuring the reliability and validity of the data used for training and testing models. Ground truth information can help identify errors, inconsistencies, or biases in the dataset that could affect model performance. For iterative improvement, ground truth information can facilitate iterative model improvement by providing feedback on model predictions. Discrepancies between predicted outputs and ground truth labels can help highlight areas where the model may need refinement or additional training data.
[0076] Process 600 can include UE 210 measuring and logging positioning information (block 640) . For example, UE 210 can be configured to perform measurements and log positing information periodically, according to a schedule, and / or in response to one or more trigger events. Logging positioning information, as referred to herein, can include UE 210 generating logs, records, or other types of information relating to positioning information. Logging positioning information can also refer to UE 210 storing the positioning information locally (e.g., in a designated memory buffer) . Location information, positioning information, and similar terms, as used herein, can refer to measurements and information generated by UE 210, which can be used to determine a geographic location of UE 210. The location information, positioning information, etc., can be used to train, validate, and otherwise enhance the accuracy of AI / ML positioning models. Configuration information received by UE 210 (from base station 222) can cause or determine, at least in part, the frequency or periodicity, duration, quantity, and type of information measured at logged by UE 210.
[0077] With respect to periodic or scheduled logging, for each configured time interval. In some implementations, UE 210 can also be configured with a timer to limit how long UE 210 is to measure and / or log positioning information. Additionally, or alternatively, UE 210 can be configured with a counter to limit the number of measurements UE 210 is to take or logs (e.g., records) that UE 210 is to generate. Upon expiration of the timer or upon reaching the counter, UE 210 can be configured to discontinue measurement and / or logging procedures in order to, for example, conserve battery power.
[0078] With respect to trigger event logging, UE 210 can be configured to perform measurements and logging in response to detecting one or more triggers or events. An example of a trigger event can include UE 210 entering into a geographic area that matches an area ID with which the UE 210 has been configured. As such, upon detecting that UE 210 has entered into the area associated with the area ID, UE 210 can respond by measuring and logging positioning data for a period of time, until a threshold number of measurements are taken, until a threshold number of positioning records have been logged, etc. Enabling UE 210 to respond to trigger events can help ensure that UE 210 creates positioning data in certain areas (e.g., areas designated as high value) . Another example of a trigger event can include scenarios in which measurements and logged positioning data can be associated with a specified level of accuracy or reliability (e.g., when measurements or positioning data can be associated with a ground truth label) . Other examples of a trigger event can include one or more the following scenarios: upon detecting that the UE 210 is served by one configured PRS; upon detecting that the UE 210 is served by a PRS with configured associated ID; upon detecting that the UE 210 enters one area covered by one configured TRP; upon detecting that the UE 210 is moving with a speed lower than one configured threshold.
[0079] In some implementations, a trigger event can include multiple conditions (which could also be described as multiple trigger events) . For example, one condition can be UE 210 entering into a geographic area that matches an area ID and a second condition can be when the measurement can be associated with ground-truth label. Trigger events can also be configured with one or more L1 or L3 measurement events. Examples of an L1 measurement event can include measuring an RSRP, RSRQ, signal-to-interference-plus-noise ratio (SINR) , RSSI, etc. Examples of an L3 measurement event can include L1 measurements being filtered to remove the effect of fast fading and ignore short-term variations and may therefore be performed less often than L1 measurements.
[0080] As shown, UE 210 can be capable of reporting location information on-demand and / or in response to one or more event triggers. UE 210 can perform one or both types of reporting based on, for example, the capability information provided to LMF 320 and / or the configuration information received from LMF 320. Operations corresponding to blocks, 650, 660, and 670 are associated with on-demand reporting.
[0081] With reference to on-demand reporting, process 600 can include UE 210 an communicating an LPP message to LMF 320 (block 650) . The LPP message can include an indication or notification that UE 210 is available to report location information and / or that UE 210 has location information ready to be reported. The LPP message can indicate to LMF 320 that measurements and positioning information stored in a memory buffer of UE 210 has reached or exceeded a storage threshold. The LPP message can include a ProvideLocationInformation message of the LPP protocol with an indication that UE 210 is available to report location information and / or that UE 210 has location information ready to be reported. In some implementations, new LPP signaling can be used, which can involve UE 210 sending LMF 320 positioning information using an AvailabiltyInformation message or another type of new LPP message. In some implementations, UE 210 can be configured to send LMF 320 and indication of having positioning information in response to one or more trigger events, such as those discussed below with reference to block 480 (e.g., UE 210 entering a location that matches an area ID, UE 210 reaching a buffer storage minimum or maximum, etc. ) .
[0082] Process 600 can include LMF 320 communicating an LPP message to UE 210 (block 660) . The LPP message can include a request, prompt, or instructions for UE 210 to provide location or positioning information to LMF 320. The LPP message can include a RequestLocationInformation message of the LPP protocol, which includes a request for UE 210 to reportion positioning information. In some implementations, new LPP signaling can be used, which can involve UE 210 sending LMF 320 a new LPP message. In some implementations, LMF 320 can send a request to UE 210 for positioning information (block 660) in response to UE 210 notifying LMF 320 of having positioning information to report (see, e.g., block 650) . In some implementations, LMF 320 can also, or alternatively, LMF 320 can send a request to UE 210 for positioning information (block 660) proactively (e.g., without a notification from UE 210) .
[0083] Process 600 can include UE 210 communicating an LPP message to LMF 320 (block 670) . The LPP message can include location or positioning information generated and logged by UE 210. The LPP message can include a ProvideLocationInformation message of the LPP protocol. In some implementations, new LPP signaling can be used, which can involve UE 210 sending LMF 320 positioning information using a LoggedMeasurements message or another type of new LPP message. The information provided can include UE positioning information, such as information resulting from measurements taken by UE 210 and / or ground truth labels regarding UE positioning.
[0084] With reference to reporting positioning information in response to a trigger event, process 600 can include UE 210 detecting one or more trigger events (block 680) . For example, UE 210 can be configured to monitor for, and detect, one or more trigger events associated with reporting positioning information. A trigger event for reporting positioning information can be the same as, or different than, a trigger event for measuring and logging positioning information.
[0085] An example of a trigger event for reporting positioning information can include UE 210 entering into a geographic area that matches an area ID with which the UE 210 has been configured. The area ID can be the same area ID, or a different area ID, than an area ID of a trigger event for measuring and logging positioning information. As such, upon detecting that UE 210 has entered into the area associated with the area ID, UE 210 can respond by communicating positioning information to LMF 320.
[0086] Another example of a trigger event for reporting positioning information can include UE 210 entering into a geographic area that does not match an area ID associated with measuring and logging positioning information. Additionally, or alternatively, positioning information logged by UE 210 can include aera IDs associated with the logged information. In such a scenario, a trigger event can include UE 210 entering into a geographic area with an area ID that does not match an area ID of any of positioning information records stored by UE 210. Other examples of a trigger event for reporting can include one or more the following scenarios: upon detecting that the UE 210 is served by one configured PRS; upon detecting that the UE 210 is served by a PRS with configured associated ID; upon detecting that the UE 210 enters one area covered by one configured TRP; upon detecting that the UE 210 is moving with a speed lower than one configured threshold.
[0087] Other examples of a trigger event for reporting positioning information can include UE 210 determining that a quality indicator associated with measurements and / or positioning information is less than a quality threshold or the quality indicator of a ground-truth label is less than a quality threshold. Examples of quality indicators can include global navigation satellite system (GNSS) integrity and confidence level of the ground truth label. A quality threshold (e.g., for a measurement, positioning information, ground truth label or information, etc. ) can be received by UE 210 from LMF 320 via configuration information. Yet another example of a trigger event for reporting positioning information can include an amount of positioning data stored in a memory buffer of UE 210 reaching or surpassing a minimum amount of positioning data or number of positioning data records, reaching or being within a threshold amount of a memory buffer maximum or a maximum number of positioning data records, and so on. Another example of a trigger event for reporting positioning information can include positioning information stored in a memory buffer being older than a time threshold.
[0088] In some implementations, a trigger event can include multiple conditions (which could also be described as multiple trigger events) . For example, one condition can be UE 210 entering into a geographic area that matches an area ID associated with reporting positioning information and a second condition can be when the quality of measurements is less than a measurement quality threshold, and a third condition can be when a quality indicator for ground truth information is less than a ground truth quality threshold. In such a scenario, the even trigger can be configured to be satisfied when any one condition is satisfied, when a number or ratio of conditions are satisfied, or when all conditions are satisfied.
[0089] Trigger events for reporting positioning information can also be configured with one or more L1 or L3 measurement events. Examples of an L1 measurement event can include measuring an RSRP, RSRQ, SINR, RSSI, etc. Examples of an L3 measurement event can include L1 measurements being filtered to remove the effect of fast fading and ignore short-term variations and may therefore be performed less often than L1 measurements.
[0090] Process 600 can include UE 210 communicating an LPP message to LMF 320 (block 690) . The LPP message can include location or positioning information generated and logged by UE 210. The LPP message can include a ProvideLocationInformation message of the LPP protocol. In some implementations, new LPP signaling can be used, which can involve UE 210 sending LMF 320 positioning information using a LoggedMeasurements message or another type of new LPP message. The information provided can include UE positioning information, such as information resulting from measurements taken by UE 210 and / or ground truth labels regarding UE positioning. Prior to reporting, the positioning information can be stored in a memory buffer of UE 210.
[0091] Fig. 7 is a diagram of an example for monitoring and responding to a current memory buffer capacity and a current battery power according to one or more implementations described herein. UE 210 can include a memory buffer, which can be an access stratum (AS) buffer. In some implementations, a buffer size of a memory buffer of UE 210 for storing or logging positioning information can be configured (e.g., by UE configuration information from LMF 230) . In some implementations, a buffer size of a memory buffer of UE 210 for storing or logging positioning information can be a pre-selected buffer size with a static maximum size. In some implementations, the buffer size of the memory buffer of UE 210 can be the same size as a buffer size of a memory buffer or other storage capacity used by the network (e.g., used by base station 222, LMF 320, etc. ) to store positioning information received from UE 210. In some implementations, the buffer size of the memory buffer of UE 210 can be a different size as a buffer size of a memory buffer or other storage capacity used by the network (e.g., used by base station 222, LMF 320, etc. ) to store positioning information received from UE 210. In some implementations, a minimum buffer size of the memory buffer of UE 210 can be 64 kilobytes (KB) . UE 210 can report an actual AS buffer via LPP capability signaling as described above.
[0092] UE 210 can also, or alternatively, be capable of monitoring the availability of storage capacity of the memory buffer of UE 210. When the memory buffer is full, UE 210 can discontinue measuring signals and determining positioning information, which can enable UE 210 to conserve power. Doing so can be referred to herein as UE 210 entering into a power saving mode. Additionally, or alternatively, UE 210 can notify LMF 320 of positioning information being available to be transmitted to LMF 320 in response to detecting that the memory buffer is full.
[0093] UE 210 can also, or alternatively, be capable of monitoring a batter power of UE 210 and comparing a current battery power with a power threshold. UE 210 can be configured with the power threshold via UE configuration information received from LMF 320 and / or use a default power threshold consistent with performing LPP communications or other types of operating conditions. In some implementations, UE 210 can discontinue measuring signals and determining positioning information in response to a current batter power falling below a batter power threshold, which can enable UE 210 to conserve power. Doing so can be referred to herein as UE 210 entering into a power saving mode. Additionally, or alternatively, UE 210 can notify LMF 320 of positioning information being available to be transmitted to LMF 320 in response to the current batter power falling below the batter power threshold. LMF 320 can be capable of de-configuring data collection in response to receiving an indication of positioning information availability from UE 210.
[0094] Fig. 8 is a diagram of an example of components of a device according to one or more implementations described herein. In some implementations, device 800 can include application circuitry 802, baseband circuitry 804, RF circuitry 806, front-end module (FEM) circuitry 808, one or more antennas 810, and power management circuitry (PMC) 812 coupled together at least as shown. In some implementations, device 800 can include fewer elements (e.g., a RAN node may not utilize application circuitry 802 and can instead include a processor / controller to process data received from a core network. In some implementations, device 800 can include additional elements such as, for example, memory / storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device 800, etc. ) , or input / output (I / O) interface. In other implementations, the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for cloud-RAN (C-RAN) implementations) .
[0095] Application circuitry 802 can include one or more application processors. For example, application circuitry 802 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor (s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc. ) . The processors can be coupled with or can include memory / storage and can be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on device 800. In some implementations, processors of application circuitry 802 can process data packets received from a core network.
[0096] Baseband circuitry 804 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 804 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of RF circuitry 806 and to generate baseband signals for a transmit signal path of RF circuitry 806. Baseband circuity 804 can interface with application circuitry 802 for generation and processing of the baseband signals and for controlling operations of RF circuitry 806. For example, in some implementations, baseband circuitry 804 can include a 3G baseband processor 804A, a 4G baseband processor 804B, a 5G baseband processor 804C, or other baseband processor (s) 804D for other existing generations, generations in development or to be developed in the future (e.g., 5G, 6G, 8G, etc. ) . Baseband circuitry 804 (e.g., one or more of baseband processors 804A-D) can handle various radio control functions that enable communication with one or more radio networks via RF circuitry 806. In other implementations, some or all of the functionality of baseband processors 804A-D can be included in modules stored in memory 804G and executed via a central processing unit (CPU) 804E. The radio control functions can include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, modulation / demodulation circuitry of baseband circuitry 804 can include Fast-Fourier Transform (FFT) , precoding, or constellation mapping / de-mapping functionality. In some implementations, encoding / decoding circuitry of baseband circuitry 804 can include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functionality. Implementations of modulation / demodulation and encoder / decoder functionality are not limited to these examples and can include other suitable functionality in other implementations.
[0097] In some implementations, memory 804G can receive and / or store information and instructions for data collection design for AI / ML based positioning using LPP. UE 210 can provide LMF 320 with capability information relating to an ability of UE 210 to support LPP, collect positioning information, and report positioning information to LMF 320. LMF 320 can configure UE 210 to take measurements and to generate and store positioning information according to a periodicity, schedule, and / or one or more trigger events. UE 210 can report the positioning information on-demand and / or in response to one or more trigger events. Communications between UE 210 and LMF 320 can involve new and / or repurposed LPP signaling. Many other aspects and examples are also described herein.
[0098] In some implementations, baseband circuitry 804 can include one or more audio digital signal processor (s) (DSP) 804F. Audio DSP 804F can include elements for compression / decompression and echo cancellation and can include other suitable processing elements in other implementations. Components of baseband circuitry 804 can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some implementations. In some implementations, some or all of the constituent components of baseband circuitry 804 and application circuitry 802 can be implemented together such as, for example, on a system on a chip (SOC) .
[0099] In some implementations, baseband circuitry 804 can provide for communication compatible with one or more radio technologies. For example, in some implementations, baseband circuitry 804 can support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) , etc. Implementations in which baseband circuitry 804 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.
[0100] RF circuitry 806 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various implementations, RF circuitry 806 can include switches, filters, amplifiers, etc., to facilitate the communication with the wireless network. RF circuitry 806 can include a receive signal path which can include circuitry to down-convert RF signals received from FEM circuitry 808 and provide baseband signals to baseband circuitry 804. RF circuitry 806 can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by baseband circuitry 804 and provide RF output signals to FEM circuitry 808 for transmission.
[0101] In some implementations, the receive signal path of RF circuitry 806 can include mixer circuitry 806A, amplifier circuitry 806B and filter circuitry 806C. In some implementations, the transmit signal path of RF circuitry 806 can include filter circuitry 806C and mixer circuitry 806A. RF circuitry 806 can also include synthesizer circuitry 806D for synthesizing a frequency for use by mixer circuitry 806A of the receive signal path and the transmit signal path. In some implementations, mixer circuitry 806A of the receive signal path can be configured to down-convert RF signals received from FEM circuitry 808 based on the synthesized frequency provided by synthesizer circuitry 806D. Amplifier circuitry 806B can be configured to amplify the down-converted signals and filter circuitry 806C can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to baseband circuitry 804 for further processing. In some implementations, the output baseband signals can be zero-frequency baseband signals, although this may not be a requirement. In some implementations, mixer circuitry 806A of the receive signal path can comprise passive mixers, although the scope of the implementations is not limited in this respect.
[0102] In some implementations, mixer circuitry 806A of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by synthesizer circuitry 806D to generate RF output signals for FEM circuitry 808. The baseband signals can be provided by baseband circuitry 804 and can be filtered by filter circuitry 806C. In some implementations, mixer circuitry 806A of the receive signal path and mixer circuitry 806A of the transmit signal path can include two or more mixers and can be arranged for quadrature down conversion and up conversion, respectively. In some implementations, mixer circuitry 806A of the receive signal path and mixer circuitry 806A of the transmit signal path can include two or more mixers and can be arranged for image rejection. In some implementations, mixer circuitry 806A of the receive signal path and mixer circuitry 806A can be arranged for direct down conversion and direct up conversion, respectively. In some implementations, mixer circuitry 806 of the receive signal path and mixer circuitry 806A of the transmit signal path can be configured for super-heterodyne operation.
[0103] In some implementations, the output baseband signals, and the input baseband signals can be analog baseband signals, although the scope of the implementations is not limited in this respect. In some alternate implementations, the output baseband signals, and the input baseband signals can be digital baseband signals. In these alternate implementations, RF circuitry 806 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and baseband circuitry 804 can include a digital baseband interface to communicate with RF circuitry 806.
[0104] In some dual-mode implementations, a separate radio integrated circuitry can be provided for processing signals for each spectrum, although the scope of the implementations is not limited in this respect. In some implementations, synthesizer circuitry 806D can be a fractional-N synthesizer or a fractional N / N+1 synthesizer, although the scope of the implementations is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 806D can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
[0105] Synthesizer circuitry 806D can be configured to synthesize an output frequency for use by mixer circuitry 806A of RF circuitry 806 based on a frequency input and a divider control input. In some implementations, synthesizer circuitry 806D can be a fractional N / N+1 synthesizer. In some implementations, frequency input can be provided by a voltage-controlled oscillator (VCO) . Divider control input can be provided by either baseband circuitry 804 or the applications circuitry 802 depending on the desired output frequency. In some implementations, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications circuitry 802.
[0106] Synthesizer circuitry 806D of RF circuitry 806 can include a divider, a delay-locked loop (DLL) , a multiplexer, and a phase accumulator. In some implementations, the divider can be a dual modulus divider (DMD) , and the phase accumulator can be a digital phase accumulator (DPA) . In some implementations, the DMD can be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example implementations, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these implementations, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
[0107] In some implementations, synthesizer circuitry 806D can be configured to generate a carrier frequency as the output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some implementations, the output frequency can be a LO frequency (fLO) . In some implementations, RF circuitry 806 can include an in-phase / quadrature (I / Q) / polar converter.
[0108] FEM circuitry 808 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 810, amplify the received signals and provide the amplified versions of the received signals to RF circuitry 806 for further processing. FEM circuitry 808 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by RF circuitry 806 for transmission by one or more of the one or more antennas 810. In various implementations, the amplification through the transmit or receive signal paths can be done solely in RF circuitry 806, solely in FEM circuitry 808, or in both RF circuitry 806 and FEM circuitry 808.
[0109] In some implementations, FEM circuitry 808 can include a transmit / receive switch to switch between transmit mode and receive mode operation. FEM circuitry 808 can include a receive signal path and a transmit signal path. The receive signal path of FEM circuitry 808 can include a low noise amplifier to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to RF circuitry 806) . The transmit signal path of FEM circuitry 808 can include a power amplifier to amplify input RF signals (e.g., provided by RF circuitry 806) , and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of one or more antennas 810) .
[0110] In some implementations, PMC 812 can manage power provided to baseband circuitry 804. In particular, PMC 812 can control power-source selection, voltage scaling, battery charging, or direct current (DC) to DC (DC-to-DC) conversion. PMC 812 can often be included when device 800 is capable of being powered by a battery, for example, when device 800 is included in a UE. PMC 812 can increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
[0111] While Fig. 8 shows PMC 812 coupled only with baseband circuitry 804. However, in other implementations, PMC 812 can be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 802, RF circuitry 806, or FEM circuitry 808.
[0112] In some implementations, PMC 812 can control, or otherwise be part of, various power saving mechanisms of device 800. For example, if device 800 is in an RRC_Connected state, where device 800 is still connected to the RAN node as device 800 expects to receive traffic shortly, then device 800 can enter a state known as discontinuous reception mode (DRX) after a period of inactivity. During this state, device 800 can power down for brief intervals of time and thus save power.
[0113] If there is no data traffic activity for an extended period of time, then device 800 can transition off to an RRC_Idle state, where device 800 disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. Device 800 can go into a very low power state and device 800 can perform paging where again device 800 periodically can wake up to listen to the network and then power down again. Device 800 may not receive data in this state; in order to receive data, device 800 can transition back to RRC_Connected state.
[0114] An additional power saving mode can allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours) . During this time, the device 800 can be unreachable to the network and can power down completely. Any data sent during this time can incur a large delay and device 800 can assume the delay is acceptable.
[0115] Processors of application circuitry 802 and processors of baseband circuitry 804 can be used to execute elements of one or more instances of a protocol stack. For example, processors of baseband circuitry 804, alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of baseband circuitry 804 can utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers) . As referred to herein, Layer 3 can comprise a radio resource control layer. As referred to herein, Layer 2 can comprise a medium access control layer, a radio link control layer, and a packet data convergence protocol layer, described in further detail below. As referred to herein, Layer 1 can comprise a physical layer of a UE / RAN node.
[0116] Fig. 9 is a diagram of example interfaces 900 of baseband circuitry according to one or more implementations described herein. One or more components or features of example interfaces 900 can correspond to one or more components or features described above or elsewhere. Baseband circuitry 904 can comprise processors 904A, 904B, 904C, 904D, and 904E and a memory 904G utilized by said processors. Each of processors 904A, 904B, 904C, 904D, and 904E can include a memory interface, 906A, 906B, 906C, 906D, and 906E, respectively, to send / receive data to / from memory 904G. Baseband circuitry can be a component of a UE and / or another type of device or system capable of transmitting and / or receiving wireless signals.
[0117] Baseband circuitry 904 can further include one or more interfaces to communicatively couple to other circuitries / devices, such as memory interface 912 (e.g., an interface to send / receive data to / from memory external to baseband circuitry 904) , an application circuitry interface 914 (e.g., an interface to send / receive data to / from the application circuitry as described herein) , an RF circuitry interface 916, a wireless hardware connectivity interface 918 (e.g., an interface to send / receive data to / from near field communication components, components (e.g., Low Energy) , components, and other communication components) , and a power management interface 920 (e.g., an interface to send / receive power or control signals to / from a PMC) .
[0118] Fig. 10 is a block diagram illustrating components, according to some example implementations, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Fig. 10 shows a diagrammatic representation of hardware resources 1000 including one or more processors 1010 (or processor cores) , one or more memory / storage devices 1020, and one or more communication resources 1030, each of which can be communicatively coupled via a bus 1040. For implementations where node virtualization or network function virtualization is utilized, a hypervisor can be executed to provide an execution environment for one or more network slices / sub-slices to utilize hardware resources 1000. Hardware resources 1000 can interact with hypervisor 1002. For example, hypervisor 1002 can schedule or otherwise manage hardware resource 1000.
[0119] Processors 1010 (e.g., a central processing unit (CPU) , a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU) , a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC) , a radio-frequency integrated circuit (RFIC) , another processor, or any suitable combination thereof) can include, for example, a processor 1012 and a processor 1014.
[0120] Memory / storage devices 1020 can include main memory, disk storage, or any suitable combination thereof. Memory / storage devices 1020 can include, but are not limited to any type of volatile or non-volatile memory such as dynamic random-access memory (DRAM) , static random-access memory (SRAM) , erasable programmable read-only memory (EPROM) , electrically erasable programmable read-only memory (EEPROM) , flash memory, solid-state storage, etc.
[0121] In some implementations, memory / storage devices 1020 receive and / or store information and instructions 1055 for data collection design for AI / ML based positioning using LPP. UE 210 can provide LMF 320 with capability information relating to an ability of UE 210 to support LPP, collect positioning information, and report positioning information to LMF 320. LMF 320 can configure UE 210 to take measurements and to generate and store positioning information according to a periodicity, schedule, and / or one or more trigger events. UE 210 can report the positioning information on-demand and / or in response to one or more trigger events. Communications between UE 210 and LMF 320 can involve new and / or repurposed LPP signaling. Many other aspects and examples are also described herein.
[0122] Communication resources 1030 can include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 via a network 1008. For example, communication resources 1030 can include wired communication components (e.g., for coupling via a universal serial bus) , cellular communication components, near field communication components, components (e.g., Low Energy) , components, and other communication components.
[0123] Instructions 1050A, 1050B, 1050C, 1050D, and / or 1050E can comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of processors 1010 to perform any one or more of the methodologies discussed herein. Instructions 1050 can reside, completely or partially, within at least one of processors 1010 (e.g., within a cache memory) , memory / storage devices 1020, or any suitable combination thereof. Furthermore, any portion of instructions 1050A-E can be transferred to hardware resources 1000 from any combination of peripheral devices 1004 or databases 1006. Accordingly, memory of processors 1010, memory / storage devices 1020, peripheral devices 1004, and databases 1006 are examples of computer-readable and machine-readable media.
[0124] Fig. 11 is a diagram of an example process for process 1100 for data collection using LPP for AI / ML positioning according to one or more implementations described herein. As shown, process 1100 can be implemented by UE 210 and / or baseband circuitry 804. In some implementations, some or all of process 1100 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 1100 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 11. In some implementations, some or all of the operations of process 1100 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 1100. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 11.
[0125] As shown, process 1100 can include receiving, from a location management function (LMF) via long-term evolution (LTE) positioning protocol (LPP) , configuration information for collecting positioning data for artificial intelligence / machine learning (AI / ML) based positioning (block 1110) . Process 1100 can include measuring one or more signals in accordance with the configuration information (block 1120) . Process 1100 can include determining, based on the measuring of the one or more signals, positioning information regarding a current location of the UE (block 1130) . Process 1100 can include communicating, to the LMF via LPP, the positioning information (block 1140) . One or more of the examples described herein can also, or alternatively, be part of process 1100.
[0126] Fig. 12 is a diagram of an example process for process 1200 for data collection using LPP for AI / ML positioning according to one or more implementations described herein. As shown, process 1200 can be implemented by LMF 320, base station 222, baseband circuitry 804. In some implementations, some or all of process 1200 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 1200 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 12. In some implementations, some or all of the operations of process 1200 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 1200. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 12.
[0127] As shown, process 1200 can include communicating, to the UE via LPP, a request for UE capability information regarding LPP (block 1210) . Process 1200 can include receiving, from the UE via LPP, the UE capability information (block 1220) . Process 1200 can include receiving, from the UE via LPP, the UE capability information (block 1230) . Process 1200 can include receiving, from the UE via LPP, positioning information in accordance with the configuration information (block 1240) . One or more of the examples described herein can also, or alternatively, be part of process 1200.
[0128] Examples herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor (e.g., processor, etc. ) with memory, an application-specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to implementations and examples described.
[0129] In example 1, which can also include one or more of the examples described herein, a user equipment (UE) can comprise comprising one or more processor configured to perform operations comprising: receiving, from a location management function (LMF) via long-term evolution (LTE) positioning protocol (LPP) , configuration information for collecting positioning data for artificial intelligence / machine learning (AI / ML) based positioning; measuring one or more signals in accordance with the configuration information; determining, based on the measuring of the one or more signals, positioning information regarding a current location of the UE;and communicating, to the LMF via LPP, the positioning information.
[0130] In example 2, which can also include one or more of the examples described herein, the operations can comprise: receiving, from the LMF via LPP, a request for UE capability information regarding LPP; and providing, to the LMF via LPP, the UE capability information.
[0131] In example 3, which can also include one or more of the examples described herein, the request for UE capability information comprises at least one of: a request for an indication of whether the UE supports positioning information collection via LPP for artificial intelligence / machine learning (AI / ML) based positioning, a request for an indication of whether the UE supports a minimum buffer size for storing positioning information, a request for an indication of an actual buffer size for storing positioning information, a request for an indication of whether the UE supports reporting information positioning on-demand, a request for an indication of whether the UE supports reporting information positioning in response to one or more event triggers, or a combination thereof.
[0132] In example 4, which can also include one or more of the examples described herein, the request for UE capability information is received via a repurposed LPP ProvideCapabilities message.
[0133] In example 5, which can also include one or more of the examples described herein, the request for UE capability information is received via a repurposed LPP RequestLocationInformation message.
[0134] In example 6, which can also include one or more of the examples described herein, the request for UE capability information is received via a LPP AI / MLAssistanceInformation message.
[0135] In example 7, which can also include one or more of the examples described herein, the UE capability information comprises at least one of: an indication of whether the UE supports positioning information collection via LPP for artificial intelligence / machine learning (AI / ML) based positioning, an indication of whether the UE supports a minimum buffer size for storing positioning information, an indication of an actual buffer size for storing positioning information, an indication of whether the UE supports reporting information positioning on-demand, an indication of whether the UE supports reporting information positioning in response to one or more event triggers, or a combination thereof.
[0136] In example 8, which can also include one or more of the examples described herein, the UE capability information comprises at least one of: an indication of whether the UE supports a first reporting information positioning in response to a first event trigger, and an indication of whether the UE supports a second reporting information positioning in response to a second event trigger, wherein the first event trigger is different than the second event trigger.
[0137] In example 9, which can also include one or more of the examples described herein, the configuration information comprises an indication of a measurement resource and one or more measurement metrics for the measuring and the determining the position information.
[0138] In example 10, which can also include one or more of the examples described herein, the one or more measurement metrics comprise at least one of: a channel impulse response (CIR) , a power delay profile (PDP) , a delay profile (DP) . a reference signal received power (RSRP) , a reference signal received quality (RSRQ) , a received signal strength indicator (RSSI) , a reference signal received path power (RSRPP) , a reference signal time difference (RSTD) , a relative time of arrival (RTOA) , or a combination thereof.
[0139] In example 11, which can also include one or more of the examples described herein, the configuration information comprises an indication of the position information comprising the one or more measurement metrics and at least one of: a time stamp, a ground truth label, a quality indicator for measurement, a quality indicator for ground truth label, or a combination thereof.
[0140] In example 12, which can also include one or more of the examples described herein, the configuration information comprises at least one of: an indication that the UE is to measure the one or more signals periodically, an indication that the UE is to measure the one or more signals according to one or more event triggers, or a combination thereof.
[0141] In example 13, which can also include one or more of the examples described herein, the indication that the UE is to measure the one or more signals periodically comprises at least one of: an indication that the UE is to measure the one or more signals according to a periodicity, an indication that the UE is to measure the one or more signals according to a threshold counter, an indication that the UE is to measure the one or more signals according to a duration, or a combination thereof.
[0142] In example 14, which can also include one or more of the examples described herein, the indication that the UE is to measure the one or more signals according to one or more event triggers comprises at least one of: an indication that the UE is to measure the one or more signals in response to a single event trigger, an indication that the UE is to measure the one or more signals in response multiple event triggers, or a combination thereof.
[0143] In example 15, which can also include one or more of the examples described herein, the configuration information comprises at least one of: an indication that the UE is to report the positioning information on-demand, an indication that the UE is to report the positioning information periodically, the one or more signals periodically, an indication that the UE is to report the positioning information according to one or more event triggers, or a combination thereof.
[0144] In example 16, which can also include one or more of the examples described herein, the indication that the UE is to report the positioning information periodically comprises at least one of: an indication that the UE is to report the positioning information according to a periodicity, an indication that the UE is to report the positioning information according to a threshold counter, an indication that the UE is to report the positioning information according to a duration, or a combination thereof.
[0145] In example 17, which can also include one or more of the examples described herein, the indication that the UE is to report the positioning information according to one or more event triggers comprises at least one of: an indication that the UE is to report the positioning information in response to a single event trigger, an indication that the UE is to report the positioning information in response to a multiple event trigger, or a combination thereof.
[0146] In example 18, which can also include one or more of the examples described herein, the one or more operations can comprise: storing the positioning information in a memory buffer; and determining that the memory buffer is full.
[0147] In example 19, which can also include one or more of the examples described herein, the one or more operations can comprise: discontinuing the measuring of the one or more signals at least until the memory buffer is no longer full.
[0148] In example 20, which can also include one or more of the examples described herein, the one or more operations can comprise: communicating an indication to the LMF of available positioning information in response to determining that the memory buffer is full.
[0149] In example 21, which can also include one or more of the examples described herein, the one or more operations can comprise: determining that a battery power of the UE is below a battery power threshold; and communicating an indication to the LMF of available positioning information in response to determining that the memory buffer is full.
[0150] In example 22, which can also include one or more of the examples described herein, one or more server devices can be configured to implement a location management function (LMF) , the one or more server devices comprising one or more processors configured to perform operations comprising: communicating, to a user equipment (UE) via long-term evolution (LTE) positioning protocol (LPP) , configuration information for collecting positioning data for artificial intelligence / machine learning (AI / ML) based positioning; and receiving, from the UE via LPP, positioning information in accordance with the configuration information.
[0151] In example 23, which can also include one or more of the examples described herein, the one or more operations can comprise: communicating to the UE via LPP, a request for UE capability information regarding LPP; and receiving, from the UE via LPP, the UE capability information.
[0152] In example 24, which can also include one or more of the examples described herein, the UE capability information comprises at least one of: an indication of whether the UE supports positioning information collection via LPP for artificial intelligence / machine learning (AI / ML) based positioning, an indication of whether the UE supports a minimum buffer size for storing positioning information, an indication of an actual buffer size for storing positioning information, an indication of whether the UE supports reporting information positioning on-demand, an indication of whether the UE supports reporting information positioning in response to one or more event triggers, or a combination thereof.
[0153] In example 25, which can also include one or more of the examples described herein, the UE capability information comprises at least one of: an indication of whether the UE supports a first reporting information positioning in response to a first event trigger, and an indication of whether the UE supports a second reporting information positioning in response to a second event trigger, wherein the first event trigger is different than the second event trigger.
[0154] In example 26, which can also include one or more of the examples described herein, the configuration information comprises an indication of a measurement resource and one or more measurement metrics for generating the position information.
[0155] In example 27, which can also include one or more of the examples described herein, a baseband circuitry can comprise one or more processors configured to perform operations comprising: receiving, from a location management function (LMF) via long-term evolution (LTE) positioning protocol (LPP) , configuration information for collecting positioning data for artificial intelligence / machine learning (AI / ML) based positioning; measuring one or more signals in accordance with the configuration information; determining, based on the measuring of the one or more signals, positioning information regarding a current location; and communicating, to the LMF via LPP, the positioning information.
[0156] The above description of illustrated examples, implementations, aspects, etc., of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. While specific examples, implementations, aspects, etc., are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such examples, implementations, aspects, etc., as those skilled in the relevant art can recognize.
[0157] In this regard, while the disclosed subject matter has been described in connection with various examples, implementations, aspects, etc., and corresponding Figures, where applicable, it is to be understood that other similar aspects can be used or modifications and additions can be made to the disclosed subject matter for performing the same, similar, alternative, or substitute function of the subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single example, implementation, or aspect described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.
[0158] In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc. ) , the terms (including a reference to a “means” ) used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent) , even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations. In addition, while a particular feature can have been disclosed with respect to only one of several implementations, such feature can be combined with one or more other features of the other implementations as can be desired and advantageous for any given application.
[0159] As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or” . That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms “including” , “includes” , “having” , “has” , “with” , or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising. ” Additionally, in situations wherein one or more numbered items are discussed (e.g., a “first X” , a “second X” , etc. ) , in general the one or more numbered items can be distinct, or they can be the same, although in some situations the context can indicate that they are distinct or that they are the same.
[0160] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
Claims
1.A user equipment (UE) , comprising one or more processor configured to perform operations comprising:receiving, from a location management function (LMF) via long-term evolution (LTE) positioning protocol (LPP) , configuration information for collecting positioning data for artificial intelligence / machine learning (AI / ML) based positioning;measuring one or more signals in accordance with the configuration information;determining, based on the measuring of the one or more signals, positioning information regarding a current location of the UE; andcommunicating, to the LMF via LPP, the positioning information.2.The UE of claim 1, the operations further comprising:receiving, from the LMF via LPP, a request for UE capability information regarding LPP; andproviding, to the LMF via LPP, the UE capability information.3.The UE of claim 2, wherein the request for UE capability information comprises at least one of:a request for an indication of whether the UE supports positioning information collection via LPP for artificial intelligence / machine learning (AI / ML) based positioning,a request for an indication of whether the UE supports a minimum buffer size for storing positioning information,a request for an indication of an actual buffer size for storing positioning information,a request for an indication of whether the UE supports reporting information positioning on-demand,a request for an indication of whether the UE supports reporting information positioning in response to one or more event triggers, ora combination thereof.4.The UE of claim 2, wherein the request for UE capability information is received via a repurposed LPP ProvideCapabilities message or a repurposed LPP RequestLocationInformation message.5.The UE of claim 2, wherein the request for UE capability information is received via a LPP AI / MLAssistanceInformation message.6.The UE of claim 2, wherein the UE capability information comprises at least one of:an indication of whether the UE supports positioning information collection via LPP for artificial intelligence / machine learning (AI / ML) based positioning,an indication of whether the UE supports a minimum buffer size for storing positioning information,an indication of an actual buffer size for storing positioning information,an indication of whether the UE supports reporting information positioning on-demand,an indication of whether the UE supports reporting information positioning in response to one or more event triggers, ora combination thereof.7.The UE of claim 2, wherein the UE capability information comprises at least one of:an indication of whether the UE supports a first reporting information positioning in response to a first event trigger, andan indication of whether the UE supports a second reporting information positioning in response to a second event trigger,wherein the first event trigger is different than the second event trigger.8.The UE of claim 1, wherein the configuration information comprises an indication of a measurement resource and one or more measurement metrics for the measuring and the determining the position information.9.The UE of claim 8, wherein the one or more measurement metrics comprise at least one of:a channel impulse response (CIR) ,a power delay profile (PDP) ,a delay profile (DP) .a reference signal received power (RSRP) ,a reference signal received quality (RSRQ) ,a received signal strength indicator (RSSI) ,a reference signal received path power (RSRPP) ,a reference signal time difference (RSTD) ,a relative time of arrival (RTOA) , ora combination thereof.10.The UE of claim 8, wherein the configuration information comprises an indication of the position information comprising the one or more measurement metrics and at least one of:a time stamp,a ground truth label,a quality indicator for measurement,a quality indicator for ground truth label, ora combination thereof.11.The UE of claim 1, wherein the configuration information comprises at least one of:an indication that the UE is to measure the one or more signals periodically,an indication that the UE is to measure the one or more signals according to one or more event triggers, ora combination thereof.12.The UE of claim 11, wherein the indication that the UE is to measure the one or more signals periodically comprises at least one of:an indication that the UE is to measure the one or more signals according to a periodicity,an indication that the UE is to measure the one or more signals according to a threshold counter,an indication that the UE is to measure the one or more signals according to a duration, ora combination thereof.13.The UE of claim 11, wherein the indication that the UE is to measure the one or more signals according to one or more event triggers comprises at least one of:an indication that the UE is to measure the one or more signals in response to a single event trigger,an indication that the UE is to measure the one or more signals in response multiple event triggers, ora combination thereof.14.The UE of claim 1, wherein the configuration information comprises at least one of:an indication that the UE is to report the positioning information on-demand,an indication that the UE is to report the positioning information periodically,the one or more signals periodically,an indication that the UE is to report the positioning information according to one or more event triggers, ora combination thereof.15.The UE of claim 14, wherein the indication that the UE is to report the positioning information periodically comprises at least one of:an indication that the UE is to report the positioning information according to a periodicity,an indication that the UE is to report the positioning information according to a threshold counter,an indication that the UE is to report the positioning information according to a duration, ora combination thereof.16.The UE of claim 14, wherein the indication that the UE is to report the positioning information according to one or more event triggers comprises at least one of:an indication that the UE is to report the positioning information in response to a single event trigger,an indication that the UE is to report the positioning information in response to a multiple event trigger, ora combination thereof.17.One or more server devices configured to implement a location management function (LMF) , the one or more server devices comprising one or more processors configured to perform operations comprising:communicating, to a user equipment (UE) via long-term evolution (LTE) positioning protocol (LPP) , configuration information for collecting positioning data for artificial intelligence / machine learning (AI / ML) based positioning; andreceiving, from the UE via LPP, positioning information in accordance with the configuration information.18.The one or more server devices of claim 21, the operations comprising:communicating, to the UE via LPP, a request for UE capability information regarding LPP; andreceiving, from the UE via LPP, the UE capability information.19.The one or more server devices of claim 22, wherein the UE capability information comprises at least one of:an indication of whether the UE supports positioning information collection via LPP for artificial intelligence / machine learning (AI / ML) based positioning,an indication of whether the UE supports a minimum buffer size for storing positioning information,an indication of an actual buffer size for storing positioning information,an indication of whether the UE supports reporting information positioning on-demand,an indication of whether the UE supports reporting information positioning in response to one or more event triggers, ora combination thereof.20.Baseband circuitry comprising one or more processors configured to perform operations comprising:receiving, from a location management function (LMF) via long-term evolution (LTE) positioning protocol (LPP) , configuration information for collecting positioning data for artificial intelligence / machine learning (AI / ML) based positioning;measuring one or more signals in accordance with the configuration information;determining, based on the measuring of the one or more signals, positioning information regarding a current location; andcommunicating, to the LMF via LPP, the positioning information.