Analytics-assisted positioning ue management function

ZA202610020APending Publication Date: 2026-10-28INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
ZA202610020
Authority / Receiving Office
ZA · ZA
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-05-10
Filing Date
2026-10-16
Publication Date
2026-10-28

AI Technical Summary

Technical Problem

Existing location services in 3GPP systems face delays and degraded performance due to reactive selection and configuration of positioning UEs, leading to inaccurate or outdated location information, especially when direct UE access is unavailable or QoS requirements are not met.

Method used

Implement an analytics-assisted Positioning UE Management (PUM) function that proactively collects predictive information to dynamically select and configure positioning UEs, enhancing location services by generating analytics output for improved UE management.

Benefits of technology

The PUM function ensures timely and accurate location information by anticipating UE dynamics, reducing delays and failures in obtaining required location data.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

NOT VISIBLE DUE TO STATUS OF PATENT
Need to check novelty before this filing date? Find Prior Art

Description

ANALYTICS-ASSISTED POSITIONINGUE MANAGEMENT FUNCTIONCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 645,389, filed May 10, 2024, which is hereby incorporated by reference in its entirety.BACKGROUND

[0002] Using reference user equipments (UEs) (e.g. vehicles) and indirect positioning in a location service for tracking a mobile UE (drone) may result in delays and degraded performance during the configuration of a target and reference UE. By the time the configuration is complete, location data may be inaccurate and / or outdated. A system may not be able to take proactive actions to update the selection and configuration of positioning UEs, which may result in degraded performance or even failure to obtain the required location information. Accordingly, there is a need for a mechanism for proactive selection and configuration of positioning UEs.SUMMARY

[0003] This Summary' is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to limitations that solve any or all disadvantages noted in any part of this disclosure.

[0004] Methods are described herein to enable analytics-assisted positioning UE management (PUM) function. Location services in the 3GPP system may not always be able to obtain the location information from a target UE / object directly (e.g. UE is out of coverage or unavailable), or the QoS (e.g. accuracy, granularity) of the obtained location information may not meet certain requirements. In such cases, the location service may derive the location information of the target UE / object indirectly based on the location information of a referenceUE and the relative location / position information of the target regarding the reference UE. Existing services select and configure target and reference UEs based on the current status and conditions of UEs and take reactive actions for updating the selection and configuration. However, due to dynamics in the system, such fixed and reactive management approach may result in degraded performance or even failure to obtain the required location information. In with one embodiment, an analytics-assisted PUM function enables dynamic and proactive selection and configuration of positioning UEs. including target and reference UEs. The analytics-assisted PUM function may enhance the location services in 3GPP systems by: collecting predictive information of positioning UEs and determining positioning UE selection and configuration proactively; generating positioning UE related analytics output to assist the location service in selecting and configuring positioning UEs; generating enhanced location and mobility analytics with positioning UEs determined by the PUM function.BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In order to facilitate a more robust understanding of the application, reference is now made to the accompanying drawings, in which like elements are referenced with like numerals. These drawings should not be construed to limit the application and are intended only to be illustrative.

[0006] FIG. 1 is a system diagram of an example machine-to-machine (M2M), Internet of Things (loT), or Web of Things (WoT) communication system in which one or more disclosed embodiments may be implemented;

[0007] FIG. 2 is a system diagram of an example architecture that may be used within the M2M / IoT / WoT communications system illustrated in FIG. 1;

[0008] FIG. 3 is a system diagram of an example communication network node, such as an M2M / IoT / WoT device, gateway, or server that may be used within the communications system illustrated in FIGs. 1 and 2;

[0009] FIG. 4 is a block diagram of an example computing system in which a node of the communication system of FIG. 1 and 2 may be embodied;

[0010] FIG. 5 shows an example of indirect positioning using reference UEs;

[0011] FIG. 6 shows an example use case;

[0012] FIG. 7 shows an example procedure for a PUM-enhanced location service;

[0013] FIG. 8 shows an example service procedure with PUM functioning as enhanced LMS;

[0014] FIG. 9 shows an example service procedure with PUM functioning as new analytics ID;

[0015] FIG. 10 shows an example service procedure with PUM functioning as enhancements to location analytics; and

[0016] FIG. 11 shows an example graphical user interface (GUI).DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

[0017] Methods are descnbed herein to enable analytics-assisted PUM function.

[0018] The following abbreviations are described herein:

[0019] Definitions for the following terms, per their intended meaning and usage herein, are provided below for reference:

[0020] FIG. 1 is a diagram of an example machine-to machine (M2M). Internet of Things (loT), or Web of Things (WoT) communication system 10 in which one or more disclosed embodiments may be implemented. Generally, M2M technologies provide building blocks for the IOT / WOT, and any M2M device, M2M gateway, M2M server, or M2M service platform may be a component or node of the IoT / WoT as well as an IoT / WoT Service Layer, etc. Any of the client, proxy, or server devices illustrated in any of FIGs. 5-11 may comprise anode of a communication system, such as the ones illustrated in FIGs. 5-11.

[0021] The service layer may be a functional layer within a network service architecture. Service layers are typically situated above the application protocol layer such asHTTP, CoAP or MQTT and provide value added services to client applications. The service layer also provides an interface to core networks at a lower resource layer, such as for example, a control layer and transport / access layer. The service layer supports multiple categories of (service) capabilities or functionalities including a service definition, service runtime enablement, policy management, access control, and service clustering. Recently, several industry standards bodies, e.g., oneM2M, have been developing M2M service layers to address the challenges associated with the integration of M2M types of devices and applications into deployments such as the Intemet / Web, cellular, enterprise, and home networks. A M2M service layer can provide applications and / or various devices with access to a collection of or a set of the above mentioned capabilities or functionalities, supported by the service layer, which can be referred to as a CSE or SCL. A few examples include but are not limited to security, charging, data management, device management, discovery, provisioning, and connectivity management which can be commonly used by various applications. These capabilities or functionalities are made available to such various applications via APIs which make use of message formats, resource structures and resource representations defined by the M2M service layer. The CSE or SCL is a functional entity that may be implemented by hardware and / or software and that provides (service) capabilities or functionalities exposed to various applications and / or devices (i.e., functional interfaces between such functional entities) in order for them to use such capabilities or functionalities.

[0022] As shown in FIG. 1, the M2M / I0T / W0T communication system 10 includes a communication network 12. The communication network 12 may be a fixed network (e.g., Ethernet, Fiber, ISDN, PLC, or the like) or a wireless network (e.g., WLAN, cellular, or the like) or a netw ork of heterogeneous netw orks. For example, the communication network 12 may be comprised of multiple access networks that provide content such as voice, data, video, messaging, broadcast, or the like to multiple users. For example, the communication network 12 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and the like. Further, the communication network 12 may comprise other networks such as a core network, the Internet, a sensor network, an industrial control network, a personal area network, a fused personal network, a satellite network, a home network, or an enterprise netw ork for example.

[0023] As shown in FIG. 1, the M2M / IOT / WOT communication system 10 may include the Infrastructure Domain and the Field Domain. The Infrastructure Domain refers to the network side of the end-to-end M2M deployment, and the Field Domain refers to the area networks, usually behind an M2M gateway. The Field Domain and Infrastructure Domain may both comprise a variety of different nodes (e.g., servers, gateways, device, and the like) of the network. For example, the Field Domain may include M2M gateways 14 and devices 18. It will be appreciated that any number of M2M gateway devices 14 and M2M devices 18 may be included in the M2M / IoT / WoT communication system 10 as desired. Each of the M2M gateway devices 14 and M2M devices 18 are configured to transmit and receive signals, using communications circuitry, via the communication network 12 or direct radio link. A M2M gateway 14 allows wireless M2M devices (e.g., cellular and non-cellular) as well as fixed network M2M devices (e.g.. PLC) to communicate either through operator networks, such as the communication network 12 or direct radio link. For example, the M2M devices 18 may collect data and send the data, via the communication network 12 or direct radio link, to an M2M application 20 or other M2M devices 18. The M2M devices 18 may also receive data from the M2M application 20 or an M2M device 18. Further, data and signals may be sent to and received from the M2M application 20 via an M2M Service Layer 22, as described below. M2M devices 18 and gateways 14 may communicate via various networks including, cellular, WLAN, WPAN (e.g., Zigbee, 6L0WPAN, Bluetooth), direct radio link, and wireline for example. Exemplary M2M devices include, but are not limited to, tablets, smart phones, medical devices, temperature and weather monitors, connected cars, smart meters, game consoles, personal digital assistants, health and fitness monitors, lights, thermostats, appliances, garage doors and other actuator-based devices, security devices, and smart outlets.

[0024] Referring to FIG. 2. the illustrated M2M Service Layer 22 in the field domain provides sendees for the M2M application 20, M2M gateways 14. and M2M devices 18 and the communication network 12. It will be understood that the M2M Service Layer 22 may communicate with any number of M2M applications, M2M gateways 14, M2M devices 18, and communication netw orks 12 as desired. The M2M Service Layer 22 may be implemented by one or more nodes of the network, which may comprise servers, computers, devices, or the like. The M2M Service Layer 22 provides service capabilities that apply to M2M devices 18. M2M gateways 14, and M2M applications 20. The functions of the M2M Service Layer 22may be implemented in a variety of ways, for example as a web server, in the cellular core network, in the cloud, etc.

[0025] Similar to the illustrated M2M Service Layer 22, there is the M2M Sendee Layer 22’ in the Infrastructure Domain. M2M Service Layer 22’ provides services for the M2M application 20’ and the underlying communication network 12 in the infrastructure domain. M2M Service Layer 22’ also provides services for the M2M gateways 14 and M2M devices 18 in the field domain. It will be understood that the M2M Service Layer 22' may communicate with any number of M2M applications. M2M gateways and M2M devices. The M2M Service Layer 22’ may interact with a Service Layer by a different service provider. The M2M Service Layer 22’ may be implemented by one or more nodes of the network, which may comprise servers, computers, devices, virtual machines (e.g., cloud computing / storage farms, etc.) or the like.

[0026] Referring also to FIG. 2, the M2M Service Layers 22 and 22’ provide a core set of service delivery capabilities that diverse applications and verticals may leverage. These sen ice capabilities enable M2M applications 20 and 20’ to interact with devices and perform functions such as data collection, data analysis, device management, security, billing, service / device discovery, etc. Essentially, these service capabilities free the applications of the burden of implementing these functionalities, thus simplifying application development and reducing cost and time to market. The Service Layers 22 and 22' also enable M2M applications 20 and 20’ to communicate through various networks such as network 12 in connection with the services that the Service Layers 22 and 22’ provide.

[0027] The M2M applications 20 and 20’ may include applications in various industries such as, without limitation, transportation, health and wellness, connected home, energy management, asset tracking, and security and surveillance. As mentioned above, the M2M Service Layer, running across the devices, gateways, servers and other nodes of the system, supports functions such as, for example, data collection, device management, security, billing, location tracking / geofencing, device / service discovery, and legacy systems integration, and provides these functions as services to the M2M applications 20 and 20’.

[0028] Generally, a Service Layer, such as the Service Layers 22 and 22’ illustrated in FIG. 2, defines a software middleware layer that supports value-added service capabilities through a set of Application Programming Interfaces (APIs) and underlying networking interfaces. Both the ETSI M2M and oneM2M architectures define a Service Layer. ETSIM2M’s Service Layer is referred to as the Service Capability Layer (SCL). The SCL may be implemented in a variety of different nodes of the ETSI M2M architecture. For example, an instance of the Service Layer may be implemented within an M2M device (where it is referred to as a device SCL (DSCL)), a gateway (where it is referred to as a gateway SCL (GSCL)) and / or a network node (where it is referred to as a network SCL (NSCL)). The oneM2M Service Layer supports a set of Common Service Functions (CSFs) (i.e., service capabilities). An instantiation of a set of one or more particular types of CSFs is referred to as a Common Services Entity (CSE) which may be hosted on different types of network nodes (e.g.. infrastructure node, middle node, application-specific node). The Third Generation Partnership Project (3GPP) has also defined an architecture for machine-type communications (MTC). In that architecture, the Service Layer, and the service capabilities it provides, are implemented as part of a Service Capability Server (SCS). Whether embodied in a DSCL, GSCL, or NSCL of the ETSI M2M architecture, in a Service Capability Server (SCS) of the 3GPP MTC architecture, in a C SF or C SE of the oneM2M architecture, or in some other node of a network, an instance of the Service Layer may be implemented as a logical entity (e g., software, computer-executable instructions, and the like) executing either on one or more standalone nodes in the network, including servers, computers, and other computing devices or nodes, or as part of one or more existing nodes. As an example, an instance of a Service Layer or component thereof may be implemented in the form of software running on a network node (e.g., server, computer, gateway, device or the like) having the general architecture illustrated in FIG. 3 or FIG. 4 described below.

[0029] Further, the methods and functionalities described herein may be implemented as part of an M2M network that uses a Service Oriented Architecture (SOA) and / or a Resource- Oriented Architecture (ROA) to access services.

[0030] FIG. 3 is a block diagram of an example hardware / software architecture of a node of anetwork, such as one of the clients, servers, or proxies illustrated in FIGs. 5-11, which may operate as an M2M server, gateway, device, or other node in an M2M network such as that illustrated in FIGs. 5-11. As shown in FIG. 3, the node 30 may include a processor 32, non-removable memory 44, removable memory 46. a speaker / microphone 38, a keypad 40, a display, touchpad, and / or indicators 42, a power source 48, a global positioning system (GPS) chipset 50, and other peripherals 52. The node 30 may also include communication circuitry, such as a transceiver 34 and a transmit / receive element 36. It will be appreciated that the node30 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment. This node may be a node that implements the methods described herein, e.g., in relation to the methods described in reference to FIGs. 5-11 or the data structures of FIGs. 5-11, Tables 1-9, or in a claim.

[0031] The processor 32 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association wi th a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs). Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. In general, the processor 32 may execute computer-executable instructions stored in the memory (e.g., memory 44 and / or memory 46) of the node in order to perform the various required functions of the node. For example, the processor 32 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the node 30 to operate in a wireless or wired environment. The processor 32 may run application-layer programs (e.g., browsers) and / or radio access-layer (RAN) programs and / or other communications programs. The processor 32 may also perform security’ operations such as authentication, security key agreement, and / or cryptographic operations, such as at the access-layer and / or application layer for example.

[0032] As shown in FIG. 3, the processor 32 is coupled to its communication circuitry’ (e.g., transceiver 34 and transmit / receive element 36). The processor 32, through the execution of computer executable instructions, may control the communication circuitry in order to cause the node 30 to communicate with other nodes via the network to which it is connected. In particular, the processor 32 may control the communication circuitry' in order to perform the methods described herein, e.g., in relation to FIGs. 5-11, or in a claim. While FIG. 3 depicts the processor 32 and the transceiver 34 as separate components, it will be appreciated that the processor 32 and the transceiver 34 may be integrated together in an electronic package or chip.

[0033] The transmit / receive element 36 may be configured to transmit signals to, or receive signals from, other nodes, including M2M servers, gateways, device, and the like. For example, in an embodiment, the transmit / receive element 36 may be an antenna configured to transmit and / or receive RF signals. The transmit / receive element 36 may support various networks and air interfaces, such as WLAN, WPAN, cellular, and the like. In an embodiment, the transmit / receive element 36 may be an emitter / detector configured to transmit and / orreceive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 36 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit / receive element 36 may be configured to transmit and / or receive any combination of wireless or wired signals.

[0034] In addition, although the transmit / receive element 36 is depicted in FIG. 3 as a single element, the node 30 may include any number of transmit / receive elements 36. More specifically, the node 30 may employ MIMO technology. Thus, in an embodiment, the node 30 may include two or more transmit / receive elements 36 (e.g.. multiple antennas) for transmitting and receiving wireless signals.

[0035] The transceiver 34 may be configured to modulate the signals that are to be transmitted by the transmit / receive element 36 and to demodulate the signals that are received by the transmit / receive element 36. As noted above, the node 30 may have multi-mode capabilities. Thus, the transceiver 34 may include multiple transceivers for enabling the node 30 to communicate via multiple RATs, such as UTRA and IEEE 802. 11, for example.

[0036] The processor 32 may access information from, and store data in, any ty pe of suitable memory, such as the non-removable memory 44 and / or the removable memory 46. For example, the processor 32 may store session context in its memory, as described above. The non-removable memory 44 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other ty pe of memory7storage device. The removable memory 46 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 32 may access information from, and store data in, memory that is not physically located on the node 30, such as on a server or a home computer. The processor 32 may be configured to control lighting patterns, images, or colors on the display or indicators 42.

[0037] The processor 32 may receive power from the power source 48, and may be configured to distribute and / or control the power to the other components in the node 30. The power source 48 may be any suitable device for powering the node 30. For example, the power source 48 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0038] The processor 32 may also be coupled to the GPS chipset 50, which is configured to provide location information (e.g., longitude and latitude) regarding the currentlocation of the node 30. It will be appreciated that the node 30 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0039] The processor 32 may further be coupled to other peripherals 52, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity'. For example, the peripherals 52 may include various sensors such as an accelerometer, biometrics (e.g., finger print) sensors, an e- compass. a satellite transceiver, a sensor, a digital camera (for photographs or video), a universal serial bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

[0040] The node 30 may be embodied in other apparatuses or devices, such as a sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, truck, train, or airplane. The node 30 may connect to other components, modules, or systems of such apparatuses or devices via one or more interconnect interfaces, such as an interconnect interface that may comprise one of the peripherals 52.

[0041] FIG. 4 is a block diagram of an exemplary' computing system 90 which may also be used to implement one or more nodes of a network, such as the clients, servers, or proxies illustrated in FIGs. 5-11, which may operate as an M2M server, gateway, device, or other node in an M2M network such as that illustrated in FIGs. 5-11.

[0042] Computing system 90 may comprise a computer or server and may be controlled primarily by computer readable instructions, which may be in the form of software, wherever, or by whatever means such software is stored or accessed. Such computer readable instructions may be executed within a processor, such as central processing unit (CPU) 91, to cause computing system 90 to do work. In many known workstations, servers, and personal computers, central processing unit 91 is implemented by a single-chip CPU called a microprocessor. In other machines, the central processing unit 91 may comprise multiple processors. Coprocessor 81 is an optional processor, distinct from main CPU 91, that performs additional functions or assists CPU 91. CPU 91 and / or coprocessor 81 may receive, generate,and process data related to the disclosed systems and methods for E2E M2M Service Layer sessions, such as receiving session credentials or authenticating based on session credentials.

[0043] In operation, CPU 91 fetches, decodes, and executes instructions, and transfers information to and from other resources via the computer’s main data-transfer path, system bus 80. Such a system bus connects the components in computing system 90 and defines the medium for data exchange. System bus 80 ty pically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0044] Memories coupled to system bus 80 include random access memory' (RAM) 82 and read only memory' (ROM) 93. Such memories include circuitry that allows information to be stored and retrieved. ROMs 93 generally contain stored data that cannot easily be modified. Data stored in RAM 82 may be read or changed by CPU 91 or other hardware devices. Access to RAM 82 and / or ROM 93 may be controlled by memory controller 92. Memory controller 92 may provide an address translation function that translates virtual addresses into physical addresses as instructions are executed. Memory controller 92 may also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in a first mode may access only memory' mapped by its own process virtual address space; it cannot access memory within another process’s virtual address space unless memory sharing between the processes has been set up.

[0045] In addition, computing system 90 may contain peripherals controller 83 responsible for communicating instructions from CPU 91 to peripherals, such as printer 94, keyboard 84, mouse 95, and disk drive 85.

[0046] Display 86. which is controlled by display controller 96. is used to display visual output generated by computing system 90. Such visual output may include text, graphics, animated graphics, and video. Display 86 may be implemented with a CRT-based video display, an LCD-based flat-panel display, gas plasma-based flat-panel display, or a touch-panel. Display controller 96 includes electronic components required to generate a video signal that is sent to display 86.

[0047] Further, computing system 90 may' contain communication circuitry, such as for example a network adaptor 97, that may be used to connect computing system 90 to anexternal communications network, such as network 12 of FIGs. 1-4, to enable the computing system 90 to communicate with other nodes of the network.

[0048] Location information of a target UE / object. such as its geographical coordinates or area, position, orientation, direction, etc. can be obtained via a location service in 3GPP system such as LMF and SEAL location management server. For example, 3GPP defines location management sendee in SEAL that offers the location management related capabilities to one or more vertical applications. Location information of VAL service may be provided by the location management client on the UE to the location management server. The location information reporting triggers are based on the location reporting configuration. Different types of location information can be provided.

[0049] FIG. 5 show s an example of indirect positioning using reference UEs 500. In some scenarios, it may not be possible for the location service to obtain the location information from the target UE / object directly (e.g. UE is out of coverage or unavailable), or the QoS of the obtained location information does not meet certain requirements. In such cases, as shown in FIG. 5, the location service may obtain the location information of the target UE / object indirectly with the assistance of UEs in the vicinity of the target UE / object, i.e. reference UEs. The location service may calculate the location information of the target UE / object based on the location information of the reference UE and the relative location / position information of the target regarding the reference UE.

[0050] The reference UEs may utilize positioning methods (including both 3GPP methods and non 3 GPP methods) and / or services such as ranging (as defined in 3 GPP TS 23.586 vl 8.3.0), sensing, or application layer methods to measure the relative location / position of the target UE / object. For example, 3GPP system supports Sidelink positioning and ranging which refers to the determination of the distance between two UEs or more UEs and / or the direction of one UE (i.e. target UE) from another UE (i.e. reference UE) via PC5 interface. Particularly, a sidelink reference UE is defined in 3GPP TS 23.586 vl 8.3.0 as a UE supporting positioning of target UE, e.g. by transmitting and / or receiving reference signals for positioning, providing positioning-related information, etc. using Sidelink.

[0051] FIG. 6 shows an example use case 600 of using reference UEs (e.g. vehicles) and indirect positioning in a location service for tracking a mobile UE (drone). At time period 1, vehicle A, B and C may be selected as reference UEs as they are in the vicinity of the target. Later in time period2, the target moves to a new' location. Vehicle A and B may still functionas the reference UEs as they are moving in the same direction as the target, but Vehicle C has moved out of the v icinity of the target, thus Vehicle C is removed from the reference UE list. Vehicle D comes into the vicinity of the target and can be selected to be a reference UE. The system may configure Vehicle D and the target to establish connection between them and enable positioning operations.

[0052] In the use case example, Vehicle D is added to the reference UE list after the system detects it moves into the vicinity of the target. However, the configuration of the target and reference UE may introduce additional delay. By the time the configuration is complete. Vehicle D may have already moved out of the vicinity of the target as it is moving in the opposite direction of the target. It can be seen that if the positioning UE selection and configuration only rely on the current status and condition, the system may not be able to take proactive actions to update the selection and configuration of positioning UEs, which may result in degraded performance or even failure to obtain the required location information. In other words, there is a lack of a mechanism for proactive selection and configuration of Positioning UEs rather than the current, reactive mechanism.

[0053] Methods are described herein to enable analytics-assisted PUM function. Features used in some of the examples that follow include the following:

[0054] Embodiment 1 : PUM enhanced location management service for location sendee requests

[0055] A location management server supporting PUM-enhanced location service with the following operations:

[0056] Receiving a service request, wherein the request may include identifier of a target UE / object, required location information to be provided by the location service and the corresponding QoS requirements, criteria / policies on selecting and configuring positioning UEs, area of interest, etc.

[0057] Collecting information of target UE / object and candidate UEs that may act as reference UEs, wherein the information may include UE identifier, applications associated with the UE, capability of the UE, energy information, availability of the UE, schedule of the UE, location and mobility information of the UE, configurations supported by the UE, authorization information of the UE. etc.

[0058] Determining the selection and configuration of positioning UEs based on the sendee request and the collected UE information, wherein the determination may be based onthe current or predicted information of the UEs, such as the (predicted) absolute or relative location / position of UEs, (predicted) UE av ailability. (predicted) UE load, QoS or confidence level of location information generated by the UEs, etc.

[0059] Sending messages to configure the target and selected reference UEs to perform positioning operations based on the determined configuration information, wherein the configuration information may include the positioning method, the corresponding QoS requirement, reporting configuration, etc. and the configuration information may apply to a future time period.

[0060] Receiving relative location or position information generated by the positioning operations performed by the target and reference UEs, based on which generating the required location information of the target UE / object.

[0061] Sending a message to the requestor, wherein the message may include the generated location information of the target UE / object.

[0062] Embodiment 2: PUM enhanced location management service for predictive target optimizations

[0063] A location management server supporting PUM-enhanced location serv ice with the following operations:

[0064] Receiving a first type of request or configuration message , wherein the first type of message may include criteria / policies on selecting and configuring reference UEs, e.g. an area for selecting reference UEs.

[0065] Collecting information of candidate UEs that may act as reference UEs, wherein the information may include UE identifier, applications associated with the UE, capability of the UE, policies associated with the UE, providers (e.g. MNO, service provider) associated with the UE, energy information, availability of the UE, schedule of the UE, location and mobility information of the UE, configurations supported by the UE, authorization information of the UE, etc.

[0066] Determining the selection and configuration of reference UEs based on the received request and the collected UE information, wherein the determination may be based on the current or predicted information of the UEs, such as the (predicted) absolute or relative location / position of UEs, (predicted) UE availability, (predicted) UE load, QoS or confidence level of location information generated by the UEs, etc.

[0067] Sending a second type of request or configuration message to configure the selected reference UEs to perform positioning operations based on the message information, wherein the message information may include criteria for determining positioning target UEs or objects, the positioning method, the corresponding QoS requirement, reporting configuration, etc. and the configuration information may apply to a future time period.

[0068] Receiving positioning information generated by the reference UEs for one or more target UEs / objects identified from the given criteria for positioning target UEs or objects.

[0069] Generating comprehensive location information of the target UE / object based on information including the received positioning information.

[0070] The server in embodiment 2 above, where the criteria for determining positioning target UEs or objects is provided to the sen- er by the requestor in the first type of request or configuration message.

[0071] The server in embodiment 2 above, where the criteria for determining positioning target UEs or objects is provided to the server via pre-provisioning or local policies.

[0072] The server in embodiment 2 above, where the criteria for determining positioning target UEs or objects is determined by the server based in part on one or more messages received from other entities.

[0073] Embodiment 3: Positioning UE related analytics ID

[0074] An analytics service supporting positioning UE related analytics ID with the following operations:

[0075] Receiving an analytics service request from a location service, wherein the request may include analytics ID, identifier of a target UE / object, analytics period, required analytics information to be provided by the analytics service and the corresponding confidence level, criteria / policies on selecting and configuring positioning UEs, area of interest, etc.

[0076] Collecting analytics input including information of target UE / object and candidate UEs that may act as reference UEs, wherein the information may include UE identifier, (predicted) location and mobility7information of the UE, and other information as described in embodiment 1 , etc.

[0077] Generating analytics output such as the selection and configuration of positioning UEs for a future time period, wherein the analytics output may be generated based on the analytics service request and the current and / or predicted information of the UEs.

[0078] Sending a message to the requesting location service, wherein the message may include the generated analytics output.

[0079] Embodiment 4: PUM-enhanced location analytics ID

[0080] An analytics service supporting PUM-enhanced location analytics ID with the following operations:

[0081] Receiving an analytics service request, wherein the request may include analytics ID, identifier of a target UE / object, analytics period, required analytics information to be provided by the analytics service and the corresponding confidence level, area of interest, etc.

[0082] Collecting analytics input including information of target UE / object and candidate UEs that may act as reference UEs, wherein the information may include UE identifier, (predicted) location and mobility information of the UE, and other information as described in embodiment 1, etc.

[0083] Determining the selection and configuration of positioning UEs based on the sendee request and the collected UE information, wherein the determination may be based on the current or predicted information of the UEs.

[0084] Sending a request to a location service for relative location / position information regarding a target UE / object and one or more reference UEs, wherein the request may include information of the selected positioning UEs and their configurations determined by the analytics service.

[0085] Receiving relative location / position information from the location service as a response to the previous step.

[0086] Generating analytics output such as the predicted location information of the target UE / object for a future time period, wherein the analytics output may be generated based on the analytics service request, current and / or predicted information of the UEs, and the received relative location / position information.

[0087] Sending a message to the analytics service requestor, wherein the message may include the generated analy tics output.

[0088] The proposed Positioning UE Management (PUM) function may assist the location services in the 3GPP system in managing the selection and configuration of Positioning UEs. which may be used for obtaining or calculating location information of a target UE / object indirectly using relative location / position information.

[0089] In an example, a server for reference UE management, may receive a message indicating a request to determine and configure one or more reference user equipments (UEs), wherein the one or more reference UEs are used to support measuring location information of a target UE. The server may comprise a 3GPP SEAL location management server. The message may comprise an identifier of the target UE and / or a list of the one or more candidate reference UEs or selection criteria of the one or more reference UEs. The server may receive capability information of the target UE and one or more candidate reference UEs. The server may request, from an analytics service, predicted location information of the target UE and the one or more candidate reference UEs. The server may receive, from the analytics service, the predicted location information. Based on the message, the received capability7information, and the predicted location information, the server may determine one or more reference UEs from the one or more candidate reference UEs. The server may send, to each reference UE of the determined one or more reference UEs, a configuration request. The configuration request may comprise a reporting configuration, a required positioning method to be used by the determined one or more reference UEs and a schedule to use the required positioning method, and / or proactive or predictive configuration information. The required positioning method may comprise sidelink positioning or ranging. The server may receive, from the determined one or more reference UEs, positioning information. The server may request, from the analytics sendee, predicted capability’ information of the target UE and the one or more candidate reference UEs. The server may receive, from the analytics service, the predicted capability information.

[0090] FIG. 7 shows an example procedure 700 for a PUM-enhanced location service. The location service may be, for example, a location management function in the core network or in SEAL. The analytics service may be the NWDAF, ADAE, etc. The steps shown in FIG. 7 may be repeated as needed, and / or performed in a different order than shown. Note that the PUM function is shown as a standalone entity in FIG. 7, but it may be incorporated within an analytics or location service.

[0091] In the following descriptions, the terms “location”, “location sendee”, etc. are used at times to include positioning of UEs or object, i.e. to determine an overall location which may include aspects relative to other Ues and determined via positioning methods. The term “positioning” is used when only the aspects relative to other Ues are determined.

[0092] Referring to FIG. 7, at step 1, the PUM function (or the location / analytics sendee where the PUM function is integrated in) may collect information of UEs which may be the candidates for Reference UEs. The candidate UE information may be included in an application client profile and / or LMC / ADAEC profile, which may be shared with the PUM function (or the corresponding location / analytics sendee) via a registration procedure, or collected by the PUM function using request / response or subscription / notification procedure. The collected information may include information show n in Table 1. Note that the information collection procedure and the list of information in Table 1 may also apply to a target UE / object.

[0093] Location and mobility information may be collected from the core network to assist with identifying reference UE candidates.Table 1. Location / positioning service-related UE information

[0094] At step 2, the PUM function may detect positioning UE management is requested. This may be triggered when the location information of a target UE / object is requested but the location information obtained by the system does not meet the QoS requirements in the request, the target UE / object is offline or not in coverage, the target is a non-3GPP object, or it is explicitly required by the requestor, etc. A positioning UE selection and configuration task may be created accordingly. The task may be a one-time instantaneous request which the PUM function may process to select positioning UEs. Alternatively, the task may be a longstanding request in which the PUM function may select / re-select / de-select positioning UEs for a specified time duration and / or schedule. If / when positioning UEs are selected / re-selected / de-selected, the PUM function may send notifications to the relevant services or the requestor.

[0095] At step 3, as information of the UE / object may have changed (as compared to the information collected in step 1) or will change at a future time (e.g. due to mobility), the PUM function may collect updated or predictive information of the candidate UEs (potential reference UEs). such as predicted capability information, energy information, location information, mobility information, predicted UE availability and status (e.g. active, offline), etc. The PUM function may also collect current and predictive information of the targetUE / object. When collecting predictive information from an analytics service, the PUM function may also collect information of the accuracy or confidence level associated with the predictive information generated by the analytics service. The types of predictive information may involve one or more of the information elements defined in Table 1.

[0096] At step 4, the PUM function may select positioning UEs and determine the configurations of the positioning UEs based on the received UE information and service request. Particularly, the PUM function may maintain a running list of positioning UEs and update the list dynamically, as shown in Table 2.Table 2. Dynamic positioning UE configuration information

[0097] The selection and configuration of positioning UEs may be based on the information received in steps 1 to 3, including predictive information obtained from analytics services. For example:

[0098] For example, the PUM function may determine reference UEs based on whose mobility is moving towards the target UE / object and / or area of interest (or vice versa). As another example, the positioning capability' (e.g. ranging as opposed to sensing) may also determine good candidates for reference UEs.

[0099] A current reference UE may be predicted to move away from the target UE / object and / or area of interest (or vice versa) in at a future time period based on information such as the predicted location of the reference UE, predicted location of the target UE / object, predicted relative location / position between the reference UE and the target UE / object (e.g. from ranging or sensing results). In this case, the PUM function may remove the reference UE from the list in the configuration information for the upcoming time period.

[0100] A candidate UE (currently out of range of the target UE / object) may be predicted to move into the vicinity of the target UE / object and / or area of interest (or vice versa) at a future time instance and remain at the location. The candidate UE may be capable of providing positioning result with higher QoS (e.g. has ranging capability as opposed to sensing capability) as compared to the current reference UEs. The PUM function may select this UE to serve as a reference UE starting from the future time instance and proactively configure the UEto prepare for the positioning operations (e.g. requesting the candidate UE to establish sidelink connection with the target UE / object).

[0101] The target UE / object may be scheduled or predicted to be turned off due to low battery level in an upcoming time period based on the (predicted) schedule information and / or energy information of the UE. In this case, the PUM function may configure the reference UEs to switch to a new positioning method (e.g. from ranging to sensing) or re-select reference UEs which can support the new positioning method. The newly selected reference UEs may be configured proactively to support the positioning operations.

[0102] The PUM function may perform load balancing on the reference UEs if more than enough candidate UEs are available to serve as reference UEs. The PUM function may schedule different subsets of reference UEs to perform location / positioning operations alternately.

[0103] The PUM function may configure reference UEs based on the accuracy or confidence level of collected / predicted information. The PUM function may detect that the accuracy of location information received from a reference UE is degrading, or the confidence level of received analytics information related to a reference UE is low, then the PUM function may exclude the reference UE from the selection and find a replacement UE with higher accuracy or confidence level.

[0104] At step 5, the selected positioning UEs may be configured (by the location service) based on the configuration information determined by the PUM function. The positioning UEs may be configured proactively based on the predictive configuration information determined by the PUM function. The PUM function may send (via the location sendee or other entities such as other positioning UEs) to positioning UEs a request comprising information which they may use to proactively schedule and configure themselves to perform positioning UE selection / de-selection operations (such as the UE configuration in Table 2). For example, the request may include information of positioning UE schedule comprising time windows of when they are to function as target / reference UEs, locations or service areas where they are to function as target / reference UEs, list of target UEs they are to provide reference UE services for, etc.

[0105] At step 6, the Positioning UEs may perform location / positioning operations and report the results to the location service.

[0106] At step 7, the required results or notification may be reported / sent to the requestor.

[0107] Steps 3 to 7 may be repeated, and their sequence may be changed depending on the use case and initial conditions of each step. In the repetitive procedure, the candidate UEs for a current round may include positioning UEs that have been selected in a previous round.

[0108] The PUM function may be implemented as part of or an enhancement to the location service and / or analytics service in the system. Examples of PUM embodiment options are described later on. The procedures in the embodiment options and the procedure in FIG. 7 may be combined.

[0109] Embodiment 1: PUM enhanced SEAL LMS

[0110] FIG. 8 shows an example service procedure 800 with a PUM-enhanced location sendee. In this example, the proposed PUM function may be implemented as an enhancement to the SEAL location management function. Note, one skilled in the art will recognize that the proposed PUM function may also be implemented as an enhancement to other location services.

[0111] Referring to FIG. 8, at step 1, the location management clients (LMCs) of candidate UEs may register to the location management server (LMS), where the registration messages may include information of the candidate UEs as shown in Table 1. The LMS may also collect information of the candidate UEs from other entities, such as the core network, other enabler layer servers, an analytics service, etc.

[0112] At step 2, the PUM-enhanced LMS may receive a location sen ice request from a requestor (e.g. a VAL server, a VAL client on UE via the LMC). The request may imply the need for PUM function. For example, the request may indicate the need for higher accurate location information and / or for the use of ranging / sensing capability for determining location information. For example, the request may require the LMS to provide the location of a target UE / object to the requestor periodically or under certain conditions, where the required location accuracy cannot be satisfied with direct location reporting as the target UE / object is alternating between on and off modes (e g. for power saving). The LMS may obtain the location information of the offline target UE / object indirectly by using Reference UEs, and may use the PUM function to perform positioning UE selection and configuration. The requestor may specify information of the target UE / object (e.g. identifier, the approximate area / location wherethe target UE is at) and / or an area of interest in the request. Optionally, the request may specify a list of candidate UEs that can be used as reference UEs, and / or the selection criteria (e.g. rules, filters, conditions on the information in Table 1). The requestor may also request the LMS to provide a list of candidate UEs. Table 3 shows example information that may be included in the location service request.Table 3. Location service request

[0113] After receiving the request, the PUM-enhanced LMS may create a positioning UE selection and configuration task, as described in step 2 of FIG. 7.

[0114] At step 3, if the request received in step 2 has specified a target UE / object, then the LMS may collect information of the target UE / object. Information of the target UE / object may be received from the LMC of the UE or from other entities. The LMS may collect location information of the target UE / object, while the location information may not satisfy the requirements specified by the requestor, which indicates the need for PUM function. Note that information of the target UE / object may also be collected during step 1 if the target UE / object is also a candidate UE. If the request received in step 2 has specified an area of interest, the LMS may first locate UEs in the vicinity of the target UE using existing core network and / or location services. After obtaining the list of UEs in the area of interest, the LMS may perform the aforementioned functionality.

[0115] At step 4, based on the information of the target UE / object, candidate UEs and the location service request, the PUM-enhanced LMS may select reference UEs from the candidate UEs (and select other positioning UEs). For example, the LMS may select UEs that are (or will be) in the vicinity of the target UE / object and / or area of interest as reference UEs.

[0116] At step 5, after the initial selection of positioning UEs, the PUM-enhanced LMS may further collect (updated) information of the selected positioning UEs, if it has not been provided in previous steps or if the information has been updated. The PUM-enhanced LMS may also collect predictive information of the positioning UEs from analytics services. For example, the LMS may collect the current and predicted location information and energy information of the positioning UEs (including reference UEs and target UEs). The PUM-enhanced LMS may also collect current and predicted mobility information of UEs in the vicinity of the target UEs / objects and / or area of interest. The LMS may update the list of selected positioning UEs based on the collected information.

[0117] At step 6, with the collected information of positioning UEs, the PUM- enhanced LMS may determine the configuration of the positioning UEs, such as the positioning method to use, reporting requirements, and other information as described in Table 2. The LMS may proactively determine the selection of positioning UEs and the corresponding configuration information for future time periods / periods based on the predictive information collected from analytics services.

[0118] At step 7, the LMS may configure the positioning UEs and the target UE / object (directly or via other entities) based on the configuration information determined by the PUM function. The LMS may send the identifiers and other information of the reference UEs to the target UE / object and / or send information of the reference UEs to the target UE / object so that they may establish necessary connection with each other to perform the required positioning operations. The LMS may also send configuration information (as in Table 2) to the positioning UEs to instruct them to proactively schedule and configure themselves.

[0119] After configuration, the positioning UEs (including the reference UEs and the target UE / object) may perform location / positioning operations (e.g. using ranging and / or sensing technologies) to generate relative location / position information (e.g. distance between the reference UE and the target UE / object). which may be reported to the LMS according to the reporting requirements specified in the configuration information. The positioning UEs may also report their cunent location information to the LMS, which may be used to derive the location information of the target UE / object.

[0120] At step 8, the PUM-enhanced LMS may derive the location information of the target UE / object based on the received relative location / position information and the location information of the reference UEs. The PUM-enhanced LMS may update the selection and / or configuration of the positioning UEs if it is unable to derive the required location information of the target UE / object or the derived location information does not meet the requirements from the requestor. In this case, step 3 to 9 may be repeated.

[0121] At step 9. the LMS may send a response or notification message to the requestor or the designated notification target based on the derived target UE / object location information.

[0122] The procedure disclosed above may be used for more generic location / positioning configuration services, with the main differences as follows:

[0123] Step 2 may be a service configuration request including criteria / policies on selecting and configuring reference UEs, e.g. an area for selecting reference UEs, UE type. UE capabilities, etc. Alternatively, the request may include the beforementioned information and criteria for determining positioning target UEs or objects. In another alternative, criteria for determining positioning target UEs or objects is pre-provisioned or provided via polices to the server.

[0124] Step 4 may be used to determine the reference UEs and their configuration, followed by providing the configuration in step 5.

[0125] For the PUM function and Location service determining the target UEs of interest, several alternatives can be envisioned, so that the information is: received in step 2 from the service / configuration requestor, or determined based on pre-provisioning or local policies, or determined based in part on messages received from other entities / requestors.

[0126] Embodiment 2: Positioning UE-related analytics ID

[0127] FIG. 9 shows an example procedure 900 in which the proposed PUM function is implemented as an enhancement to an analytics service (e.g. NWDAF, ADAE) to generate Positioning UE-related analytics outputs. Pre-condition: The location service (e.g. LMS) may collect information of target UE / object and candidate UEs (from the LMC), similar to step 1 of FIG. 8.

[0128] Referring to FIG. 9. at step 1, the location service (e.g. LMS) may receive a location service request from a requestor (e.g. a VAL server, a VAL client on UE), which may indicate the need for PUM function (similar to step 2 of FIG. 8).

[0129] At step 2, in order to get assistance on positioning UE selection and configuration, the location service may send a request or subscribe to the PUM-enhanced analytics service which may provide positioning UE-related analytics. The positioning UE- related analytics may provide positioning UE selection and configuration information based on predictive information for current and future time periods. The request may include information as shown in Table 4.Table 4. Positioning UE-related analytics request

[0130] After receiving the request, the PUM-enhanced analytics service may create a positioning UE selection and configuration task (which in this case may be a positioning UE analytics task / instance), as described in step 2 of FIG. 7.

[0131] At step 3, the PUM-enhanced analytics service may collect input data in order to generate the required analytics output. The input data may be included in the analytics request received in step 2, or collected from the location service, the candidate / reference UEs, the target UE / object, or other entities (not shown in FIG. 9) such as the core network, other application enablement services, etc. The input data may include analytics output associated with other analytics IDs that are generated by the PUM-enhanced analytics service or collected from other analytics services. The input data may include information as shown in Table 5 (and Table 1).Table 5. Positioning UE-related analytics input

[0132] At step 4, the PUM-enhanced analytics service may generate analytics output based on the collected input data. The output may include information as shown in Table 6 (and Table 2).Table 6. Positioning UE-related analytics output

[0133] At step 5, the PUM-enhanced analytics service may send a response or notification message to the notification target with the generated analytics output according to the analytics request as indicated in Table 5.

[0134] At step 6, based on the received analytics output, the location service may determine or update the selection and configuration of the positioning UEs.

[0135] At step 7, the location service may configure the positioning UEs (including reference UEs and the target UE / object). receive relative location / position information fromthe positioning UEs, and derive location information of the target UE / object (similar to step 7 to 8 of FIG. 8).

[0136] At step 8, the location service may send a response or notification message to the requestor or the designated notification target based on the derived target UE / object location information (similar to step 10 of FIG. 8).

[0137] Step 3 to 8 may be repeated. The analytes output generated in a previous round or time period may be used as analytics input for the next rounds or time periods. For example, in step 3. the location service may send the relative location / position information and the target UE / object location information generated in step 8 from the previous round to the PUM-enhanced analytics service, which may be used by the analytics service as updated analytics input (e.g. for generating analytics output for the next round or time period).

[0138] Embodiment 3: PUM-enhanced location analytics ID

[0139] FIG. 10 shows an example procedure 1000 for PUM-enhanced location analytics. In this example, the proposed PUM function may be implemented as an enhancement to an analytics service (e.g. NWDAF, ADAE) to improve location-related analytics outputs (e.g. UE mobility, movement behavior). Alternatively, a new analytics ID can be defined to specifically provide PUM-enhanced location analytics.

[0140] At step 1, the PUM-enhanced analytics service may receive an analytics request related to location information of a target UE / object and / or area of interest. The request may indicate (explicitly or implicitly) that PUM function is needed. For example, the request is to predict the location of a target UE / object which may be out of coverage and not able to report its location to the system reliably. Alternatively, the analytics service may determine that PUM function is needed based on the received request or in later steps. The analytics request may include information as shown in Table 7.Table 7. PUM-enhanced Location analytics request

[0141] After receiving the request and determining PUM function is needed, the PUM-enhanced analytics service may create a positioning UE selection and configuration task (as described in step 2 of FIG. 7) to support the analytics.

[0142] At step 2, the PUM-enhanced analytics service may collect input data in order to generate the required analytics output. The input data may be included in the analytics request received in step 1, or collected from the location service, the candidate / reference UEs, the target UE / object, or other entities (not shown in FIG. 7) such as the core network, other application enablement services, etc. The input data may include analytics output associated with other analytics IDs that are generated by the PUM-enhanced analytics service or collected from other analytics services. The input data may include information as shown in Table 8 (and Table 1).Table 8. PUM-enhanced location analytics input

[0143] At step 3, the PUM-enhanced analytics service may select positioning UEs and determine their configuration based on the analytics request and the collected data. For example, the PUM-enhanced analytics service may determine candidate reference UEs whosemobility is (or will be) moving towards the target UE / object and / or area of interest. As another example, the positioning capability (e.g. ranging as opposed to sensing) may also determine good candidates for reference UEs.

[0144] At step 4, the PUM-enhanced analytics service may send a request to the location service (e.g. LMS) to collect relative location / position information. The request may include the list of positioning UEs and their configuration information which are determined by the PUM-enhanced analytics service (in the previous step). Alternatively, the PUM- enhanced analytics service may request relative location / position information from the positioning UEs directly.

[0145] At step 5, the location service may configure the positioning UEs (including reference UEs and the target UE / object) based on the request from the PUM-enhanced analytics service, and receive relative location / position information from the positioning UEs (similar to step 7 of FIG. 8).

[0146] At step 6, the PUM-enhanced analytics service may receive relative location / position information from the location service or the positioning UEs, which will be used as input data for generating the required analytics output. The PUM-enhanced analytics service may also receive (updated) location information of the positioning UEs including target UE / object and reference UEs (or other information as shown in Table 7).

[0147] At step 7, the PUM-enhanced analytics service may generate analytics output based on the collected input data, including the relative location / position information. The output may include information as shown in Table 9.Table 9. PUM-enhanced location analytics output

[0148] At step 8. the PUM-enhanced analytics service may send a response or notification message to the notification target with the generated analytics output according to the analytics request.

[0149] Step 3 to 8 may be repeated. The analytics output generated in a previous round or time period may be used as analytics input for the next rounds or time periods.

[0150] In one embodiment. PUM-enhanced location / analytics servers and / or clients may implement PUM function related information elements (such as but not limited to those defined in the aforementioned tables) as one or more RESTful resources. The RESTful resources may have unique addresses (e.g. URIs, URNs, etc.) and may also have one or more attributes that comprise resource data and / or metadata. These resources may be created, retrieved, discovered, updated, or deleted by VAL clients and servers, as well as by other entities in the system such as but not limited to those shown in the aforementioned figures. PUM-enhanced location / analytics servers and clients may support RESTful APIs based on these resources. Via these APIs the positioning UE management operations described herein may be initiated. In addition, the APIs may also be used to initiate the positioning UE management procedures described herein. These APIs may be based on RESTful protocols such as HTTP and CoAP.

[0151] In another embodiment, PUM-enhanced location / analytics servers and / or clients PUM function related information elements (such as but not limited to those defined in aforementioned tables) as one or more topics within a topic space of a message broker (e.g., MQTT broker, AMQP broker, etc.). A PUM-enhanced location / analytics server and / or client may function as the message broker. Alternatively, the message broker may be hosted external to PUM-enhanced location / analytics server and / or client. For example, by another entity in the system which the PUM-enhanced location / analytics server or client may communicate with. A PUM-enhanced location / analytics server and / or client may send and / or receive publish and / or subscribe requests to topics within a message broker. The topics may have unique addresses (e.g. topic names, etc.) and one or more attributes that contain topic data and / or metadata.

[0152] These positioning UE management topics may be created, retrieved, discovered, updated, or deleted by VAL clients and servers, as well as by other entities in the system such as but not limited to those shown in the aforementioned figures. PUM-enhanced location / analytics servers and clients may support APIs based on these topics. Via these APIs the positioning UE management operations described herein may be initiated. In addition, the APIs may also be used to initiate the positioning UE management procedures described herein. These APIs may be based on Pub / Sub protocols such as MQTT and AMQP.

[0153] FIG. 11 shows an example of a GUI 1100 for configuring positioning UEs. A requestor may specify the area of interest, service period, management policy or selection criteria for the PUM function, provide information of the UEs, and view the results of management operations, such as the selection and configuration information of positioning UEs. Particularly, the requestor may view the selection and configuration information for a future time stamp / period that is generated by the analytics assisted PUM function.

Claims

What is claimed:

1. A method for use in a server for reference UE management, the method comprising: receiving a message indicating a request to determine and configure one or more reference user equipments (UEs), wherein the one or more reference UEs are used to support measuring location information of a target UE; receiving capability information of the target UE and one or more candidate reference UEs; requesting, from an analytics service, predicted location information of the target UE and the one or more candidate reference UEs; receiving, from the analytics service, the predicted location information; based on the message, the received capability information, and the predicted location information, determining one or more reference UEs from the one or more candidate reference UEs; and sending, to each reference UE of the determined one or more reference UEs, a configuration request.

2. The method of claim 1, wherein the message comprises an identifier of the target UE.

3. The method of claim 1, wherein the message comprises a list of the one or more candidate reference UEs or selection criteria of the one or more reference UEs.

4. The method of claim 1. further comprising: requesting, from the analytics service, predicted capability information of the target UE and the one or more candidate reference UEs; and receiving, from the analytics service, the predicted capability information.

5. The method of claim 1, wherein the configuration request comprises a reporting configuration.

6. The method of claim 1 , wherein the configuration request comprises a required positioning method to be used by the determined one or more reference UEs and a schedule to use the required positioning method.

7. The method of claim 6, wherein the required positioning method comprises sidelink positioning or ranging.

8. The method of claim 1, wherein the configuration request comprises proactive or predictive configuration information.

9. The method of claim 1. further comprising: receiving, from the determined one or more reference UEs, positioning information.

10. The method of claim 1, wherein the server comprises a 3GPP SEAL location management server.

11. A server comprising one or more processors and memory storing instructions which, when executed by the one or more processors, cause the server to: receive a message indicating a request to determine and configure one or more reference user equipments (UEs), wherein the one or more reference UEs are used to support measuring location information of a target UE; receive capability information of the target UE and one or more candidate reference UEs; request, from an analytics service, predicted location information of the target UE and the one or more candidate reference UEs; receive, from the analytics service, the predicted location information; based on the message, the received capability information, and the predicted location information, determine one or more reference UEs from the one or more candidate reference UEs; and send, to each reference UE of the determined one or more reference UEs, a configuration request.

12. The server of claim 11 , wherein the message comprises an identifier of the targetUE.

13. The server of claim 11, wherein the message comprises a list of the one or more candidate reference UEs or selection criteria of the one or more reference UEs.

14. The server of claim 11, further comprising: requesting, from the analytics service, predicted capability information of the target UE and the one or more candidate reference UEs; and receiving, from the analytics service, the predicted capability information.

15. The server of claim 11 , wherein the configuration request comprises a reporting configuration.

16. The server of claim 11, wherein the configuration request comprises a required positioning method to be used by the determined one or more reference UEs and a schedule to use the required positioning method.

17. The server of claim 16, wherein the required positioning method comprises sidelink positioning or ranging.

18. The server of claim 11, wherein the configuration request comprises proactive or predictive configuration information.

19. The server of claim 11. further comprising: receiving, from the determined one or more reference UEs, positioning information.

20. The server of claim 11, wherein the server comprises a 3GPP SEAL location management server.