Method for discovering and selecting positioned WTRU according to state of target WTRU

Abstract

A first wireless transmit / receive unit (WTRU) may be used to provide SL positioning services. The first WTRU may include a processor. A solicitation message may be received from the second WTRU. The solicitation message may indicate a state of the second WTRU and may indicate service information associated with the SL positioning service. It may be determined that the first WTRU can provide the SL positioning service based on the status of the second WTRU and the service information. When the first WTRU can provide the SL positioning service, a response message may be sent to the second WTRU.

Description

[0001] Cross-reference to related applications This application claims the benefit of Provisional Patent Application No. 63 / 457,565, filed on April 6, 2023, the contents of which are incorporated herein by reference. Background Technology

[0002] Mobile communications using wireless communication continue to evolve. The fifth-generation mobile radio access technology (RAT) can be referred to as 5G New Radio (NR). Previous-generation (traditional) mobile communication RATs could be, for example, fourth-generation (4G) Long Term Evolution (LTE). Summary of the Invention

[0003] This document discloses a system, method, and apparatus for providing a way to discover and / or select located wireless transmitter / receiver units (WTRUs) based on the status of a target WTRU. The target WTRU may send a solicitation message for Model B discovery to discover located WTRUs for SL positioning services. The solicitation message may include the status of the target WTRU and / or the capabilities of the requested located WTRUs, enabling the target WTRU to discover and select an appropriate WTRU to perform SL positioning.

[0004] The first wireless transmit / receive unit (WTRU) may perform (e.g., be configured to perform) one or more of the following: The first WTRU may receive a solicitation message from the second WTRU. This solicitation message may indicate the status of the second WTRU and / or service information associated with side-link (SL) positioning services. The first WTRU may determine, based on the status and service information of the second WTRU, that the first WTRU is capable of providing SL positioning services. The first WTRU may send a response message to the second WTRU based on the determination that the first WTRU is capable of providing SL positioning services. This response message may indicate that the first WTRU is capable of providing SL positioning services.

[0005] The first WTRU can receive a connection request message from the second WTRU to establish a connection. The first WTRU can then use this connection to perform a Single-Side Location (SL) operation. The SL operation can be based on the state of the second WTRU. The state of the second WTRU can indicate whether it has an available Non-Access Stratum (NAS) connection. The SL operation can be a synchronization method.

[0006] The solicitation message can indicate a connection status associated with the second WTRU, a positioning method, and / or a location associated with the second WTRU. The response message can indicate a capability of the first WTRU to perform a SL positioning operation associated with the status of the second WTRU. In an example, the response message can not be integrity protected (e.g., thus the response message can be sent via a connection). In an example, the response message is integrity protected and confidentiality protected.

[0007] A first wireless transmit / receive unit (WTRU) can perform (e.g., be configured to perform) one or more of the following. The first WTRU can receive an announcement message from a second WTRU. The announcement message can indicate service information associated with a sidelink (SL) positioning service, an identity of the second WTRU, and / or a capability of the second WTRU to support the SL positioning service. The first WTRU can determine that the second WTRU is configured to provide the SL positioning service to the first WTRU based on a status of the first WTRU and the capability of the second WTRU. The first WTRU can establish a connection to the second WTRU based on determining that the second WTRU is configured to provide the SL positioning service.

[0008] In an example, the first WTRU can receive a service message from the second WTRU using the connection. The service message can be associated with the SL positioning service. The SL positioning service can be a round trip time (RTT) positioning method or a time difference of arrival (TDOA) positioning method.

[0009] The status of the first WTRU can indicate whether the first WTRU has a non-access stratum (NAS) connection available.

[0010] In an example, the first WTRU can receive a second announcement message from a third WTRU. The determination that the second WTRU is to provide the SL positioning service can be based on the second announcement message. The determination that the second WTRU is to provide the SL positioning service can be based on a link quality associated with the first WTRU.

[0011] The first WTRU can receive a candidate list indicating a capability of the second WTRU to support the SL positioning service. The candidate list can include a first group of WTRUs associated with a first SL positioning service and a second group of WTRUs associated with a second SL positioning service. For example, the first group of WTRUs can include the second WTRU and the first SL positioning service can be the SL positioning service.

[0012] A first wireless transmit / receive unit (WTRU) can be configured to provide a SL positioning service. The first WTRU can include a processor. A solicitation message can be received from a second WTRU. The solicitation message can indicate a status of the second WTRU and can indicate service information associated with the SL positioning service. The first WTRU can be determined to be capable of providing the SL positioning service based on the status of the second WTRU and the service information. A response message can be transmitted to the second WTRU when the first WTRU is capable of providing the SL positioning service.

[0013] A first wireless transmit / receive unit (WTRU) can be configured to receive a service message associated with a SL positioning service. An announcement message can be received from a second WTRU, the announcement message indicating service information associated with the SL positioning service, an identity of the second WTRU, and a capability of the second WTRU to support the SL positioning service. The second WTRU can be determined to provide the SL positioning service based on a status of the first WTRU and the capability of the second WTRU. A connection to the second WTRU can be established based on the determination that the second WTRU is to provide the SL positioning service. The service message can be received from the second WTRU using the connection. BRIEF DESCRIPTION OF DRAWINGS

[0014] Figure 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments can be implemented.

[0015] Figure 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that can be used within the communications system 100 of Figure 1A is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that can be used within the communications system 100 of

[0016] Figure 1C is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that can be used within the communications system 100 of Figure 1A is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that can be used within the communications system 100 of

[0017] Figure 1D is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that can be used within the communications system 100 of Figure 1A is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that can be used within the communications system 100 of

[0018] Figure 2 is a system diagram illustrating an example architecture of a network.

[0019] Figure 3 is a system diagram illustrating an example architecture of a network that can be used to or will provide location services.

[0020] Figure 4 is a system diagram illustrating an example positioning control plane (CP) / user plane (UP) architecture.

[0021] Figure 5 is a flow diagram illustrating an example method of discovering and selecting a positioned WTRU using discovery.

[0022] Figure 6 is a flow diagram illustrating an example method of discovering and selecting a positioned WTRU using discovery.

[0023] Figure 7 is a flow diagram illustrating an example method of SL positioning protocol between a target WTRU and a positioned WTRU. DETAILED DESCRIPTION

[0024] Figure 1A is a schematic diagram illustrating an example communications system 100 in which one or more disclosed embodiments can be implemented. The communications system 100 can be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 can enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 can 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 OFDM (ZT UWDTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0025] As Figure 1AAs shown, the communication system 100 can include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which can be referred to as a “station” and / or a “STA”)) can be configured to transmit and / or receive wireless signals and can include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), industrial devices and applications (e.g., a robot or other wireless devices operating in an industrial and / or an automated processing chain environments), consumer electronics, a device operating on a commercial and / or industrial wireless network, and the like. Any of the WTRUs 102a, 102b, 102c, and 102d can be interchangeably referred to as a UE.

[0026] The communication system 100 can also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b can be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b can be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b can include any number of interconnected base stations and / or network elements.

[0027] The base stations 114a can be part of the RAN 104 / 113, which can also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base stations 114a and / or the base stations 114b can be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which can be referred to as a cell (not shown). These frequencies can be in the licensed spectrum, the unlicensed spectrum, or a combination of the licensed and unlicensed spectrums. A cell can provide wireless service coverage to a particular geographic area, which can be relatively fixed or can change over time as users who are using the cells move throughout the network. The cell can further be divided into cell sectors. For example, a cell associated with a base station 114a can be divided into three sectors. Thus, in one embodiment, the base station 114a can include three transceivers, one for each sector of the cell. In one embodiment, the base station 114a can employ multiple-input multiple-output (MIMO) techniques, and can 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.

[0028] The base stations 114a, 114b can communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over the air interface 116, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 can be established using any suitable radio access technology (RAT).

[0029] More specifically, as noted above, the communications system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a and the WTRUs 102a, 102b, 102c in the RAN 104 / 113 can implement a radio technology such as UMTS Terrestrial Radio Access (UTRA), which can establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

[0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c can implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-A Pro.

[0031] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c can implement a radio technology such as NR Radio Access, which can establish the air interface 116 using New Radio (NR).

[0032] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c can implement multiple radio access technologies. For example, the base station 114a and WTRUs 102a, 102b, 102c can implement LTE wireless access and NR wireless access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., a eNB and a gNB).

[0033] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0034] For example, Figure 1AThe base station 114b in the embodiment can be a wireless router, Home Node B, Home eNode B, or access point, for example, and can utilize any suitable RAT for facilitating wireless connectivity access to the Internet, such as IEEE 802.11, 802.16, 802.20, 802.22, or WiMAX, for example. The base station 114b and the WTRUs 102c, 102d in the embodiment can implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d can implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b can have a direct connection to the Internet 110. Thus, the base station 114b can not be required to access the Internet 110 via the CN 106 / 115. Figure 1A

[0035] The RAN 104 / 113 can be in communication with the CN 106 / 115, which can be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data can have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 / 115 can provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in Figure 1A Although not shown in FIG. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 can be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which can employ a NR radio technology, the CN 106 / 115 can also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0036] ​The CN 106 / 115 can also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 can include circuit-switched telephone networks that provide infrastructure for the provision of voice telephony. The Internet 110 can include a global system of interconnected computer networks and devices that use the Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or the internet protocol suite (IP) to communicate with one another. The networks 112 can include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 can include another CN that employs a different RAT than the RAN 104 / 113.

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

[0038] Figure 1B Figure 1 C is a system diagram of an example WTRU 102. As shown in Figure 1 C, the WTRU 102 can include a plurality of subsystems. For example, the WTRU 102 can include 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 source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 can include any subcombination of the foregoing elements while remaining consistent with an embodiment. Figure 1B

[0039] ​The processor 118 can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 can perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to the transceiver 120, which can be coupled to the transmit / receive element 122. While Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but can be integrated together in an electronic package or chip.

[0040] The transmit / receive element 122 can be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 can be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 can be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 can be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0041] Although the transmit / receive element 122 is depicted in the WTRU 102 Figure 1B In one embodiment, the WTRU 102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) to facilitate increasing the WTRU's 102 capacity.

[0042] The transceiver 120 can be configured to modulate information to be transmitted by the transmit / receive element 122 and to demodulate information received by the transmit / receive element 122. As noted above, the WTRU 102 can have multi-mode capabilities. Thus, the transceiver 120 can include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

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

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

[0045] The processor 118 can also be coupled to the GPS chipset 136, which can be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or

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

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

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

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

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

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

[0052] The MME 162 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 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 RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0053] The SGW 164 can connect to each of the eNode Bs 160a, 160b, and 160c in RAN 104 via the S1 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.

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

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

[0056] Despite WTRU in Figures 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.

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

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

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

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

[0061] 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).

[0062] 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).

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

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

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

[0066] 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).

[0067] 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).

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

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

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

[0071] 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 182 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.

[0072] 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 WTRU 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.

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

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

[0075] Given Figures 1A-1D as well as Figures 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-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF183a-b, DN 185a-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.

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

[0077] 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 implement the testing of 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).

[0078] The following abbreviations may be used here: Non-access stratum (NAS), sidelink-based positioning (SL positioning), radio access technology (RAT), radio access network (RAN), or proximity-based service (ProSe).

[0079] The timer reference here can refer to time, time period, time tracking, time period tracking, or a combination thereof. The timer expiration mentioned here can mean that the exact time has arrived or the time period has expired.

[0080] This document discloses systems, methods, and apparatus for providing methods of discovering and / or selecting located WTRUs, for example, based on the state of a target WTRU. For example, discovery and / or selection via PC5 based on 5G ProSe can be provided. Ranging and SL Positioning Protocol (RSPP) for SL positioning operations via PC5 connectivity can be provided.

[0081] Discovery typically refers to the process by which a device finds and connects to other devices and / or available network resources. Discovery may involve processes such as scanning for available networks, identifying suitable access points, and establishing initial communication with the network. In the example, two discovery methods can be defined. The first discovery method can be referred to as Model A discovery and is often combined with proactive reporting (e.g., by the device). The second discovery method can be referred to as Model B discovery and is often combined with proactive polling / requesting (e.g., by the device). In the example, the device can be configured to employ multiple discovery methods (e.g., in different scenarios).

[0082] Model A discovery (e.g., it could be referred to as "I'm here" discovery) can be a method used by a monitoring WTRU (e.g., a target WTRU) to discover an announcing WTRU (e.g., a located WTRU), for example, by receiving / monitoring an announcement message from the announcing WTRU. The announcing WTRU can be a WTRU that has announced the information (e.g., has not received an explicit request from the monitoring WTRU). The announced information can be used by a WTRU (e.g., a monitoring WTRU) that is near the announcing WTRU and has permission to discover it. The monitoring WTRU can be a WTRU that is monitoring information of interest in the vicinity of the announcing WTRU. In Model A, the announcing WTRU can broadcast discovery messages at predefined discovery intervals, and monitoring WTRUs interested in these messages can receive and process them. The announced information can include one or more of the following: SL positioning capabilities (e.g., those of the announcing WTRU), the location associated with the announcing WTRU, or an indication of the announcing WTRU's ability to support the monitoring WTRU (e.g., depending on the status of the monitoring WTRU).

[0083] For Model A discovery, the located WTRU can send an announcement message. The announcement message can include capabilities supported by the located WTRU (e.g., enabling it to perform the procedures required for SL positioning with a target WTRU that does not have a NAS connection). Based on the announced supported capabilities, the target WTRU can discover and select a located WTRU, for example, to perform SL positioning. In the example, the target WTRU can wait for a period of time (e.g., until a timer expires) so that the target WTRU can receive announcement information from multiple located WTRUs.

[0084] The target WTRU can further select a located WTRU based on its state. In the example, the state of the target WTRU can indicate its NAS connectivity (e.g., whether the target WTRU has a NAS connection). The located WTRU can provide the requested capabilities (e.g., for SL positioning) based on the state of the target WTRU. The target WTRU and the selected located WTRU can establish a PC5 connection and / or perform SL positioning operations (e.g., based on the state of the target WTRU).

[0085] Model B discovery (which may be referred to as "who's there" or "are you there" discovery) can be a method used by a discoverer WTRU (e.g., a target WTRU) to discover a discoverer WTRU (e.g., a located WTRU) by sending a solicitation message and receiving a response message (e.g., from the discoverer WTRU). A discoverer WTRU can be a WTRU that sends a request for information (e.g., an indication of whether the discoverer WTRU is able to provide services to the discoverer WTRU). A discoverer WTRU can be a WTRU that receives a solicitation message and can respond with some information related to the discoverer's request.

[0086] For Model B discovery, the target WTRU can send a solicitation message to discover located WTRUs, for example, to provide SL location services to located WTRUs. The solicitation message can include the status of the target WTRU (e.g., whether the target WTRU has NAS connectivity) and / or the capabilities of the requested located WTRU. The solicitation message can be configured to allow the target WTRU to discover and select a located WTRU configured to provide services (e.g., SL location procedures) based on the target WTRU's status. In the example, the target WTRU can wait for a period of time (e.g., until a timer expires) so that the target WTRU can receive responses from multiple located WTRUs before selecting a located WTRU. In the example, the target WTRU can wait to select a located WTRU until it receives responses from multiple located WTRUs (e.g., multiple located WTRUs to which the solicitation message is sent or all located WTRUs).

[0087] For example, a target WTRU can select a located WTRU based on the ability of the located WTRU to provide services to the target WTRU according to its state. The target WTRU and the selected located WTRU can establish (e.g., set up) a PC5 connection. The target WTRU and the selected located WTRU can perform SL positioning operations (e.g., via the PC5 connection) according to the state of the target WTRU.

[0088] In one example, for an SL positioning operation, the target WTRU and the positioned WTRU can negotiate the state of the target WTRU. The state of the target WTRU can indicate whether the target WTRU has NAS connectivity. The requested capabilities of the positioned WTRU can be provided based on the state of the target WTRU so that the roles of the SL positioning method (e.g., synchronization method, measurement mechanism, etc.) and / or one or more WTRUs, such as which entity can report location, can be determined (e.g., based on the state of the target WTRU and the capabilities of the positioned WTRU). For example, the target WTRU can determine that the capabilities of the positioned WTRU are associated with a specific SL positioning method.

[0089] A located Wireless Transmit / Receive Unit (WTRU) (e.g., a first WTRU) may include a processor and may (e.g., be configured to) perform one or more of the following (e.g., for Model B discovery): The located WTRU may be configured to provide SL location services. The located WTRU may receive solicitation messages from a target WTRU (e.g., a second WTRU). The solicitation messages may indicate the status of the target WTRU and / or service information associated with the SL location services. The located WTRU may, for example, determine, based on the solicitation messages, that it is capable of providing SL location services to the target WTRU. The located WTRU may send a response message to the target WTRU, the response message including an indication that the located WTRU is capable of providing SL location services.

[0090] In the example, the request message may indicate one or more of the following: the requested capability, the connectivity status associated with the target WTRU, the location method, or the location (e.g., associated with the target WTRU). In the example, the response message may include information about one or more of the requested capability or the capability associated with the status of the target WTRU.

[0091] In the example, the located WTRU can receive a connection request message from the target WTRU. The connection request message can indicate a request to establish a connection (e.g., a PC5 connection) with the located WTRU. For example, based on the received connection request message, a connection can be established between the located WTRU and the target WTRU. For example, the connection between the located WTRU and the target WTRU can be used to perform an SL positioning operation. The performed SL positioning operation can be based on the state of the target WTRU (e.g., whether the target WTRU has a NAS connection).

[0092] A target wireless transmit / receive unit (WTRU) (e.g., a first WTRU) may include a processor and may (e.g., be configured to) perform one or more of the following (e.g., for model A discovery): The target WTRU may receive service messages associated with the SL positioning service. The target WTRU may receive notification messages from a located WTRU (e.g., a second WTRU). The notification messages may indicate service information associated with the SL positioning service, the identity of the located WTRU, and / or the ability of the located WTRU to support the SL positioning service. The target WTRU may determine that the located WTRU is capable of providing (e.g., configured to provide) the SL positioning service. Determining that the located WTRU is capable of providing the SL positioning service may be based on the state of the target WTRU and / or the capabilities of the located WTRU. The target WTRU may select a located WTRU based on this determination. For example, based on the determination that the located WTRU will provide the SL positioning service, a connection may be established to the selected located WTRU. The target WTRU and the selected located WTRU may, for example, perform the SL positioning service through this connection. The performed SL positioning service may be based on the state of the target WTRU.

[0093] In the example, determining that a located WTRU will provide SL location services (e.g., selecting a located WTRU) can be further based on the NAS connection status associated with the target WTRU.

[0094] In the example, the notification message can be a first notification message, and a second notification message can be received from a third WTRU. Determining that a located WTRU can provide SL location services (e.g., selecting a located WTRU) can further be based on the second notification message.

[0095] A located wireless transmit / receive unit (WTRU) (e.g., a first WTRU) may include a processor and may (e.g., be configured to) perform one or more of the following (e.g., for the SL positioning protocol): The located WTRU may be used to perform positioning-based operations. The located WTRU may receive a first message from a target WTRU (e.g., a second WTRU) indicating the connection status associated with the target WTRU. The negotiated capabilities may be determined based on the connection status, the capabilities of the located WTRU, and the capabilities of a third WTRU (e.g., an SL positioning server, an SL reference WTRU). The located WTRU may determine and / or receive SL positioning operations. The located WTRU may use the negotiated capabilities to perform SL positioning operations. SL positioning operations may be, for example, synchronization methods or measurement mechanisms.

[0096] In the example, the located WTRU can receive, for example, a service message indicating the result of the SL location operation from the target WTRU and / or the third WTRU.

[0097] In the example, auxiliary messages including auxiliary data associated with the SL positioning method can be received from the third WTRU. For example, the auxiliary data may be the characteristics and format of the transmission signal and / or time slot.

[0098] In the example, the located WTRU can send a report message associated with the performed SL location operation. This report message can be sent to, for example, the target WTRU and / or a third WTRU. The report message may include data associated with the result of the SL operation. For example, the result of the SL location operation may have already been received by the located WTRU. For example, the result of the SL location operation may have already been determined by the located WTRU (e.g., using data collected during the execution of the SL location operation).

[0099] It can provide the ability to discover and / or select located WTRUs based on the status of the target WTRU (e.g., connection status).

[0100] Model B discovery can be used to discover and / or select located WTRUs. For Model B discovery, for example, a target WTRU can send a solicitation message to discover located WTRUs that can provide SL location services. The target WTRU can include its status and / or the capabilities of the requested located WTRU in the solicitation message (e.g., enabling the target WTRU to discover and select a located WTRU to perform SL location based on its status). The target WTRU and the selected located WTRU can establish a PC5 connection based on the target WTRU's status and perform the SL location operation.

[0101] The system can provide discovery and / or selection of located WTRUs via Model A discovery. For Model A discovery, the located WTRU can send an announcement message. The announcement message can indicate the supported capabilities of the located WTRU to perform an SL location procedure utilizing a target WTRU that may not have a NAS connection. Based on the announced capabilities, the target WTRU can discover and / or select the located WTRU to perform an SL location operation based on the target WTRU's state (e.g., whether the target WTRU has a NAS connection). The target WTRU and the selected located WTRU can establish a PC5 connection, and the SL location operation can be performed, for example, based on the target WTRU's state.

[0102] The target WTRU can share its state regarding whether it has available NAS connectivity. The target can share its state to select an appropriate SL positioning method and / or determine (e.g., each) the role of the WTRU in the SL positioning operation. For example, the target WTRU can share its state while both the target WTRU and the positioned WTRU are performing an SL positioning operation. Based on the target WTRU's state and the determined SL positioning method, it can be determined (e.g., by the target WTRU, the selected positioned WTRU, or a different WTRU) whether the selected positioned WTRU or the target WTRU can collect the SL positioning results and report them to the network.

[0103] Figure 2 This is a system diagram illustrating an example architecture for 5G or next-generation networks.

[0104] As described in this article, RAN can refer to a radio access network based on 5G RAT or evolved E-UTRA that is connected to the next-generation core network.

[0105] Access control and mobility management functions (AMF) can include functions such as registration management, connection management, reachability management, and mobility management.

[0106] Session management functions (SMF) may include functions such as session management (e.g., including session establishment, modification and / or release); WTRU IP address allocation; selection and control of UP functions; and so on.

[0107] User plane functions (UPF) may include the following features: such as packet routing and forwarding; packet inspection; service usage reporting; and other features.

[0108] Location services (LCS), such as 5G location services, can be provided. Location services (e.g., 5G location services) can provide the functionality to provide location information for WTRUs.

[0109] The location of the WTRU can be supported by a RAT location method, which may rely on measurements. These measurements could include, for example, RAT measurements obtained from the target WTRU (e.g., 3GPP RAT measurements) and / or measurements of RAT signals transmitted by the target WTRU (e.g., 3GPP RAT signals) obtained from the access network. The location of the WTRU can also be supported by a RAT-independent location method, which may rely on non-RAT measurements and / or other information obtained from the WTRU.

[0110] Location information of one or more target WTRUs may be requested and reported to them by LCS, client and / or application functions (AF) inside or outside the operating network (e.g., 3GPP operator network) or by control plane network functions (NF) within the system (e.g., 3GPP system).

[0111] For location requests from LCS clients or AFs, you can request that privacy verification be enabled for the target WTRU to check whether it is allowed to obtain WTRU location information.

[0112] It can support several different types of location requests.

[0113] It can support Mobile Termination Location Request (MT-LR) requests. The LCS client or AF can send MT-LR to the network (e.g., a 5G network) for the location of the target WTRU.

[0114] It can support Mobile Initiated Location Request (MO-LR). When MO-LR occurs, the WTRU can send a request for location-related information of the WTRU to the network (e.g., a 5G network).

[0115] It supports real-time location requests. Using real-time location requests, the LCS client or AF can send or initiate location requests to (multiple) target WTRUs and can receive responses containing location information for (multiple) target WTRUs within a short time period. It can be used with MT-LR or MO-LR.

[0116] Delayed location requests are supported. Using delayed location requests, LCS clients or AFs can send location requests to the network (e.g., a 5G network) for (multiple) target WTRUs and can expect to receive a response when the indicated event may occur at some future time for a potential target WTRU. It can be used with MT-LR.

[0117] Figure 3 This is a system diagram illustrating an example architecture of 5G or next-generation networks that can be used to or provide location services. (Example:) Figure 3 As shown, (R)AN can represent NG-RAN, trusted non-3GPP access, or untrusted non-3GPP access. The access network may be involved in handling various positioning processes, including locating the target WTRU, providing location-related information that may not be associated with a specific target WTRU, and transmitting positioning messages between the AMF or LMF and the target WTRU.

[0118] AF and NF can access LCS services from GMLC in the same 3GPP operator network.

[0119] LCS clients can access LCS services from GMLC, and external AFs can access LCS services from NEF.

[0120] If the AF can be an external AF, the Gateway Mobile Location Center (GMLC) can process requests from external LCS client AFs via the NEF and forward the location requests to the appropriate NF.

[0121] Location retrieval function (LRF) is responsible for retrieving or verifying location information. LRF can be co-located with GMLC (Gateway Mobility Location Center), or LRF can be located independently.

[0122] The Location Management Function (LMF) manages the overall coordination and scheduling of resources for WTRUs that can register with or access the core network (e.g., 5GCN) for location requests (e.g., required resources). It can calculate or verify location-related information and ensure accuracy.

[0123] Positioning protocols and signals, such as NR positioning protocols and signals, can be provided. Positioning protocols and RAN-based positioning signals can be used to implement emergency and location-based services.

[0124] Location protocols such as NR positioning protocols can be supported by a control plane (CP) positioning architecture via the Uu interface (NG-RAN node to WTRU). Positioning architectures such as NR positioning can be supported by a Secure User Plane Location (SUPL) server, which may be referred to as a SUPL Location Platform (SLP) or location server, and can utilize any Internet protocol as a carrier. Interoperability between CP and UP positioning solutions can be provided, where the SUPL can be used as a tunnel for CP positioning protocols (e.g., LPP).

[0125] Figure 4 This is a system diagram illustrating an example positioning control plane (CP) / user plane (UP) architecture, such as the New Radio (NR) positioning CP / UP architecture.

[0126] Various protocols can be used to implement several positioning technologies and methods (GNSS, sensors, positioning signals, etc.). For example, LPP (LTE positioning protocol) can be terminated between WTRU and LMF (location management function). LPP can be a point-to-point LCS (Location Service) and a non-access stratum (NAS) messaging protocol.

[0127] Radio Resource Control (RRC) can be a protocol used to provide transmission of LPP messages and other positioning procedures via the NR-Uu interface, which can be terminated between the gNB and WTRU.

[0128] On the network side, the NG Application Protocol (NGAP) can be terminated between the AMF and (multiple) NG-RAN nodes (e.g., gNB / TRP). It can be transmitted via LPP and NR Positioning Protocol A (NRPPa) messages on the NG-C interface. NRPPa can carry information between (multiple) NG-RAN nodes and the LMF.

[0129] NR positioning mode can be provided. Positioning can be performed in standalone, WTRU-based, or WTRU-assisted modes.

[0130] In stand-alone positioning, the WTRU can handle one or more (e.g., all) aspects of positioning, can scan accessible positioning and measurement sources, and / or can process positioning signals / sources. The WTRU can calculate its own position in two or more dimensions (such as two-dimensional or three-dimensional). In stand-alone positioning, the Uu interface may affect WTRU capability exchange and / or WTRU position reporting.

[0131] In WTRU-based localization, which can be referred to as WTRU-based positioning (WTRU-B), the network can provide acquisition assistance data, and the WTRU can scan accessible localization and measurement sources and process localization signals / sources (e.g., based on assistance information from the network). The WTRU can use two or more dimensions (e.g., two-dimensional or three-dimensional) to calculate its position and report its position to the network.

[0132] In WTRU-assisted positioning, which may be referred to as WTRU-assisted positioning (WTRU-A), the network provides acquisition assistance, and the WTRU scans accessible location sources and measures the location signal / source (e.g., based on assistance information from the NW). The WTRU can return the measurement results to the network, and the network can calculate the device location (e.g., at a location server / LMF).

[0133] Table 1 shows the technologies that can be supported for WTRU positioning methods.

[0134] Table 1: Technical aspects of WTRU positioning methods Timing / angle positioning methods can refer to those that can use reference signals such as SL-PRS (e.g., any positioning method). A WTRU can receive multiple reference signals from (multiple) WTRUs and measure RSTD, RSRP, and / or AoA. Examples of angle / timing positioning methods are SL-AoD or SL-TDOA positioning. Another example could be that a WTRU sends an SL-PRS to (multiple) WTRUs, and the receiver performs measurements (e.g., RSTD, AoA, RSRP) to determine the position of the WTRU that sent the SL-PRS.

[0135] "RTT positioning method" can refer to any positioning method in which two WTRUs can send SL-PRS to each other. In one example, the anchor WTRU can send SL-PRS to the target WTRU. The target WTRU can receive SL-PRS from the anchor WTRU, and the target WTRU can send SL-PRS to the anchor WTRU. The target WTRU can measure the WTRU Tx-Rx time difference (e.g., it could be the difference between the time the SL PRS is sent from the target WTRU and the time the SL-PRS is received from the anchor WTRU). The target WTRU can report the WTRU Tx-Rx time difference to the anchor WTRU, the server WTRU, and / or the network (e.g., gNB, LMF).

[0136] The LTE Positioning Protocol (LPP) can be executed. An LPP message related to a WTRU-assisted location request can include several procedures. For example, capabilities can be requested in an LMF request to the WTRU. Capabilities can be provided in the WTRU's response to the LMF. Assistance data can be requested in a WTRU request for location assistance data / information to the LMF.

[0137] Auxiliary data can be provided (e.g., to the WTRU). For example, the LMF can send WTRU positioning auxiliary data information / configuration. Positioning auxiliary data (AD) can be broadcast via the Positioning System Information Block (posSIB) and / or carried in SI messages.

[0138] Location information can be requested and provided. For example, the LMF can send a request for location / measurement to the WTRU. The WTRU can send a response to the LMF with its location and / or measurement.

[0139] The device may be able to terminate an LPP session. Errors associated with (multiple) positioning processes can be identified and / or processed.

[0140] SL positioning services can be provided. For example, a WTRU can use SL positioning to obtain absolute position, relative position, or ranging information (e.g., via PC5).

[0141] Ranging can refer to determining the distance between two or more WTRUs and / or the direction of one WTRU (e.g., target WTRU) from another WTRU (e.g., reference WTRU) via an interface (such as a PC5 interface).

[0142] It can provide the target WTRU, SL reference WTRU, SL positioning client WTRU, and located WTRU for SL positioning.

[0143] A target WTRU can be provided. The target WTRU can be a WTRU whose distance, orientation, and / or positioning can be measured with the support of one or more SL reference WTRUs, for example, in range-based services and SL positioning using SL.

[0144] A located WTRU can be provided. The located WTRU can be an SL reference WTRU, whose location is known or can be known, for example, using Uu-based positioning. The located WTRU can be used to determine the location of the target WTRU using SL positioning.

[0145] An SL reference WTRU can be provided. The SL reference WTRU can support the positioning of the target WTRU, for example, by sending and / or receiving reference signals for positioning, and providing positioning-related information through the SL.

[0146] An SL positioning client WTRU can be provided. The SL positioning client WTRU can be a third-party WTRU (e.g., in addition to the SL reference WTRU and the target WTRU), which can initiate ranging / SL positioning service requests on behalf of the applications residing on it.

[0147] Ranging / SL positioning operations can be performed using network-assisted operations or WTRU-A (e.g., WTRU-only) operations. In network-assisted operations, network functions (e.g., multiple 5GC NFs) may be involved in service request processing and / or result calculation. In WTRU operations (e.g., WTRU-only operations), the service request processing and / or result calculation process can be performed by the WTRU.

[0148] When using network-assisted operations, the LMF identified (e.g., defined) in 5G location services can be used to support the triggering of SL positioning, coordination of SL positioning operations, and / or delivery of results to the client. Ranging / SL positioning service requests can be initiated by WTRUs (e.g., SL positioning client WTRU, target WTRU, SL reference WTRU), 5GC NF, LCS clients, or AFs.

[0149] When WTRU-a (e.g., only) operation is available, WTRUs can interact with each other as needed via an interface (e.g., PC5) to perform SL positioning operations. SL positioning server WTRUs can be identified (e.g., defined) to coordinate SL positioning operations and calculate positioning results.

[0150] A Location Server WTRU can be provided. The Location Server WTRU can be a WTRU that provides method determination, auxiliary data distribution, location calculation functions, and / or location calculation functions for SL positioning and ranging-based services.

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

[0152] Network-assisted SL positioning characteristics can have several scenarios, such as two scenarios. For example, one scenario could be when the WTRU can establish a NAS signaling connection. Another scenario could be when the WTRU might not be able to establish a NAS signaling connection.

[0153] When a WTRU establishes a NAS connection, it can enter the CM connection state by executing a WTRU-triggered service request for 5GC-MO-LR or a network-triggered service request for 5GC-NI-LR or 5GC-MT-LR. When a target WTRU establishes a NAS signaling connection with an AMF, it can reuse functions specified in the 5G location services, such as 5GC-MO-LR, 5GC-MT-LR, and 5GC-NI-LR. The target WTRU or LMF can determine whether network-assisted SL positioning can be applied. The target WTRU can discover (multiple) located WTRUs for network-assisted SL positioning.

[0154] The target WTRU and the located WTRU(s) can perform ranging / SL positioning. The target WTRU may include the WTRU identity of the located WTRU(s) of the LMF, for example, having ranging measurement data and / or estimation results. The LMF can interact with the GMLC to obtain the location of the located WTRU.

[0155] LMF can estimate the location of the target WTRU using the location of the located WTRU, ranging or SL positioning measurement data, estimates reported by the target WTRU, and / or estimates reported by the located WTRU.

[0156] If the target WTRU is outside the coverage area, it may be unable to establish a NAS connection with the AMF. In one example, for 5GC-MO-LR or a pending 5GC-MT-LR (e.g., a delayed 5GC-MT-LR), several principles can be applied. The target WTRU can perform discovery and selection of located WTRUs. The target WTRU can send its ranging measurements / results to (multiple) located WTRUs. Located WTRUs can report ranging or SL positioning measurement results to the LMF. This can include ranging measurements or results received from the target WTRU. The endpoints of the LPP message can be the LMF and (multiple) located WTRUs. The LMF can use the received information to calculate the location of the target WTRU. The LMF can provide the obtained location of the target WTRU to the target WTRU, for example, via (e.g., via) a located WTRU. The LMF can provide the obtained location of the target WTRU to an LCS client or AS, for example, via a network function (e.g., 5G NF).

[0157] SL location services can be provided that are exposed to WTRUs. WTRUs (e.g., SL location client WTRUs) can request SL location via PC5 or via NW.

[0158] When an SL positioning client WTRU requests SL positioning services via a connection (e.g., a PC5 connection), it can discover a reference WTRU and / or a target WTRU, and it can invoke a ranging / SL positioning service request to the discovered reference WTRU / target WTRU (e.g., to obtain ranging and SL positioning results between the reference WTRU and the target WTRU). This request may include user information for one or more of the following: the SL positioning client WTRU, the reference WTRU, or the target WTRU.

[0159] In NW-assisted SL positioning, there may be different use cases where the located WTRU is used (e.g., two possible use cases based on the presence of NAS connectivity).

[0160] For example, a use case (e.g., case 1) could be when the target WTRU has a NAS connection. In this case, the located WTRU can be selected for SL positioning, and location reporting can be performed by the target WTRU. In this case, the requested capability of the located WTRU could be the availability of the located WTRU for Uu positioning and / or the ability to utilize the target WTRU's SL positioning.

[0161] For example, a use case (e.g., case 2) could be when the target WTRU does not have a NAS connection. In this case, the located WTRU can be selected for SL positioning. Location reporting can be performed by the selected located WTRU. In this case, the requested capability of the located WTRU could be the ability of the located WTRU to perform location reporting for the target WTRU, for example, by transmitting parameters received from the target WTRU. This capability could be a capability other than other requested capabilities, such as those related to other cases (e.g., as described in the previous use case regarding the presence of a NAS connection).

[0162] The located WTRU can be selected based on the status of the target WTRU. The capabilities of the requested located WTRUs in Case 1 and Case 2 may differ and may depend on the status of the target WTRU (e.g., within or outside coverage). The target WTRU may be able to select a located WTRU with the requested capabilities based on its status. The located WTRU can be selected based on the status of the target WTRU.

[0163] The SL positioning method can be determined based on the state of the target WTRU. The role of one or more WTRUs in the SL positioning method can be determined based on the state of the target WTRU. As shown in Cases 1 and 2, the requested role of the positioned WTRU may differ depending on the state of the target WTRU. The target WTRU may gain or lose connectivity with the core network (e.g., NAS connectivity with the 5GC) based on its mobility and other factors, and the state of the target WTRU may change. The positioned WTRU and the target WTRU may request (e.g., may need) to synchronize with each other on the state of the target WTRU so that the SL positioning method and the role of each WTRU can be determined (e.g., based on the state of the target WTRU). Examples (e.g., as described herein) may allow one or more WTRUs to synchronize with each other on the state of the target WTRU to determine the SL positioning method, and / or to determine (e.g., the role of each) WTRU based on the state of the target WTRU.

[0164] In the example, the WTRU may support PC5 signaling. PC5 signaling may be supported by the ProSe layer in the WTRU. In the example, the WTRU may have ranging and SL positioning capabilities. SL positioning may refer to positioning via an interface (e.g., a PC5 interface), and ranging may refer to determining the distance between two or more WTRUs and / or the orientation and / or relative positioning of one WTRU to another.

[0165] A process for discovering and selecting located WTRUs in Model B discovery can be provided. For Model B discovery, a target WTRU can send a solicitation message to discover located WTRUs for SL location services. The target WTRU may include its state or the requested capabilities of the located WTRUs, enabling the target WTRU to discover and select located WTRUs, which can be used to perform SL location based on the state of the target WTRU. The target WTRU and the selected located WTRU can establish a connection, such as a PC5 connection, and SL location operations can be performed based on the state of the target WTRU.

[0166] Figure 5 This is a flowchart illustrating an example method for discovering and selecting a located WTRU (e.g., it could be Model B discovery). To discover a located WTRU, at point 1, the target WTRU can send a solicitation message. The solicitation message can include ProSe service information indicating the SL location service and the type of WTRU requested that can be indicated to the located WTRU. The solicitation message can include the target WTRU's status information (e.g., whether the target WTRU has a connection to a network, such as a NAS connection) and / or the requested capabilities of the located WTRU. The requested capabilities of the located WTRU could be, for example, the ability to support SL location operations when the target WTRU might not have a connection to a network (e.g., it might not have a NAS connection).

[0167] In one example, the solicitation message may include the localization method that the target WTRU may wish to use (e.g., RTT, TDOA, AoA, AoD).

[0168] In another example, the solicitation message may include the location of the target WTRU determined based on a positioning method (e.g., a RAT-independent positioning method, such as GNSS). The target WTRU may indicate the positioning method (e.g., a RAT-independent positioning method) used to determine its location.

[0169] Continue to refer to Figure 5 At point 1, the message (e.g., the target WTRU state IE) can be protected for integrity. In the example, the message can also be protected for confidentiality. If a security association is established at point 1, the parameters exchanged at points 1-3 can be analyzed (e.g., examined) at point 4.

[0170] At point 2, the located WTRU can receive a solicitation request message to discover other located WTRUs for the SL location service. The located WTRU can then check if it has the capability to support the SL location operation included in the solicitation message. The capabilities of the located WTRU can vary based on, for example, the state of the target WTRU.

[0171] At point 3, if the located WTRU supports the requested capability, the located WTRU can respond to the target WTRU with a response message. This response message can include an indication of the capability to support the target WTRU's status. For example, the response message can indicate whether the located WTRU can support the requested capability based on the target WTRU's status or based on the requested capability itself (e.g., included in the solicitation message at point 1).

[0172] After sending a solicitation message, the target WTRU can wait for a period of time so that it can receive responses from multiple located WTRUs.

[0173] At point 3, the message, or at least an indication of the target WTRU's state IE capability, can (e.g., must) be protected at least by integrity, such as with optional confidentiality protection. If this is not possible (e.g., due to the lack of security association at point 1), the parameters exchanged at points 1-3 can be analyzed (e.g., examined) at point 4.

[0174] At point 4, after receiving multiple response messages, the target WTRU can select the located WTRU for SL positioning based on the capabilities of the located WTRU and other conditions (e.g., link quality). The target WTRU can perform connection establishment (e.g., it can perform PC5 connection establishment).

[0175] If the security of the connection (such as a PC5 connection) can be established during connection setup (e.g., PC5 setup), then the parameters exchanged in 1-3 can be verified. In one example, the parameters exchanged in 1-3 can be executed after the connection setup.

[0176] At point 5, both the target WTRU and the located WTRU can perform a SL positioning operation. The SL positioning operation may depend on the state of the target WTRU.

[0177] It can provide a process for discovering and selecting located WTRUs in Model A discovery.

[0178] For Model A discovery, the located WTRU can send an announcement message including its supported capabilities (e.g., enabling it to perform the requested process for SL positioning of a target WTRU that may not have a connection (e.g., may not have a NAS connection)). Based on the announced capabilities, the target WTRU can discover and select the located WTRU, which can be used to perform SL positioning based on the target WTRU's state, which may indicate whether the target WTRU has a connection (e.g., may have or may not have a NAS connection). The target WTRU and the selected located WTRU can establish a connection (e.g., a PC5 connection can be established), and SL positioning operations can be performed based on the target WTRU's state.

[0179] Figure 6 This is a flowchart illustrating an example process of discovering and selecting a located WTRU using discovery (e.g., it could be Model A discovery). At point 1, the located WTRU can send an announcement message indicating that it can support the SL location service and can indicate the type of WTRU it supports (e.g., it could be a located WTRU type). For example, when the target WTRU may not have connectivity (e.g., it may not have NAS connectivity), the located WTRU can indicate its ability to support SL location operations. In one example, the located WTRU can indicate the location methods it supports (e.g., RTT, TDOA, AoA, AoD) in the announcement message.

[0180] At point 2, when a target WTRU determines to perform SL positioning, it can discover and select an appropriate located WTRU based on multiple announcement messages received from the located WTRUs. The target WTRU can receive multiple announcement messages from the located WTRUs, and can select an appropriate located WTRU that can announce its SL positioning capabilities compatible with the requested capabilities, according to the target WTRU's status. The target WTRU's status may indicate that it may not have connectivity (e.g., it may not have NAS connectivity). The target WTRU can select an appropriate located WTRU based on one or more conditions, such as link quality.

[0181] At point 3, the target WTRU and the selected located WTRU can establish a connection, which can be a PC5 connection. Verification (e.g., notification) of parameters exchanged at point 1 can be performed at point 3 after point 3 or when connection security (e.g., PC5 connection security) is established.

[0182] At four locations, both the target WTRU and the located WTRU can perform SL positioning operations. The SL positioning operation may vary depending on the state of the target WTRU.

[0183] A list of qualified, pre-positioned WTRUs can be provided.

[0184] Core networks such as 5GC can provide a list of candidate located WTRUs for NW-assisted SL localization of a target WTRU via control plane NAS signaling (registration, WTRU configuration update command, WTRU parameter update, SoR, etc.).

[0185] The candidate list may include (for example, the capability of each) a located WTRU, enabling the located WTRU to perform the requested SL location operation using the target WTRU which does not have a NAS connection.

[0186] If the core network (e.g., 5GC) provides a list of capable candidate located WTRUs, the target WTRU can attempt to discover a located WTRU in the list that has the appropriate capabilities based on the target WTRU's state.

[0187] In one example, the list provided by the core network (e.g., 5GC) may include one or more sets of located WTRUs, where each set (e.g., each set) may be associated with a different positioning method. For example, a set of located WTRUs may include located WTRUs that support Round-Trip Time (RTT) positioning methods. In another example, a set of located WTRUs (e.g., another set of located WTRUs) may include located WTRUs that support Time Difference of Arrival (TDOA) positioning methods.

[0188] If a target WTRU attempts to discover a located WTRU in a list of capable WTRUs, it can perform either Model A or Model B discovery without indicating the target WTRU's status and the capabilities of the located WTRUs in the relevant message. The target WTRU can select the appropriate located WTRU from the discovered located WTRUs by referring to the capabilities of the located WTRUs found in the candidate list.

[0189] The process of selecting the SL positioning protocol to utilize the located WTRU can be considered in light of the target WTRU's state. While the target WTRU and the located WTRU are performing SL positioning, the target WTRU can share its state to select the appropriate SL positioning method and determine (e.g., each) the role of the WTRU in the SL positioning operation. For example, the target WTRU can indicate whether it has available connectivity (e.g., NAS connectivity). Based on the target WTRU's state and the determined SL positioning method, it can be determined (e.g., by the target WTRU) whether either the located WTRU or the target WTRU can collect the SL positioning results and report them to the network.

[0190] Figure 7 This is a flowchart illustrating an example process of the SL positioning protocol between a target WTRU and a located WTRU. At point 1, the target WTRU, the located WTRU, the SL reference WTRU, and the SL positioning server WTRU or LMF can communicate to negotiate SL positioning capabilities. During capability negotiation, the state of the target WTRU, which may not have network connectivity (e.g., NAS connectivity), and the requested capabilities of the located WTRU, are negotiated, along with the state of each target WTRU.

[0191] In one example, the state of the target WTRU can be shared separately via signaling and capability negotiation, or information about the target WTRU's state that was pre-configured or pre-acquired during discovery or connection establishment (e.g., PC5 connection establishment) can be reused. In this case, capability negotiation may not include the target WTRU's state.

[0192] In one example, capability negotiation between the target WTRU, the located WTRU, and one or more SL reference WTRUs can occur between the target WTRU, the located WTRU, and one or more SL reference WTRUs. At point 2, the capability for negotiation regarding SL positioning decisions can be notified to the SL positioning server WTRU and / or LMF.

[0193] In one example, the functionality of the SL location server WTRU can be co-located with the target WTRU, the located WTRU, or one or more SL reference WTRUs.

[0194] At point 2, for example, the SL positioning server WTRU or LMF can determine the SL positioning method based on negotiated capabilities (e.g., which may include the state of the target WTRU, the capabilities of the located WTRUs based on the state of the target WTRU, and one or more available SL reference WTRUs and their capabilities). Based on the determined SL positioning method, the roles of the target WTRU and the located WTRUs can be determined at point 2.

[0195] In one example, an SL positioning method can be determined between a target WTRU and a located WTRU, or between a target WTRU, a located WTRU, and one or more SL reference WTRUs. This determination can be based on negotiated capabilities, which may include the state of the target WTRU, the capabilities of the located WTRUs according to the state of the target WTRU, and / or one or more SL reference WTRUs and their capabilities.

[0196] At three locations, auxiliary data used for performing SL positioning can be shared. Auxiliary data may include the characteristics and format of transmitted signals, time slots, etc. Auxiliary data can be provided by the SL positioning server WTRU or LMF to the target WTRU, the positioned WTRU, and / or one or more involved SL reference WTRUs. This can be based on the determined SL positioning method.

[0197] In one example, auxiliary data can be shared among the target WTRU, the located WTRU, and one or more SL reference WTRUs involved. (Pre-)configuration information at the located WTRU, the target WTRU, and / or one or more SL reference WTRUs can be used as auxiliary data for performing SL localization.

[0198] In one example, the location method can be determined based on (for example, by) the number of located WTRUs that have already established a connection with the target WTRU.

[0199] At four locations, the located WTRU, the target WTRU, and one or more SL reference WTRUs can perform the determined SL positioning operation.

[0200] At point 5, the results of the SL localization operation can be collected from both the located WTRU and / or the target WTRU. Based on the SL localization method and the state of the target WTRU, it can be determined whether the results can be collected from the located WTRU or the target WTRU.

[0201] At point 6, the location report can include the results of the SL positioning operation, and information about the located WTRU can be reported to the LMF or SL positioning server WTRU. Based on the status of the target WTRU, it can be determined whether the located WTRU or the target WTRU can transmit a location report.

[0202] In one example, if the located WTRU might be unable to report the result of the SL location operation to the LMF, the target WTRU can receive a message from the located WTRU indicating that the report cannot be sent to the LMF. Based on this message, the target WTRU can send a request to the located WTRU at a configured period to send the report to the LMF, until the target WTRU receives a message from the located WTRU indicating that the report to the LMF was successfully transmitted.

[0203] It can provide processing of the updated target WTRU state during SL positioning operations.

[0204] Following capability negotiation, the state of the target WTRU and / or the located WTRU may change. For example, the target WTRU may have lost connectivity (e.g., NAS connection), the target WTRU may have regained connectivity (e.g., NAS connection), and the located WTRU may have lost connectivity (e.g., NAS connection). The target WTRU or the located WTRU can notify the other WTRU of the updated state, thereby determining whether the SL positioning operation can continue or restart.

[0205] When the state of the target WTRU changes after capability negotiation, taking into account resource allocation methods, synchronization methods, etc., the target WTRU or the located WTRU can decide whether to continue the current session of SL positioning operation, or whether to update the current SLPP session based on the state of the target WTRU.

[0206] If the target WTRU decides that the current session can continue regardless of changes in the target WTRU's state, the target WTRU may not share the updated target WTRU state with the already located WTRU until the session ends.

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

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

[0209] 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-ROMs and / or 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.

Claims

1. A first wireless transmit / receive unit (WTRU), comprising: The processor is configured as follows: Receive a solicitation message from the second WTRU, wherein the solicitation message indicates the status of the second WTRU and service information associated with the side link (SL) positioning service; Based on the status of the second WTRU and the service information, it is determined that the first WTRU is capable of providing the mobile terminal positioning service; and Based on the determination that the first WTRU is capable of providing the SL positioning service, a response message is sent to the second WTRU, wherein the response message indicates that the first WTRU is capable of providing the SL positioning service.

2. The first WTRU according to claim 1, wherein, The request message also indicates the connection status associated with the second WTRU, the positioning method, and the location associated with the second WTRU.

3. The first WTRU according to claim 1, wherein, The response message also indicates the ability of the first WTRU to perform SL positioning operations associated with the state of the second WTRU.

4. The first WTRU according to claim 1, wherein, The processor is also configured to: Receive a connection request message from the second WTRU to establish a connection; and Establish a connection with the second WTRU.

5. The first WTRU according to claim 4, wherein, The processor is also configured to: The SL positioning operation is performed using the connection of the second WTRU, where the SL positioning operation is based on the state of the second WTRU.

6. The first WTRU according to claim 5, wherein, The SL positioning operation is a synchronization method.

7. The first WTRU according to claim 4, wherein, The response message is not protected by integrity, and the response message is sent via the connection.

8. The first WTRU of claim 1, wherein the response message is protected by integrity and confidentiality.

9. The first WTRU according to claim 1, wherein, The status of the second WTRU indicates that the second WTRU has available non-access stratum (NAS) connectivity.

10. The first WTRU according to claim 1, wherein, The status of the second WTRU indicates that the second WTRU has no available non-access stratum (NAS) connection.

11. A first wireless transmit / receive unit (WTRU), the first WTRU comprising: The processor is configured as follows: Receive a notification message from the second WTRU, wherein the notification message indicates service information associated with the side link (SL) positioning service, the identity of the second WTRU, and the ability of the second WTRU to support the SL positioning service; Based on the state of the first WTRU and the capabilities of the second WTRU, it is determined that the second WTRU is configured to provide the SL positioning service to the first WTRU; Based on the determination that the second WTRU is configured to provide the SL positioning service, a connection is established to the second WTRU; and The connection is used to receive service messages from the second WTRU, wherein the service messages are associated with the SL location service.

12. The first WTRU according to claim 11, wherein, The status of the first WTRU indicates that the first WTRU has available non-access stratum (NAS) connectivity.

13. The first WTRU according to claim 11, wherein, The status of the first WTRU indicates that the first WTRU has no available non-access stratum (NAS) connection.

14. The first WTRU according to claim 11, wherein, The notification message is a first notification message, and the processor is further configured to: Receive the second notification message from the third WTRU.

15. The first WTRU according to claim 14, wherein, The determination that the second WTRU will provide the SL positioning service is also based on the second notification message.

16. The first WTRU according to claim 15, wherein, The determination that the second WTRU will provide the SL positioning service is also based on the link quality associated with the first WTRU.

17. The first WTRU according to claim 11, wherein, The processor is also configured to: Receive a candidate list indicating the capability of the second WTRU to support SL location services.

18. The first WTRU of claim 17, wherein the candidate list includes a first set of WTRUs associated with a first SL location service and a second set of WTRUs associated with a second SL location service, wherein the first set of WTRUs includes the second WTRU, and wherein the first SL location service is the SL location service.

19. The first WTRU of claim 11, wherein the SL positioning service is a round-trip time (RTT) positioning method.

20. The first WTRU of claim 11, wherein the SL positioning service is a Time Difference of Arrival (TDOA) positioning method.

Images