Selection of Sidelink Positioning Devices in Wireless Communication Networks

Abstract

A user equipment (UE) device for wireless communication is provided, comprising a processor and memory coupled to the processor, wherein the processor is configured to cause the UE device to transmit a first message to a first device of a wireless communication network, the first message including one or more parameters indicating the sidelink positioning capability of the UE device.

Description

Technical Field

[0001] The subject matter disclosed in this specification generally relates to the field of implementing the selection of sidelink positioning devices in a wireless communication network. This document defines user equipment devices for wireless communication, a first device and a second device in a wireless communication network, and methods in the user equipment device, the first device, and the second device.

Background Art

[0002] Sidelink (SL) positioning in Release 18 New Radio (NR) is being studied in the 3GPP work item description (WID) RP-223549 titled "New WID on Expanded and Improved NR Positioning" by the 3rd Generation Partnership Project (3GPP™). This is being studied to support specific target accuracy requirements for SL positioning.

[0003] SL positioning is intended to be applied to various use cases such as vehicle-to-everything (V2X), public safety, industrial Internet of Things (IIoT), and commercial use cases. The purpose of SL positioning is to determine the location of a user equipment (UE) by using SL positioning methods such as round-trip time (RTT) type solutions that use SL, SL angle of arrival (AoA), and SL time difference of arrival (TDOA).

[0004] SL positioning is supported in all coverage scenarios (i.e., in-coverage scenarios, partial-coverage scenarios, and out-of-coverage scenarios), as well as in PC5-only and joint PC5-Uu-based operation scenarios, based on a new SL positioning reference signal (PRS) transmitted via the PC5 interface. A new protocol, designated Sidelink Positioning Protocol (SLPP), is introduced to exchange SL positioning-related information between UEs via the PC5 interface. Functions to be supported by SLPP include SL positioning capability transfer, SL positioning support data exchange, SL location information transfer, error handling, and interruption.

[0005] Cast types considered for SLPP signaling include unicast, groupcast, and broadcast, but unicast / one-to-one operation is assumed as the baseline for SLPP signaling exchange between UEs. For the exchange of SL positioning capability and SL positioning support data information, groupcast and broadcast (in addition to unicast) are assumed to be supported only when protection of groupcast / broadcast for SL positioning signaling can be guaranteed. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] 3GPP Technical Specification TS 37.355 [Non-Patent Document 2] 3GPP Technical Specification TS 38.331 [Non-Patent Document 3] 3GPP Technical Specification TS 23.273 [Non-Patent Document 4] 3GPP Technical Specification TS 23.304 [Non-Patent Document 5] 3GPP Technical Specification TS 24.501 [Non-Patent Document 6] 3GPP Technical Specification TS 29.572 [Overview of the project] [Problems that the invention aims to solve]

[0007] In Uu-based positioning, the Access and Mobility Management Function (AMF) performs location management function (LMF) selection based on available information (e.g., required location service (LCS) quality of service (QoS) requirements, LMF capabilities, LMF load, LMF location) or based on the AMF local configuration (if the AMF is configured locally with a mapping table of UE identities and LMF addresses).

[0008] Currently, in positioning based on Joint PC5-Uu, the AMF may need to select an LMF with SL positioning capability for result calculation, method determination, support data distribution, and anchor UE selection. Based on the required LCS QoS, the AMF knows whether SL positioning is required for the Mobile Incoming Location Request (MT-LR) procedure or the Mobile Outgoing Location Request (MO-LR) procedure. However, there are specific issues for the AMF when selecting an LMF. Specifically, an SL positioning-capable LMF may be available, but due to current load, the LMF may decide that the SL positioning server UE needs to perform result calculation, method determination, support data distribution, and / or anchor UE selection. Furthermore, an available LMF may not be SL positioning-capable.

[0009] To solve the above problem, a solution is needed for how the AMF can provide a selected LMF using information about available SL positioning server UEs and anchor UEs, so that the LMF can perform SL positioning.

[0010] A concise solution to support SL positioning in a positioning operation scenario based on Joint PC5-Uu is to configure the AMF locally with a mapping table of UE identity and LMF address for SL positioning-enabled LMFs. However, this solution is quite static and cannot completely avoid the aforementioned problems. [Means for solving the problem]

[0011] Disclosed herein is a procedure for selecting a sidelink positioning device in a wireless communication network. The procedure may be implemented by a user equipment for wireless communication, a first and second device in a wireless communication network, and a method in the user equipment, the first and second device.

[0012] A user equipment (UE) device for wireless communication is provided, comprising a processor and memory coupled to the processor, wherein the processor is configured to cause the UE device to transmit a first message to a first device of a wireless communication network, the first message including one or more parameters indicating the sidelink positioning capability of the UE device.

[0013] Further provided is a first device in a wireless communication network, comprising a processor and a memory coupled to the processor, wherein the processor is configured to cause the first device to receive a request from a consumer entity to locate a target UE in a target area, determine one or more UE devices in the target area, each having sidelink positioning capability, and transmit a fourth message to a second device in the wireless communication network indicating one or more UE devices and their respective sidelink positioning capabilities.

[0014] Further provided is a second device in a wireless communication network, comprising a processor and memory coupled to the processor, wherein the processor is configured to cause the second device to receive a fourth message from a first device of the wireless communication network indicating one or more UE devices and their respective sidelink positioning capabilities for locating a target UE in a target area, determine a server UE device from one or more UE devices for performing location calculations for sidelink positioning of the target UE, and transmit a second message to the server UE device requesting sidelink positioning of the target UE, wherein the second message includes one or more QoS requirements for location estimation of the target UE and one or more identifiers of one or more anchor UEs in the target area of ​​the target UE.

[0015] A method in a user equipment device for wireless communication is further provided, comprising the step of transmitting a first message to a first device of a wireless communication network, wherein the first message includes one or more parameters indicating the sidelink positioning capability of the UE device.

[0016] A method in a first device in a wireless communication network is further provided, comprising the steps of: receiving a request from a consumer entity to locate a target UE in a target area; determining one or more UE devices in the target area, each having sidelink positioning capability; and transmitting a fourth message to a second device in the wireless communication network, indicating one or more UE devices and their respective sidelink positioning capabilities.

[0017] A method in a second device in a wireless communication network, the method comprising: receiving, from a first device in the wireless communication network, a fourth message indicating one or more UE devices for identifying the location of a target UE within a target area and their respective sidelink positioning capabilities; determining, from the one or more UE devices, a server UE device for performing location calculations for sidelink positioning of the target UE; and transmitting, to the server UE device, a second message requesting sidelink positioning of the target UE, the second message including one or more QoS requirements for location estimation of the target UE and one or more identifiers of one or more anchor UEs within the target area of the target UE. A method is further provided.

[0018] To explain how the advantages and features of the present disclosure can be obtained, the present disclosure will be described by referring to specific devices and methods shown in the accompanying drawings. Each of these drawings merely illustrates a specific aspect of the present disclosure and should not be considered as limiting its scope. The drawings may be simplified for clarity and are not necessarily drawn to scale.

[0019] Next, a method and apparatus for selecting a sidelink positioning device in a wireless communication network will be described by way of example, with reference to the accompanying drawings.

Brief Description of the Drawings

[0020] [Figure 1] A diagram showing an embodiment of a wireless communication system. [Figure 2] A diagram showing an embodiment of a user equipment device. [Figure 3] A diagram showing an embodiment of a network node. [Figure 4] A diagram showing an example of LPP message transfer between a LMF and a UE. [Figure 5]This is a diagram showing an example of the LCS architecture. [Figure 6] This is a diagram showing an example of the 5GC-MT-LR procedure for a regulated location service for non-roaming. [Figure 7] This is a diagram showing an example of the 5GC-MO-LR procedure. [Figure 8] This is a diagram showing an example of a sidelink communication scenario. [Figure 9] This is a diagram showing an embodiment of a format for signaling SL positioning capabilities. [Figure 10] This is a diagram showing an embodiment of a format for listing SL positioning information in the Nlmf_Location_DetermineLocation request message. [Figure 11] This is a diagram showing the message flow in an embodiment of a positioning operation scenario based on joint PC5-Uu. [Figure 12] This is a diagram showing an embodiment of a method in a user equipment device. [Figure 13] This is a diagram showing an embodiment of a method in a first device. [Figure 14] This is a diagram showing an embodiment of a method in a second device.

Embodiments for Carrying Out the Invention

[0021] As will be appreciated by those skilled in the art, aspects of the present disclosure can be embodied as a system, apparatus, method, or program product. Accordingly, the configurations described herein can be implemented in entirely hardware form, entirely software form (including firmware, resident software, microcode, etc.), or in a form combining software aspects and hardware aspects.

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

[0023] Furthermore, the methods and apparatus may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereafter referred to as code. The storage device may be tangible, non-temporary, and / or non-transmitting. The storage device may not embody signals. In certain configurations, the storage device merely employs signals for accessing the code.

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

[0025] More specific examples of storage devices (a non-exclusive list) include, namely, electrical connections having one or more wires, portable computer diskettes, hard disks, random access memory ("RAM"), read-only memory ("ROM"), erasable programmable read-only memory ("EPROM") or flash memory, portable compact disk read-only memory ("CD-ROM"), optical storage devices, magnetic storage devices, or any suitable combination of the above. In the context of this document, a computer-readable storage medium may be any tangible medium that contains or can store programs for use by or in connection with an instruction execution system, apparatus, or device.

[0026] Throughout this specification, any reference to a particular method or apparatus, or to an example of similar wording, means that the particular features, structure, or characteristics described in relation to that example are included in at least one implementation of the methods and apparatus described herein. Thus, all references to a particular method or apparatus, or to an example of similar wording, mean "one or more examples, but not all," although they may, not necessarily, refer to the same example. The terms "including," "comprising," and "having," and their variations, mean "including, but not limited to," unless otherwise specified. The enumeration of items does not imply that any or all of the items are mutually exclusive unless otherwise specified. The terms "a," "an," and "the" also mean "one or more," unless otherwise specified.

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

[0028] Furthermore, the features, structures, or properties described herein can be combined in any suitable manner. The following description provides numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, and hardware chips, in order to give a full understanding of the disclosure. However, those skilled in the art will recognize that the disclosed methods and apparatus can be practiced without one or more of the specific details, or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.

[0029] The embodiments of the disclosed methods and apparatus are described below with reference to schematic flowcharts and / or schematic block diagrams of the methods, apparatus, systems, and program products. It should be understood that each block in the schematic flowcharts and / or schematic block diagrams, as well as any combination of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, a dedicated computer, or other programmable data processing device to create a machine, and as a result, instructions executed via the computer or other programmable data processing device processor create means for implementing the functions / actions specified in the schematic flowcharts and / or schematic block diagrams.

[0030] Code that can instruct a computer, other programmable data processing device, or other device to function in a particular way may also be stored in a storage device, and as a result, the instructions stored in the storage device produce a product containing instructions that implement the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0031] The code can also be loaded onto a computer, other programmable data processing device, or other device to perform a series of operational steps on the computer, other programmable device, or other device to create a process executed by the computer, and as a result, the code executed on the computer or other programmable device provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0032] The schematic flowcharts and / or schematic block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, a segment, or a portion of code containing one or more executable instructions for implementing a specified logical function.

[0033] It should also be noted that in some alternative implementations, the functions described within a block may be performed in a different order than that shown in the diagram. For example, two blocks shown consecutively may actually be executed substantially simultaneously, or blocks may sometimes be executed in reverse order depending on the functions involved. Other steps and methods may be considered equivalent in function, logic, or effect to one or more blocks or parts thereof shown in the diagram.

[0034] The descriptions of elements in each figure may refer to elements in preceding figures. Similar numbers refer to the same elements in all figures.

[0035] Figure 1 illustrates one embodiment of a wireless communication system 100 for selecting a sidelink positioning device in a wireless communication network. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although a specific number of remote units 102 and network units 104 are illustrated in Figure 1, those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100. The wireless communication system may comprise a wireless communication network and at least one wireless communication device. The wireless communication device is typically a 3GPP user equipment (UE). The wireless communication network may comprise at least one network node. The network node may be a network unit.

[0036] In one embodiment, the remote unit 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smartphones, smart televisions (e.g., Internet-connected televisions), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), aircraft, and drones. In some embodiments, the remote unit 102 includes wearable devices such as smartwatches, fitness bands, and optical head-mounted displays. Furthermore, the remote unit 102 may be referred to as a subscriber unit, mobile, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or by other terms used in the art. The remote unit 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote unit 102 may communicate directly with other remote units 102 via side-link communication.

[0037] The network unit 104 may be distributed across geographical areas. In certain embodiments, the network unit 104 may include access points, access terminals, bases, base stations, node B, eNB, gNB, home node B, relay nodes, devices, core network, airborne servers, radio access nodes, APs, NRs, network entities, access and mobility management functions ("AMF"), integrated data management functions ("UDM"), integrated data repository ("UDR"), UDM / UDR, policy management functions ("PCF"), radio access network ("RAN"), network slice selection functions ("NSSF"), operation, administration and management ("OAM"), session management functions ("SMF"), and user plane functions ("UPF"). These may be referred to as application functions, authentication server functions ("AUSF"), security anchor functions ("SEAF"), trusted non-3GPP gateway functions ("TNGF"), application functions, service enabler architecture layer ("SEAL") functions, vertical application enabler server, edge enabler server, edge configuration server, mobile edge computing platform functions, mobile edge computing applications, application data analysis enabler server, SEAL data distribution server, middleware entities, network slice capability management server, or by any other terminology used in the art. Network unit 104 is generally part of a radio access network that includes one or more controllers commutably coupled to one or more corresponding network units 104. A radio access network is generally commutably coupled to one or more core networks, and one or more core networks may be coupled to other networks, among many others, such as the Internet and public switched telephone networks. These and other elements of radio access networks and core networks are not shown but are generally well known to those skilled in the art.

[0038] In one implementation, the wireless communication system 100 conforms to the New Radio (NR) protocol standardized by 3GPP, with the network unit 104 transmitting on the downlink (DL) using orthogonal frequency division multiplexing ("OFDM") modulation, and the remote unit 102 transmitting on the uplink (UL) using either single-carrier frequency division multiple access ("SC-FDMA") or OFDM. However, more generally, the wireless communication system 100 may implement any other open or proprietary communication protocol, such as WiMAX, IEEE 802.11 variant, GSM, GPRS, UMTS, LTE variant, CDMA2000, Bluetooth®, ZigBee, Sigfox, or LoraWAN. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0039] The network unit 104 can serve several remote units 102 within a serving area, for example, a cell or cell sector, via a wireless communication link. The network unit 104 transmits DL communication signals to serve the remote units 102 in the time domain, frequency domain, and / or spatial domain.

[0040] Figure 2 illustrates a user device 200 that may be used to implement the methods described herein. The user device 200 is used to implement one or more of the solutions described herein. The user device 200 follows one or more of the user devices described in the embodiments herein. Specifically, the user device 200 may include, for example, UE530 in Figure 5 or UE1120, 1180, 1190 in Figure 11. The user device 200 includes a processor 205, memory 210, input device 215, output device 220, and transceiver 225.

[0041] The input device 215 and output device 220 may be combined into a single device such as a touchscreen. In some implementations, the user equipment 200 does not include any input device 215 and / or output device 220. The user equipment 200 may include one or more of the processor 205, memory 210, and transceiver 225, and may not include the input device 215 and / or output device 220.

[0042] As illustrated, the transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The transceiver 225 can communicate with one or more cells (or wireless coverage areas) supported by one or more base units. The transceiver 225 may be capable of operating on unlicensed spectrum. Furthermore, the transceiver 225 may include multiple UE panels supporting one or more beams. In addition, the transceiver 225 may support at least one network interface 240 and / or application interface 245. The application interface 245 may support one or more APIs. The network interface 240 may support 3GPP reference points such as Uu, N1, PC5, etc. Other network interfaces 240 may be supported as will be understood by those skilled in the art.

[0043] The processor 205 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 205 may be a microcontroller, microprocessor, central processing unit ("CPU"), graphics processing unit ("GPU"), auxiliary processing unit, field-programmable gate array ("FPGA"), or similar programmable controller. The processor 205 may execute instructions stored in memory 210 to perform the methods and routines described herein. The processor 205 is communicatively coupled to memory 210, input device 215, output device 220, and transceiver 225.

[0044] The processor 205 can control the user device 200 to implement the behavior of the user device described herein. The processor 205 may include an application processor (also known as the “main processor”) that manages application domain and operating system (“OS”) functions, and a baseband processor (also known as the “baseband radio processor”) that manages radio functions.

[0045] Memory 210 may be a computer-readable storage medium. Memory 210 may include volatile computer storage media. For example, memory 210 may include RAM including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). Memory 210 may include non-volatile computer storage media. For example, memory 210 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. Memory 210 may include both volatile and non-volatile computer storage media.

[0046] Memory 210 may store data related to implementing traffic category fields, as described herein. Memory 210 may also store program code and related data, such as an operating system or other controller algorithms running on device 200.

[0047] The input device 215 may include any known computer input device, including touch panels, buttons, keyboards, styluses, microphones, etc. The input device 215 may be integrated with the output device 220, for example, as a touchscreen or similar touch-sensitive display. The input device 215 may include a touchscreen on which text can be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. The input device 215 may include two or more different devices, such as a keyboard and a touchscreen.

[0048] The output device 220 may be designed to output visual signals, audible signals, and / or tactile signals. The output device 220 may include an electronically controllable display or display device capable of outputting visual data to the user. For example, the output device 220 may include, but is not limited to, a liquid crystal display ("LCD"), a light-emitting diode ("LED") display, an organic LED ("OLED") display, a projector, or a similar display device capable of outputting images, text, etc., to the user. As another non-limiting example, the output device 220 may include a wearable display, such as a smartwatch, smart glasses, or a head-up display, that is detached from the rest of the user equipment device 200 but communicatively coupled to it. Furthermore, the output device 220 may be a component of a smartphone, personal digital assistant, television, tablet computer, notebook (laptop) computer, personal computer, or vehicle dashboard.

[0049] The output device 220 may include one or more speakers for generating sound. For example, the output device 220 may produce an audible alert or notification (e.g., a beep or chime). The output device 220 may include one or more haptic devices for producing vibration, motion, or other tactile feedback. All or part of the output device 220 may be integrated with the input device 215. For example, the input device 215 and the output device 220 may form a touchscreen or similar touch-sensitive display. The output device 220 may be located near the input device 215.

[0050] The transceiver 225 communicates with one or more network functions of the mobile communication network via one or more access networks. The transceiver 225 operates under the control of the processor 205 to transmit messages, data, and other signals, and to receive messages, data, and other signals. For example, the processor 205 may selectively activate the transceiver 225 (or a portion thereof) at certain times to send or receive messages.

[0051] The transceiver 225 includes at least one transmitter 230 and at least one receiver 235. One or more transmitters 230 may be used to provide uplink communication signals to a base unit of a wireless communication network. Similarly, one or more receivers 235 may be used to receive downlink communication signals from the base unit. Although only one transmitter 230 and one receiver 235 are shown, the user equipment 200 may have any suitable number of transmitters 230 and receivers 235. Furthermore, the transmitters 230 and receivers 235 may be any suitable type of transmitter and receiver. The transceiver 225 may include a first transmitter / receiver pair used to communicate with a mobile communication network over a licensed radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communication network over an unlicensed radio spectrum.

[0052] A first transmitter / receiver pair used to communicate with a mobile communication network via a licensed radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communication network via an unlicensed radio spectrum may be combined into a single transceiver unit, for example, a single chip that performs functions for use with both licensed and unlicensed radio spectra. The first and second transmitter / receiver pairs may share one or more hardware components. For example, a particular transceiver 225, transmitter 230, and receiver 235 may be implemented as physically separate components that access shared hardware and / or software resources, such as a network interface 240.

[0053] One or more transmitters 230 and / or one or more receivers 235 may be implemented and / or incorporated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an application-specific integrated circuit ("ASIC"), or other type of hardware component. One or more transmitters 230 and / or one or more receivers 235 may be implemented and / or incorporated into a multi-chip module. Other components, such as a network interface 240 or other hardware components / circuits, may be incorporated into a single chip together with any number of transmitters 230 and / or receivers 235. Transmitters 230 and receivers 235 may be logically configured as transceivers 225 using one or more common control signals, or as modular transmitters 230 and receivers 235 implemented on the same hardware chip or in a multi-chip module.

[0054] Figure 3 illustrates further details of a network node 300 that may be used to implement the method described herein. The network node 300 may be an implementation of one entity in a wireless communication network, for example, in one or more of the wireless communication networks described herein. The network node 300 may comprise, for example, the AMF522 or LMF523 in Figure 5, or the AMF1140 or LMF1150 in Figure 11. The network node 300 includes a processor 305, memory 310, input device 315, output device 320, and transceiver 325.

[0055] The input device 315 and output device 320 may be combined into a single device such as a touchscreen. In some implementations, the network node 300 does not include any input device 315 and / or output device 320. The network node 300 may include one or more of the processor 305, memory 310, and transceiver 325, and may not include the input device 315 and / or output device 320.

[0056] As illustrated, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335, where the transceiver 325 communicates with one or more remote units 200. In addition, the transceiver 325 may support at least one network interface 340 and / or application interface 345. The application interface 345 may support one or more APIs. The network interface 340 may support 3GPP reference points such as Uu, N1, N2, and N3. Other network interfaces 340 may be supported, as will be understood by those skilled in the art.

[0057] The processor 305 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 305 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. The processor 305 may execute instructions stored in memory 310 to perform the methods and routines described herein. The processor 305 is communicatively coupled to memory 310, input device 315, output device 320, and transceiver 325.

[0058] Memory 310 may be a computer-readable storage medium. Memory 310 may include a volatile computer storage medium. For example, memory 310 may include RAM including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). Memory 310 may include a non-volatile computer storage medium. For example, memory 310 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. Memory 310 may include both volatile and non-volatile computer storage media.

[0059] Memory 310 may store data related to establishing multipath unicast links and / or mobile operations. For example, memory 310 may store parameters, configurations, resource allocations, policies, etc., as described herein. Memory 310 may also store program code and related data, such as operating systems or other controller algorithms running on network node 300.

[0060] The input device 315 may include any known computer input device, including touch panels, buttons, keyboards, styluses, microphones, etc. The input device 315 may be integrated with the output device 320, for example, as a touchscreen or similar touch-sensitive display. The input device 315 may include a touchscreen on which text can be entered using a virtual keyboard displayed on the touchscreen and / or by writing on the touchscreen. The input device 315 may include two or more different devices, such as a keyboard and a touchscreen.

[0061] The output device 320 may be designed to output visual signals, audible signals, and / or tactile signals. The output device 320 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 320 may include, but is not limited to, an LCD, LED display, OLED display, projector, or similar display device capable of outputting images, text, etc., to a user. As another non-limiting example, the output device 320 may include a wearable display, such as a smartwatch, smart glasses, or head-up display, that is detached from the rest of the network node 300 but communicatively coupled to it. Furthermore, the output device 320 may be a component of a smartphone, personal digital assistant, television, tablet computer, notebook (laptop) computer, personal computer, or vehicle dashboard.

[0062] The output device 320 may include one or more speakers for generating sound. For example, the output device 320 may produce an audible alert or notification (e.g., a beep or chime). The output device 320 may include one or more haptic devices for producing vibration, motion, or other haptic feedback. All or part of the output device 320 may be integrated with the input device 315. For example, the input device 315 and the output device 320 may form a touchscreen or similar touch-sensitive display. The output device 320 may be located near the input device 315.

[0063] The transceiver 325 includes at least one transmitter 330 and at least one receiver 335. One or more transmitters 330 may be used to communicate with a UE as described herein. Similarly, one or more receivers 335 may be used to communicate with network functions in the PLMN and / or RAN as described herein. Although only one transmitter 330 and one receiver 335 are shown, a network node 300 may have any suitable number of transmitters 330 and receivers 335. Furthermore, the transmitters 330 and receivers 335 may be any suitable type of transmitter and receiver.

[0064] To aid in understanding the solutions disclosed herein, a description of specific target accuracy requirements, specific features, and specific functions is then provided.

[0065] Table 1 provides the target accuracy requirements for SL positioning in specific 3GPP use cases. The references to "Set A" and "Set B" indicate the categorization of requirements into two sets.

[0066] [Table 1]

[0067] Support for positioning in NR should also be described. In 3GPP Rel-15, only cell ID and radio access technology (RAT) independent positioning methods (e.g., Global Navigation Satellite System (GNSS)) are supported in NR. To meet the positioning requirements of regulatory use cases (i.e., emergency services) and commercial use cases (e.g., IIoT) listed in Table 2, RAT-dependent positioning methods (for both frequency range (FR) 1 and FR 2) and RAT-independent positioning methods (such as Precision Single Positioning (PPP) and Real-time Kinematic (RTK)) are specified in 3GPP Rel-16. Table 3 further lists the RAT-dependent positioning methods specified in 3GPP Rel-16.

[0068] [Table 2]

[0069] [Table 3]

[0070] Furthermore, higher positioning requirements for commercial use cases, and especially for IIoT use cases, are listed in Table 4.

[0071] [Table 4]

[0072] In particular, to meet the higher positioning requirements specified in Table 4, further enhancements to NR positioning are specified in 3GPP Rel-17. These include improvements to positioning accuracy and latency (extension of uplink angle of arrival (UL-AoA), extension of downlink angle of departure (DL-AoD), pre-configured measurement gap, pre-configured positioning reference signal (PRS) processing window, etc.), improvements to network efficiency (on-demand PRS transmission), improvements to device efficiency (positioning with RRC_INACTIVE), provision of high integrity and reliability requirements (GNSS integrity), and enhancements to assisted GNSS positioning.

[0073] In the 5GS architecture applicable to UE positioning, either the UE itself or the location server determines the UE's location depending on the applied positioning method. Furthermore, the LTE Positioning Protocol (LPP), specified in 3GPP technical specification TS 37.355, is used point-to-point between the location server and the UE to exchange positioning-related information (e.g., location-related measurements, location estimates, and support data). LPP supports the following message types: Request Capabilities, Provide Capabilities, Request Assistance Data, Provide Assistance Data, Request Location Information, Provide Location Information, Abort, and Error.

[0074] Figure 4 shows an example of LPP message transfer 400 between the LMF450 (location server) and the UE420. LPP messages are carried across the intermediate network interface as transparent protocol data units (PDUs) using the appropriate protocol.

[0075] In the first step 401, the LMF450 sends an LPP message to the AMF440. The LPP message may be a Request Capabilities message requesting the UE420 to send its positioning capabilities. This is shown as the "LPP message".

[0076] In a further step 402, AMF440 transports the received LPP message to NG-RAN node 430 by including the LPP message within the LPP message container of the DL NAS transport message. This is shown as "DL NAS transport (LPP message container)".

[0077] In a further step 403, the NG-RAN node 430 transports the received LPP message container to the UE420 by including the LPP message container in the RRC DLInformationTransfer message specified in the 3GPP technical specification TS 38.331, entitled “NR Radio Resource Control (RRC) Protocol specification.” This is referred to as “DLInformationTransfer(LPP message).”

[0078] In a further step 404, upon receiving a Request Capabilities message, UE420 generates a Provide Capabilities message in response. UE420 then sends the Provide Capabilities message to NG-RAN node 430 by including the LPP message within the RRC ULInformationTransfer message, as specified in the 3GPP technical specification TS 38.331, entitled "NR Radio Resource Control (RRC) Protocol specification." This is referred to as "ULInformationTransfer (LPP message)."

[0079] In a further step 405, the NG-RAN node 430 transports the LPP messages received from the UE420 to the AMF440 by including the LPP messages within the LPP message container of the UL NAS transport message. This is shown as "UL NAS transport (LPP message container)".

[0080] In a further step 406, the AMF440 extracts the LPP message from the received NAS message / LPP message container and sends it to the LMF450. This is shown as the "LPP message".

[0081] Figure 5 shows an example of a Location Services (LCS) architecture 500. The LCS functionality in 3GPP provides a mechanism to support mobile location services for operators, subscribers, and third-party service providers. Examples of location-based services include emergency services, tracking services, and location-based information services (navigation, city tours, location-dependent content broadcasts, mobile yellow pages, etc.). Location information can be requested and reported to clients (applications) associated with the UE or clients within or attached to the 5GC. In Figure 5, an external LCS client 510 requests the current location of a target UE 530 from the 5GC 520. This figure illustrates the relationships between various LCS entities, as will be described in more detail below.

[0082] An external LCS client 510 interacts with the GMLC 521 to obtain location information for one or more (target) UEs 530. The LCS client 510 may reside in the UE and may be implemented as hardware (HW) or software (SW) (i.e., an application). Examples of LCS clients 510 include 911 Emergency Dispatch Centers (PSAPs) and Google Maps.

[0083] GMLC521 is the first node, and the external LCS client 510 accesses it on the Public Land Mobile Network (PLMN), acting as a location server for external applications regarding location information.

[0084] The LMF523 manages the overall coordination and scheduling of resources required for the location of a UE530 that is registered with or accessing the 5GC520. The LMF523 can also calculate or validate the final location and any velocity estimates and estimate the accuracy to be achieved. The LMF523 processes location service requests that may include transferring support data to the target UE530 to assist UE-based and / or UE-assisted positioning, and / or positioning of the target UE530. The LMF523 then returns the location estimate of the UE530 to the Access and Mobility Management Function (AMF) 522. For location services requested by entities other than the AMF522 (e.g., GMLC521 or UE), the AMF522 returns the location results to that entity. In the C plane, the LMF523 acts as a location server.

[0085] The AMF522 includes the functionality to manage the positioning of the target UE530 for all types of location requests. The AMF522 receives a request from another entity (e.g., GMLC521 or UE) for some location service associated with a particular target UE530, or the AMF522 itself decides to initiate some location service for a particular target UE530 (e.g., in the case of an emergency call from a UE). The AMF522 then sends the location service request to the LMF523.

[0086] NG-RAN node 524 (i.e., gNB) is involved in handling various positioning procedures, including positioning target UE530, providing location-related information not associated with a specific target UE530, and transferring positioning messages between AMF522 or LMF523 and target UE530.

[0087] Target UE530 is a UE whose location (absolute or relative) will be obtained either by the network or by the UE itself.

[0088] NRPPa is a C-plane radio network layer signaling protocol between NG-RAN node 524 (gNB) and LMF523.

[0089] LPP is a point-to-point positioning protocol that supports positioning and location-related services for a target device. In the C-plane, LPP is terminated between the target UE530 and the LMF523.

[0090] Next, a brief explanation of specific types of location requests specified in 3GPP will be provided.

[0091] A Network Induced Location Request (NI-LR) relates to the Serving AMF for a UE to initiate localization of the UE for regulatory services (e.g., emergency calls from the UE) or for verifying the UE's location (country or international area) for NR satellite access.

[0092] A Mobile Terminated Location Request (MT-LR) involves an LCS client, either external or internal to the serving PLMN, sending a location request to the PLMN to seek the location of a target UE.

[0093] A Mobile Originated Location Request (MO-LR) relates to a UE that sends a request to the Serving PLMN for location-related information about the UE itself.

[0094] An Immediate Location Request relates to an LCS client that sends or triggers a location request for a target UE (or group of target UEs) and expects to receive a response containing the location information of the target UE (or group of target UEs) within a short time period that may be specified using LCS QoS. In regulated cases, one or more responses containing the location information of the target UE may be expected. Immediate Location Requests can be used for NI-LR, MT-LR, or MO-LR.

[0095] A Deferred Location Request (LCS) relates to an LCS client that sends a location request for a target UE (or group of target UEs) to the PLMN and expects to receive a response at some future point in time (or multiple points in time) that includes an instruction for an event to occur, which may be associated with a specific event associated with the target UE (or group of target UEs), and, if necessary, location information for the target UE (or group of target UEs). Deferred Location Requests are supported only for MT-LR.

[0096] Figure 6 shows an example of 5GC-MT-LR procedure 600 for regulated location services for a non-roaming scenario specified in 3GPP technical specification TS 23.273, entitled "5G System (5GS) Location Services (LCS) - Stage 2". In this scenario, an external LCS client 670 requests the current location of a target UE620 from 5GC. The target UE620 is assumed to be identified using SUPI or GPSI.

[0097] In the first step 601, the external client 670 sends a request to the GMLC660 for the current location of the target UE620. The request includes several items, among others, the requested LCS QoS, which is shown as the "LCS Service Request".

[0098] In a further step 602, GMLC660 sends a Namf_Location_ProvidePositioningInfo request to AMF640 to request the current location of UE620.

[0099] In a further step 603, if the UE620 is in the CM-IDLE state, the AMF640 initiates a network-triggered service request procedure to establish a signaling connection with the UE620. This is referred to as a "network-triggered service request".

[0100] In a further step 604, the AMF640 selects an LMF650 based on available information (e.g., the requested LCS QoS, LMF capacity, LMF load, LMF location) or based on the AMF local configuration (if the AMF640 is locally configured with a mapping table for UE identity and LMF address). This is referred to as "LMF selection".

[0101] In a further step 605, the AMF640 sends an Nlmf_Location_DetermineLocation request to the selected LMF650 to request the current location of the UE620. The request includes, among several items, the requested LCS QoS and, if available, UE positioning capability.

[0102] In a further step 606, the LMF650 performs a positioning procedure to determine the geographical location of the UE620. This is referred to as "UE positioning".

[0103] In a further step 607, the LMF650 returns an Nlmf_Location_DetermineLocation response to the AMF640 to return the current location of the UE620, i.e., the location estimate and accuracy, which may include information about the positioning method and the timestamp of the location estimate.

[0104] In a further step 608, the AMF640 returns a Namf_Location_ProvidePositioningInfo response to the GMLC660 to return the current location of the UE620.

[0105] In a further step 609, the GMLC660 sends a location service response to the external client 670, which includes the location information of the UE620. This is referred to as the "LCS service response".

[0106] Figure 7 shows an exemplary 5GC-MO-LR procedure 700 specified in 3GPP technical specification TS 23.273, entitled “5G System (5GS) Location Services (LCS) - Stage 2,” where the UE requests the Serving PLMN to acquire its own location or simply provide positioning assistance data. It is assumed that an LCS client is present in the UE and initiates MO-LR.

[0107] In the first step 701, if UE720 is in the CM-IDLE state, UE720 triggers a UE-triggered service request procedure to establish a signaling connection with AMF740. This is referred to as a "UE-triggered service request".

[0108] In a further step 702, UE720 sends an MO-LR request message to AMF740 contained within the UL NAS TRANSPORT message. Different types of location services may be requested, namely, the UE's location estimate, the UE's location estimate to be sent to the LCS client, or positioning assistance data. If UE720 requests that its own location or (for example, to use a location-based service) its own location be sent to the LCS client, this message carries the requested LCS QoS information (e.g., accuracy, response time). If UE720 requests that its location be sent to the LCS client, the message also includes the identity of the LCS client and the address of the GMLC through which the LCS client should access. If UE720 requests positioning assistance data instead, the embedded LPP message specifies the type of assistance data and the positioning method to which the assistance data applies.

[0109] In a further step 703, the AMF740 selects an LMF750 based on available information (e.g., requested LCS QoS, LMF capacity, LMF load, LMF location) or based on the AMF local configuration (if the AMF740 is locally configured with a mapping table for UE identity and LMF address). This is referred to as "LMF selection".

[0110] In a further step 704, the AMF740 sends an Nlmf_Location_DetermineLocation request to the selected LMF750. The request includes an indication, among several items, whether location estimates or positioning assistance data are requested.

[0111] In a further step 705, if the UE720 requests its own location, the LMF750 performs the positioning procedure to determine the geographical location of the UE720. If the UE720 requests positioning assistance data instead, the LMF750 transfers this data to the UE720. This is referred to as "UE Positioning".

[0112] In a further step 706, when the location estimate that best satisfies the required LCS QoS is obtained, or when the requested location assistance data is transferred to the UE720, the LMF750 returns an Nlmf_Location_DetermineLocation response to the AMF740. The response includes the location estimate, its age, and accuracy. If the UE720 is requesting positioning assistance data, steps 707 through 711 are skipped.

[0113] In a further step 707, if the location estimate is successfully obtained, the AMF740 sends an Ngmlc_Location_LocationUpdate request to the GMLC760. The request carries the identity of the UE720, the event (5GC-MO-LR) that triggers the location estimate, the location estimate, its age, and the accuracy obtained. In addition, the request includes the identity of the LCS client 770.

[0114] In a further step 708, the GMLC760 forwards a location information message to the LCS client 770 that carries the identity of the UE720, the event that triggers location estimation (5GC-MO-LR), and the location estimate in accordance with the LCS QoS requested by the UE720.

[0115] In a further step 709, the LCS client 770 sends a location information acknowledgment message to the GMLC 760 signaling that the location estimate from the UE 720 has been successfully received.

[0116] In a further step 710, the GMLC760 sends an Ngmlc_Location_LocationUpdate response to the AMF740 to acknowledge the successful reception of the location estimate by the LCS client 770.

[0117] In a further step 711, the AMF740 sends an MO-LR response message contained within the DL NAS TRANSPORT message. If the UE720 requests its own location, the response carries a timestamp of the location estimate (if available), including any location estimate requested by the UE720 and instructions received from the LMF750 indicating whether the obtained location estimate meets the required precision, or an indicator of whether the location estimate was successfully transferred to the identified LCS client 770.

[0118] Next, NR SL communication and discovery will be described further. To support V2X and non-V2X services, the SL communication feature was introduced in 3GPP Rel-16 NR. The interface used for SL communication (transmit / receive) between two adjacent UEs is shown as PC5. Table 5 and Figure 8 show a supported scenario 800 for SL communication where the first UE (UE1) 811, 821, 831 and the second UE (UE2) 812, 822, 832 are located in the coverage (IC) 810, partial coverage (PC) 820, and out-of-coverage (OOC) 830 of cell (gNB) 813, 823, 833.

[0119] [Table 5]

[0120] Sending and receiving user traffic via the PC5 interface is supported for unicast, groupcast, and broadcast transmissions. Sending and receiving signaling traffic via the PC5 interface is supported only for unicast transmissions. An SL connection via PC5 is defined as a logical connection between pairs of source and destination Layer 2 IDs. The source and destination Layer 2 IDs identify the sender and target of the SL communication, respectively. The corresponding pairs of source and destination Layer 2 IDs are used for the cast type. SL communication is based on the Proximity-Based Services (ProSe) function.

[0121] To enable SL communication between nearby UEs, the SL discovery procedure may need to be performed by the UE. The SL discovery procedure is used by the UE to discover other nearby UEs or to be discovered by other nearby UEs. For example, a UE that wishes to discover other nearby UEs sends a discovery message via PC5. Other nearby UEs monitor the discovery message and respond with a discovery response message if they wish to be discovered. After discovery, the UE can establish an SL communication connection with each of the responding UEs. Further details on NR sidelink communication and discovery can be found in the 3GPP technical specification TS 23.304 entitled "Proximity based Services (ProSe) in the 5G System (5GS)".

[0122] Specific SL positioning terminology is appropriate for disclosure in this specification. These terms are then briefly explained and used to refer to the roles of specific UEs / devices participating in an SL positioning session.

[0123] The initiator device starts the SL positioning / distancing session. The initiator device can be a network entity (e.g., gNB, LMF) or an UE / roadside unit (RSU).

[0124] The responder device responds to an SL positioning / distancing session from the initiator device. The responder device can be a network entity (e.g., gNB, LMF) or an UE / roadside unit (RSU).

[0125] A target UE is a target UE whose location (absolute or relative) will be obtained by the network or by the UE itself.

[0126] The term "sidelink positioning" refers to the positioning of a UE using SL, i.e., a reference signal transmitted via the PC5 interface, to acquire absolute position, relative position, or distance information.

[0127] The term "distancing" refers to determining the distance and / or direction between an UE and another entity, such as an anchor UE.

[0128] An anchor UE is a UE that supports the positioning of a target UE by, for example, transmitting and / or receiving a reference signal for positioning and providing positioning-related information via the PC5 interface (sometimes called an SL reference UE).

[0129] The Assistant UE is a UE that supports distance measurement / sidelink positioning between the SL Reference UE / Anchor UE and the Target UE via the PC5 when direct distance measurement / sidelink positioning between the SL Reference UE / Anchor UE and the Target UE is not possible. The measured values / results of distance measurement / sidelink positioning between the Assistant UE and the SL Reference UE and the measured values / results of distance measurement / sidelink positioning between the Assistant UE and the Target UE are determined and used to derive the distance measurement / sidelink positioning result between the Target UE and the SL Reference UE.

[0130] The SL positioning server UE is a UE that provides location calculations for services based on SL positioning and ranging. The SL positioning server UE interacts with other UEs via PC5 as needed to calculate the location of the target UE. If location calculation is supported, the target UE or SL reference UE can act as the SL positioning server UE.

[0131] An SL positioning client UE is a third-party UE other than the SL reference UE and target UE that initiates ranging / sidelink positioning service requests for applications residing on it.

[0132] To support SL positioning in positioning operation scenarios based on Joint PC5-Uu, several solutions are proposed herein. These include instructing the UE's SL positioning capability to the network, extending the Nlmf_Location_DetermineLocation request message, and defining new LPP / SLPP messages for inter-server communication.

[0133] Regarding the instruction of a UE's SL positioning capability to the network, the UE indicates its SL positioning capability to the AMF as part of NAS signaling, for example, in a NAS registration request message specified in 3GPP technical specification TS 24.501, entitled "Non-Access-Stratum (NAS) protocol for 5G System (5GS) - Stage 3". Figure 9 shows one embodiment of the SL positioning capability signaling format 900. As shown, format 900 is defined as a bit string, and the UE sets the corresponding bits if the corresponding capability is supported. The value "server-ue" 910 is set if the UE can act as a server UE, the value "anchor-ue" 920 is set if the UE can act as an anchor UE, the value "lpp" 930 is set if the UE supports LPP, and the value "slpp" 940 is set if the UE supports SLPP. Alternatively, the UE may indicate its SL positioning capability to the RAN node (i.e., gNB) as part of AS signaling, specifically in a UE capability information message specified in the 3GPP technical specification TS 38.331 entitled "NR Radio Resource Control (RRC) Protocol specification." The RAN node then forwards this information to the AMF.

[0134] Regarding the extension of the Nlmf_Location_DetermineLocation request message, the Nlmf_Location_DetermineLocation request message (specified in 3GPP technical specification TS 29.572 entitled “5G System Location Management Services - Stage 3”) is extended to include SL positioning information. The SL positioning information includes a list of available anchor UEs and server UEs within the area of ​​the target UE. Figure 10 shows one embodiment of format 1000 of this list. Format 1000 of the list can contain up to 64 entries, each entry containing information about the UE's identity (value of “ue-Identity” 1010), the area where the UE is located (value of “areaInfo” 1020 given by the cell identity and tracking area identity), and the SL positioning capability supported by the UE (value of “sl-PositioningCapability” 1030).

[0135] Regarding the definition of new LPP / SLPP messages, new LPP / SLPP messages for inter-server communication, "Determine Location Request" and "Determine Location Response," are defined.

[0136] The "Determine Location Request" message is sent from the LMF to the server UE to request the location of the target UE. This message includes the requested LCS QoS for estimating the target UE's location and information about available anchor UEs within the target UE's area.

[0137] The "Determine Location Response" message is sent from the server UE to the LMF and includes the location estimate and accuracy of the target UE.

[0138] Alternatively, if the server UE is LPP-enabled, existing LPP messages can be used as request / response messages, such as the RequestLocationInformation and ProvideLocationInformation messages specified in the 3GPP technical specification TS 37.355 entitled "LTE Positioning Protocol (LPP)".

[0139] The advantages of the proposed solution include the support for SL positioning in positioning operation scenarios based on joint PC5-Uu when an SL positioning-enabled LMF is available, but the LMF may be determined to be used when the SL positioning server UE performs result calculation, method determination, support data distribution and / or anchor UE selection due to current load, and when an LMF that is not SL positioning-enabled is available.

[0140] Figure 11 shows the message flow in one embodiment 1100 of a positioning operation scenario based on Joint PC5-Uu that benefits from the proposed solution. In this particular embodiment 1100, certain assumptions are made, including that the target UE, anchor UE, and server UE are all within network coverage. Furthermore, this embodiment is applicable to MO-LR and MT-LR procedures. Based on a location request from an LCS client (not shown in Figure 11), SL positioning needs to be performed for the target UE (determined by LCS QoS). Furthermore, it is assumed that the LMF is capable of SL positioning.

[0141] Figure 11 shows the message flow in one embodiment 1100 of a positioning operation scenario based on Joint PC5-Uu.

[0142] In steps 1101a / 1101b, 1102a / 1102b, and 1103a / 1103b, while the NAS registration procedure is successful, the UEs (Target UE1120, Anchor UE1180, and Server UE1190) demonstrate their SL positioning capabilities to the AMF1140. These steps are indicated as "Registration Request" and "Registration Accept" for UE1120, 1180, and 1190, respectively.

[0143] Target UE1120 indicates that it supports LPP and SLPP, and the bits for "server-ue" 910 and "anchor-ue" 920 in Figure 9 are not set.

[0144] The anchor UE1180 indicates that it supports LPP and SLPP. Furthermore, the anchor UE1180 can function as an anchor UE, and the bit for "server-ue" 910 in Figure 9 is not set.

[0145] Server UE1190 indicates that it supports LPP and SLPP. Furthermore, it indicates that Server UE1190 can function as a Server UE, and the bits for "anchor-ue" 920 in Figure 9 are not set.

[0146] In a further step 1104, the AMF1140 selects an SL positioning-enabled LMF1150 based on its local configuration, i.e., based on the mapping of the target UE identity and LMF address. This is shown as "LMF selection".

[0147] In a further step 1105, the AMF1140 sends an Nlmf_Location_DetermineLocation request message to the selected LMF1150. The request includes several items, including a request for the location estimate of the target UE, the requested LCS QoS, and SL positioning information including the available anchor UE1180 and server UE1190 within the area of ​​the target UE1120.

[0148] In a further step 1106, due to the current load, the selected LMF1150 determines that the SL positioning server UE1190 will perform result calculation, method determination, support data distribution, and anchor UE selection. Therefore, the selected LMF1150 sends a “Determine Location Request” message to the server UE1190 via LPP or SLPP to request the location of the target UE1120. The “Determine Location Request” message includes the requested LCS QoS for location estimation of the target UE1120 and information about available anchor UEs within the area of ​​the target UE1120.

[0149] In a further step 1107, SL positioning of target UE1120 is performed between server UE1190, anchor UE1180, and target UE1120.

[0150] In a further step 1108, the server UE1190 sends a “Determine Location Response” message to the LMF1150 via LPP or SLPP. The response message includes the estimated location and precision of the target UE1120.

[0151] In a further step 1109, the LMF1150 sends an Nlmf_Location_DetermineLocation response message to the AMF1140 to return the current location of the target UE1120, i.e., the location estimate and accuracy.

[0152] This disclosure provides a user equipment “UE” device for wireless communications, comprising a processor and memory coupled to the processor, wherein the processor is configured to cause the UE device to transmit a first message to a first device of a wireless communications network, the first message comprising one or more parameters indicating the sidelink positioning capability of the UE device.

[0153] In some embodiments, the first device includes an access and mobility management function "AMF".

[0154] In some embodiments, the processor is configured to cause the UE device to send a first message as part of a non-access layer "NAS" registration request message.

[0155] In some embodiments, one or more parameters are selected from a list of parameters consisting of a server UE parameter indicating whether the UE device can act as a server UE for location calculation for sidelink positioning, an anchor UE parameter indicating whether the UE device can act as an anchor UE to support sidelink positioning, an LTE positioning protocol "LPP" parameter indicating whether the UE device supports LPP, and a sidelink positioning protocol "SLPP" parameter indicating whether the UE device supports SLPP.

[0156] In some embodiments, the UE provides one or more parameters indicating sidelink positioning capability as part of AS signaling to the RAN node, which then forwards these to the AMF.

[0157] In some embodiments, the processor is further configured to cause the UE device to receive a second message from a second device of the wireless communication network requesting sidelink positioning of a target UE, wherein the second message includes one or more quality of service (QoS) requirements for location estimation of the target UE and one or more identifiers of one or more anchor UEs within the target area of ​​the target UE.

[0158] The second message may be called a “determine location request” LPP / SLPP message, or it may be part of an existing LPP message.

[0159] In some embodiments, the processor is further configured to cause the UE device to determine the estimated location of the target UE and the associated location accuracy using one or more QoS requirements and one or more anchor UEs.

[0160] In some embodiments, the processor is further configured to cause the UE device to transmit a third message to a second device, the third message including an estimated location and associated location accuracy.

[0161] In some embodiments, the second device includes a location management function "LMF".

[0162] Figure 12 shows one embodiment of Method 1200 in a user device for wireless communication.

[0163] The first step 1210 includes the step of transmitting a first message to a first device of a wireless communication network, wherein the first message includes one or more parameters indicating the sidelink positioning capability of the UE device.

[0164] In certain embodiments, method 1200 may be implemented by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0165] In some embodiments, the first apparatus includes an AMF.

[0166] In some embodiments, one or more parameters are selected from a list of parameters consisting of a server UE parameter indicating whether the UE device can act as a server UE for location calculation for sidelink positioning, an anchor UE parameter indicating whether the UE device can act as an anchor UE to support sidelink positioning, an LPP parameter indicating whether the UE device supports LPP, and an SLPP parameter indicating whether the UE device supports SLPP.

[0167] In some embodiments, the method includes the step of receiving a second message from a second device of a wireless communication network requesting sidelink positioning of a target UE, wherein the second message includes one or more QoS requirements for location estimation of the target UE and one or more identifiers of one or more anchor UEs within the target area of ​​the target UE.

[0168] In some embodiments, the method further includes the step of determining the estimated location of a target UE and the associated location accuracy using one or more QoS requirements and one or more anchor UEs.

[0169] In some embodiments, the method further includes the step of sending a third message to a second device, wherein the third message includes an estimated location and associated location accuracy.

[0170] In some embodiments, the second device includes an LMF.

[0171] This disclosure further provides a first device in a wireless communication network, comprising a processor and a memory coupled to the processor, wherein the processor is configured to cause the first device to receive a request from a consumer entity to locate a target UE in a target area, determine one or more UE devices in the target area, each having sidelink positioning capability, and transmit a fourth message to a second device in the wireless communication network indicating one or more UE devices and their respective sidelink positioning capabilities.

[0172] In some embodiments, the consumer entity may include a UE, a network entity, and / or an external client.

[0173] In some embodiments, the processor is configured to cause the first device to determine one or more UE devices by causing the first device to receive one or more first messages from one or more UE devices, each first message including one or more parameters indicating the sidelink positioning capability of the respective UE device.

[0174] In some embodiments, the processor is configured to cause the first device to receive one or more first messages as part of each NAS registration request message.

[0175] In some embodiments, one or more parameters are selected from a list of parameters consisting of a server UE parameter indicating whether each UE device can act as a server UE for location calculation for sidelink positioning, an anchor UE parameter indicating whether each UE device can act as an anchor UE to support sidelink positioning, an LPP parameter indicating whether each UE device supports LPP, and an SLPP parameter indicating whether each UE device supports SLPP.

[0176] In some embodiments, the fourth message includes a list of anchor UE devices and server UE devices within the target area of ​​the target UE.

[0177] In some embodiments, each entry in the list includes the identifier of the respective UE, the location area of ​​the respective UE, and the SL positioning capability of the respective UE.

[0178] In some embodiments, a request to locate the location of a target UE within a target area includes one or more QoS requirements for estimating the location of the target UE, and a fourth message includes one or more QoS requirements.

[0179] The fourth message may include an Nlmf_Location_DetermineLocation request message.

[0180] In some embodiments, the processor is further configured to cause the first device to determine the second device based on a predetermined mapping of the target UE to the second device.

[0181] In some embodiments, the processor is further configured to cause the first device to receive a fifth message from the second device, the fifth message including the estimated location of the target UE and the associated location accuracy.

[0182] In some embodiments, the processor is further configured to cause the first device to transmit the estimated location and location accuracy to the consumer entity.

[0183] The fifth message could be the Nlmf_Location_DetermineLocation response message.

[0184] In some embodiments, the first apparatus includes an AMF, and the second apparatus includes an LMF.

[0185] Figure 13 shows one embodiment of Method 1300 in a first device in a wireless communication network.

[0186] The first step 1310 includes receiving a request from a consumer entity asking to locate the location of a target UE within a target area.

[0187] A further step 1320 includes determining one or more UE devices within the target area, each having side-link positioning capability.

[0188] A further step 1330 includes sending a fourth message to a second device of the wireless communication network indicating one or more UE devices and their respective sidelink positioning capabilities.

[0189] In certain embodiments, method 1300 may be implemented by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0190] In some embodiments, determining one or more UE devices includes receiving one or more first messages from one or more UE devices, each of which includes one or more parameters indicating the sidelink positioning capability of the respective UE device.

[0191] In some embodiments, one or more parameters are selected from a list of parameters consisting of a server UE parameter indicating whether each UE device can act as a server UE for location calculation for sidelink positioning, an anchor UE parameter indicating whether each UE device can act as an anchor UE to support sidelink positioning, an LPP parameter indicating whether each UE device supports LPP, and an SLPP parameter indicating whether each UE device supports SLPP.

[0192] In some embodiments, the fourth message includes a list of anchor UE devices and server UE devices within the target area of ​​the target UE.

[0193] In some embodiments, each entry in the list includes the identifier of the respective UE, the location area of ​​the respective UE, and the SL positioning capability of the respective UE.

[0194] In some embodiments, a request to locate the location of a target UE within a target area includes one or more QoS requirements for estimating the location of the target UE, and a fourth message includes one or more QoS requirements.

[0195] Some embodiments include determining the second device based on a predetermined mapping of the target UE to the second device.

[0196] Some embodiments involve receiving a fifth message from a second device, the fifth message including the estimated location of a target UE and associated location accuracy.

[0197] In some embodiments, the first apparatus includes an AMF, and the second apparatus includes an LMF.

[0198] This disclosure further provides a second device in a wireless communication network, comprising a processor and memory coupled to the processor, wherein the processor is configured to cause the second device to: receive a fourth message from a first device of the wireless communication network indicating one or more UE devices and their respective sidelink positioning capabilities for locating a target UE in a target area; determine a server UE device from one or more UE devices for performing location calculations for sidelink positioning of the target UE; and transmit a second message to the server UE device requesting sidelink positioning of the target UE, wherein the second message includes one or more QoS requirements for location estimation of the target UE and one or more identifiers of one or more anchor UEs in the target area of ​​the target UE.

[0199] In some embodiments, the processor is further configured to cause a second device to receive a third message from a server UE device, the third message including the estimated location of a target UE and associated location accuracy.

[0200] In some embodiments, the sidelink positioning capability per UE device includes one or more parameters selected from a list of parameters consisting of a server UE parameter indicating whether the UE device can act as a server UE for location calculation for sidelink positioning, an anchor UE parameter indicating whether the UE device can act as an anchor UE to support sidelink positioning, an LPP parameter indicating whether the UE device supports LPP, and an SLPP parameter indicating whether the UE device supports SLPP.

[0201] In some embodiments, the second device is an LMF, and the first device is an AMF.

[0202] In some embodiments, the second message may be a “determine location request” LPP / SLPP message, or, if the UE supports LPP, the second message may form part of an existing LPP message (i.e., a RequestLocationInformation message).

[0203] In some embodiments, the third message may be a “determine location response” message, or an existing ProvideLocationInformation LPP message from the server UE containing the location estimate and precision of the target UE.

[0204] In some embodiments, the fourth message includes a list of anchor UE devices and server UE devices within the target area of ​​the target UE.

[0205] In some embodiments, each entry in the list includes the identifier of the respective UE, the location area of ​​the respective UE, and the SL positioning capability of the respective UE.

[0206] In some embodiments, the processor is further configured to cause the second device to receive a fifth message from the server UE device, the fifth message including the estimated location of the target UE and the associated location accuracy.

[0207] Figure 14 shows one embodiment of method 1400 in a second device in a wireless communication network.

[0208] The first step 1410 includes receiving a fourth message from a first device of the wireless communication network indicating one or more UE devices and their respective sidelink positioning capabilities for locating the location of a target UE within a target area.

[0209] A further step 1420 includes determining, from one or more UE devices, a server UE device to perform location calculations for sidelink positioning of the target UE.

[0210] A further step 1430 is to send a second message to a server UE device requesting sidelink positioning of a target UE, the second message comprising one or more QoS requirements for location estimation of the target UE and one or more identifiers of one or more anchor UEs within the target area of ​​the target UE.

[0211] Some embodiments include receiving a third message from a server UE device, the third message including the estimated location of a target UE and the associated location accuracy.

[0212] In certain embodiments, method 1400 may be implemented by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0213] In some embodiments, the sidelink positioning capability per UE device includes one or more parameters selected from a list of parameters consisting of a server UE parameter indicating whether the UE device can act as a server UE for location calculation for sidelink positioning, an anchor UE parameter indicating whether the UE device can act as an anchor UE to support sidelink positioning, an LPP parameter indicating whether the UE device supports LPP, and an SLPP parameter indicating whether the UE device supports SLPP.

[0214] In some embodiments, the second device is an LMF, and the first device is an AMF.

[0215] In some embodiments, the second message is either a “determine location request” LPP / SLPP message, or, if the UE supports LPP, part of an existing LPP message (i.e., RequestLocationInformation).

[0216] In some embodiments, the third message may be a “determine location response” message or may be part of an existing ProvideLocationInformation LPP message from the server UE that includes the location estimate and precision of the target UE.

[0217] In some embodiments, the fourth message includes a list of anchor UE devices and server UE devices within the target area of ​​the target UE.

[0218] In some embodiments, each entry in the list includes the identifier of the respective UE, the location area of ​​the respective UE, and the SL positioning capability of the respective UE.

[0219] Some embodiments include receiving a fifth message from a server UE device, wherein the fifth message includes the estimated location of a target UE and the associated location accuracy.

[0220] To support SL positioning in positioning operation scenarios based on Joint PC5-Uu, several novel embodiments of the proposed solution are provided.

[0221] The first novel aspect includes a UE that, as part of NAS signaling, for example in a NAS registration request message, indicates its SL positioning capability to the AMF. The SL positioning capability includes indications of whether the UE can act as a server UE and / or anchor UE, and whether the UE supports LPP and / or SLPP. Alternatively, the UE indicates its SL positioning capability to a RAN node (i.e., a gNB) as part of AS signaling, i.e., in a UE capability information message, and the RAN node forwards the information to the AMF.

[0222] Further novel aspects include an extended Nlmf_Location_DetermineLocation request message that includes SL positioning information. The SL positioning information includes a list of available anchor UEs and server UEs within the area of ​​the target UE.

[0223] Further novel aspects include new LPP / SLPP messages for server-to-server communication, defined herein and referred to as “Determine Location Request” and “Determine Location Response.” The “Determine Location Request” message is sent from the LMF to the server UE to request the location of the target UE. This message includes the requested LCS QoS for estimating the target UE's location and information about available anchor UEs within the target UE's area. The “Determine Location Response” message is sent from the server UE to the LMF and includes the estimated location and precision of the target UE. Alternatively, if the server UE is LPP-enabled, existing LPP messages may be used as request / response messages, e.g., RequestLocationInformation and ProvideLocationInformation messages.

[0224] A method for sidelink positioning of a target device in network coverage is provided, comprising the steps of: a second communication device receiving a first message from the first communication device including sidelink positioning capability; the second communication device deciding to select a third communication device in accordance with the received first message; the second communication device sending a second message from the second communication device to the third communication device including a request for sidelink positioning; the third communication device deciding to trigger sidelink positioning for a fourth communication device; and the third communication device sending a third message from the third communication device to the fourth communication device including a request for sidelink positioning.

[0225] In some embodiments, the first communication device is a sidelink device, the second communication device is an AMF, the third communication device is an LMF, and the fourth communication device is a sidelink positioning server device.

[0226] In some embodiments, the first message, including sidelink positioning capability, includes instructions for supported positioning protocols or supported roles in sidelink positioning, or any combination thereof.

[0227] In some embodiments, a second message including a request for sidelink positioning includes information on available sidelink positioning anchor devices and server devices within the area of ​​the target device.

[0228] In some embodiments, a third message including a request for sidelink positioning includes the requested QoS for location estimation of the target device and information on available sidelink positioning anchor devices within the area of ​​the target device.

[0229] It should be noted that the methods and apparatus described above are illustrative of the invention, not limiting it, and that many alternative configurations can be designed by those skilled in the art without departing from the scope of the appended claims. The word “comprising” does not exclude the presence of elements or steps other than those listed in the claims, and “a” or “an” does not exclude plurals; a single processor or other unit may perform the functions of several units enumerated in the claims. No reference numerals in the claims should be construed to limit their scope.

[0230] Furthermore, although the examples are given in the context of specific communication standards, these examples are not intended to be a limitation on the communication standards to which the disclosed methods and apparatus may be applied. For example, while specific examples are given in the context of 3GPP, the principles disclosed herein can also be applied to other wireless communication systems, and in fact, to any communication system that uses routing rules.

[0231] The method can also be embodied in a set of instructions that, when stored on a computer-readable medium and loaded into a computer processor, digital signal processor (DSP), or similar processor, cause the processor to perform the method described above.

[0232] The methods and apparatus described may be practiced in other specific forms. The methods and apparatus described should be considered in all respects as illustrative and not limiting. Accordingly, the scope of the invention is indicated not by the above description but by the appended claims. All modifications that fall within the meaning and scope of the equivalent claims should be encompassed within their scope.

[0233] The following abbreviations are relevant to the fields covered in this document: 3GPP, Third Generation Partnership Project; 5GS, 5G Systems; A-GNSS, Assisted GNSS; AMF, Access and Mobility Management Function; AoA, Angle of Arrival; AoD, Angle of Departure; AS, Access Layer; CM, Connection Management; DL, Downlink; DL TDOA, Downlink Arrival Time Difference; E-CID, Extended Cell ID; FR, Frequency Range; GMLC, Gateway Mobile Location Center; GNSS, Global Navigation Satellite System; GPSI, General Purpose Public Subscription Identifier; HW, Hardware; IC, In-Coverage; IIoT, Industrial IoT; IoT, Internet of Things; KPI, Key Performance Indicator; LCS, Location Services; LMF, Location Management Function; LPP, LTE Positioning Protocol; LTE, Long-Term Evolution; MO-LR, Mobile Outgoing Location Request; MT-LR, Mobile Incoming Location Request; Multi-RTT, Multi-Round Trip Time; NAS, Non-Access Layer; NG-RAN, Next Generation RAN; NI-LR, Network Induction Location Request; NR, New Radio NRPPa, NR Positioning Protocol A; OOC, Out-of-Coverage; PC, Partial Coverage; PDU, Protocol Data Unit; PHY, Physical Layer; PLMN, Public Land Mobile Network; PPP, Precision Single-Person Positioning; ProSe, Proximity-Based Service; PRS, Positioning Reference Signal; PSAP, Public Safety Response Point; QoS, Quality of Service; RAN, Radio Access Network; RAT, Radio Access Technology; RRC, Radio Resource Control; RSU, Roadside Unit; RTK, Real-Time Kinematic; SL, Sidelink; SLPP, Sidelink Positioning Protocol; SUPI, Subscription Permanent Identifier; SW, Software; TDOA, Time to Arrival Difference; TTFF, Initial Position Calculation Time; UE, User Equipment; UL, Uplink; V2X, Vehicle-to-Everything; WID, Work Item Description [Explanation of symbols]

[0234] 100 Wireless Communication Systems 102 Remote Unit 104 Network Units 200 User equipment, devices 205 Processor 210 memory 215 Input Devices 220 Output Devices 225 Transceiver 230 Transmitter 235 Receiver 240 network interfaces 245 Application Interfaces 300 network nodes 305 Processor 310 memory 315 Input Devices 320 Output Devices 325 Transceiver 330 Transmitter 335 Receiver 340 Network Interfaces 345 Application Interfaces 400 LPP message transfers 420 UE 430 NG-RAN nodes 440 AMF 450 LMF 500 Location Services (LCS) Architecture 510 External LCS client, LCS client 520 5GC 521 GMLC 522 AMF 523 LMF 524 NG-RAN nodes 530 UE, Target UE 600 5GC-MT-LR Procedure 620 Target UE 640 AMF 650 LMF 660 GMLC 670 External LCS client, external client 700 5GC-MO-LR Procedure 720 UE 740 AMF 750 LMF 760 GMLC 770 L Cs Client 800 Scenarios 810 Coverage (IC) 811 First UE (UE1) 812 Second UE (UE2) 813 cells (gNB) 820 Partial coverage (PC) 821 First UE (UE1) 822 Second UE (UE2) 823 cells (gNB) 830 Out of Coverage (OOC) 831 First UE (UE1) 832 Second UE (UE2) 833 cells (gNB) 900 format 910 server-ue 920 anchor-ue 930 lpp 940 slpp 1000 format 1010 ue-Identity 1020 areaInfo 1030 sl-PositioningCapability 1100 Embodiment 1120 UE, Target UE 1140 AMF 1150 LMF 1180 UE, Anchor UE 1190 UE, Server UE 1200 methods 1300 methods 1400 methods

Claims

1. A user equipment (UE) device for wireless communication, Processor and The UE device comprises the aforementioned processor and a memory coupled thereto, and the processor provides the UE device Transmitting a first message to a first device of a wireless communication network, wherein the first message includes one or more parameters indicating the sidelink positioning capability of the UE device. A UE device configured to perform the following actions.

2. The UE device according to claim 1, wherein the first device includes an access and mobility management function "AMF".

3. The one or more of the above parameters are Server UE parameters indicating whether the UE device can function as a server UE for location calculation for sidelink positioning, Anchor UE parameters indicating whether the aforementioned UE device can function as an anchor UE to support side-link positioning, The LTE positioning protocol "LPP" parameter indicating whether the UE device supports LPP, and The Sidelink Positioning Protocol "SLPP" parameter indicates whether the UE device supports SLPP. The UE device according to claim 1 or 2, selected from a list of parameters comprising:

4. The processor provides the UE device, Receiving a second message from a second device of the wireless communication network requesting sidelink positioning of a target UE, wherein the second message is One or more Quality of Service (QoS) requirements for estimating the location of the target UE, One or more identifiers of one or more anchor UEs within the target area of ​​the aforementioned target UE and Including receiving The UE apparatus according to claim 3, further configured to perform the following:

5. The processor provides the UE device, Using the one or more QoS requirements and the one or more anchor UEs, determine the estimated location of the target UE and the associated location accuracy. The UE apparatus according to claim 4, further configured to perform the following.

6. The processor provides the UE device, Transmitting a third message to the second device, wherein the third message includes the estimated location and associated location accuracy. The UE apparatus according to claim 5, further configured to perform the following:

7. The UE device according to any one of claims 4 to 6, wherein the second device includes a location management function "LMF".

8. A first device in a wireless communication network, Processor and The device comprises a memory coupled with the processor, and the processor is configured in the first device. Receiving a request from a consumer entity to identify the location of a target UE within a target area, To determine one or more UE devices having side-link positioning capabilities within the aforementioned target area, A fourth message indicating the one or more UE devices and their respective sidelink positioning capabilities is transmitted to the second device of the wireless communication network. A first device configured to perform the following action.

9. The processor is provided to the first device, Receiving one or more first messages from the one or more UE devices, wherein each first message includes one or more parameters indicating the sidelink positioning capability of the respective UE device. The first device according to claim 8, configured to cause the first device to determine one or more UE devices by performing the following.

10. The one or more of the above parameters are Server UE parameters indicating whether each UE device can function as a server UE for location calculations for sidelink positioning. Anchor UE parameters indicating whether each of the aforementioned UE devices can function as an anchor UE to support sidelink positioning, LPP parameters indicating whether each of the aforementioned UE devices supports LPP, and SLPP parameters indicating whether each of the aforementioned UE devices supports SLPP. The first apparatus according to claim 8 or 9, selected from a list of parameters comprising:

11. The first device according to claim 10, wherein the fourth message includes a list of anchor UE devices and server UE devices within the target area of ​​the target UE.

12. Each entry in the aforementioned list is The identifier of each of the aforementioned UE devices, The location area of ​​each of the aforementioned UE devices, and The sidelink positioning capability of each of the aforementioned UE devices The first apparatus according to claim 11, including the following:

13. The first device according to any one of claims 8 to 12, wherein the request for identifying the location of the target UE within the target area includes one or more QoS requirements for location estimation of the target UE, and the fourth message includes the one or more QoS requirements.

14. The processor is provided to the first device, Determining the second device based on a predetermined mapping of the target UE to the second device. The first apparatus according to any one of claims 8 to 13, further configured to perform the following:

15. The processor is provided to the first device, Receiving a fifth message from the second device, wherein the fifth message includes the estimated location of the target UE and the associated location accuracy. The first apparatus according to any one of claims 8 to 14, further configured to perform the following:

16. The first apparatus according to any one of claims 8 to 15, wherein the first apparatus includes an AMF and the second apparatus includes an LMF.

17. A second device in a wireless communication network, Processor and The device comprises a memory coupled with the processor, and the processor provides the second device, Receiving a fourth message from the first device of the wireless communication network indicating one or more UE devices for locating the position of a target UE within a target area and their respective sidelink positioning capabilities, From the one or more UE devices mentioned above, a server UE device is determined for performing location calculations for sidelink positioning of the target UE. Sending a second message to the server UE device requesting sidelink positioning of the target UE, wherein the second message is One or more QoS requirements for estimating the location of the target UE, One or more identifiers of one or more anchor UEs within the target area of ​​the target UE and Sending and A second device configured to perform the following action.

18. The processor provides the second device with Receiving a third message from the server UE device, wherein the third message includes the estimated location of the target UE and the associated location accuracy. A second apparatus according to claim 17, further configured to perform the following:

19. The side link positioning capability for each UE device is, Server UE parameters indicating whether the UE device can function as a server UE for location calculation for sidelink positioning, Anchor UE parameters indicating whether the aforementioned UE device can function as an anchor UE to support side-link positioning, An LPP parameter indicating whether the UE device supports LPP, and SLPP parameter indicating whether the UE device supports SLPP The second apparatus according to claim 17 or 18, comprising one or more parameters selected from a list of parameters consisting of the following.

20. The second apparatus according to any one of claims 17 to 19, wherein the second apparatus is an LMF and the first apparatus is an AMF.

Images