Sidelink positioning operations based on a wtru acting as a positioning server

Abstract

Systems and methods of sidelink positioning operations based on interactions between a location management function (LMF) and a sidelink positioning server wireless transmit / receive unit (WTRU) are described herein. Sidelink (SL) positioning operations can be performed based on interactions between a network entity and a SL positioning server WTRU. A WTRU can receive configuration information associated with SL positioning assistance. The WTRU can send a positioning service message to a network entity. The WTRU can determine a SL positioning service request associated with a target WTRU. The WTRU can determine positioning service information. The positioning service can be associated with the target WTRU. The WTRU can receive a message from the network entity, where the message can include a candidate list of SL reference WTRUs (e.g., a first candidate list of SL reference WTRUs). The determined SL reference WTRU can be from the candidate list of SL reference WTRUs.

Description

[0001] Cross-reference to related applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 465,701, filed May 11, 2023, the disclosure of which is incorporated herein by reference in its entirety. Background Technology

[0002] Mobile communication using wireless communication continues to evolve. The fifth generation can be called 5G. The previous generation (traditional) mobile communication can be, for example, the fourth generation (4G) Long Term Evolution (LTE). Summary of the Invention

[0003] This paper describes a system and method for sidelink positioning operations based on the interaction between the Location Management Function (LMF) and the Sidelink Positioning Service Radio Transmit / Receive Unit (WTRU).

[0004] Sidelink (SL) positioning operations can be performed based on the interaction between a network entity (e.g., a location management function) and an SL positioning server WTRU. A WTRU may include a sidelink (SL) positioning server WTRU. A WTRU may be associated with one or more locations or service areas. A WTRU may receive configuration information associated with SL positioning assistance. A WTRU may send positioning service messages to the network entity. Capability information may indicate that a WTRU is capable of acting as an SL positioning server WTRU. A WTRU may determine an SL positioning service request associated with a target WTRU. An SL positioning service request may indicate one or more of WTRU ID, reference WTRU information, or positioning request information. An SL positioning service request may indicate a first WTRU and a second WTRU (e.g., a first target WTRU and a second target WTRU). A WTRU may determine positioning service information associated with the positioning service. The positioning service may be associated with a target WTRU. Positioning service information may include a positioning method and / or an SL reference WTRU. The positioning service information may be determined based on one or more of the configuration information associated with SL positioning assistance and / or indications received from the network entity. The WTRU can receive messages from network entities, which may include a candidate list of SL reference WTRUs (e.g., a first candidate list of SL reference WTRUs). The determined SL reference WTRU may come from the candidate list of SL reference WTRUs. The WTRU may be collocated with either the target WTRU or the SL reference WTRU. The WTRU may send an SL location response to the target WTRU. The SL location response may indicate the determined location service information. Attached Figure Description

[0005] Figure 1A This is a system diagram illustrating an example communication system in which one or more of the disclosed embodiments may be implemented.

[0006] Figure 1B The illustration shows a method according to one embodiment. Figure 1A The diagram shows a system diagram of an example wireless transmit / receive unit (WTRU) used in a communication system.

[0007] Figure 1C The illustration shows a method according to one embodiment. Figure 1A The diagram illustrates a system diagram of an example radio access network (RAN) and an example core network (CN) used in the communication system.

[0008] Figure 1D The illustration shows a method according to one embodiment. Figure 1A The illustrated system diagram shows yet another example RAN and yet another example CN used in the communication system.

[0009] Figure 2 An example reference model for a network used for location services is shown.

[0010] Figure 3 An example procedure for an SL positioning operation that utilizes one or more interactions between the LMF and the SL positioning server WTRU is shown. Detailed Implementation

[0011] Figure 1A This is a schematic diagram illustrating an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multi-access system that provides content such as voice, data, video, messages, and broadcasts to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail Unique Word DFT Spread Spectrum OFDM (ZT UWDTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0012] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, Public Switched Telephone Network (PSTN) 108, Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0013] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), node Bs, eNode Bs (eNBs), home node Bs, home eNode Bs, gNode Bs (gNBs), NR node Bs, site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are each depicted as a single element, it should be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0014] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in a desired spatial direction.

[0015] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116. Air interface 116 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

[0016] More specifically, as described above, the communication system 100 can be a multi-access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 / 113 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish air interfaces 115 / 116 / 117 using Wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​UL Packet Access (HSUPA).

[0017] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which may use Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro) to establish air interface 116.

[0018] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can establish an air interface 116 using a new radio (NR).

[0019] In one embodiment, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can jointly implement LTE radio access and NR radio access, for example, using the dual connectivity (DC) principle. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0020] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0021] For example, Figure 1ABase station 114b can be a wireless router, home node B, home eNodeB, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for drone use), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can be directly connected to the Internet 110. Therefore, base station 114b may not need to access the Internet 110 via CN 106 / 115.

[0022] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, and / or perform advanced security functions such as user authentication. Although in Figure 1A Although not shown, it should be understood that RAN104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which may utilize NR radio technology, CN106 / 115 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0023] CN 106 / 115 can also serve as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 113 or a different RAT.

[0024] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multi-mode capabilities (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). For example... Figure 1A The WTRU 102c shown can be configured to communicate with base station 114a, which may employ cellular-based radio technology, and to communicate with base station 114b, which may employ IEEE 802 radio technology.

[0025] Figure 1B This is a system diagram illustrating example WTRU 102. (Example:) Figure 1B As shown, among other things, WTRU 102 may include, in particular, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and / or other peripheral devices 138, etc. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0026] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, which may be coupled to transmitting / receiving element 122. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it should be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0027] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In one embodiment, transmitting / receiving element 122 can be, for example, a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF and optical signals. It should be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0028] Although the transmitting / receiving element 122 is in Figure 1B While depicted as a single element, WTRU 102 may include any number of transmit / receive elements 122. More specifically, WTRU 102 may employ MIMO technology. Thus, in one embodiment, WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals on air interface 116.

[0029] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, for example, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0030] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Furthermore, the processor 118 can access and store information from any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a user identification module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access and store information from memory that is not physically located on WTRU 102 (e.g., a server or home computer (not shown)).

[0031] The processor 118 can receive power from the power supply 134 and can be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 can be any suitable device that powers the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0032] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information on the air interface 116 from base stations (e.g., base stations 114a, 114b) and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method while remaining consistent with the embodiments.

[0033] The processor 118 may be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or videos), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, such as gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, attitude sensors, biosensors, and / or humidity sensors.

[0034] WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and / or substantially eliminate self-interference via hardware (e.g., chokes) or via signal processing by a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, WTRU 102 may include a half-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0035] Figure 1C This diagram illustrates a system diagram of RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with CN 106.

[0036] RAN 104 may include eNode-Bs 160a, 160b, and 160c; however, it should be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c on air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit and / or receive radio signals from WTRU 102a.

[0037] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other on the X2 interface.

[0038] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. While each of the foregoing elements is described as part of CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0039] The MME 162 can connect to each of the eNode-B 160a, 160b, and 160c in RAN104 via the SL interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0040] The SGW 164 can connect to each of the eNode Bs 160a, 160b, and 160c in RAN104 via the SL interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions such as anchoring the user plane during inter-eNode B handover, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0041] SGW 164 can connect to PGW 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks such as Internet 110, so as to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0042] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRU 102a, 102b, and 102c with access to a circuit-switched network such as PSTN 108, facilitating communication between WTRU 102a, 102b, and 102c and traditional landline communication equipment. For example, CN 106 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRU 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0043] Despite WTRU in Figure 1A-1D While described as a wireless terminal, it is conceivable that, in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

[0044] In a representative embodiment, another network 112 may be a WLAN.

[0045] A WLAN in Infrastructure Basic Services Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or interface with a distributed system (DS) or another type of wired / wireless network that transmits traffic to and / or out of the BSS. Traffic originating outside the BSS destined for a STA can reach and be delivered to the STA via the AP. Traffic originating from a STA destined for an external BSS can be sent to the AP for delivery to the appropriate destination. For example, traffic between STAs within the BSS can be transmitted via the AP, where the source STA can send traffic to the AP, and the AP can deliver traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be transmitted between source and destination STAs (e.g., directly between them) using Direct Link Establishment (DLS). In some representative embodiments, the DLS can use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode is sometimes referred to here as an "ad-hoc" communication mode.

[0046] When using 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of a fixed width (e.g., a wide bandwidth of 20 MHz) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, Carrier Sense Multiple Access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, each STA, including the AP, can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0047] High-throughput (HT) STAs can communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels.

[0048] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data passes through a segment resolver, which splits the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. These streams can be mapped onto two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0049] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidth and carrier in 802.11af and 802.11ah are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV whitespace (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support metering-type control / machine-type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only) certain and / or limited bandwidths. MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0050] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include channels that can be designated as the primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA among all STAs operating in the BSS that supports the minimum bandwidth operating mode. In the example of 802.11ah, for STAs that support (e.g., only support) the 1 MHz mode (e.g., MTC type devices), the primary channel can be 1 MHz wide, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports the 1 MHz operating mode) is transmitting to the AP, the entire available band can be considered busy, even if most of the available band remains idle and can be available.

[0051] In the United States, the available frequency band for 802.11ah is from 902 MHz to 928 MHz. In South Korea, the available frequency band is from 917.5 MHz to 923.5 MHz. In Japan, the available frequency band is from 916.5 MHz to 927.5 MHz. The total available bandwidth for 802.11ah is 6 MHz to 26 MHz, depending on the country code.

[0052] Figure 1D This diagram illustrates a system diagram of RAN 113 and CN 115 according to one embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

[0053] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c on air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, for example, gNB 180a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In one embodiment, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers (not shown) to WTRU 102a. A subset of these component carriers can be on unlicensed spectrum, while the remaining component carriers can be on licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0054] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable digitization. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can differ for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a variable number of OFDM symbols and / or a continuously variable absolute time).

[0055] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, while also communicating / connecting with another RAN such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, as well as one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can act as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0056] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing user plane data to User Plane Functions (UPF) 184a and 184b, and routing control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other on the Xn interface.

[0057] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0058] AMF 182a and 182b can connect to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, and so on. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the service types used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency Time (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, services for Machine Type Communication (MTC) access, and / or so on. AMF 162 can provide control plane functions for handover between RAN 113 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies such as WiFi.

[0059] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure the routing of services through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0060] UPF 184a and 184b can be connected to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N3 interface. This N3 interface provides WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0061] CN 115 can facilitate communication with other networks. For example, CN 115 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 115 and PSTN 108. Furthermore, CN 115 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, and 102c may be connected to local data networks (DNs) 185a and 185b via the N3 interface to UPFs 184a and 184b and the N6 interface between UPFs 184a and 184b and DNs 185a and 185b.

[0062] Given Figure 1A-1D as well as Figure 1A-1D The corresponding descriptions herein indicate that one or more of the following functions can be performed by one or more emulation devices (not shown): WTRU 102a-d, Base Station 114a-b, eNode-B160a-c, MME 162, SGW 164, PGW 166, gNB180a-c, AMF 182a-b, UPF 184a-b, SMF183a-b, DN185a-b, and / or any other device(s) described herein. An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0063] Simulation devices can be designed to perform tests on one or more other devices in laboratory and / or carrier network environments. For example, one or more simulation devices can perform one or more or all of the functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices can perform one or more or all of the functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices can be directly coupled to another device for testing purposes and / or can perform tests using over-the-air wireless communication.

[0064] One or more simulation devices may perform one or more functions, including all functions, rather than being implemented / deployed as part of a wired and / or wireless communication network. For example, simulation devices may be used to test test scenarios in laboratory and / or non-deployment (e.g., testing) wired and / or wireless communication networks to test one or more components. One or more simulation devices may be test devices. Simulation devices may transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0065] This paper describes a system and method for sidelink positioning operations based on the interaction between the Location Management Function (LMF) and the Sidelink Positioning Service Radio Transmit / Receive Unit (WTRU).

[0066] Sidelink (SL) positioning operations can be performed based on the interaction between a network entity (e.g., a location management function) and an SL positioning server WTRU. A WTRU may include a sidelink (SL) positioning server WTRU. A WTRU may be associated with one or more locations or service areas. A WTRU may receive configuration information associated with SL positioning assistance. A WTRU may send positioning service messages to the network entity. Capability information may indicate that a WTRU is capable of acting as an SL positioning server WTRU. A WTRU may determine an SL positioning service request associated with a target WTRU. An SL positioning service request may indicate one or more of WTRU ID, reference WTRU information, or positioning request information. An SL positioning service request may indicate a first WTRU and a second WTRU (e.g., a first target WTRU and a second target WTRU). A WTRU may determine positioning service information associated with the positioning service. The positioning service may be associated with a target WTRU. Positioning service information may include a positioning method and / or an SL reference WTRU. The positioning service information may be determined based on one or more of the configuration information associated with SL positioning assistance and / or indications received from the network entity. The WTRU can receive messages from network entities, which may include a candidate list of SL reference WTRUs (e.g., a first candidate list of SL reference WTRUs). The determined SL reference WTRU may be from the candidate list of SL reference WTRUs. The WTRU may be co-located with either the target WTRU or the SL reference WTRU. The WTRU may send an SL location response to the target WTRU. The SL location response may indicate the determined location service information.

[0067] A WTRU (e.g., a side-link (SL) positioning server WTRU) may (e.g., be configured to) perform one or more of the following: receive configuration information (e.g., for SL positioning server WTRU to assist SL positioning services) from a network function (NF) such as a policy control function (PCF); send a positioning service message (e.g., to the LMF) that may indicate the capabilities of acting as a positioning server WTRU (e.g., it may include one or all actions supported by the positioning server WTRU); receive (e.g., from the LMF) a list of available positioning SL reference WTRUs based on the location or service area of ​​the server WTRU; receive (e.g., from the LMF) a common resource pool for each area or each server WTRU if multiple server WTRUs are located in the same area (e.g., where the definition of the area may be determined by the LMF); receive messages via a PC5 link (e.g., from the target and / or reference WTRUs), which may include, for example, the target WTRU ID, multiple SL reference WTRUs, etc. SL positioning service request messages containing ID, WTRU capabilities, NAS / NAS-free connectivity and / or positioning requirements for each WTRU; determining (e.g., based on received input) the positioning method and / or SL reference WTRU; interacting with the LMF (e.g., round-trip messaging), for example, to determine the positioning method and / or SL reference WTRU for a given positioning service request; receiving from the LMF dedicated radio resources(s) for the requested positioning service (e.g., resources available for PC5 communication between the target WTRU and the SL reference WTRU, and between the SL reference WTRU and the SL positioning WTRU); sending messages via PC5 links (e.g., to the target WTRU and / or the SL reference WTRU) including the selected positioning method, the selected SL reference WTRU, the corresponding target WTRU (e.g., if the message can be sent to the reference WTRU), and the assigned radio resources; and so on.

[0068] It can perform and / or provide (multiple) side-link (SL) positioning operations. (Multiple) SL positioning operations may include one or more interactions between the Location Management Function (LMF) and the server WTRU.

[0069] The SL positioning server WTRU can (e.g., be configured to) perform one or more of the following: receive configuration information from a network function (NF) such as a policy control function (PCF) (e.g., for SL positioning server WTRU to assist SL positioning services); send a positioning service message to the LMF, which may indicate the capabilities of acting as a positioning server WTRU (e.g., it may include actions(s) supported by the positioning server WTRU); receive from the LMF a list of available positioned SL reference WTRUs, for example, based on the location or service area of ​​the server WTRU; receive from the LMF a common resource pool for each area or each server WTRU, for example, if multiple server WTRUs are located in the same area (e.g., where the definition of the area may be determined by the LMF); receive messages via a PC5 link (e.g., from the target and / or reference WTRUs), which may include, for example, the target WTRU ID,(s) the SL reference WTRU(s) ID,(s) the target WTRU ... SL positioning service request messages containing ID, WTRU capabilities, NAS / NAS-free connectivity and / or positioning requirements for each WTRU; determining (e.g., based on received input) the positioning method and / or SL reference WTRU; interacting with the LMF (e.g., round-trip messaging), for example, to determine the positioning method and / or SL reference WTRU for a given positioning service request; receiving from the LMF multiple dedicated radio resources for the requested positioning service (e.g., where these resources can be used for PC5 communication between the target WTRU and the SL reference WTRU, and between the SL reference WTRU and the SL positioning WTRU); sending messages via PC5 links (e.g., to the target WTRU and / or the SL reference WTRU) including the selected positioning method, the selected SL reference WTRU and the corresponding target WTRU (e.g., if the message can be sent to the reference WTRU), and the assigned radio resources; and so on.

[0070] The target WTRU may (for example, be configured to) perform one or more of the following: send a sidelink location request message to the SL location server WTRU, the sidelink location request message may include one or more located SL reference WTRU IDs, their status and capabilities, and / or location service requirements; receive a message from the server WTRU, the message may include the selected location method, the selected SL reference WTRU and / or the assigned radio resources; and so on.

[0071] The SL reference WTRU may (e.g., be configured to) perform one or more of the following: send a sidelink positioning request message to the SL positioning server WTRU, the sidelink positioning request message including one or more located target WTRU IDs, their status and capabilities, and / or positioning service requirements (e.g., if available, shared by the target WTRU and the SL reference WTRU); receive a message from the server WTRU (e.g., if selected as the SL reference WTRU), the message including the selected positioning method, the corresponding target WTRU and / or the assigned radio resources; and so on.

[0072] LMF can (for example, be configured to) perform one or more of the following: for example, requesting PCF to send any policy update to LMF based on SL location server WTRU ID; (for example, to location server WTRU) send a common resource pool for each region or each WTRU, for example, if multiple WTRUs are located in a given region; send a request to location server for WTRU-specific resources for PC5 communication between target, SL reference and server WTRUs; and so on.

[0073] It can perform and / or provide (multiple) location services (LCS).

[0074] Multiple location services (e.g., 5G location services) can provide functionality for providing location information for WTRUs.

[0075] For example, WTRU positioning can be supported by a RAT-dependent positioning method, which can use (e.g., rely on) RAT measurements obtained from the target WTRU and / or measurements of RAT signals transmitted by the target WTRU obtained from the access network. WTRU positioning can also be supported by a RAT-independent positioning method, which can use (e.g., rely on) non-RAT measurements obtained from the WTRU and / or use other information.

[0076] Location information of one or more target WTRUs can be requested and reported to LCS clients or AFs or systems (e.g., wireless systems such as WTRUs) within or outside the operator's network.

[0077] Privacy (e.g., settings) verification of the target WTRU may (e.g., will) be enabled to check whether it may (e.g., is allowed) obtain WTRU location information, for example, in response to location requests from LCS clients or AFs.

[0078] It can support different types of location requests, such as one or more of the following: Mobile-Terminated Location Request (MT-LR); Mobile-Initiated Location Request (MO-LR); Immediate Location Request; Deferred Location Request; etc.

[0079] The Mobile Termination Location Request (MT-LR) can include the LCS client or AF sending a location request to the network to obtain the location of the target WTRU.

[0080] Mobile-Initiated Location Request (MO-LR) can include a WTRU sending a request to the network for location-related information about the WTRU.

[0081] Location requests (e.g., instant location requests) may include (e.g., an LCS client or AF) sending or initiating location requests for (multiple) target WTRUs, where the LCS client or AF may (e.g., expects) to receive a response containing location information for (multiple) target WTRUs within a time period (e.g., a short time period). Location requests (e.g., may be instant location requests) may be used for MT-LR or MO-LR.

[0082] Deferred location requests may include (e.g., an LCS client or AF) sending a location request to the network for (multiple) target WTRUs, whereby the LCS client or AF can expect to receive a response if (e.g., when) an indicated event occurs for the target WTRU (e.g., at some future time). Deferred location requests can be used for MT-LR.

[0083] Figure 2 An example reference model of a network for location services is shown. (R)AN herein can refer to (e.g., denote) NG-RAN, trusted (e.g., non-3GPP) access, or untrusted (e.g., non-3GPP) access. The access network can involve processing various location procedures, such as the location of a target WTRU, the provision of location-related information not associated with a specific target WTRU, and / or the transmission of location messages between the AMF or LMF and the target WTRU.

[0084] For example, AF and NF can access LCS services from GMLC in the same operator network.

[0085] LCS clients can access LCS services from GMLC. External AFs can access LCS services from NEF.

[0086] The Gateway Mobility Location Center (GMLC) can handle requests from external LCS clients, such as via NEF, or AFs (e.g., if the AF is an external AF, it forwards the location request to the appropriate NF).

[0087] Location retrieval function (LRF) can retrieve or verify (e.g., responsible for retrieving or verifying) location information, and can be co-located with GMLC or stand alone.

[0088] LMF can manage the overall coordination and scheduling of resources used (e.g., required) by WTRUs that register with or access the core network (e.g., 5GCN). It can calculate or verify the accuracy of final location-related information and the results achieved.

[0089] It can enable, use, and / or provide SL positioning (e.g., sidelink-based positioning) services.

[0090] SL positioning can specify a WTRU (e.g., using PC5) to obtain absolute position, relative position, or ranging information. Ranging can refer to determining the distance between two or more WTRUs and / or the direction of one WTRU (e.g., a target WTRU) from another WTRU (e.g., a reference WTRU) via the PC5 interface.

[0091] For SL positioning, the target WTRU, SL reference WTRU, SL positioning client WTRU, and / or located WTRU can be defined (e.g., but not limited to) and used as follows: The target WTRU may include a WTRU whose distance, orientation, and / or location can be measured using sidelink and sidelink positioning in a ranging service, supported by one or more SL reference WTRUs. The located WTRU may include an SL reference WTRU whose location may be known or potentially known (e.g., using Uu-based positioning). The located WTRU can be used to determine the location of the target WTRU, for example, using sidelink positioning. The SL reference WTRU may include a WTRU that supports the positioning of the target WTRU using sidelinks (e.g., by sending and / or receiving reference signals for positioning), provides positioning-related information, etc. The SL positioning client WTRU may include a third-party WTRU (e.g., in addition to the SL reference WTRU or the target WTRU) that can initiate ranging / sidelink positioning service requests on behalf of the applications residing thereon.

[0092] Ranging / sidelink localization operations can be performed as network-assisted operations or WTRU-only operations. For example, in network-assisted operations, (multiple) core network NFs (e.g., 5GC NFs) can participate in service request processing and result calculation. For example, in WTRU-only operations, service request processing and result calculation operations can be performed by the WTRU.

[0093] LMF (e.g., as defined in the location service) can be used to support the coordination of triggering SL positioning, SL positioning operations, and / or delivering results to clients, for example, if (e.g., when) network-assisted operations are used. Ranging / sidelink positioning service requests can be initiated by WTRUs (e.g., SL positioning client WTRU, target WTRU, SL reference WTRU), core network NFs (e.g., 5GCNF), LCS clients, and / or AFs.

[0094] WTRUs can interact with each other when necessary (e.g., via PC5) to perform SL positioning operations, if (e.g., when) WTRU (e.g., WTRU-only) operations are used. An SL positioning server WTRU can be defined to coordinate SL positioning operations and compute positioning results.

[0095] The SL positioning server WTRU may include WTRUs that provide method determination, auxiliary data distribution and / or location calculation functions and / or location calculation functions for sidelink positioning and range-based services.

[0096] It can enable, perform, and / or provide NW-assisted SL positioning.

[0097] NW-assisted SL positioning can be used to estimate the location of WTRUs with the assistance of the network by using the location of one or more located WTRUs and the distance and / or orientation between the WTRU and (multiple) located WTRUs.

[0098] Network-assisted SL positioning features may include one or more of the following: if (e.g., when) the WTRU can establish a NAS signaling connection; if (e.g., when) the WTRU prevents (e.g., cannot establish) the NAS signaling connection; and so on.

[0099] A WTRU can enter the CM connected state by executing a WTRU-triggered service request for the MO-LR (e.g., 5GC-MO-LR) or a network-triggered service request for the NI-LR (e.g., 5GC-NI-LR) or MT-LR (e.g., 5GC-MT-LR), for example, if (e.g., when) the WTRU can establish a NAS connection. For example, when the target WTRU can establish a NAS signaling connection with the AMF, the functions specified in the location service can be reused (e.g., including MO-LR, MT-LR, and NI-LR).

[0100] The target WTRU or LMF can determine whether network-assisted SL positioning can be applied.

[0101] The target WTRU can discover (multiple) located WTRUs used for network-assisted SL localization.

[0102] The target WTRU and multiple located WTRUs can perform ranging / SL positioning. The target WTRU can include the WTRU identity of multiple located WTRUs in the LMF along with ranging measurement data or estimation results. The LMF can interact with the GMLC to obtain the location of the located WTRUs.

[0103] LMF can estimate the location of the target WTRU using the locations of (multiple) located WTRUs together with ranging / SL positioning measurement data or estimation results reported by the target WTRU and / or (optionally) the located WTRUs.

[0104] If (for example, when) a target WTRU is prevented from establishing (e.g., unable to establish) a NAS connection with the AMF due to the target WTRU being outside coverage or for other reasons (e.g., invalid subscription, rejected by NW), then one or more of the following may apply: the target WTRU may perform discovery and selection of located WTRUs; the target WTRU may send its ranging measurements / results to (multiple) located WTRUs; (multiple) located WTRUs may report ranging / SL positioning measurement results to the LMF (e.g., which may include ranging measurements / results received from the target WTRU, and the endpoints of the LPP message may be the LMF and (multiple) located WTRUs); the LMF may use the received information to calculate the location of the target WTRU and may provide the obtained location to the target WTRU via the located WTRU or to the LCS client or application server via the NF.

[0105] It can enable and / or provide SL location services exposed to WTRU.

[0106] WTRU (e.g., SL location client WTRU) can request SL location via PC5 or NW.

[0107] The SL positioning client WTRU can discover one of the reference WTRU and the target WTRU, and it can invoke the ranging / SL positioning service request of the discovered reference WTRU / target WTRU to obtain the ranging and SL positioning results between the reference WTRU and the target WTRU, for example, if (e.g., when) the SL positioning client UE requests the SL positioning service via a PC5 connection. This request may include user information for the SL positioning client WTRU, the reference WTRU, and / or the target WTRU.

[0108] For example, multiple SL location service operations utilizing LMF or SL location server WTRU can be performed based on receiving an SL location service request (e.g., after receiving an SL location service request).

[0109] The SL positioning server WTRU can coordinate with the LMF (e.g., for SL positioning services) to better assist SL positioning between the target WTRU and the SL reference WTRU.

[0110] The SL positioning server WTRU can be discovered and selected for outcome calculation, method determination, auxiliary data distribution, and / or SL reference UE selection, for example, for use outside coverage or for WTRU-only operation (e.g., if the serving network does not support ranging / SL positioning). The LMF can determine whether the SL positioning server WTRU (e.g., co-located / integrated with a target WTRU or reference WTRU) can perform outcome calculations, for example, if the ranging / SL positioning LMF is reachable by the target WTRU and / or reference WTRU. The SL positioning server WTRU can be co-located with a target WTRU or reference WTRU.

[0111] The LMF may know the available SL location server WTRUs within its service area (e.g., it can be assumed (based on the above) that the LMF may know the available SL location server WTRUs within its service area). Each service area may have one or more SL location server WTRUs. Coordination between the LMF and the SL location server WTRUs may be unclear.

[0112] The quality of service provided by SL location services may not be as good as that provided by LMF (e.g., because the resources used by WTRUs coordinating based on SL location servers may be shared among many WTRUs performing SL location operations, and the configuration used for SL location operations may be based on pre-configured parameters that are more likely to conflict with other similar operations), for example, if (e.g., when) SL location server WTRUs participate in the coordination of SL location operations. It can avoid such conflicts.

[0113] The SL location server WTRU can assist (e.g., better assist) the SL location between the target WTRU and the SL reference WTRU, for example, if the LMF knows the SL location server WTRU.

[0114] The SL positioning server WTRU can assist the SL positioning client WTRU in selecting the SL reference WTRU for the SL positioning service.

[0115] The LMF can determine whether the SL positioning server WTRU (e.g., co-located / integrated with a target WTRU or reference WTRU) can perform outcome calculations, for example (e.g., as described herein), if the LMF capable of ranging / SL positioning is reachable by the target WTRU and / or reference WTRU. It may be unclear whether (e.g., when) the LMF will move positioning service operations to the server WTRU.

[0116] The SL location server WTRU can better understand nearby available SL reference WTRUs, for example, because it can perform coordination between peer WTRUs (e.g., between SL reference WTRUs and / or between SL client WTRUs and SL reference WTRUs). This information can be used to assist in the operation of location services provided by the server WTRU.

[0117] The SL positioning server WTRU can interact with the LMF, for example, to receive available auxiliary data in the LMF (e.g., which can be used to improve positioning services in the service area of ​​the positioning server).

[0118] The SL positioning server WTRU can assist the SL positioning client WTRU in selecting the SL reference WTRU for the SL positioning service.

[0119] WTRU can be one or more of the following: client WTRU, SL client WTRU, reference WTRU, SL reference WTRU, SL positioning reference WTRU, server WTRU, positioning server WTRU, SL server WTRU, SL positioning server WTRU, etc.

[0120] The terms SL client WTRU and client WTRU (as described herein, for example) are used interchangeably.

[0121] The terms SL location reference WTRU, SL reference WTRU, and reference WTRU (as described herein, for example) are used interchangeably.

[0122] The terms SL location server WTRU, SL server WTRU, location server WTRU, and server WTRU (as described herein, for example) are used interchangeably.

[0123] The WTRU may (for example, assume) support PC5 signaling. This PC5 signaling may be supported by the ProSe layer in the WTRU.

[0124] Multiple WTRUs (e.g., as described herein) may have ranging and sidelink positioning capabilities and / or the ability to position a sidelink server WTRU. Sidelink positioning may refer to positioning via a PC5 interface, and ranging may refer to determining the distance between two or more WTRUs and / or the direction and / or relative positioning from one WTRU to another.

[0125] It can perform, enable, and / or provide SL positioning operations that utilize one or more interactions between the LMF and the SL positioning server WTRU.

[0126] A WTRU, such as a location server WTRU, can (e.g., if / when registering with the network) receive policy configuration information from an NF (e.g., a PCF, which may be specific to an SL location server WTRU, for example, based on its capabilities and subscription information). The SL location server can inform the LMF of its capabilities as a server WTRU and can share some or all of the policy configuration information it receives. The LMF can request (e.g., also request) the PCF, for example, if there are updates in the policy linked to the SL location server WTRU.

[0127] The LMF (e.g., based on input received from an SL location server WTRU, its service area, and / or location) can send a list of located SL reference WTRUs in that area. The LMF can send a resource pool (e.g., a general resource pool) for each server WTRU or for each service area, and / or auxiliary data (e.g., any) that is useful to the server WTRU in location service operations.

[0128] The location server WTRU can use this input (e.g., from the LMF) to assist the target WTRU, for example, based on (e.g., at) receiving a location service request from one of the target or SL reference WTRUs. The SL location server can receive further information as part of the SL location service request, which can help the server WTRU determine the location method and select (multiple) SL reference WTRUs. The location server WTRU can coordinate with the LMF during the determination process (e.g., if needed).

[0129] Figure 3 An example procedure for an SL positioning operation that utilizes one or more interactions between the LMF and the SL positioning server WTRU is shown.

[0130] like Figure 3 As shown in 310, the SL positioning server WTRU (e.g., it may also be a target WTRU or an SL reference WTRU) can receive configuration information from the NF (e.g., such as a PCF for the SL positioning server WTRU) to assist the SL positioning service (e.g., the configuration information may be associated with SL positioning assistance). The configuration information may be provided by the AF for ranging / positioning (e.g., also).

[0131] In the example, authentication and authorization (e.g., mutual authentication and authorization) can (e.g., should) be performed. Authorization evidence (e.g., such as an authorization token) can (e.g., should) be issued to the SL location server WTRU (e.g., over the network).

[0132] like Figure 3As shown in 320, the SL location server WTRU can send location service messages (e.g., indicating capability information, such as indicating the ability to act as a location server WTRU) to network entities such as LMF. For example, it may include the ability to perform some or all of the actions supported by the location server WTRU (e.g., result calculation, method determination, auxiliary data distribution, and / or SL reference WTRU selection).

[0133] like Figure 3 As shown in 330, the SL location server WTRU can receive (e.g., from a network entity / LMF) a list of available located SL reference WTRUs (e.g., a candidate list of SL reference WTRUs) based on the server WTRU's location or service area. It can share a list of other nearby SL server WTRUs and the capabilities they support. The definition of this area can be determined by the LMF; for example, the area can be a broad region such as a TA, the LMF's service area, or a more concentrated area within the immediate vicinity of the server WTRU.

[0134] like Figure 3 As shown in 340, the SL positioning server WTRU can be assigned a general / general resource pool for each region by the LMF for SL positioning operations, or a different resource pool for each SL positioning server WTRU, for example, if there are multiple WTRUs sharing the same region.

[0135] The target WTRU or SL reference WTRU may initiate an SL location request (e.g., an SL location request associated with the target WTRU; an SL location request instructing a first WTRU and / or a second WTRU), which may include information about at least one or a list of SL reference WTRUs discovered by the WTRU (e.g., WTRU ID, status information (e.g., NAS / No NAS), capabilities), target WTRU information, and / or location information (e.g., a request). The SL location service request may be determined, for example, by an SL location server WTRU (e.g., which may be co-located with the target WTRU or SL reference WTRU, or may be the target WTRU or SL reference WTRU).

[0136] Location service information (e.g., location method and / or SL reference WTRU) can be determined (e.g., selected), such as Figure 3 As shown in 350a and 350b.

[0137] like Figure 3As shown in 350a, the SL positioning server WTRU can determine (e.g., itself) positioning service information (e.g., positioning method and / or SL reference WTRU) based, for example, on configuration information received from the NF (e.g., PCF, LMF) or AF and inputs from the WTRU for ranging / positioning. The SL positioning server WTRU can select one or more SL reference WTRUs and can select auxiliary data for distribution and / or its availability for result calculation.

[0138] like Figure 3 As shown in 350b, the SL positioning server WTRU can communicate with the LMF (e.g., one or more messages exchanged between the server WTRU and the LMF, wherein a positioning request can be sent to the LMF and received by the server WTRU) to select an SL positioning method, such as requesting additional auxiliary data or a better resource assignment from the LMF before performing the action in 350a.

[0139] For example, such as Figure 3 As shown in 360 (e.g., if 5a is true), the SL positioning server WTRU can request dedicated radio resources from the LMF for the requested positioning service (e.g., if highly accurate positioning is desired), and there are many WTRUs requesting positioning services from the SL positioning server WTRU, and there is a chance of message collisions.

[0140] like Figure 3 As shown in 370a and 7b, the SL positioning server can send one or more of the following.

[0141] like Figure 3 As shown in 370a, for example, the SL positioning server can send a message (e.g., an SL positioning response message) to the target WTRU via a PC5 link. This message may include positioning information (e.g., the selected positioning method and / or (multiple) SL reference WTRUs) and may select (multiple) SL reference WTRU IDs and assigned radio resources.

[0142] like Figure 3 As shown in 370b, the SL positioning server can send a message to the SL reference WTRU (e.g., an indication of whether it is selected as the SL reference WTRU for positioning assistance of the target WTRU), which may include the selected positioning method, the corresponding target WTRU ID and / or the assigned radio resources.

[0143] In the example, (for example, in) Figure 3At point 350 in the example, the SL location server WTRU (e.g., based on capacity and load) can forward the request to another server WTRU. In this example (e.g., alternatively), the SL location server WTRU selection can be done by the SL location server itself or with assistance from the LMF. During this process, based on (e.g., when) a location service request comes from an SL location client WTRU, the server WTRU can either redirect the request to another server WTRU itself or request the LMF to suggest another server ID that may be able to handle the location request from the client WTRU. The current server WTRU may be in a situation where it cannot handle the request from the client WTRU.

[0144] Although the above features and elements are described in specific combinations, each feature or element may be used alone without other features and elements of the preferred embodiment, or in various combinations with or without other features and elements.

[0145] While the implementations described herein may take into account 3GPP-specific protocols, it should be understood that the implementations described herein are not limited to this scenario and can be applied to other wireless systems. For example, although the solutions described herein take into account LTE, LTE-A, New Radio (NR), or 5G-specific protocols, it should be understood that the solutions described herein are not limited to this scenario and can also be applied to other wireless systems.

[0146] The above processes can be implemented in computer programs, software, and / or firmware incorporated in computer-readable media for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as, but not limited to, internal hard disks and removable disks), magneto-optical media, and / or optical media (such as CD-ROM discs and / or digital versatile discs (DVDs)). The processor associated with the software can be used to implement a radio frequency transceiver used in WTRUs, terminals, base stations, RNCs, and / or any host computer.

Claims

1. A wireless transmit / receive unit (WTRU), comprising: The processor is configured as follows: Receive configuration information associated with side-link (SL) positioning assistance; Send a location service message indicating capability information to a network entity, wherein the capability information indicates that the WTRU can act as an SL location server WTRU; Identify the SL location service request associated with the target WTRU; Determine location service information associated with a location service, wherein the location service is associated with the target WTRU, and wherein the location service information includes at least one of a location method or an SL reference WTRU; Send an SL positioning response to the target WTRU, indicating the determined positioning service information.

2. The WTRU according to claim 1, wherein, The processor is also configured to: Receive a message from the network entity including a candidate list of SL reference WTRUs, wherein the SL reference WTRUs are from the candidate list of SL reference WTRUs.

3. The WTRU of claim 1, wherein the SL location service request indicates at least one of the target WTRU ID, reference WTRU information, or location request information.

4. The WTRU according to claim 1, wherein the WTRU is a sidelink positioning server WTRU.

5. The WTRU of claim 1, wherein the WTRU is a target WTRU or an SL reference WTRU.

6. The WTRU of claim 1, wherein the SL reference WTRU is associated with at least one of a location or service area.

7. The WTRU according to claim 1, wherein, The location service information associated with the location service associated with the target WTRU is determined based on at least one of the configuration information received associated with SL location assistance or an indication received from the network entity.

8. The WTRU of claim 1, wherein the target WTRU is a first WTRU, and wherein the SL location service request indicates the first WTRU and the second WTRU.

9. A method, the method comprising: Receive configuration information associated with side-link (SL) positioning assistance; Send a location service message to a network entity indicating capability information, wherein the capability information indicates that the wireless transmit / receive unit (WTRU) is capable of acting as an SL location server WTRU; Identify the SL location service request associated with the target WTRU; Determine location service information associated with a location service, wherein the location service is associated with the target WTRU, and wherein the location service information includes at least one of a location method or an SL reference WTRU; and Send an SL positioning response, indicating the determined positioning service information, to the target WTRU.

10. The method of claim 9, wherein the method further comprises: Receive a message from the network entity including a candidate list of SL reference WTRUs, wherein the SL reference WTRUs are from the candidate list of SL reference WTRUs.

11. The method of claim 9, wherein the SL location service request indicates at least one of a target WTRU ID, reference WTRU information, or location request information.

12. The method of claim 9, wherein the method is performed by a WTRU, wherein the WTRU is a sidelink positioning server WTRU.

13. The method of claim 9, wherein the method is performed by a WTRU, wherein the WTRU is a target WTRU or an SL reference WTRU.

14. The method of claim 9, wherein the SL reference WTRU is associated with at least one of a location or service area.

15. The method according to claim 9, wherein, The location service information associated with the location service associated with the target WTRU is determined based on at least one of the configuration information received associated with SL location assistance or an indication received from the network entity.

16. The method of claim 9, wherein the target WTRU is a first WTRU, and wherein the SL location service request indicates the first WTRU and the second WTRU.

Images