Selecting sidelink positioning device in wireless communication network

Abstract

There is provided a user equipment "UE" apparatus for wireless communication, the UE apparatus comprising: a processor; and a memory coupled to the processor, the processor configured to cause the UE device to send a first message to a first device of the wireless communication network, where the first message includes one or more parameters indicative of a sidelink positioning capability of the UE device.

Description

Technical Field

[0001] The subject matter disclosed herein generally relates to the field of enabling selection of a sidelink positioning device in a wireless communication network. This document defines a user equipment device for wireless communication, a first device and a second device in a wireless communication network, and a method in the user equipment device, the first device, and the second device. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) has considered sidelink (SL) positioning in Rel-18 New Radio (NR) in 3GPP WIDRP-223549, titled "New Work Item Description (WID) on Extending and Improving NR Positioning." This has been considered to support certain target accuracy requirements for SL positioning.

[0003] SL positioning is designed 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 the user equipment (UE) by using SL positioning methods such as round-trip time (RTT) solutions using SL, SL angle of arrival (AoA), and SL time difference of arrival (TDOA).

[0004] SL positioning will be based on a new SL Positioning Reference Signal (PRS) (which is sent over the PC5 interface) and will be supported in all coverage scenarios (i.e., in-coverage, partial coverage, and out-of-coverage scenarios), as well as PC5-only and PC5-Uu-based joint operation scenarios. In order to exchange SL positioning-related information between UEs over the PC5 interface, a new protocol denoted as the Sidelink Positioning Protocol (SLPP) will be introduced. The functions that SLPP should support include: SL positioning capability transfer; SL positioning assistance data exchange; SL location information transmission; error handling; and abort.

[0005] The propagation types considered for SLPP signaling include unicast, multicast, and broadcast, but unicast / one-to-one operation is assumed as the baseline for SLPP signaling exchanges between UEs. For the exchange of SL positioning capabilities and SL positioning assistance data information, it is assumed that multicast and broadcast (in addition to unicast) are supported only when multicast / broadcast protection of SL positioning signaling can be ensured. Summary of the Invention

[0006] In Uu-based positioning, the access and mobility management function (AMF) performs location management function (LMF) selection based on available information (e.g., requested location service (LCS) quality of service (QoS) requirements, LMF capabilities, LMF load, LMF location) or based on AMF local configuration (if the AMF is locally configured with a mapping table of UE identity and LMF address).

[0007] Now, in joint positioning based on PC5-Uu, the AMF may need to select an LMF with SL positioning capability for result calculation, method determination, auxiliary data distribution and anchor UE selection. Based on the requested LCS QoS, the AMF knows whether SL positioning is required for the Mobile Terminated Location Request (MT-LR) or Mobile Originated Location Request (MO-LR) process. However, there are certain issues for the AMF when selecting the LMF. In particular, an LMF with SL positioning capability may be available, but due to the current load, the LMF may decide that a SL positioning server UE is required to perform result calculation, method determination, auxiliary data distribution and / or anchor UE selection. In addition, the available LMF may not have SL positioning capability.

[0008] In order to solve the above problem, a solution is needed on how the AMF can provide information about available SL positioning server UEs and anchor UEs to the selected LMF so that the LMF can perform SL positioning.

[0009] Although the direct solution to support SL positioning in the joint positioning operation scenario based on PC5-Uu is to locally configure the AMF with a mapping table of UE identity and LMF address of LMF with SL positioning capability, this solution is very static and cannot completely avoid the above problems.

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

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

[0012] A first device in a wireless communication network is also provided, the first device comprising: a processor; and a memory coupled to the processor, the processor being configured to enable the first device to: receive a request from a consumer entity for locating a target UE in a target area; determine one or more UE devices with corresponding sidelink positioning capabilities in the target area; and send a fourth message to a second device in the wireless communication network, the fourth message indicating the one or more UE devices and their corresponding sidelink positioning capabilities.

[0013] A second device in a wireless communication network is also provided, the second device including: a processor; and a memory coupled to the processor, the processor being configured to enable the second device to: receive a fourth message from a first device in the wireless communication network, the fourth message indicating one or more UE devices and their corresponding sidelink positioning capabilities for locating a target UE in a target area; determine a server UE device from the one or more UE devices, the server UE device being used to perform position calculation for sidelink positioning of the target UE; and send 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 position estimation of the target UE; and one or more identifiers of one or more anchor UEs in the target area of ​​the target UE.

[0014] Also provided is a method for wireless communication in a user equipment device, the method comprising sending a first message to a first device of a wireless communication network, wherein the first message comprises one or more parameters indicating a sidelink positioning capability of the UE device.

[0015] A method in a first device in a wireless communication network is also provided, the method comprising: receiving a request from a consumer entity for locating a target UE in a target area; determining one or more UE devices with corresponding sidelink positioning capabilities in the target area; and sending a fourth message to a second device in the wireless communication network, the fourth message indicating the one or more UE devices and their corresponding sidelink positioning capabilities.

[0016] A method in a second device in a wireless communication network is also provided, the method comprising: receiving a fourth message from a first device in the wireless communication network, the fourth message indicating one or more UE devices and their corresponding sidelink positioning capabilities for locating a target UE in a target area; determining a server UE device from the one or more UE devices, the server UE device being used to perform position calculation for sidelink positioning of the target UE; and sending a second message to the server UE device requesting sidelink positioning of the target UE, wherein the second message comprises: one or more QoS requirements for position estimation of the target UE; and one or more identifiers of one or more anchor UEs in the target area of ​​the target UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to illustrate the manner in which the advantages and features of the present disclosure can be obtained, the present disclosure is described by reference to certain devices and methods shown in the accompanying drawings. Each of these drawings depicts only certain aspects of the present disclosure and, therefore, should not be considered as limiting the scope thereof. For the sake of clarity, the drawings may have been simplified and are not necessarily drawn to scale.

[0018] Methods and apparatus for selecting a sidelink positioning device in a wireless communication network will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0019] Figure 1 An embodiment of a wireless communication system is illustrated;

[0020] Figure 2 An embodiment of a user equipment device is illustrated;

[0021] Figure 3 An embodiment of a network node is illustrated;

[0022] Figure 4 An example of LPP message transmission between the LMF and the UE is shown;

[0023] Figure 5 An example of an LCS architecture is illustrated;

[0024] Figure 6 illustrates an example of the 5GC-MT-LR procedure for non-roaming regulated location services;

[0025] Figure 7 An example of a 5GC-MO-LR process is illustrated;

[0026] Figure 8 An example of a sidelink communication scenario is illustrated;

[0027] Figure 9 illustrates an embodiment of a format for signaling SL positioning capabilities;

[0028] Figure 10 illustrates an embodiment of a format for listing SL positioning information in an Nlmf_Location_DetermineLocation request message;

[0029] Figure 11 The figure illustrates the message flow in an embodiment of a PC5-Uu based joint positioning operation scenario;

[0030] Figure 12 An embodiment of a method in a user equipment device is illustrated;

[0031] Figure 13 An embodiment of a method in a first apparatus is illustrated; and

[0032] Figure 14 An embodiment of a method in a second apparatus is illustrated. DETAILED DESCRIPTION

[0033] Those skilled in the art will appreciate that aspects of the present disclosure may be embodied as systems, devices, methods, or program products. Thus, the arrangements described herein may be implemented in a completely hardware form, a completely software form (including firmware, resident software, microcode, etc.), or a combination of software and hardware aspects.

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

[0035] Furthermore, the methods and apparatus may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transmitting. The storage device may not embody signals. In some arrangements, the storage device utilizes only signals for accessing the code.

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

[0037] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0038] In this specification, references to examples of particular methods or devices or similar language indicate that the specific features, structures or characteristics described in conjunction with the examples are included in at least one implementation of the methods and devices described herein. Therefore, unless otherwise expressly provided, references to features of examples of particular methods or devices or similar language may, but do not necessarily, all refer to the same examples, but rather to "one or more but not all examples". Unless otherwise expressly provided, the terms "including", "comprising", "having" and their variations mean "including but not limited to". Unless otherwise expressly provided, a list of enumerated items does not mean that any or all items are mutually exclusive. Unless otherwise expressly provided, the terms "a", "an" and "the" also mean "one or more".

[0039] As used herein, a list with the conjunction "and / or" includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, 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 a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, 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 one and only one of any single item in the list. For example, "one of A, B, and C" includes only A, only B, or only C, but does not include a combination of A, B, and C. As used herein, "a member selected from a group including A, B, and C" includes one and only one of A, B, or C, but does not include a combination of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof” includes only A, only B, only C, 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.

[0040] In addition, the described features, structures or characteristics described herein may be combined in any suitable manner. In the following description, many specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a comprehensive understanding of the present disclosure. However, those skilled in the relevant art will recognize that the disclosed methods and apparatus can be practiced without one or more of the specific details, or can be practiced using other methods, components, materials, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid obscuring aspects of the present disclosure.

[0041] Aspects of the disclosed methods and apparatus are described below with reference to schematic flow charts and / or schematic block diagrams of methods, apparatuses, systems, and program products. It will be understood that each block of the schematic flow charts and / or schematic block diagrams, and combinations of blocks in the schematic flow charts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine such that instructions executed by the processor of the computer or other programmable data processing device can create components for implementing the functions / actions specified in the schematic flow charts and / or schematic block diagrams.

[0042] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other device to operate in a specific manner so that the instructions stored in the storage device produce an article of manufacture that includes instructions for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0043] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device, so that a series of operating steps are executed on the computer, other programmable apparatus, or other device, thereby producing a computer-implemented process, so that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0044] The schematic flow charts and / or schematic block diagrams in the figures illustrate the architecture, functions and operations of possible implementations of devices, systems, methods and program products. In this regard, each box in the schematic flow charts and / or schematic block diagrams may represent a module, segment or portion of code, which includes one or more executable instructions of the code for implementing (multiple) specified logical functions.

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

[0046] The description of an element in each figure may refer to an element in a subsequent figure. The same numbers refer to the same elements throughout the drawings.

[0047] Figure 1An embodiment of a wireless communication system 100 for selecting a sidelink location device in a wireless communication network is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although Figure 1 A specific number of remote units 102 and network units 104 are depicted in the figure, but 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. A wireless communication system may include 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 include at least one network node. A network node may be a network unit.

[0048] In one embodiment, the remote unit 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smartphone, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), an in-vehicle computer, a network device (e.g., a router, a switch, a modem), an aircraft, a drone, etc. In some embodiments, the remote unit 102 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. Furthermore, the remote unit 102 may be referred to as a subscriber unit, a mobile station, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or 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 some embodiments, the remote unit 102 may communicate directly with other remote units 102 via sidelink communications.

[0049] The network elements 104 may be distributed over a geographical area. In some embodiments, the network elements 104 may also be referred to as access points, access terminals, base stations, base stations, node Bs, eNBs, gNBs, home node Bs, relay nodes, devices, core networks, air servers, radio access nodes, APs, NRs, network entities, access and mobility management functions (AMFs), unified data management functions (UDMs), unified data repositories (UDRs), UDM / UDRs, policy control functions (PCFs), radio access networks (RANs), network slice selection functions (NSSFs), operations, administration, and management (OAMs), session management functions (SMFs), user plane functions (UPFs), application functions, authentication server functions (AUSFs), security anchor functions (SEAFs), trusted non-3GPP gateway functions (TNGFs), application functions, service enabler architecture layer (SEAL) functions, vertical application enabler servers, edge enabler servers, border configuration servers, mobile edge computing platform functions, mobile edge computing applications, application data analysis enabler servers, SEAL data delivery servers, middleware entities, network slice capability management servers, or any other terminology used in the art. The network elements 104 are typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network elements 104. The radio access network is typically communicatively coupled to one or more core networks, which can be coupled to other networks, such as the Internet and a public switched telephone network. These and other elements of the radio access network and core network are not shown but are generally familiar to those of ordinary skill in the art.

[0050] In one implementation, the wireless communication system 100 conforms to the New Radio (NR) protocol standardized in 3GPP, wherein the network unit 104 transmits on the downlink (DL) using an orthogonal frequency division multiple access (OFDM) modulation scheme, and the remote unit 102 transmits on the uplink (UL) using a single carrier frequency division multiple access (SC-FDMA) scheme or an OFDM scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as WiMAX, an IEEE 802.11 variant, GSM, GPRS, UMTS, an LTE variant, CDMA2000, ZigBee, Sigfox, LoraWAN, etc. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0051] The network unit 104 can serve multiple remote units 102 within a service area (e.g., a cell or cell sector) via wireless communication links. The network unit 104 sends DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0052] Figure 2 A user equipment device 200 is depicted that can be used to implement the methods described herein. The user equipment device 200 is used to implement one or more of the solutions described herein. The user equipment device 200 conforms to one or more of the user equipment devices described in the embodiments herein. Specifically, the user equipment device 200 may include, for example Figure 5 UE 530 or Figure 11 UE 1120, 1180, 1190. The user equipment device 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225.

[0053] The input device 215 and the output device 220 can be combined into a single device, such as a touch screen. In some implementations, the user equipment apparatus 200 does not include any input device 215 and / or output device 220. The user equipment apparatus 200 can include one or more of the following: a processor 205, a memory 210, and a transceiver 225, and can include no input device 215 and / or output device 220.

[0054] As shown, 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 can operate on an unlicensed spectrum. In addition, the transceiver 225 can include multiple UE panels supporting one or more beamforms. Additionally, the transceiver 225 can support at least one network interface 240 and / or application interface 245. (Multiple) application interface 245 can support one or more APIs. (Multiple) network interface 240 can support 3GPP reference points such as Uu, N1, PC5, etc. As will be appreciated by those skilled in the art, other network interfaces 240 may be supported.

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

[0056] Processor 205 may control user equipment device 200 to implement the user equipment device behaviors described herein. Processor 205 may include an application processor (also referred to as a main processor) that manages application domain and operating system (OS) functions and a baseband processor (also referred to as a baseband radio processor) that manages radio functions.

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

[0058] Memory 210 may store data related to implementing the traffic class field as described herein.Memory 210 may also store program code and related data, such as an operating system or other controller algorithms operating on device 200.

[0059] Input device 215 may include any known computer input device, including a touchpad, buttons, keyboard, stylus, microphone, etc. Input device 215 may be integrated with output device 220, for example, as a touch screen or similar touch-sensitive display. Input device 215 may include a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. Input device 215 may include two or more different devices, such as a keyboard and a touchpad.

[0060] The output device 220 may be designed to output visual, auditory, and / or tactile signals. The output device 220 may include an electronically controllable display or display device capable of outputting visual data to a 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, and the like to a user. As another non-limiting example, the output device 220 may include a wearable display that is separate from but communicatively coupled to the rest of the user device apparatus 200, such as a smart watch, smart glasses, a head-up display, and the like. In addition, the output device 220 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, and the like.

[0061] The output device 220 may include one or more speakers for generating sound. For example, the output device 220 may generate an audible alarm or notification (e.g., a beep or buzzer). The output device 220 may include one or more haptic devices for generating 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 touch screen or similar touch-sensitive display. The output device 220 may be located near the input device 215.

[0062] 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 also receives messages, data, and other signals. For example, the processor 205 can selectively activate the transceiver 225 (or portions thereof) at specific times to transmit and receive messages.

[0063] The transceiver 225 includes at least one transmitter 230 and at least one receiver 235. One or more transmitters 230 can be used to provide uplink communication signals to a base unit of a wireless communication network. Similarly, one or more receivers 235 can 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 device 200 can have any suitable number of transmitters 230 and receivers 235. In addition, (multiple) transmitters 230 and (multiple) receivers 235 can be any suitable type of transmitter and receiver. The transceiver 225 may include a first transmitter / receiver pair for communicating with a mobile communication network via a licensed radio spectrum, and a second transmitter / receiver pair for communicating with a mobile communication network via an unlicensed radio spectrum.

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

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

[0066] Figure 3 depicts further details of a network node 300 that may be used to implement the methods described herein. The network node 300 may be a wireless communication network (e.g., one or more of the wireless communication networks described herein). The network node 300 may include, for example Figure 5 AMF 522 or LMF 523, or Figure 11 The network node 300 includes a processor 305 , a memory 310 , an input device 315 , an output device 320 , and a transceiver 325 .

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

[0068] As shown, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. Here, the transceiver 325 communicates with one or more remote units 200. Additionally, the transceiver 325 may support at least one network interface 340 and / or application interface 345. The application interface(s) 345 may support one or more APIs. The network interface(s) 340 may support 3GPP reference points such as Uu, N1, N2, and N3. As will be appreciated by those skilled in the art, other network interfaces 340 may be supported.

[0069] 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, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or a similar programmable controller. The processor 305 may execute instructions stored in the memory 310 to perform the methods and routines described herein. The processor 305 is communicatively coupled to the memory 310, the input device 315, the output device 320, and the transceiver 325.

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

[0071] The memory 310 may store data related to establishing a multipath unicast link and / or mobile operations. For example, as described herein, the memory 310 may store parameters, configurations, resource allocations, policies, etc. The memory 310 may also store program code and related data, such as an operating system or other controller algorithms operating on the network node 300.

[0072] Input device 315 may include any known computer input device, including a touchpad, buttons, keyboard, stylus, microphone, etc. Input device 315 may be integrated with output device 320, for example, as a touch screen or similar touch-sensitive display. Input device 315 may include a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. Input device 315 may include two or more different devices, such as a keyboard and a touchpad.

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

[0074] Output device 320 may include one or more speakers for generating sound. For example, output device 320 may generate an audible alarm or notification (e.g., a beep or buzzer). Output device 320 may include one or more haptic devices for generating vibration, motion, or other tactile feedback. All or part of output device 320 may be integrated with input device 315. For example, input device 315 and output device 320 may form a touch screen or similar touch-sensitive display. Output device 320 may be located near input device 315.

[0075] The transceiver 325 includes at least one transmitter 330 and at least one receiver 335. The one or more transmitters 330 can be used to communicate with the UE, as described herein. Similarly, the one or more receivers 335 can 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, the network node 300 can have any suitable number of transmitters 330 and receivers 335. Furthermore, the transmitter(s) 330 and the receiver(s) 335 can be any suitable type of transmitter and receiver.

[0076] To aid in understanding the solutions disclosed herein, a description of certain target accuracy requirements, certain features, and certain functionality will now be provided.

[0077] Table 1 provides the target accuracy requirements for SL positioning in specific 3GPP use cases.

[0078] References to "Set A" and "Set B" indicate that the requirements are divided into two sets.

[0079]

[0080] Table 1

[0081] Positioning support 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 for regulatory (i.e., emergency services) and commercial use cases (e.g., IIoT) listed in Table 2, RAT-dependent (for both frequency range (FR) 1 and FR2) and RAT-independent positioning methods (such as Precise Point Positioning (PPP) and Real-Time Kinematics (RTK)) are specified in 3GPP Rel-16. Table 3 also shows a list of RAT-dependent positioning methods specified in 3GPP Rel-16.

[0082]

[0083] Table 2

[0084] method Based on UE UE-assisted, LMF-based NG-RAN node assistance DL-TDOA yes yes no DL-AoD yes yes no Multiple RTT no yes yes NR E-CID no yes yes UL-TDOA no no yes UL-AoA no no yes

[0085] Table 3

[0086] In addition, higher positioning requirements for business use cases, especially IIoT use cases, are listed in Table 4.

[0087]

[0088] Table 4

[0089] In order to specifically meet the higher positioning requirements specified in Table 4, additional enhancements for NR positioning are specified in 3GPP Rel-17. These enhancements include: improvements in positioning accuracy and latency (uplink angle of arrival (UL-AoA) enhancement, downlink angle of departure (DL-AoD) enhancement, pre-configured measurement gaps, pre-configured positioning reference signal (PRS) processing windows, etc.); improved network efficiency (on-demand PRS transmission); improved device efficiency (positioning in RRC_INACTIVE); provision of high integrity and reliability requirements (GNSS integrity); and enhancements to assisted GNSS positioning.

[0090] In the 5GS architecture for UE positioning, the UE's location is determined by either the UE itself or a location server, depending on the positioning method used. Furthermore, to exchange positioning-related information (e.g., location-related measurements, position estimates, assistance data), the LTE Positioning Protocol (LPP), as specified in 3GPP Technical Specification TS 37.355 entitled "LTE Positioning Protocol (LPP)," is used point-to-point between the location server and the UE. The following message types are supported in the LPP: Request Capability; Provide Capability; Request Assistance Data; Provide Assistance Data; Request Location Information; Provide Location Information; Abort; and Error.

[0091] Figure 4Illustrated is an example 400 of LPP message transmission between an LMF 450 (location server) and a UE 420. LPP messages are carried as transparent protocol data units (PDUs) over intermediate network interfaces using an appropriate protocol.

[0092] In a first step 401, the LMF 450 sends an LPP message to the AMF 440. The LPP message may be a request capability message requesting the UE 420 to send its positioning capabilities. This is illustrated as an "LPP message".

[0093] In a further step 402, the AMF 440 transmits the received LPP message to the NG-RAN 430 node by including the LPP message into an LPP message container of a DL NAS transport message. This is illustrated as "DL NAS Transport (LPP Message Container)".

[0094] In a further step 403, NG-RAN node 430 transmits the received LPP message container to UE 420 by including the LPP message container into an RRC DLInformationTransfer message specified in 3GPP technical specification TS 38.331 entitled "NR Radio Resource Control (RRC) Protocol Specification." This is illustrated as "DLInformationTransfer (LPP message)."

[0095] In a further step 404, after receiving the request capabilities message, the UE 420 generates an offer capabilities message in response. The UE 420 then sends the offer capabilities message to the NG-RAN node 430 by including the LPP message in an RRC ULInformationTransfer message specified in 3GPP technical specification TS 38.331 entitled "NR Radio Resource Control (RRC) Protocol Specification." This is illustrated as "ULInformationTransfer (LPP message)."

[0096] In a further step 405, the NG-RAN node 430 transmits the LPP message received from the UE 420 to the AMF 440 by including the LPP message into an LPP message container of a UL NAS transport message. This is illustrated as "UL NAS Transport (LPP Message Container)".

[0097] In a further step 406, the AMF 440 extracts the LPP message from the received NAS message / LPP message container and sends it to the LMF 450. This is illustrated as "LPP message".

[0098] Figure 5The figure shows an example of a location service (LCS) architecture 500. The LCS feature in 3GPP provides a mechanism for operators, subscribers and third-party service providers to support mobile location services. Examples of location-based services include emergency services, tracking services, location-based information services (navigation, city tours, location-related content broadcasting, mobile yellow pages, etc.). Location information can be requested by a client (application) associated with the UE, or by a client within or attached to the 5GC and reported to the client. Figure 5 In FIG, an external LCS client 510 requests the current location of the target UE 530 from the 5GC 520. The figure shows the relationship of the various LCS entities, which will now be described in more detail.

[0099] The 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 the LCS client 510 include a 911 emergency dispatch center (PSAP) and Google Maps.

[0100] The GMLC 521 is the first node that the external LCS client 510 accesses in a public land mobile network (PLMN) and acts as a location server for external applications to obtain location information.

[0101] The LMF 523 manages the overall coordination and scheduling of the resources required for the location of UEs 530 that register with or access the 5GC 520. It also calculates or verifies the final position and any velocity estimate, and can estimate the accuracy achieved. The LMF 523 processes location service requests, which may include the transmission of assistance data to the target UE 530 to assist in UE-based positioning and / or UE-assisted positioning, and / or may include the positioning of the target UE 530. The LMF 523 then returns the position estimate for the UE 530 to the Access and Mobility Management Function (AMF) 522. In the event that location services are requested by an entity other than the AMF 522 (e.g., the GMLC 521 or the UE), the AMF 522 returns the position result to that entity. In the C-plane, the LMF 523 acts as a location server.

[0102] The AMF 522 includes functions responsible for managing positioning of the target UE 530 for all types of location requests. The AMF 522 receives a request for some location services associated with a specific target UE 530 from another entity (e.g., the GMLC 521 or the UE), or the AMF 522 itself decides to initiate some location services (e.g., for emergency calls from the UE) on behalf of the specific target UE 530. The AMF 522 then sends a location service request to the LMF 523.

[0103] The NG-RAN node 524 (i.e., gNB) is involved in handling various positioning procedures, including positioning of the target UE 530, provision of location-related information that is not associated with a specific target UE 530, and transmission of positioning messages between the AMF 522 or LMF 523 and the target UE 530.

[0104] The target UE 530 is the UE whose position (absolute or relative) is to be acquired by the network or by the UE itself.

[0105] NRPPa is the C-plane radio network layer signaling protocol between the NG-RAN node 524 (gNB) and the LMF 523.

[0106] LPP is a point-to-point positioning protocol that supports positioning and location-related services for target devices. In the C-plane, LPP terminates between the target device 530 and the LMF 523.

[0107] Certain types of location requests specified in 3GPP will now be briefly described.

[0108] A Network Induced Location Request (NI-LR) involves the UE’s serving AMF initiating positioning of the UE for regulatory services (e.g., emergency calls from the UE) or for verifying the UE’s location (national or international region) for NR satellite access.

[0109] Mobile Terminated Location Request (MT-LR) involves an LCS client outside or inside the serving PLMN sending a location request to the PLMN for the location of the target UE.

[0110] Mobile Originated Location Request (MO-LR) involves the UE sending a request for the UE's own location-related information to the serving PLMN.

[0111] An Immediate Location Request involves the LCS Client sending, or initiating, a location request for a target UE (or a group of target UEs) and expecting to receive a response containing location information for the target UE (or a group of target UEs) within a short period of time, which may be specified using LCS QoS. In regulatory situations, one or more responses with the location information of the target UE may be expected. An Immediate Location Request can be used for NI-LR, MT-LR, or MO-LR.

[0112] Deferred Location Request involves the LCS client sending a location request for a target UE (or a group of target UEs) to the PLMN and expecting to receive a response at a future time (or times) containing an indication of an event occurrence and location information for the target UE (or a group of target UEs) (if requested), which response may be associated with a specific event associated with the target UE (or a group of target UEs). Deferred Location Request is only supported for MT-LR.

[0113] Figure 6 An example 600 of the 5GC-MT-LR procedure for supervised location services in non-roaming scenarios, as specified in 3GPP Technical Specification TS 23.273, entitled "5G System (5GS) Location Services (LCS) - Phase 2," is shown. In this scenario, an external LCS client 670 requests the 5GC for the current location of a target UE 620. It is assumed that the target UE 620 is identified using a SUPI or GPSI.

[0114] In a first step 601, an external client 670 sends a request to the GMLC 660 for the current location of the target UE 620. The request includes, among other things, the requested LCS QoS. This is illustrated as "LCS Service Request".

[0115] In a further step 602, the GMLC 660 sends a Namf_Location_ProvidePositioningInfo request to the AMF 640 to request the current location of the UE 620.

[0116] In a further step 603, if the UE 620 is in the CM-IDLE state, the AMF 640 initiates a network-triggered service request procedure to establish a signaling connection with the UE 620. This is illustrated as "Network Triggered Service Request".

[0117] In a further step 604, the AMF 640 selects the LMF 650 based on available information (e.g. requested LCS QoS, LMF capabilities, LMF load, LMF location) or based on AMF local configuration (if the AMF 640 is locally configured with a mapping table of UE identities and LMF addresses). This is illustrated as "LMF selection".

[0118] In a further step 605, the AMF 640 sends a Nlmf_Location_DetermineLocation request to the selected LMF 650 to request the current location of the UE 620. The request includes, among other items, the requested LCS QoS and UE positioning capabilities (if available).

[0119] In a further step 606, the LMF 650 performs a positioning procedure and determines the geographical location of the UE 620. This is illustrated as "UE Positioning".

[0120] In a further step 607, the LMF 650 returns an Nlmf_Location_DetermineLocation response to the AMF 640 to return the current location of the UE 620, i.e., the location estimate and accuracy, and may include information about the positioning method and the timestamp of the location estimate.

[0121] In a further step 608, the AMF 640 returns a Namf_Location_ProvidePositioningInfo response to the GMLC 660 to return the current location of the UE 620.

[0122] In a further step 609, the GMLC 660 sends a location service response including the location information of the UE 620 to the external client 670. This is illustrated as "LCS Service Response".

[0123] Figure 7 An exemplary 5G C-MO-LR procedure 700, as specified in 3GPP technical specification TS 23.273, entitled "5G System (5GS) Location Services (LCS) - Phase 2," is illustrated, in which a UE requests a serving PLMN to obtain its own location or to provide only positioning assistance data. It is assumed that an LCS client resides in the UE and initiates MO-LR.

[0124] In a first step 701, if the UE 720 is in the CM-IDLE state, the UE 720 starts a UE-triggered service request procedure in order to establish a signaling connection with the AMF 740. This is illustrated as "UE-triggered service request".

[0125] In a further step 702, the UE 720 sends a MO-LR request message included in an UL NAS transport message to the AMF 740. Different types of location services may be requested: a position estimate of the UE, a position estimate of the UE to be sent to an LCS client, or positioning assistance data. If the UE 720 is requesting its own location, or requesting that its own location be sent to an LCS client (e.g. for use of location based services), the message carries the requested LCS QoS information (e.g. accuracy, response time). If the UE 720 is requesting that its location be sent to an LCS client, the message also includes an identification of the LCS client and the address of the GMLC through which the LCS client should be accessed. If the UE 720 is instead requesting positioning assistance data, the embedded LPP message specifies the type of assistance data and the positioning method to which the assistance data applies.

[0126] In a further step 703, the AMF 740 selects the LMF 750 based on available information (e.g. requested LCS QoS, LMF capabilities, LMF load, LMF location) or based on AMF local configuration (if the AMF 740 is locally configured with a mapping table of UE identities and LMF addresses). This is illustrated as "LMF selection".

[0127] In a further step 704, the AMF 740 sends a Nlmf_Location_DetermineLocation request to the selected LMF 750. The request comprises, among other items, an indication whether a position estimate or positioning assistance data is requested.

[0128] In a further step 705, if the UE 720 is requesting its own location, the LMF 750 performs a positioning procedure and determines the geographical location of the UE 720. If the UE 720 is instead requesting positioning assistance data, the LMF 750 transmits this data to the UE 720. This is illustrated as "UE Positioning".

[0129] In a further step 706, when the position estimate that best meets the requested LCS QoS has been obtained, or when the requested location assistance data has been transmitted to the UE 720, the LMF 750 returns an Nlmf_Location_DetermineLocation response to the AMF 740. The response includes the position estimate, its age, and accuracy. If the UE 720 is requesting positioning assistance data, steps 707 to 711 are skipped.

[0130] In a further step 707, if the location estimate is successfully obtained, the AMF 740 sends a Ngmlc_Location_LocationUpdate request to the GMLC 760. The request carries the identity of the UE 720, the event that caused the location estimate (5GC-MO-LR), and the location estimate, its age and the obtained accuracy indication. In addition, the request includes the identity of the LCS client 770.

[0131] In a further step 708, according to the LCS QoS requested by the UE 720, the GMLC 760 transmits a location information message to the LCS client 770, the message carrying the identity of the UE 720, the event leading to the location estimation (5GC-MO LR) and the location estimate.

[0132] In a further step 709, the LCS client 770 sends a Location Information Acknowledge message to the GMLC 760, which signals that the position estimate of the UE 720 has been successfully received.

[0133] In a further step 710 , the GMLC 760 sends a Ngmlc_Location_LocationUpdate response to the AMF 740 to acknowledge the successful reception of the location estimate by the LCS client 770 .

[0134] In a further step 711, the AMF 740 sends a MO-LR response message included in the DL NAS transport message. If the UE 720 is requesting its own location, the response carries any position estimate requested by the UE 720 and the timestamp of the position estimate (if available), including an indication of whether the acquired position estimate received from the LMF 750 meets the requested accuracy, or an indicator of whether the position estimate has been successfully transmitted to the identified LCS client 770.

[0135] NR SL communication and discovery will now also be described. 3GPP Rel-16 NR introduced the feature of SL communication to support V2X and non-V2X services. The interface for SL communication (transmission / reception) between two UEs in proximity is denoted as PC5. Table 5 and Figure 8 A scenario 800 supported for SL communication is shown, where a first UE (UE1) 811, 821, 831 and a second UE (UE2) 812, 822, 832 are located within the coverage (IC) 810, partial coverage (PC) 820 and out of coverage (OOC) 830 of a cell (gNB) 813, 823, 833.

[0136] # Coverage scenario UE1 UE2 830 Out of coverage Out of coverage Out of coverage 820 Partial coverage Coverage Out of coverage 810 Coverage Coverage Coverage

[0137] Table 5

[0138] The transmission and reception of user services on the PC5 interface are supported for unicast, multicast, and broadcast transmissions. The transmission and reception of signaling services on the PC5 interface are supported only for unicast transmissions. A SL connection on PC5 is defined as a logical connection between a pair of source Layer 2ID and destination Layer 2ID. The source Layer 2ID and destination Layer 2ID identify the sender and target of SL communication, respectively. Furthermore, for each transmission type, a corresponding pair of source Layer 2ID and destination Layer 2ID is used. SL communication is based on the Proximity-Based Services (ProSe) feature.

[0139] In order to enable SL communication between neighboring UEs, the UE may need to perform a SL discovery procedure. The SL discovery procedure is used by (multiple) UEs to discover neighboring (multiple) other UEs or to be discovered by neighboring (multiple) other UEs. For example, a UE that wants to discover neighboring (multiple) other UEs sends a discovery message via PC5. The neighboring (multiple) other UEs monitor the discovery message and, if they want to be discovered, they respond with a discovery response message. After discovery, the UE can establish a SL communication connection with each of the (multiple) UEs that responded. More details on NR sidelink communication and discovery can be found in the 3GPP technical specification TS 23.304 entitled "Proximity-based Services (ProSe) in 5G Systems (5GS)".

[0140] Certain SL positioning terms are relevant to the disclosure herein. These terms will now be briefly discussed and are used to refer to the role of a specific UE / device participating in a SL positioning session.

[0141] The initiator device initiates the SL positioning / ranging session. The initiator device can be a network entity (e.g., gNB, LMF) or UE / Roadside Unit (RSU).

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

[0143] The target UE is the UE of interest, whose position (absolute or relative) is to be acquired by the network or by the UE itself.

[0144] The term "sidelink positioning" refers to positioning the UE using a reference signal sent through the SL (ie, PC5 interface) to obtain absolute position, relative position or ranging information.

[0145] The term "ranging" refers to determining the distance and / or direction between a UE and another entity (eg, an anchor UE).

[0146] An anchor UE is a UE that supports positioning of a target UE (also referred to as a SL reference UE), for example, by sending and / or receiving reference signals for positioning on a PC5 interface, providing positioning-related information, and the like.

[0147] An assist UE is a UE that supports ranging / sidelink positioning between the SL reference UE and the target UE via PC5 when direct ranging / sidelink positioning between the SL reference UE / anchor UE and the target UE is not supported. Measurements / results of ranging / sidelink positioning between the assist UE and the SL reference UE, and between the assist UE and the target UE, are determined and used to derive ranging / sidelink positioning results between the target UE and the SL reference UE.

[0148] The SL Positioning Server UE is a UE that provides location calculation for SL positioning and ranging-based services. It 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.

[0149] The SL positioning client UE is a third-party UE other than the SL reference UE and the target UE, which initiates ranging / sidelink positioning service requests on behalf of the applications resident on it.

[0150] To support SL positioning in joint positioning operation scenarios based on PC5-Uu, this paper proposes several solutions. These solutions include indicating to the network: the UE's SL positioning capability; an extension of the Nlmf_Location_DetermineLocation request message; and the definition of new LPP / SLPP messages for server-to-server communication.

[0151] With regard to indicating the UE's SL positioning capabilities to the network, the UE indicates its SL positioning capabilities to the AMF as part of NAS signaling, for example in the NAS Registration Request message specified in 3GPP technical specification TS 24.501 entitled "Non-Access Stratum (NAS) Protocol for 5G Systems (5GS) - Stage 3". Figure 9An embodiment 900 of the format of SL positioning capability signaling is illustrated. As shown, the format 900 is defined as a bit string, and the UE sets the relevant bits if the corresponding capability is supported. If the UE can act as a server UE, the value "serverue" 910 is set, if the UE can act as an anchor UE, the value "anchorue" 920 is set, if the UE supports LPP, the value "lpp" 930 is set, and if the UE supports SLPP, the value "slpp" 940 is set. Alternatively, the UE can indicate its SL positioning capability to the RAN node (i.e., gNB) as part of the AS signaling, i.e., in the UE Capability Information message specified in 3GPP Technical Specification TS 38.331 entitled "NR Radio Resource Control (RRC) Protocol Specification". The RAN node then forwards this information to the AMF.

[0152] Regarding the extension of the Nlmf_Location_DetermineLocation request message, the Nlmf_Location_DetermineLocation request message (as described in 3GPP technical specification TS 29.572 entitled "5G System Location Management Service - Phase 3") is extended to include SL positioning information. The SL positioning information contains a list of available anchor UEs and server UEs in the area of ​​the target UE. Figure 10 An embodiment of the format of the list is illustrated in FIG1000. The format of the list 1000 may contain up to 64 entries, and each entry contains information about the identity of the UE (the value of "ue-Identity" 1010), the area where the UE is located (the value of "areaInfo" 1020 given by the cell identity and tracking area identity), and the SL positioning capability supported by the UE (the value of "sl-PositioningCapability" 1030).

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

[0154] The "Determine Location Request" message is sent from the LMF to the server UE to request the location of the target UE. The message includes the requested LCS QoS for the location estimation of the target UE and information about available anchor UEs in the area of ​​the target UE.

[0155] 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.

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

[0157] The advantages of the proposed solution include supporting SL positioning in joint positioning operation scenarios based on PC5-Uu when a LMF with SL positioning capability is available but due to the current load the LMF may decide that the result calculation, method determination, auxiliary data distribution and / or anchor UE selection shall be performed by the SL positioning server UE, and when a LMF without SL positioning capability is available.

[0158] Figure 11 The message flow in an embodiment 1100 of a PC5-Uu based joint positioning operation scenario is illustrated, which conveys the benefits of the proposed solution. In this particular embodiment 1100, certain assumptions are made. These assumptions include that the target UE, anchor UE, and server UE are all within network coverage. In addition, this embodiment is applicable to both MO-LR and MT-LR procedures. Based on the information from the LCS client ( Figure 11 In order to receive a location request (not shown in FIG), SL positioning needs to be performed for the target UE (determined by LCS QoS). In addition, an assumption is made that LMF is capable of SL positioning.

[0159] Figure 11 The message flow in an embodiment 1100 of a PC5-Uu based joint positioning operation scenario is illustrated.

[0160] In steps 1101a / 1101b, 1102a / 1102b, 1103a / 1103b, during a successful NAS registration procedure, the UEs (target UE 1120, anchor UE 1180, and server UE 1190) indicate their SL positioning capabilities to the AMF 1140. These steps are illustrated as "Registration Request" and "Registration Accept" for each UE 1120, 1180, and 1190.

[0161] The target UE 1120 indicates its support for LPP and SLPP and is used Figure 9 The bits of “server ue” 910 and “anchor ue” 920 in are not set.

[0162] Anchor UE 1180 indicates its support for LPP and SLPP. In addition, this indicates that it can act as an anchor UE and is used for Figure 9 The bit of "server ue" 910 is not set.

[0163] The server UE 1190 indicates its support for LPP and SLPP. In addition, this indicates that it can act as a server UE and is used for Figure 9 The bit of "anchorue" 920 in is not set.

[0164] In a further step 1104, the AMF 1140 selects a LMF 1150 with SL positioning capability based on local configuration (i.e. based on the mapping of the target UE identity and the LMF address). This is illustrated as "LMF selection".

[0165] In a further step 1105, the AMF 1140 sends an Nlmf_Location_DetermineLocation request message to the selected LMF 1150. The request includes, but is not limited to, a request for a location estimate for the target UE, the requested LCS QoS and SL positioning information including available anchor UEs 1180 and server UEs 1190 in the area of ​​the target UE 1120.

[0166] In a further step 1106, due to the current load, the selected LMF 1150 decides that the SL positioning server UE 1190 perform result calculation, method determination, assistance data distribution, and anchor UE selection. Therefore, it sends a "Determine Position Request" message to the server UE 1190 via LPP or SLPP to request the location of the target UE 1120. The "Determine Position Request" message includes the requested LCS QoS for the position estimate of the target UE 1120 and information about available anchor UEs in the area of ​​the target UE 1120.

[0167] In a further step 1107 , SL positioning of the target UE 1120 is performed between the server UE 1190 , the anchor UE 1180 and the target UE 1120 .

[0168] In a further step 1108, the server UE 1190 sends a "Determine Position Response" message via LPP or SLPP to the LMF 1150. The response message includes the location estimate and accuracy of the target UE 1120.

[0169] In a further step 1109, the LMF 1150 sends an Nlmf_Location_DetermineLocation response message to the AMF 1140 to return the current location of the target UE 1120, i.e. the location estimate and accuracy.

[0170] The disclosure herein provides a user equipment (UE) device for wireless communication, the UE device comprising: a processor; and a memory coupled to the processor, the processor being configured to cause the UE device to: send a first message to a first device of a wireless communication network, wherein the first message includes one or more parameters indicating a sidelink positioning capability of the UE device.

[0171] In some embodiments, the first device comprises an Access and Mobility Management Function "AMF".

[0172] In some embodiments, the processor is configured to cause the UE device to: send the first message as part of a Non-Access Stratum "NAS" Registration Request message.

[0173] In some embodiments, one or more parameters are selected from a list of parameters, the list of parameters including: a server UE parameter indicating whether the UE device is capable of acting as a server UE for position calculation for sidelink positioning; an anchor UE parameter indicating whether the UE device is capable of acting as an anchor UE for supporting 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.

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

[0175] In some embodiments, the processor is further arranged to cause the UE device to: receive a second message requesting sidelink positioning of the target UE from a second device of the wireless communication network, wherein the second message includes: one or more quality of service "QoS" requirements for the position estimate of the target UE; and one or more identifiers of one or more anchor UEs in the target area of ​​the target UE.

[0176] The second message may be referred to as a "Determine Location Request" LPP / SLPP message, or the second message may be part of an existing LPP message.

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

[0178] In some embodiments, the processor is further configured to cause the UE device to: send a third message to the second device, wherein the third message includes the estimated location and the associated location accuracy.

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

[0180] Figure 12 An embodiment 1200 of a method in a user equipment device for wireless communication is illustrated.

[0181] A first step 1210 comprises sending a first message to a first device of a wireless communication network, wherein the first message comprises one or more parameters indicative of a sidelink positioning capability of the UE device.

[0182] In some embodiments, the method 1200 may be performed by a processor that executes program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or the like.

[0183] In some embodiments, the first device comprises an AMF.

[0184] In some embodiments, one or more parameters are selected from a list of parameters, the list of parameters including: a server UE parameter indicating whether the UE device is capable of acting as a server UE for position calculation for sidelink positioning; an anchor UE parameter indicating whether the UE device is capable of acting as an anchor UE for supporting sidelink positioning; an LPP parameter indicating whether the UE device supports LPP; and an SLPP parameter indicating whether the UE device supports SLPP.

[0185] In some embodiments, the method further includes receiving a second message requesting sidelink positioning of the target UE from a second device of the wireless communication network, wherein the second message includes: one or more QoS requirements for the position estimate of the target UE; and one or more identifiers of one or more anchor UEs in the target area of ​​the target UE.

[0186] In some embodiments, the method further comprises determining an estimated location and an associated location accuracy of the target UE using the one or more QoS requirements and the one or more anchor UEs.

[0187] In some embodiments, the method further comprises sending a third message to the second device, wherein the third message comprises the estimated location and the associated location accuracy.

[0188] In some embodiments, the second device comprises a LMF.

[0189] The disclosure herein also provides a first device in a wireless communication network, the first device comprising: a processor; and a memory coupled to the processor, the processor being configured to enable the first device to: receive a request from a consumer entity for locating a target UE in a target area; determine one or more UE devices with corresponding sidelink positioning capabilities in the target area; and send a fourth message to a second device in the wireless communication network, the fourth message indicating the one or more UE devices and their corresponding sidelink positioning capabilities.

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

[0191] 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 corresponding first messages from the one or more UE devices, wherein each corresponding first message includes one or more parameters indicating the sidelink positioning capability of the corresponding UE device.

[0192] In some embodiments, the processor is configured to cause the first apparatus to receive the one or more first messages as part of corresponding NAS registration request messages.

[0193] In some embodiments, one or more parameters are selected from a list of parameters, the list of parameters including: a server UE parameter indicating whether the corresponding UE device is capable of acting as a server UE for position calculation for sidelink positioning; an anchor UE parameter indicating whether the corresponding UE device is capable of acting as an anchor UE for supporting sidelink positioning; an LPP parameter indicating whether the corresponding UE device supports LPP; and an SLPP parameter indicating whether the corresponding UE device supports SLPP.

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

[0195] In some embodiments, each entry in the list includes: an identifier for the corresponding UE; a location area of ​​the corresponding UE; and the SL positioning capability of the corresponding UE.

[0196] In some embodiments, the request for locating the target UE in the target area includes one or more QoS requirements for the position estimate of the target UE, and wherein the fourth message includes the one or more QoS requirements.

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

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

[0199] In some embodiments, the processor is further configured to cause the first apparatus to: receive a fifth message from the second apparatus, the fifth message comprising an estimated location of the target UE and an associated location accuracy.

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

[0201] The fifth message may be an Nlmf_Location_DetermineLocation response message.

[0202] In some embodiments, the first device comprises an AMF and the second device comprises an LMF.

[0203] Figure 13 An embodiment 1300 of a method in a first device in a wireless communication network is illustrated.

[0204] A first step 1310 comprises receiving a request from a customer entity for locating a target UE in a target area.

[0205] A further step 1320 comprises determining one or more UE devices having corresponding sidelink positioning capabilities in the target area.

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

[0207] In some embodiments, the method 1300 may be performed by a processor that executes program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or the like.

[0208] In some embodiments, determining the one or more UE devices includes receiving one or more respective first messages from the one or more UE devices, wherein each respective first message includes one or more parameters indicative of a sidelink positioning capability of the respective UE device.

[0209] In some embodiments, one or more parameters are selected from a list of parameters, the list of parameters including: a server UE parameter indicating whether the corresponding UE device is capable of acting as a server UE for position calculation for sidelink positioning; an anchor UE parameter indicating whether the corresponding UE device is capable of acting as an anchor UE for supporting sidelink positioning; an LPP parameter indicating whether the corresponding UE device supports LPP; and an SLPP parameter indicating whether the corresponding UE device supports SLPP.

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

[0211] In some embodiments, each entry in the list includes: an identifier for the corresponding UE; a location area of ​​the corresponding UE; and the SL positioning capability of the corresponding UE.

[0212] In some embodiments, the request for locating the target UE in the target area includes one or more QoS requirements for the position estimate of the target UE, and wherein the fourth message includes the one or more QoS requirements.

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

[0214] Some embodiments further comprise receiving a fifth message from the second apparatus, the fifth message comprising an estimated location of the target UE and an associated location accuracy.

[0215] In some embodiments, the first device comprises an AMF and the second device comprises an LMF.

[0216] The disclosure herein also provides a second device in a wireless communication network, the second device comprising: a processor; and a memory coupled to the processor, the processor being configured to enable the second device to: receive a fourth message from a first device in the wireless communication network, the fourth message indicating one or more UE devices and their corresponding sidelink positioning capabilities for locating a target UE in a target area; determine a server UE device from the one or more UE devices, the server UE device being used to perform position calculation for sidelink positioning of the target UE; and send a second message to the server UE device requesting sidelink positioning of the target UE, wherein the second message comprises: one or more QoS requirements for position estimation of the target UE; and one or more identifiers of one or more anchor UEs in the target area of ​​the target UE.

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

[0218] In some embodiments, the sidelink positioning capability for each UE device includes one or more parameters selected from a list of parameters, the list of parameters including: a server UE parameter indicating whether the UE device is capable of acting as a server UE for position calculation for sidelink positioning; an anchor UE parameter indicating whether the UE device is capable of acting as an anchor UE for supporting sidelink positioning; an LPP parameter indicating whether the UE device supports LPP; and an SLPP parameter indicating whether the UE device supports SLPP.

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

[0220] In some embodiments, the second message is a "Determine Location Request" LPP / SLPP message, or if the UE supports LPP, the second message may form part of an existing LPP message (ie, a RequestLocationInformation message).

[0221] In some embodiments, the third message is a "Determine Location Response" message, or may be an existing ProvideLocationInformation LPP message from the server UE, which includes the location estimate and accuracy of the target UE.

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

[0223] In some embodiments, each entry in the list includes: an identifier for the corresponding UE; a location area of ​​the corresponding UE; and the SL positioning capability of the corresponding UE.

[0224] 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 comprising the estimated location of the target UE and the associated location accuracy.

[0225] Figure 14 An embodiment 1400 of a method in a second device in a wireless communication network is illustrated.

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

[0227] A further step 1420 comprises determining a server UE device from the one or more UE devices, the server UE device for performing position calculations for sidelink positioning of the target UE.

[0228] A further step 1430 comprises sending a second message to the server UE device requesting sidelink positioning of the target UE, wherein the second message comprises: one or more QoS requirements for position estimation of the target UE; and one or more identifiers of one or more anchor UEs in the target area of ​​the target UE.

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

[0230] In some embodiments, the method 1400 may be performed by a processor that executes program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or the like.

[0231] In some embodiments, the sidelink positioning capability for each UE device includes one or more parameters selected from a list of parameters, the list of parameters including: a server UE parameter indicating whether the UE device is capable of acting as a server UE for position calculation for sidelink positioning; an anchor UE parameter indicating whether the UE device is capable of acting as an anchor UE for supporting sidelink positioning; an LPP parameter indicating whether the UE device supports LPP; and an SLPP parameter indicating whether the UE device supports SLPP.

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

[0233] In some embodiments, the second message is a "Determine Location Request" LPP / SLPP message, or if the UE supports LPP, the second message forms part of an existing LPP message (ie, RequestLocationInformation).

[0234] In some embodiments, the third message is a "Determine Location Response" message, or may be part of an existing ProvideLocationInformation LPP message from the server UE, which includes the location estimate and accuracy of the target UE.

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

[0236] In some embodiments, each entry in the list includes: an identifier for the corresponding UE; a location area of ​​the corresponding UE; and the SL positioning capability of the corresponding UE.

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

[0238] In order to support SL positioning in PC5-Uu based joint positioning operation scenarios, certain novel aspects of the proposed solution are provided.

[0239] The first novel aspect includes a UE that indicates its SL positioning capabilities to the AMF as part of NAS signaling, for example, in a NAS Registration Request message. The SL positioning capabilities include an indication 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 capabilities to a RAN node (i.e., gNB) as part of AS signaling, i.e., in a UE Capability Information message, and the RAN node forwards this information to the AMF.

[0240] Additional novel aspects include extending the Nlmf_Location_DetermineLocation request message to include SL positioning information. The SL positioning information contains a list of available anchor UEs and server UEs in the area of ​​the target UE.

[0241] Additional novel aspects include new LPP / SLPP messages defined herein for server-to-server communication, 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. The message includes the requested LCS QoS for the target UE's location estimate, and information about available anchor UEs in the target UE's area. The "Determine Location Response" message is sent from the server UE to the LMF and includes the target UE's location estimate and accuracy. Alternatively, if the server UE is LPP capable, existing LPP messages may be used as request / response messages, such as the RequestLocationInformation message and the ProvideLocationInformation message.

[0242] A method for sidelink positioning of a target device within network coverage is provided, the method comprising: receiving a first message from a first communication device by a second communication device comprising a sidelink positioning capability; determining by the second communication device to select a third communication device based on the received first message; sending a second message from the second communication device to the third communication device, the second message comprising a request for sidelink positioning; determining by the third communication device to trigger sidelink positioning to a fourth communication device; and sending a third message from the third communication device to the fourth communication device, the third message comprising a request for sidelink positioning.

[0243] 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 location server device.

[0244] In some embodiments, the first message including the sidelink positioning capability includes an indication of supported positioning protocols, or supported roles, or any combination thereof in sidelink positioning.

[0245] In some embodiments, the second message containing the request for sidelink positioning includes information of available sidelink positioning anchor devices and server devices in the area of ​​the target device.

[0246] In some embodiments, the third message containing the request for sidelink positioning includes a requested QoS for the position estimate of the target device and information of available sidelink positioning anchor devices in the area of ​​the target device.

[0247] It should be noted that the above-described methods and apparatus illustrate rather than limit the present invention, and that those skilled in the art will be able to design many alternative arrangements 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 a claim, and "a" or "an" does not exclude a plurality, and a single processor or other unit may perform the functions of several units recited in a claim. Any reference signs in a claim should not be construed as limiting its scope.

[0248] Furthermore, while examples are given in the context of specific communication standards, these examples are not intended to limit 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 may also be applied to other wireless communication systems, and indeed any communication system that uses routing rules.

[0249] The method may also be embodied in a set of instructions stored on a computer-readable medium, which, when loaded into a computer processor, digital signal processor (DSP), etc., causes the processor to perform the above-described method.

[0250] The described methods and apparatus may be practiced in other specific forms. The described methods and apparatus are to be considered in all respects only as illustrative and not restrictive. The scope of the present invention is therefore indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalence of the claims are intended to be included within their scope.

[0251] The following abbreviations are relevant to the areas covered by this document: 3GPP, 3rd Generation Partnership Project; 5GS, 5G System; A-GNSS, Assisted GNSS; AMF, Access and Mobility Management Function; AoA, Angle of Arrival; AoD, Angle of Departure; AS, Access Stratum; CM, Connection Management; DL, Downlink; DL TDOA, Downlink Time Difference of Arrival; E-CID, Enhanced Cell ID; FR, Frequency Range; GMLC, Gateway Mobile Positioning Centre; GNSS, Global Navigation Satellite System; GPSI, General Public Subscription Identifier; HW, Hardware; IC, Coverage; IIoT, Industrial IoT; IoT, Internet of Things; KPI, Key Performance Indicator; LCS, Location Service; LMF, Location Management Function; LPP, LTE Positioning Protocol; LTE, Long Term Evolution; MO-LR, Mobile Originated Location Request; MT-LR, Mobile Terminated Location Request; Multi-RTT, Multiple Round Trip Time; NAS, Non-Access Stratum; NG-RAN, Next Generation RAN; NI-LR, Network Induced 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, precise point positioning; ProSe, proximity-based services; PRS, positioning reference signal; PSAP, public safety answering point; QoS, quality of service; RAN, radio access network; RAT, radio access technology; RRC, radio resource control; RSU, roadside unit; RTK, real-time kinematic technology; SL, sidelink; SLPP, sidelink positioning protocol; SUPI, subscription permanent identifier; SW, software; TDOA, time difference of arrival; TTFF, time to first fix; UE, user equipment; UL, uplink; V2X, vehicle-to-everything; WID, work item description.

Claims

1. A user equipment (UE) apparatus for wireless communication, comprising: processor; as well as A memory is coupled to the processor, and the processor is configured to cause the UE device to: A first message is sent to a first device of a wireless communication network, wherein the first message includes one or more parameters indicating a sidelink positioning capability of the UE device.

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

3. The UE device of any preceding claim, wherein the one or more parameters are selected from a list of parameters, the list of parameters comprising: a server UE parameter indicating whether the UE device is capable of acting as a server UE for position calculation for sidelink positioning; An anchor UE parameter indicating whether the UE device is capable of acting as an anchor UE for supporting sidelink positioning; LTE Positioning Protocol "LPP" parameter, indicating whether the UE device supports LPP; as well as The Sidelink Positioning Protocol "SLPP" parameter indicates whether the UE device supports SLPP.

4. The UE device of claim 3 , wherein the processor is further configured to cause the UE device to: receiving, from a second device of the wireless communication network, a second message requesting sidelink positioning of a target UE, wherein the second message comprises: one or more quality of service (QoS) requirements for the target UE's location estimate; as well as One or more identifiers of one or more anchor UEs in a target area of ​​the target UE.

5. The UE device according to claim 4, wherein the processor is further configured to cause the UE device to: An estimated location and an associated location accuracy of the target UE is determined using the one or more QoS requirements and the one or more anchor UEs.

6. The UE device according to claim 5, wherein the processor is further configured to cause the UE device to: A third message is sent to the second device, wherein the third message includes the estimated location and the associated location accuracy.

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, comprising: processor; as well as a memory coupled to the processor, the processor being configured to cause the first device to: receiving, from a consumer entity, a request for locating a target UE in a target area; determining one or more UE devices having corresponding sidelink positioning capabilities in the target area; as well as A fourth message is sent to a second device of the wireless communication network, the fourth message indicating the one or more UE devices and their respective sidelink positioning capabilities.

9. The first device of claim 8, wherein the processor is configured to cause the first device to determine the one or more UE devices by causing the first device to: One or more respective first messages are received from the one or more UE devices, wherein each respective first message includes one or more parameters indicative of a sidelink positioning capability of the respective UE device.

10. The first apparatus according to any one of claims 8 to 9, wherein the one or more parameters are selected from a list of parameters, the list of parameters comprising: a server UE parameter indicating whether the corresponding UE device is capable of acting as a server UE for position calculation for sidelink positioning; an anchor UE parameter indicating whether the corresponding UE device is capable of acting as an anchor UE for supporting sidelink positioning; LPP parameter, indicating whether the corresponding UE device supports LPP; as well as SLPP parameter, indicating whether the corresponding UE device supports SLPP.

11. The first device according to claim 10, wherein the fourth message comprises: A list of anchor UE devices and server UE devices in the target area of ​​the target UE.

12. The first device of claim 11, wherein each entry in the list comprises: an identifier for the corresponding UE; The location area of ​​the corresponding UE; as well as The SL positioning capability of the corresponding UE.

13. The first apparatus according to any one of claims 8 to 12, wherein the request for locating the target UE in the target area comprises: One or more QoS requirements for the position estimate of the target UE, and wherein the fourth message includes the one or more QoS requirements.

14. The first device according to any one of claims 8 to 13, wherein the processor is further configured to cause the first device to: The second device is determined based on a predetermined mapping of the target UE to the second device.

15. The first device according to any one of claims 8 to 14, wherein the processor is further configured to cause the first device to: A fifth message is received from the second apparatus, the fifth message including an estimated location of the target UE and an associated location accuracy.

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

17. A second device in a wireless communication network, comprising: processor; as well as a memory coupled to the processor, the processor being configured to cause the second device to: receiving a fourth message from a first device of the wireless communication network, the fourth message indicating one or more UE devices and their respective sidelink positioning capabilities for locating a target UE in a target area; determining a server UE device from the one or more UE devices, the server UE device configured to perform position calculation for sidelink positioning of the target UE; as well as sending 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 the location estimate of the target UE; as well as One or more identifiers of one or more anchor UEs in the target area of ​​the target UE.

18. The second device according to claim 17, wherein the processor is further configured to cause the second device to: A third message is received from the server UE device, wherein the third message includes an estimated location of the target UE and an associated location accuracy.

19. The second apparatus according to any one of claims 17 to 18, wherein the sidelink positioning capability for each UE apparatus comprises one or more parameters selected from a list of parameters, the list of parameters comprising: a server UE parameter indicating whether the UE device is capable of acting as a server UE for position calculation for sidelink positioning; An anchor UE parameter indicating whether the UE device is capable of acting as an anchor UE for supporting sidelink positioning; LPP parameter, indicating whether the UE device supports LPP; as well as SLPP parameter, indicating whether the UE device supports SLPP.

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

Images