MÉTODOS E APARELHOS PARA DESCOBERTA E AUTORIZAÇÃO DE UNIDADE DE TRANSMISSÃO / RECEPÇÃO SEM FIO (WTRU) CLIENTE PARA POSICIONAMENTO DE ENLACE LATERAL

Abstract

This disclosure generally pertains to procedures, methods, architectures, apparatus, systems, devices, and computer program products for, and / or directed to the discovery and / or authorization of client Wireless Transmit / Receive Units (WTRUs) for sidelink positioning in a wireless network.

Description

1 / 66 “METHODS AND APPARATUS FOR DISCOVERY AND AUTHORIZATION OF WIRELESS TRANSMISSION / RECEPTION UNIT (WTRU) CLIENT FOR SIDE LINK POSITIONING” Cross-reference to related orders

[001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 457,661, filed April 6, 2023, which is incorporated herein by reference in its entirety. FIELD

[002] Examples of modalities described herein refer to procedures, methods, architectures, apparatus, systems, devices and computer program products for, and / or directed to, the discovery and authorization of Wireless Transmit / Receive Units (WTRUs) client for side link (SL) placement in a wireless network. SUMMARY

[003] In one embodiment, a WTRU may be a destination of a side link (SL) positioning request from a client WTRU for SL positioning. The WTRU (e.g., destination) may receive a request (e.g., a request message) from an SL Reference WTRU, including SL positioning WTRU information. In one example, the WTRU may transmit a message (e.g., an authorization check) to an SL Positioning Server WTRU or Location Management Function (LMF) seeking to determine whether the SL Positioning WTRU is authorized to receive positioning information about the WTRU (e.g., the destination WTRU). For example, the WTRU may receive a response from the SL Positioning Server WTRU or LMF indicating whether the client WTRU for SL positioning is authorized to receive positioning information from the WTRU (e.g., the destination WTRU).WTRU can determine if the Customer WTRU for SL Positioning is... Petition 870250084602, dated 09 / 19 / 2025, p. 8 / 99 2 / 66 authorized to receive positioning information from the destination WTRU (e.g., based on the response received). For example, when the Client WTRU for SL Positioning is authorized to receive positioning information from the WTRU (e.g., the destination WTRU), the WTRU may transmit a response to the request (e.g., the request form), including information associated with the SL Positioning WTRU and / or WTRU (e.g., the destination WTRU). For example, when the Client WTRU for SL Positioning is not authorized to receive positioning information from the WTRU (e.g., the destination WTRU), the WTRU may transmit a rejection response to the Request Form.

[004] In one embodiment, a method might involve a first WTRU sending, to a second WTRU, information associated with one or more reference WTRUs near the first WTRU. The method might involve receiving an SL positioning request from the second WTRU. For example, in some embodiments, the SL positioning request might indicate one or more of (1) information associated with the second WTRU, (2) information associated with the first WTRU, and / or (3) information associated with one or more reference WTRUs. The method might involve determining whether the second WTRU is authorized to receive positioning information associated with the first WTRU.Provided the second WTRU is authorized to receive the positioning information associated with the first WTRU, the method may include performing an SL positioning operation with at least one or more reference WTRUs and / or sending an SL positioning response indicating the positioning information to the second WTRU. If the second WTRU is not authorized to receive the positioning information associated with the first WTRU, the method may include sending a rejection response to the second WTRU. BRIEF DESCRIPTION OF THE DRAWINGS

[005] A more detailed understanding can be obtained from the description Petition 870250084602, dated 09 / 19 / 2025, p. 9 / 99 3 / 66 detailed below, given by way of example in conjunction with the attached drawings. Figures in such drawings, as well as the detailed description, are examples. Therefore, the Figures and the detailed description should not be considered limiting, and other equally effective examples are possible and probable. Furthermore, similar reference numbers (ref.) in the Figures indicate similar elements, wherein: Figure 1A is a system diagram illustrating an exemplary communications system in which one or more of the advertised modes can be implemented; Figure 1B is a system diagram illustrating an example of a wireless transmit / receive unit (WTRU) that can be used within the communications system illustrated in Figure 1A according to one mode; Figure 1C is a system diagram illustrating an example of a radio access network (RAN) and an example of a core network (CN) that can be used within the communications system illustrated in Figure 1A according to a modality; Figure 1D is a system diagram illustrating an additional exemplary RAN and an additional exemplary CN that can be used within the communications system illustrated in Figure 1A according to a modality; Figure 2 is a block diagram of a reference model for a 5G / NextGen network; Figure 3 is a block diagram showing a reference model of a 5G / NextGen network for location services; Figure 4 is a diagram illustrating the CP / UP positioning architecture in NR; Figure 5 is a signal flow diagram illustrating the signal flow for SL positioning by a client WTRU with Destination WTRU discovery according to some exemplary modalities; Petition 870250084602, dated 09 / 19 / 2025, page 10 / 99 4 / 66 Figure 6 is a signal flow diagram illustrating the signal flow for SL placement by a client WTRU with client authorization for SL placement during discovery according to some exemplary modalities; Figure 7 is a signal flow diagram illustrating the signal flow for SL positioning with WTRU client authorization for SL positioning during PC5 establishment according to some exemplary modalities; Figure 8 is a signal flow diagram that illustrates the signal flow for WTRU client authorization for SL positioning according to some exemplary modalities; Figure 9 is a flowchart illustrating an exemplary process for SL positioning, according to some examples; and Figure 10 is a flowchart illustrating an exemplary process for SL positioning, according to some exemplary embodiments. DETAILED DESCRIPTION

[006] In the detailed description that follows, numerous specific details are presented to provide a complete understanding of embodiments and / or examples disclosed herein. However, it should be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other cases, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the description that follows. Furthermore, embodiments and examples not specifically described herein may be practiced instead of, or in combination with, the embodiments and other examples described, disclosed, or otherwise explicitly, implicitly, and / or inherently provided (collectively provided) herein.

[007] Figure 1A is a diagram illustrating an exemplary communications system 100 in which one or more disclosed modalities can be implemented. The communications system 100 can be an access system. Petition 870250084602, dated 09 / 19 / 2025, page 11 / 99 A 5 / 66 multiple system that provides content, such as voice, data, video, message exchange, broadcast, etc., to multiple wireless users. A 100 communications system can enable multiple wireless users to access this content by sharing system resources, including wireless bandwidth. For example, 100 communications systems may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero-tail single-word DFT spread OFDM (ZT UW DTS-s OFDM), single-word OFDM (UWOFDM), resource block filtered OFDM, filter bank multicarrier (FBMC), and the like.

[008] As shown in Figure 1A, the communications system 100 may include wireless transmit and 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, although it is appreciated that the disclosed embodiments may encompass any number of WTRUs, base stations, networks and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment.By way of example, WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or “STA”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a mobile phone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, an Internet access point 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), an industrial device and applications (e.g., a robot and / or other wireless devices). Petition 870250084602, dated 09 / 19 / 2025, page 12 / 99 6 / 66 wire operating in industrial and / or automated processing chain contexts), a consumer electronic device, a device operating in commercial and / or industrial wireless networks and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be referred to alternatively as a UE.

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

[010] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be called a cell (not shown). These frequencies may be in the licensed spectrum, the unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service for a specific geographic area that may be relatively fixed or that may change over time. The cell may additionally be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Then, in one embodiment, the Petition 870250084602, dated 09 / 19 / 2025, p. 13 / 99 7 / 66 base station 114a can include three transceivers, one for each sector of the cell. In one embodiment, base station 114a can employ multiple-input multiple-output (MIMO) technology and can utilize multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in desired spatial directions.

[011] Base stations 114a, 114b can communicate with one or more WTRUs 102a, 102b, 102c, 102d along an 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).

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

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

[014] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement a radio technology, such as NR Radio Access, which Petition 870250084602, dated 09 / 19 / 2025, p. 14 / 99 8 / 66 can establish the 116 air interface using New Radio (NR).

[015] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, 102c can implement LTE radio access and NR radio access together, for example, using dual connectivity (DC) principles. Thus, the air interface used 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., an eNB and a gNB).

[016] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may 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 1X, 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 Rate for GSM Evolution (EDGE), GSM EDGE (GERAN) and the like.

[017] Base station 114b in Figure 1A can be a wireless router, Home Node B, or access point, for example, and can utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as a workplace, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a highway, and the like. In one embodiment, base station 114b and WTRUs 102c, 102d can implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d can implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In another configuration, base station 114b and WTRUs 102c, 102d can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). Petition 870250084602, dated 09 / 19 / 2025, page 15 / 99 9 / 66 to establish a picocell or femtocell. As shown in Figure 1A, base station 114b may have a direct connection to the Internet 110. Thus, base station 114b may not be required to access the Internet 110 via CN 106 / 115.

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

[019] CN 106 / 115 can also serve as a gateway for WTRUs 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include circuit-switched telephone networks that provide simple traditional telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. 112 networks may include communication networks Petition 870250084602, dated 09 / 19 / 2025, p. 16 / 99 10 / 66 wired and / or wireless networks owned and / or operated by other service providers. For example, 112 networks may include another NC connected to one or more RANs, which may employ the same RAT as RAN 104 / 113 or a different RAT.

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

[021] Figure 1B is a system diagram illustrating an exemplary WTRU 102. As shown in Figure 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit and receive element 122, a speaker / microphone 124, a keyboard 126, a touchscreen / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a global positioning system (GPS) chip set 136 and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any subcombination of the foregoing elements, remaining consistent with an embodiment.

[022] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application-Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. Processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other functionality that allows it to Petition 870250084602, dated 09 / 19 / 2025, page 17 / 99 11 / 66 a WTRU 102 operates in a wireless environment. Processor 118 can be coupled to transceiver 120, which can be coupled to transmitting and receiving element 122. While Figure 1B depicts processor 118 and transceiver 120 as separate components, it will be appreciated that processor 118 and transceiver 120 can be integrated together in a single electronic package or chip.

[023] The transmit / receive element 122 can be configured to transmit signals to, or receive signals from, a base station (e.g., base station 114a) via 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 another embodiment, the transmit / receive element 122 can be a transmitter / detector configured to transmit and / or receive infrared, ultraviolet, or visible light signals, for example. In another embodiment, the transmit / receive element 122 can be configured to transmit and / or receive 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.

[024] Although the transmit / receive element 122 is represented in Figure 1B as a single element, the WTRU 102 can include any number of transmit and receive elements 122. More specifically, the WTRU 102 can employ MIMO technology. Thus, in one embodiment, the WTRU 102 can include two or more transmit and receive elements 122 (e.g., multiple antennas) to transmit and receive wireless signals over the air interface 116.

[025] Transceiver 120 can be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, WTRU 102 can have multimode capabilities. Thus, transceiver 120 can include multiple transceivers to enable WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example. Petition 870250084602, dated 09 / 19 / 2025, p. 18 / 99 12 / 66

[026] The WTRU 102 processor 118 can be coupled to, and can receive input data from, the speaker / microphone 124, keyboard 126, and / or touch screen / pad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 can also send user data to the speaker / microphone 124, keyboard 126, and / or touch screen / pad 128. In addition, the processor 118 can access information and store data in any suitable type of memory, such as non-removable memory 130 and / or removable memory 132. 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. Removable memory 132 may include a Subscriber Identity Module (SIM) card, a memory card, a Secure Digital Memory Card (SD), and the like.In other configurations, processor 118 can access information and store data in memory that is not physically located in WTRU 102, such as in a server or a home computer (not shown).

[027] Processor 118 can receive power from power supply 134 and can be configured to distribute and / or control power to the other components in WTRU 102. Power supply 134 can be any device suitable for powering WTRU 102. For example, power supply 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.

[028] Processor 118 can also be coupled to the GPS chipset 136, which can be configured to provide location information (e.g., longitude and latitude) relative to the current location of WTRU 102. In addition to, or instead of, information from the GPS chipset 136, WTRU 102 can receive location information via air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on Petition 870250084602, dated 09 / 19 / 2025, page 19 / 99 13 / 66 time of signals received from two or more nearby base stations. It will be appreciated that WTRU 102 can acquire location information through any suitable location determination method, while remaining consistent with a modality.

[029] The processor 118 may additionally be coupled with other peripherals 138, which may include one or more software and / or hardware modules that provide additional attributes, functionality and / or wired or wireless connectivity. For example, peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photographs and / or video), a Universal Serial Bus (USB) port, a vibration device, a television transceiver, a handset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker and the like.Peripherals 138 may include one or more sensors, the sensors may be one or more of the following: gyroscope, accelerometer, Hall effect sensor, magnetometer, orientation sensor, proximity sensor, temperature sensor, time sensor; geolocation sensor; altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor and / or humidity sensor.

[030] The WTRU 102 may include a full duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for uplink (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 139 to substantially reduce and / or eliminate self-interference via hardware (e.g., an inductor) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). Petition 870250084602, dated 09 / 19 / 2025, p. 20 / 99 14 / 66 include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with particular subframes for the uplink (e.g., for transmission) or downlink (e.g., for reception)).

[031] Figure 1C is a system diagram illustrating RAN 104 and CN 106 according to one mode. As noted above, RAN 104 can employ E-UTRA radio technology to communicate with WTRUs 102a, 102b, 102c via air interface 116. RAN 104 can also be in communication with CN 106.

[032] RAN 104 may include eNode-Bs 160a, 160b, 160c, although it is possible that RAN 104 may include any number of eNode-Bs, remaining consistent with one embodiment. eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communication with WTRUs 102a, 102b, 102c via air interface 116. In one embodiment, eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from WTRU 102a.

[033] Each of the eNode-Bs 160a, 160b, 160c can be associated with a particular cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, uplink (UL) and / or downlink (DL) user scheduling, and the like. As shown in Figure 1C, the eNode-Bs 160a, 160b, 160c can communicate with each other via an X2 interface.

[034] The CN 106 shown in Figure 1C may include a mobility management entity (MME) 162, a service gateway (SGW) 164, and a packet data network gateway (PDN) (or PGW) 166. Although each of the above elements is described as part of CN 106, it is important to note that any of these elements may be owned and / or operated by an entity other than the CN operator.

[035] MME 162 can be connected to each of the eNode-Bs 162a, 162b, Petition 870250084602, dated 09 / 19 / 2025, page 21 / 99 15 / 66 MME 162c in RAN 104 via an S1 interface and can serve as a control node. For example, MME 162 can be responsible for authenticating users from WTRUs 102a, 102b, 102c, carrier activation / deactivation, selecting a particular service gateway during an initial connection from WTRUs 102a, 102b, 102c, and similar locations. MME 162 can provide a control plane function to switch between RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[036] SGW 164 can be connected to each of the eNodes B 160a, 160b, 160c in RAN 104 via the S1 interface. SGW 164 can generally route and forward user data packets to / from WTRUs 102a, 102b, 102c. SGW 164 can perform other functions such as anchoring user planes during handovers between eNodes B, triggering paging when DL data is available for WTRUs 102a, 102b, 102c, managing and storing contexts of WTRUs 102a, 102b, 102c and the like.

[037] SGW 164 can be connected to PGW 166, which can provide WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between WTRUs 102a, 102b, 102c and IP-enabled devices.

[038] CN 106 can facilitate communications with other networks. For example, CN 106 can provide WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as PSTN 108, to facilitate communications between WTRUs 102a, 102b, 102c and traditional fixed-line communication devices. For example, CN 106 can include, or communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between CN 106 and PSTN 108. In addition, CN 106 can provide WTRUs 102a, 102b, 102c with access to other 112 networks, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

[039] Although the WTRU is described in Figures 1A-1D as a terminal without Petition 870250084602, dated 09 / 19 / 2025, p. 22 / 99 16 / 66 wire, it is contemplated that in certain representative embodiments such a terminal may use (for example, temporarily or permanently) wired communication interfaces with the communication network.

[040] In representative modalities, the other 112 network may be a WLAN.

[041] A WLAN in Basic Services Infrastructure Set (BSS) mode can have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a Distribution System (DS) or other type of wired / wireless network that carries inbound and / or outbound traffic from the BSS. Traffic to STAs originating outside the BSS can arrive via the AP and be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS can be sent to the AP to be delivered to the respective destinations. Traffic between STAs within the BSS can be sent via the AP, for example, where the originating STA can send traffic to the AP and the AP can deliver the traffic to the destination STA. Traffic between STAs within a BSS can be considered and / or referred to as point-to-point traffic. Point-to-point traffic can be sent between (e.g., directly between) the source and destination STAs with a Direct Link Establishment (DLS).In certain representative configurations, DLS may use either 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to here as an “ad-hoc” communication mode.

[042] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit a beacon on a fixed channel, such as a primary channel. The primary channel can have a fixed width (e.g., 20 MHz bandwidth) or a width defined dynamically via signaling. The primary channel can be the BSS operating channel and can be used by STAs to establish a connection with the AP. In certain representative embodiments, the Petition 870250084602, dated 09 / 19 / 2025, p. 23 / 99 17 / 66 Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) can be implemented, for example, in 802.11 systems. For CSMA / CA, STAs (e.g., each STA), including APs, can sense the primary channel. If the channel is sensed and / or detected as occupied by a particular STA, that particular STA can back off. An STA (e.g., only one station) can transmit at any given time on a given BSS.

[043] High-throughput (HT) STAs can use a 40 MHz wide channel for communication, for example, via a combination of the 20 MHz primary channel with an adjacent or non-adjacent 20 MHz channel to form a 40 MHz wide channel.

[044] Very High Throughput (VHT) STAs can support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. 40 MHz and / or 80 MHz channels can be formed by combining contiguous 20 MHz channels. A 160 MHz channel can be formed by combining 8 contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, can be passed through a segment analyzer that can split the data into two continuous streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed on each continuous stream separately. Continuous streams can be mapped to the two 80 MHz channels, and the data can be transmitted by a STA transmitter.At the receiving STA, the operation described above for the 80+80 configuration can be reversed, and the combined data can be sent to the Medium Access Control (MAC).

[045] Operating modes below 1 GHz are supported by 802.11af and 802.11ah. The operating channel bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports bandwidths of 5 MHz, 10 MHz, and 20 MHz in the Space spectrum. Petition 870250084602, dated 09 / 19 / 2025, page 24 / 99 18 / 66 Television White Wire (TVWS), and 802.11ah supports bandwidths of 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support Meter Type Control / Machine Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities, including support for (e.g., support only for) certain and / or limited bandwidths. MTC devices may include a battery with a lifespan exceeding a certain limit (e.g., to maintain a very long battery life).

[046] WLAN systems, which can support multiple channels and channel bandwidths, such as 11n, 802.11ac, 802.11af, and 802.11ah, include a channel that can be designated as the primary channel. The primary channel can have a bandwidth equal to the highest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be defined and / or limited by an STA, among all STAs operating in a BSS, that supports the lowest bandwidth operating mode. In the 802.11ah example, the primary channel can have a 1 MHz bandwidth for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1 MHz mode, 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 detection and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel.If the primary channel is busy, for example, due to an STA (which only supports a 1 MHz operating mode) transmitting to the AP, all available frequency bands can be considered occupied, even if most frequency bands remain idle and could be available.

[047] In the United States, the available frequency bands that can be used by 802.11ah are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the bands of Petition 870250084602, dated 09 / 19 / 2025, p. 25 / 99 The available 19 / 66 frequencies are from 916.5 MHz to 927.5 MHz. The total available bandwidth for 802.11ah is from 6 MHz to 26 MHz, depending on the country code.

[048] Figure 1D is a system diagram illustrating RAN 113 and CN 115 according to a modality. As noted above, RAN 113 can employ NR radio technology to communicate with WTRUs 102a, 102b, 102c via air interface 116. RAN 113 can also be in communication with CN 115.

[049] RAN 113 may include gNBs 180a, 180b, 180c, although it is possible that RAN 113 may include any number of gNBs while remaining consistent with a mode. gNBs 180a, 180b, 180c may each include one or more transceivers for communication with WTRUs 102a, 102b, 102c via air interface 116. In a mode, gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may use beamforming to transmit signals and / or receive signals from gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, can use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, WTRU 102a. In one embodiment, the gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, the gNB 180a can transmit multiple component carriers to WTRU 102a (not shown).A subset of these component carriers may be in unlicensed spectrum, while the remaining component carriers may be in licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c may implement CoMP (Coordinated Multipoint) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[050] WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or the OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different Petition 870250084602, dated 09 / 19 / 2025, p. 26 / 99 20 / 66 portions of the wireless transmission spectrum. WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying lengths or scalable lengths (e.g., containing a variable number of OFDM symbols and / or lasting various absolute time lengths).

[051] gNBs 180a, 180b, 180c can be configured to communicate with WTRUs 102a, 102b, 102c in a standalone and / or non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c can use one or more gNBs 180a, 180b, 180c as a mobility docking point. In a standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in an unlicensed band. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate with / connect to gNBs 180a, 180b, and 180c, while also communicating with / connecting to another RAN, such as eNode-Bs 160a, 160b, and 160c.For example, WTRUs 102a, 102b, 102c can implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNodes 160a, 160b, 160c substantially simultaneously. In the non-autonomous configuration, eNodes 160a, 160b, 160c can serve as a mobility anchor for WTRUs 102a, 102b, 102c, and gNBs 180a, 180b, 180c can provide additional coverage and / or throughput to serve WTRUs 102a, 102b, 102c.

[052] Each of the gNBs 180a, 180b, 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, uplink user scheduling (UL) and / or (DL), network slicing support, dual connectivity, NR and E-UTRA interoperability, user plane data routing to Petition 870250084602, dated 09 / 19 / 2025, page 27 / 99 21 / 66 User Plane Function (UPF) 184a, 184b, routing information from the control plane to the Access and Mobility Management Function (AMF) 182a, 182b and similar. As shown in Figure 1D, gNBs 180a, 180b, 180c can communicate with each other via an Xn interface.

[053] The CN 115 shown in Figure 1D 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 above elements is described as part of the CN 115, it is important to note that any of these elements may be owned and / or operated by an entity other than the CN operator.

[054] The AMF 182a, 182b can be connected to one or more gNBs 180a, 180b, 180c in RAN 113 via an N2 interface and can serve as a control node. For example, the AMF 182a, 182b can be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, managing the log area, terminating NAS signaling, managing mobility, and the like. Network slicing can be used by AMF 182a, 182b to customize CN support for WTRUs 102a, 102b, 102c based on the types of services used by WTRUs 102a, 102b, 102c.For example, different network slices can be established for different use cases, such as services that rely on ultra-reliable low-latency access (URLLC), services that rely on enhanced massive mobile broadband (eMBB) access, services for machine-type communication (MTC) access, and / or similar services. AMF 182a, 182b can provide a control plane function to switch between RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[055] The SMF 183a, 183b can be connected to an AMF 182a, 182b on CN 115 via an N11 interface. The SMF 183a, 183b can also be connected to a Petition 870250084602, dated 09 / 19 / 2025, page 28 / 99 22 / 66 UPF 184a, 184b on CN 115 via an N4 interface. SMF 183a, 183b can select and control UPF 184a, 184b and configure traffic routing through UPF 184a, 184b. SMF 183a, 183b can perform other functions such as managing and allocating EU IP addresses, managing PDU sessions, controlling policy and QoS enforcement, providing downlink data notifications, and the like. A PDU session type can be IP-based, non-IP-based, Ethernet-based, and the like.

[056] UPF 184a, 184b can be connected to one or more gNBs 180a, 180b, 180c in RAN 113 via an N3 interface, which can provide WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between WTRUs 102a, 102b, 102c and IP-enabled devices. UPF 184, 184b can perform other functions such as packet routing and forwarding, user plane policy enforcement, support for multihomed PDU sessions, user plane QoS handling, downlink packet buffering, mobility tethering provision, and the like.

[057] CN 115 can facilitate communications with other networks. For example, CN 115 may include, or communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between CN 115 and PSTN 108. In addition, CN 115 may provide WTRUs 102a, 102b, 102c with access to other 112 networks, which may include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, 102c can be connected to a local Data Network (DN) 185a, 185b through UPF 184a, 184b via the N3 interface to UPF 184a, 184b and an N6 interface between UPF 184a, 184b and DN 185a, 185b.

[058] In view of Figures 1A-1D and the corresponding description of Figures 1A-1D, one or more, or all, of the functions described herein relate to one or more of the following: WTRU 102a-d, Base Station 114a-b, Node-B 160a-c, MME 162, SGW 164, Petition 870250084602, dated 09 / 19 / 2025, p. 29 / 99 23 / 66 PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, or any other devices described herein may be performed by one or more emulation devices (not shown). Emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, emulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[059] Emulation devices can be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more emulation devices may perform one or more, or all, of the functions while being wholly 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 emulation devices may perform one or more, or all, of the functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for testing purposes and / or may perform tests using wireless communications over the air.

[060] One or more emulation devices may perform one or more functions, including all, without being implemented / deployed as part of a wired and / or wireless communication network. For example, emulation devices may be used in a test scenario in a test laboratory and / or an undeployed wired and / or wireless communication network (e.g., test) to implement the testing of one or more components. One or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via an RF circuit array (e.g., which may include one or more antennas) may be used by emulation devices to transmit and / or receive data. Petition 870250084602, dated 09 / 19 / 2025, page 30 / 99 24 / 66

[061] Figure 2 is a reference model of a potential 5G or NextGen network architecture.

[062] RAN here refers to a radio access network based on 5G Radio Access Technology (RAT) or E-UTRA Evolved that connects to the NextGen core network.

[063] The Access Control and Mobility Management (AMF) function includes the following functionalities: registration management, connection management, accessibility management, mobility management, etc.

[064] The Session Management Function (SMF) includes the following functionalities: session management (including session establishment, modification and release), WTRU IP address allocation, User Plan (UP) function selection and control, etc.

[065] The user plane function (UPF) includes the following functionalities: packet routing and forwarding, packet inspection, traffic usage reports, etc.

[066] The 5G location service (LCS) offers the functionality of providing positioning information for a WTRU.

[067] The positioning of a WTRU can be supported by RAT-dependent position methods, which are based, for example, on 3 GPP RAT measurements obtained by a target WTRU and / or on measurements obtained by an Access Network of 3 GPP RAT signals transmitted by a target WTRU. The positioning of a WTRU can also be supported by RAT-independent position methods, which can be based on non-RAT measurements obtained by a WTRU and / or on other information.

[068] With reference to Figure 3, which is a block diagram showing a reference model of a 5G / NextGen network for location service, location information for one or multiple target WTRUs can be requested and reported to an LCS client or an Application Function (AF) within Petition 870250084602, dated 09 / 19 / 2025, page 31 / 99 25 / 66 or outside of a 3GPP carrier network, or a Network Function (NF) of the control plane within a 3GPP system.

[069] For a location request from an LCS client or an AF, the target WTRU privacy check must be enabled to verify whether it is permitted to acquire WTRU location information.

[070] 5G supports several different types of location requests, including: (1) Mobile-Terminated Location Request (MT-LR), where an LCS or AF client sends a location request to the 5G Network for the location of a target WTRU; (2) Mobile-Originated Location Request (MO-LR), where a WTRU sends a request to the 5G Network for location-related information for the WTRU; (3) Immediate Location Request, where an LCS or AF client sends or initiates a location request to a target WTRU(s) and expects to receive a response containing location information for the target WTRU(s) within a short period of time (can be used for an MT-LR or MO-LR);and (4) Deferred Location Request, where an LCS or AF client sends a location request to the 5G network for a target WTRU(s) and waits to receive a response when a specified event has occurred for the target WTRU at some future time (can be used for an MT-LR).

[071] (R)AN here represents NG-RAN, unreliable non-3GPP access or unreliable non-3GPP access. The access network is involved in handling various positioning procedures, including positioning a target WTRU, providing location-related information not associated with a specific target WTRU, and transferring positioning messages between an AMF or LMF (Location Management Function) and a target WTRU.

[072] AFs and NFs can access LCS services from a GMLC (Mobile Gateway Location Center) on the same 3GPP carrier network. Petition 870250084602, dated 09 / 19 / 2025, p. 32 / 99 26 / 66

[073] LCS customers can access LCS services from a GMLC and external AFs can access LCS service from a Network Exposure Function (NEF).

[074] The GMLC (Mobile Gateway Location Center) handles requests from external LCS clients and AFs via a NEF if the AF is an external AF and forwards location requests to the appropriate NF.

[075] The LRF (Location Recovery Function) is responsible for retrieving or validating location information and can be co-located with a GMLC or can be located separately.

[076] The LMF (Location Management Function) manages the overall coordination and scaling of resources required for locating a registered WTRU or accessing a 5G Core Network (CN). It can calculate or verify information related to the final location and accuracy achieved.

[077] RAN-based positioning protocols and positioning signals have been specified in 3GPP since LTE version 9 to enable emergency services and location-based services.

[078] In Rel-17, 3GPP NR positioning protocols are supported by the Control Plane (CP) positioning architecture on the Uu interface (NGRAN node to WTRU). The NR positioning architecture can also be supported by a Secure User Plane Location (SUPL) server, also known as a SUPL location platform (SLP) or location server, which can leverage any IP carrier. Interoperability for CP and UP positioning solutions is defined in TS 38.305, where SUPL can also be used as a tunnel for CP positioning protocols (e.g., LPP) [4]. This is shown in Figure 4, which illustrates the CP / UP NR positioning architecture.

[079] 3GPP defined several protocols to enable various positioning technologies and methods (GNSS (Global Navigation Satellite System), sensors, positioning signals, etc.). The primary protocol, LPP (LTE positioning protocol), is terminated between the WTRU and the LMF (management function). Petition 870250084602, dated 09 / 19 / 2025, page 33 / 99 27 / 66 location). LPP is a point-to-point LCS and NAS (Non-Access Stratum) messaging protocol defined in TS 37.355. It was agreed that LPP will be reused for NR since Rel-15 and will continue to be leveraged in the near future.

[080] RRC (Radio Resource Control) is another protocol used to provide transport for LPP messages and other positioning procedures via the NR-Uu interface, which is terminated between the gNB and the WTRU.

[081] On the network side, NGAP (NG Application Protocol) is terminated between the AMF and the NG-RAN node(s) (i.e., gNB / TRP) and is used as a transport for LPP and NRPPa messages over the NG-C (Next Generation Core Network) interface.

[082] Finally, the NRPPa (NR A Positioning Protocol) carries information between the NG-RAN node(s) and the LMF.

[083] Positioning can be performed in: Autonomous, WTRU-based or WTRU-assisted modes.

[084] In autonomous positioning, the WTRU handles all aspects of positioning, verifies accessible positioning sources, measures and processes positioning signals / sources. Finally, the WTRU calculates its own position in 2 or 3 dimensions. In autonomous positioning, the impacts of the Uu interface include the exchange of WTRU capabilities and the reporting of WTRU position.

[085] In WTRU-based positioning (WTRU-B), the network provides acquisition assistance data, and the WTRU searches for accessible positioning sources, measures and processes positioning signals / sources (based on assistance information from the network). Finally, the WTRU calculates its own position in 2 or 3 dimensions and can report its position to the network.

[086] In WTRU-assisted positioning (WTRU-A), the network provides acquisition assistance, and the WTRU scans accessible positioning sources and measures positioning signals / sources (based on assistance information from the network). Finally, the WTRU returns the measurements to the network, and the network calculates the device's position (on the location server / LMF). Petition 870250084602, dated 09 / 19 / 2025, page 34 / 99 28 / 66

[087] Table 1 below shows the techniques supported by the WTRU placement methods (defined in TS38.305) Table 1 EU-Based Method EU-Assisted, LMF Based DL-TDOA Yes Yes DL-AoD Yes Yes Multi-RTT No Yes NR E-CID No Yes UL-TDOA No No UL-AoA No No

[088] LTE Positioning Protocol (LPP) messages related to WTRU-assisted location request(s) include the following procedures: - Request capabilities; LMF request to WTRU - Providing Capabilities; WTRU's Response to LMF - Request Assistance Data; WTRU request to LMF for positioning assistance data / information. - Provide Assistance Data; LMF positioning assistance data information / configuration for WTRU (in addition, positioning assistance data (AD) transmission is supported by positioning system information blocks (posSIBs) and transmitted in SI messages [3][4]) - Request location information; LMF request for WTRU for position / measurements - Provide location information; WTRU for LMF, position and / or measurements. - Abort; Abort LPP session - Error; Errors associated with the positioning procedure(s)

[089] SL positioning (or SL-based positioning service) is defined as the positioning of a WTRU using PC5 to obtain absolute position, relative position, or range information. Range refers to Petition 870250084602, dated 09 / 19 / 2025, page 35 / 99 29 / 66 determination of the distance between two or more WTRUs and / or the direction of one WTRU (i.e., destination WTRU) from another WTRU (i.e., reference WTRU) via the PC5 interface.

[090] For SL placement, the following terms can be defined and used as follows.

[091] A destination WTRU is a WTRU whose distance, direction and / or position are measured with the support of one or multiple SL reference WTRUs using side link in the side link range and positioning-based service.

[092] A located WTRU is an SL Reference WTRU whose location is known or can be known using Uu-based positioning. A located WTRU can be used to determine the location of a target WTRU using side-link positioning.

[093] An SL Reference WTRU is a WTRU that supports the positioning of a destination WTRU, for example, by transmitting and / or receiving reference signals for positioning, providing positioning-related information, etc. using a side link.

[094] A client WTRU for SL placement is a third-party WTRU, different from an SL Reference WTRU and a destination WTRU that initiates a Side Reach / Link placement service request on behalf of an application residing on it.

[095] The Reach / Side Link positioning operation can be performed with network-assisted operation or WTRU-only operation.

[096] In network-assisted operation, NF(s) 5GC are involved in handling service requests and calculating results.

[097] In the WTRU-only operation, the service request handling and result calculation are performed by WTRU.

[098] When network-assisted operation is used, the LMF defined in Petition 870250084602, dated 09 / 19 / 2025, page 36 / 99 30 / 66 5G Location Service can be used to support SL positioning triggering, coordinate SL positioning operations, and deliver the result to the client. The Side Reach / Link positioning service request can be initiated by a WTRU (i.e., client WTRU for SL positioning, destination WTRU, SL Reference WTRU), a 5GC NF, an LCS client, or an AF.

[099] When the WTRU-only operation is used, the WTRUs interact with each other via PC5, as needed, to perform SL positioning operations. An SL positioning server WTRU is defined to coordinate the SL positioning operation and calculate the positioning result.

[0100] An SL Positioning Server WTRU is a WTRU that offers method determination, assistant data distribution and / or location calculation functionalities and / or location calculation functionalities for Side Link Positioning and Reach-based service.

[0101] Network-assisted SL positioning is used to estimate the location of a WTRU with network assistance using the location of one or more located WTRUs and the distance and / or direction between the WTRU and the located WTRU(s).

[0102] The network-assisted SL placement attribute has two cases, namely, when the WTRU can establish a NAS signaling connection and when the WTRU cannot establish a NAS signaling connection.

[0103] When a WTRU can establish a NAS connection, the WTRU enters the Connection Management (CM)-Connected state by executing a WTRU-triggered Service Request to 5GC-MO-LR or performing a Network-triggered Service Request to 5GC-NI (Network Induced)LR or 5GC-MT-LR. Because the target WTRU can establish a NAS signaling connection with the AMF, the functionality specified in the 5G Location Service can be reused, including, for example, 5GC-MO-LR, 5GC-MT-LR and 5GC-NI. (Reference to Opinion 870250084602, dated 09 / 19 / 2025, page 37 / 99) 31 / 66 NLLR.

[0104] The destination WTRU or LMF determines whether network-assisted SL placement will be applied.

[0105] The destination WTRU discovers localized WTRU(s) for network-assisted SL positioning.

[0106] The target WTRU and the located WTRU(s) performing range / SL positioning. The target WTRU includes the WTRU identity of the located WTRU(s) for the LMF, along with the range measurement data or estimate result. The LMF can interact with the GMLC to obtain the location of the located WTRU.

[0107] LMF uses the location of the located WTRU(s) along with the range / SL positioning measurement data or estimation results reported by the target WTRU and, optionally, also by the located WTRUs to estimate the location of the target WTRU.

[0108] When the destination WTRU fails to establish the NAS connection with the AMF due to the destination WTRU being out of coverage, for pending 5GC-M0-LR or 5GC-MT-LR (e.g., delayed 5GC-MT-LR), the following principles apply.

[0109] The target WTRU performs the discovery and selection of located WTRUs.

[0110] The destination WTRU can transmit its range measurements / results to the located WTRU(s).

[0111] Localized WTRU(s) can report the range / SL positioning measurement result to the LMF. This may include range measurements / results received from the destination WTRU. The endpoints for LPP messages are the LMF and the localized WTRU(s).

[0112] LMF can use the information received to calculate the location of the destination WTRU and provide the resulting location via the located WTRU. Petition 870250084602, dated 09 / 19 / 2025, page 38 / 99 32 / 66 to the destination WTRU or via 5G NF to the LCS client or Application Server.

[0113] A WTRU (for example, a WTRU client call for SL positioning) can request SL positioning via PC5 or via the network.

[0114] When a client WTRU for SL positioning requests SL positioning service via PC5 connection, it can discover one of the reference WTRUs and the destination WTRU, and can invoke the range / SL positioning service request to the discovered reference WTRU / destination WTRU to obtain the range and SL positioning result between the reference WTRU and the destination WTRU. This request includes the user information of the client's WTRU for SL positioning, the reference WTRU, and the destination WTRU.

[0115] For the exposure of the SL positioning service to the WTRU, when the client WTRU for SL positioning invokes the SL positioning service for the reference WTRU that is discovered by sending a range / SL positioning service request, there are at least three operational issues to be considered. First, methods and devices are desired for the client WTRU for SL positioning to acquire the information from the Reference SL WTRU in the vicinity of the destination WTRU.

[0116] Specifically, when the WTRU client for SL placement invokes the Reach / SL placement service request, it must include the user information of the WTRU client for SL placement, the reference WTRU, and the target WTRU. However, based on the deployment and placement of each WTRU, the WTRU client for SL placement can only directly discover the target WTRU or the reference WTRU. In this case, the WTRU client for SL placement cannot acquire information from a WTRU that is not directly discoverable, and the WTRU client for SL placement cannot guarantee whether there is any reference WTRU. Petition 870250084602, dated 09 / 19 / 2025, p. 39 / 99 33 / 66 SL available for SL positioning operation with destination WTRU.

[0117] Here the question is how the WTRU client for SL positioning can acquire the SL Reference WTRU information in the vicinity of a target WTRU.

[0118] Secondly, methods and equipment are desired for the client WTRU to be authorized for SL positioning of the destination WTRU.

[0119] In particular, the location information of the target WTRU is personal and confidential information. In the LCS 5GC service, an LCS client can be verified to determine if it is authorized to acquire location information from the target WTRU by querying the target WTRU subscription data in Unified Data Management (UDM). It should be possible to verify whether or not the client WTRU for SL positioning is authorized on the network to acquire location information from the target WTRU.

[0120] In addition, the destination WTRU must be able to verify the user information of the client WTRU for SL placement to assess whether the client WTRU for SL placement is authorized or not.

[0121] Here, the question is how the WTRU client for SL positioning can be authorized for SL positioning of the destination WTRU.

[0122] Third, for range operation, methods and equipment are desired for the client WTRU for SL positioning to ensure that range service is available when a WTRU is detectable by the client WTRU.

[0123] Specifically, the WTRU client for SL placement can request reach service between two WTRUs (WTRU1 and WTRU2). If the WTRU client can discover WTRU1 and WTRU2 directly, it can check if reach service is possible between WTRU1 and WTRU2. However, if only one WTRU (i.e., WTRU1 or WTRU2) can be discovered directly by the WTRU client, Petition 870250084602, dated 09 / 19 / 2025, p. 40 / 99 34 / 66 The WTRU client cannot guarantee that the other WTRU is close enough to the discovered WTRU for the reach service to be possible.

[0124] Here, the question is how the WTRU client for SL placement can determine whether the expected reach service is available or not, even when only one WTRU can be discovered by the WTRU client.

[0125] The examples of modes presented here assume that the WTRU supports PC5 signaling. This PC5 signaling may be supported by the ProSe layer in WTRUs.

[0126] WTRUs in some modes may have lateral link placement and reach capability. Here, lateral link placement refers to placement via the PC5 interface and reach refers to determining the distance between two or more WTRUs and / or the direction and / or position of one WTRU relative to another WTRU.

[0127] One embodiment may include procedure(s) for SL placement by client WTRU(s) with destination WTRU discovery. During a discovery procedure, when a client SL placement WTRU discovers a destination WTRU, the destination WTRU may inform the client SL placement WTRU about a nearby SL Reference WTRU so that the client SL placement WTRU can invoke an SL placement service request.

[0128] Based on the request and the client WTRU information that may be included therein, the destination WTRU may initiate a procedure to verify the client WTRU's authorization for SL placement.

[0129] Figure 5 is a signal flow diagram that illustrates the signal flow for SL placement by a client WTRU with destination WTRU discovery.

[0130] In step 1, the WTRU client for SL 501 positioning is triggered to discover the target WTRU 503 for the positioning service. Petition 870250084602, dated 09 / 19 / 2025, page 41 / 99 35 / 66 from SL and transmits a request message, including SL positioning service information and destination WTRU information.

[0131] In step 2, when the destination WTRU 503 receives the request message from the client WTRU, it can attempt to discover any nearby SL reference WTRU(s) by sending a request message.

[0132] In step 3, any nearby SL reference WTRU(s) to receive the message, such as SL Reference WTRU 505, can respond to the request message from the destination WTRU.

[0133] In step 4, when the destination WTRU 503 responds to the client WTRU 501, it may include information from the discovered SL reference WTRU(s). If multiple SL reference WTRU(s) responded in step 3, the destination WTRU may include information from multiple SL reference WTRUs. Alternatively, only one or multiple SL reference WTRUs may be selected to report to the client WTRU 501 based on some condition, such as link quality.

[0134] Alternatively, when the destination WTRU 503 already has information about the nearby SL reference WTRU(s) (at least there are already a sufficient number of reference WTRUs discovered by the destination WTRU), it can include the information in the reply message to the client WTRU without performing steps 2 and 3.

[0135] In step 5, client WTRU 501 can set up a PC5 connection with destination WTRU 503 after a successful discovery procedure.

[0136] Alternatively or additionally, the target WTRU 503 may provide information from the reference SL WTRU(s) to the client WTRU 501 during a PC5 connection setup or after the PC5 connection setup, for example, as incorporated in the PC5 connection setup signaling message or using a separate signaling message. Petition 870250084602, dated 09 / 19 / 2025, page 42 / 99 36 / 66

[0137] In step 6, Client WTRU 501 can invoke an SL positioning service request including destination WTRU information and reference SL WTRU(s) information that was received from destination WTRU 503.

[0138] In step 7, after receiving the SL positioning service request, destination WTRU 503 can communicate with the SL positioning server WTRU or 5GC 507 to assess whether the client WTRU for SL positioning is authorized to receive positioning information from destination WTRU 503. Destination WTRU 503 can include a list of reference SL WTRUs in the service request for authorization to the SL positioning server WTRU or 5GC 507.

[0139] Alternatively, the destination WTRU 503 can be configured with the list of client WTRU information that is authorized for destination WTRU positioning information, in which case step 7 can be omitted.

[0140] If the client WTRU for SL placement 501 is authorized to receive placement information from the destination WTRU 503, then in step 8, the destination WTRU 503 and the reference WTRU(s) SL 505 can perform the SL placement operation as requested by the client WTRU for SL placement 501. If, on the other hand, authorization fails (for example, in step 7), then instead, the destination WTRU 503 can reject the SL placement request received in step 6 (for example, as shown in step 8a). If the WTRU's response is rejected, it may include a rejection code indicating the reason for the rejection, for example, authorization failure.

[0141] In step 8, during the SL positioning operation, if more SL reference WTRU(s) need to be discovered, the target WTRU may perform more rounds of discovery and reporting phases (i.e., steps 2 to 3).

[0142] In step 8, the service request information, including Petition 870250084602, dated 09 / 19 / 2025, p. 43 / 99 37 / 66 Information from the reference WTRUs of SL can be reported to the WTRU of the SL or LMF positioning server for coordination of SL positioning operations.

[0143] Alternatively or additionally, the SL positioning service request may also be delivered to the SL 505 reference WTRU(s) in step 6 by the client WTRU 501 or the destination WTRU 503 and, if necessary, the destination WTRU 503 and the SL 505 reference WTRU(s) may establish PC5 connection(s) between themselves.

[0144] Alternatively, after receiving the request message in step 1, destination WTRU 503 can communicate with the SL or 5GC 507 positioning server WTRU to assess whether the client WTRU for SL positioning is authorized to receive positioning information from destination WTRU 503. If authorization from client WTRU 501 fails, destination WTRU 503 can instead reject the request message received in step 1. If destination WTRU 503 rejects the request message, it can include a rejection code in the response indicating the reason for the rejection, for example, authorization failure.

[0145] Alternatively, prior to step 2, the target WTRU 503 may receive or be configured with (from or by the SL positioning server WTRU or LMF 507a) a list of candidate SL reference WTRU(s). The target WTRU 503 may select one or more SL reference WTRU(s) that are discovered and belong to the list of candidate SL reference WTRU(s) for SL positioning operation and include information from these selected WTRU(s) in the response message in step 4.

[0146] One embodiment may include procedure(s) for SL placement with authorization from the SL placement client(s) WTRU(s) during discovery. In this embodiment, the SL placement client may attempt to discover the target WTRU or the reference SL WTRU(s) in the vicinity of Petition 870250084602, dated 09 / 19 / 2025, p. 44 / 99 38 / 66 Destination WTRU for the SL positioning service. The client WTRU for SL positioning can indicate that the SL reference WTRU(s) need to be discovered in the vicinity of the destination WTRU in the request message so that the appropriate SL reference WTRU(s) can participate in the discovery procedure.

[0147] Upon receiving the request message from the client WTRU, the SL reference WTRU(s) may attempt to discover the destination WTRU. In the discovery procedure between the SL Reference WTRU and the destination WTRU, the SL Reference WTRU may indicate that it is for the client WTRU's SL positioning service, including information from the client WTRU for SL positioning.

[0148] The destination WTRU can assess whether the client's WTRU for SL positioning is authorized for the destination WTRU's positioning information and, after successful authorization, the destination WTRU can respond to the SL Reference WTRU.

[0149] After the successful discovery procedure of SL reference WTRU(s) near the target WTRU, the client WTRU can set up a PC5 connection with the SL Reference WTRU and invoke an SL positioning service request for the discovered SL Reference WTRU.

[0150] After receiving a request for SL positioning service, the SL Reference WTRU can check if the client WTRU is authorized to receive positioning information from the destination WTRU and, if so, perform an SL positioning operation with the destination WTRU.

[0151] Figure 6 is a signal flow diagram that illustrates the signal flow for SL placement by a client WTRU with client authorization for SL placement during discovery according to this modality.

[0152] In stage 1, the WTRU client for SL 601 positioning is Petition 870250084602, dated 09 / 19 / 2025, p. 45 / 99 39 / 66 is triggered to discover the destination WTRU 603 for the SL positioning service and transmits a request message, including SL positioning service information and destination WTRU 605 information, for example, destination WTRU user information. Client WTRU 601 may include an indication that nearby SL reference WTRUs 603 to destination WTRU 605 may respond.

[0153] When a Reference SL WTRU 603 receives a request message from client WTRU 601 that includes an indication that nearby Reference SL WTRUs of the destination WTRU can respond, it checks if it is near destination WTRU 605. If no information is available regarding the proximity of destination WTRU 605, in step 2, it can try to find out destination WTRU 605 by sending a request message including destination WTRU information.

[0154] The Reference WTRU SL 603 may include information from the client WTRU for SL 601 positioning that was received in step 1.

[0155] In step 3, when destination WTRU 605 receives a discovery request message for itself, it can check if the discovery request message includes information from the client WTRU for SL positioning 601 and, if so, then it checks if the identified client WTRU for SL positioning is authorized to request positioning information from the destination WTRU by communicating with the SL positioning server WTRU or the 5GC network 607.

[0156] Alternatively, the destination WTRU 607 can be configured with a list of client WTRU information that is authorized to receive positioning information from the destination WTRU, in which case step 3 can be omitted.

[0157] In step 4, destination WTRU 607 can respond to the request message from the SL Reference WTRU (assuming that it Petition 870250084602, dated 09 / 19 / 2025, page 46 / 99 40 / 66 determines that the client WTRU for SL placement is authorized to receive placement information from the destination WTRU. If the client WTRU authorization fails in step 3, the destination WTRU 605 may reject the request message or simply ignore the request message received in step 1 (not shown). If the destination WTRU 503 rejects the request message, it may send a rejection response message in step 4 (not shown) and may include a rejection code indicating the reason for the rejection, for example, authorization failure.

[0158] Steps 2, 3 and 4 may be omitted if the SL 605 Reference WTRU is aware that the destination WTRU 605 is nearby and can communicate with the destination WTRU.

[0159] Alternatively, even if the Reference WTRU of SL 603 is aware that the destination WTRU 605 is nearby, for authorization from the client WTRU for SL 601 placement, the Reference WTRU of SL 603 may send a request message including information from the client WTRU for SL 601 placement.

[0160] In step 5, the reference WTRU(s) SL 603 respond(s) to the request message from client WTRU 601. It is assumed that each responding reference WTRU(s) SL is located near destination WTRU 607.

[0161] If the SL Reference WTRU 603 received a rejection response message in step 4, the SL Reference WTRU 603 can instead send a rejection response message in step 5 to the client WTRU for SL 601 placement or simply ignore the request message received in step 1 (not shown). If the SL Reference WTRU 603 responds with a rejection in step 5, it can include a rejection code indicating the reason for the rejection, for example, authorization failure. When the SL Reference WTRU 603 sends a rejection response message in step 5, the procedures fail and all steps from step 6 to step 10 can be omitted. Petition 870250084602, dated 09 / 19 / 2025, page 47 / 99 41 / 66

[0162] Alternatively, Reference WTRU SL 603 may indicate that it is close to Destination WTRU 605 in the response message (step 5).

[0163] In step 6, the Client WTRU 601 can select a suitable Reference WTRU SL 603 and configure the PC5 connection with the selected Reference WTRU SL 603.

[0164] Alternatively, after receiving the response message in step 5 or after step 6, the client WTRU for SL 601 placement may request that the Reference WTRU SL 603 report whether the target WTRU 605 was discovered by the Reference WTRU SL 603. If requested by the client WTRU for SL 601 Placement, the Reference WTRU SL 603 may perform a discovery procedure (e.g., step 2 and step 3) and may report the result of whether the target WTRU 605 was discovered to the client WTRU for SL 601 Placement.

[0165] Alternatively, during the PC5 connection setup in step 6 or after the PC5 connection setup, the SL 603 Reference WTRU can perform a discovery procedure (e.g., step 2 and step 3) and can report whether the target WTRU 605 is near the client's WTRU 601 for SL positioning.

[0166] Alternatively, if Client WTRU 601 is aware that Reference WTRU SL 603 is not near Destination WTRU 605, Client WTRU 601 can repeat the procedure from step 1 until it discovers Destination WTRU 605 or a Reference WTRU SL 603 near Destination WTRU 605.

[0167] In step 7, WTRU Client 601 can send an SL positioning service request to the selected SL reference WTRU 603. The SL positioning service request can include client WTRU information for SL positioning, destination WTRU information, and / or SL reference WTRU(s) information for the SL positioning service.

[0168] In step 8, when the SL positioning service request Petition 870250084602, dated 09 / 19 / 2025, p. 48 / 99 42 / 66 is received, the Reference WTRU SL 603 can communicate with the SL or 5GC LMF 607 positioning server WTRU to assess whether the client WTRU for SL positioning 601 is authorized to receive positioning information from the destination WTRU 605.

[0169] Step 8 can be performed before or after step 9.

[0170] If authorization is successful, then in step 9, the SL Reference WTRU 603 and the Destination WTRU 605 set up a PC5 connection to the SL positioning service.

[0171] On the other hand, if authorization fails in step 8, then instead, the SL Reference WTRU 603 sends a rejection response message (not shown) to the client WTRU for SL 601 placement (or may simply not respond to the request message received in step 1), and the remaining steps are omitted. If the SL Reference WTRU 603 responds with a rejection, it may include a rejection code indicating the reason for the rejection, for example, authorization failure.

[0172] Assuming authorization was successful, then in step 10, destination WTRU 605 and reference WTRU(s) SL 603 perform the SL positioning operation as requested by the client WTRU for SL 601 positioning.

[0173] In step 10, destination WTRU 605 and / or reference WTRU(s) SL 603 can communicate with the SL positioning server WTRU or LMF 607 for coordination of the SL positioning operation.

[0174] If multiple SL reference WTRUs are included in the SL positioning service request in step 7, this fact will be reported to the SL positioning server WTRU or LMF 607 for coordination of the SL positioning operation.

[0175] Alternatively or additionally, if multiple SL reference WTRUs are included in the SL positioning service request in step 7, the Petition 870250084602, dated 09 / 19 / 2025, page 49 / 99 43 / 66 request can be delivered to each SL Reference WTRU included in the request by client WTRU 601 or by SL Reference WTRU 603 selected in step 6 and, if necessary, the destination WTRU and the SL reference WTRU(s) can establish PC5 connections.

[0176] Alternatively or additionally, if multiple SL reference WTRUs are included in the service request in step 7, SL Reference WTRU 603 can forward the SL positioning service request to destination WTRU 605 and the destination WTRU and the SL reference WTRU(s) can establish PC5 connections.

[0177] One embodiment may include SL positioning procedure(s) with authorization from the client WTRU for SL positioning during PC5 configuration. The client for SL positioning may attempt to discover the target WTRU or the SL reference WTRU(s) in the vicinity of the target WTRU for the SL positioning service. The client WTRU for SL positioning may indicate that the SL reference WTRU(s) need(s) to be discovered near the target WTRU in the request message so that the appropriate SL reference WTRU(s) can participate in the discovery procedure.

[0178] Upon receiving the request message from the client WTRU, the reference SL WTRU(s) may attempt to discover the destination WTRU.

[0179] After successfully discovering one or more SL reference WTRU(s) near the target WTRU, the client WTRU can set up a PC5 connection with the SL Reference WTRU and invoke an SL positioning service request to the discovered SL Reference WTRU.

[0180] The SL Reference WTRU can set up a PC5 connection for the SL positioning service as requested by the client WTRU, and the SL Reference WTRU can inform the destination WTRU of the client WTRU information during the PC5 connection setup procedure.

[0181] The destination WTRU can verify if the client WTRU is authorized. Petition 870250084602, dated 09 / 19 / 2025, p. 50 / 99 44 / 66 to receive the positioning information from the destination WTRU and configure the PC5 connection with the SL Reference WTRU for the SL positioning service.

[0182] Figure 7 is a signal flow diagram that illustrates the signal flow for SL positioning with WTRU client authorization for SL positioning during PC5 configuration according to some modes.

[0183] In step 1, the WTRU client for SL positioning 701 is triggered to discover a target WTRU for the SL positioning service. The WTRU client 701 sends a request message including SL positioning service information and target WTRU information. The WTRU client 701 may include an indication that a nearby SL Reference WTRU may respond.

[0184] In step 2, when an SL Reference WTRU 703 receives the request message from client WTRU 701 which includes the indication that SL Reference WTRUs near destination WTRU 705 can respond, it checks if it is near destination WTRU 705. If no information is available regarding the proximity of the destination WTRU, it can try to find out by sending a request message including destination WTRU information.

[0185] In step 3, destination WTRU 705 can respond to the request message from the SL Reference WTRU.

[0186] Step 2 and Step 3 may be omitted if the SL Reference WTRU 703 is aware that the destination WTRU 705 is nearby and can communicate with the destination WTRU.

[0187] In step 4, the SL reference WTRU(s) 703 respond(s) to the request message from client WTRU 701. It is assumed that each responding SL Reference WTRU is near destination WTRU 705.

[0188] Alternatively, the Reference WTRU SL 703 may indicate that you are Petition 870250084602, dated 09 / 19 / 2025, p. 51 / 99 45 / 66 next to destination WTRU 705 in the reply message.

[0189] In step 5, Client WTRU 701 can select a suitable SL Reference WTRU and configure a PC5 connection with the selected SL Reference WTRU 703.

[0190] Alternatively, after receiving the response message in step 4 or after step 5, the client WTRU for SL 701 placement may request that the Reference WTRU SL 703 report whether the target WTRU 705 was discovered by the Reference WTRU SL 703. If requested by the client WTRU for SL 701 Placement, the Reference WTRU SL 703 may perform a discovery procedure (e.g., step 2 and step 3) with the Target WTRU 705 and may report the result of whether the target WTRU 705 was discovered to the client WTRU for SL 701 Placement.

[0191] Alternatively, during the PC5 connection setup in step 5 or after the PC5 connection setup, the SL 703 Reference WTRU can perform a discovery procedure (e.g., step 2 and step 3) with the target WTRU 705 and can report the result of whether the target WTRU 705 was discovered to the client WTRU for SL 701 placement.

[0192] Alternatively, if Client WTRU 701 is aware that Reference WTRU SL 703 is not near Destination WTRU 705, Client WTRU 701 can repeat the procedure from step 1 until it discovers Destination WTRU 705 or a Reference WTRU SL 703 near Destination WTRU 705.

[0193] In step 6, Client WTRU 701 can send an SL positioning service request to the selected SL reference WTRU 703. The SL positioning service request includes client WTRU information for SL positioning, destination WTRU information, and SL reference WTRU(s) information for the SL positioning service.

[0194] In step 7, after receiving the SL positioning service request, the SL 703 Reference WTRU can communicate with the Petition 870250084602, dated 09 / 19 / 2025, p. 52 / 99 46 / 66 WTRU from SL positioning server or 5GC 707 to assess whether the client WTRU for SL positioning is authorized to receive positioning information from the destination WTRU.

[0195] If authorization from client WTRU 701 fails in step 7, SL Reference WTRU 703 may reject the SL placement request (not shown) as described above in connection with Figures 5 and 6 (see, for example, alternative step 8a in Figure 5), and the remaining steps may be omitted.

[0196] On the other hand, if authorization of client WTRU 701 is successful, then in step 8, Reference WTRU SL 703 and destination WTRU 705 configure a PC5 connection for the SL positioning service. When configuring the PC5 connection, Reference WTRU SL 703 can inform destination WTRU 705 about client WTRU positioning information for SL 701 so that destination WTRU 705 is aware that client WTRU 701 is a consumer of positioning information from destination WTRU 705.

[0197] In step 9, destination WTRU 705 can communicate with SL or 5GC positioning server WTRU 707 to assess whether client WTRU for SL positioning 701 is authorized to receive positioning information from destination WTRU 705.

[0198] Alternatively, the target WTRU 705 can be configured with a list of client WTRU information that is authorized to receive positioning information from the target WTRU 705.

[0199] If authorization from client WTRU 701 fails in step 9, destination WTRU 705 rejects the PC5 connection configuration request from Reference WTRU SL in step 10, and the remaining steps are omitted. Alternatively, it can simply ignore the PC5 connection configuration request (and the remaining steps shown in Figure 7 are omitted).

[0200] On the other hand, the WTRU client's authorization for positioning of Petition 870250084602, dated 09 / 19 / 2025, page 53 / 99 47 / 66 SL 701 is successful in step 9, so in step 10, destination WTRU 705 and reference WTRU(s) SL 703 perform the SL positioning operation as requested by the client WTRU for positioning SL 701.

[0201] Assuming authorization is successful, in step 10, destination WTRU 705 and / or reference WTRU(s) SL 703 can communicate with SL positioning server WTRU or LMF 707 for coordination of SL positioning operation.

[0202] If multiple reference WTRUs SL 703 are included in the SL positioning service request in step 7, this will be reported to the SL positioning server WTRU or LMF 707 for coordination of the SL positioning operation.

[0203] Alternatively or additionally, if multiple SL 703 reference WTRUs are included in the SL positioning service request in step 6, the request can be delivered to each SL Reference WTRU included in the request by the client WTRU or the SL Reference WTRU selected in step 5 and, if necessary, the destination WTRU and the SL reference WTRU(s) can establish PC5 connections with each other.

[0204] Alternatively or additionally, if multiple SL Reference WTRUs are included in the service request in step 7, the SL Reference WTRU can forward the SL positioning service request to the destination WTRU, and the destination WTRU and the SL Reference WTRU(s) can establish PC5 connections with each other.

[0205] A modality can be directed to a procedure for reaching with authorization from the WTRU client for SL positioning. Figure 8 is a signal flow diagram that illustrates the signal flow for reaching with authorization from the WTRU client for SL positioning according to the modalities.

[0206] In step 1, the WTRU client for SL 801 positioning is triggered to discover WTRUs (here, WTRU1 803 and WTRU2 805) to vary between Petition 870250084602, dated 09 / 19 / 2025, p. 54 / 99 48 / 66 as the two WTRUs. Client WTRU 801 sends a request message including SL positioning service information and details to WTRU1 and WTRU2. The request may include a request to check proximity between the two WTRUs.

[0207] In step 2, when WTRU1 803 and / or WTRU2 805 receive the request message from client WTRU 801, they can respond to the client WTRU. If the request includes a request to check the proximity between the two WTRUs, a WTRU that received the request (here, WTRU1, for example) can check if the other WTRU 805 is nearby, for example, by performing a discovery procedure.

[0208] Alternatively, even if a request to check proximity between the two WTRUs is not included in the request message, the WTRU may attempt to discover the other WTRU included in the request message.

[0209] In step 3, the WTRU (here, WTRU 1 803) that received the request from client WTRU 801 sends a reply message. WTRU 803 may include in its reply an indication of whether or not the other WTRU is nearby.

[0210] In step 4, WTRU Client 801 can set up a PC5 connection with the responding WTRU (here, WTRU1 803) after a successful discovery procedure. If, on the other hand, WTRU Client 801 receives an indication that the other WTRU 805 is not nearby or WTRU 803 in step 3, WTRU Client 801 can repeat the discovery procedure until it receives an indication that both WTRUs are nearby.

[0211] In step 5, the WTRU client 801 can invoke an SL positioning service request for reach, including user information from WTRU1 803, user information from WTRU2 805, and information (e.g., user information) from the WTRU client 801.

[0212] In step 6, when a positioning service request Petition 870250084602, dated 09 / 19 / 2025, page 55 / 99 49 / 66 Once SL is received, the WTRU (here, WTRU1 803) can communicate with the SL positioning server WTRU or 5GC 807 to assess whether the client WTRU for SL positioning 801 is authorized to receive range and / or positioning information from WTRU 803. WTRU1 803 can include user information from the other WTRU (here, WTRU2 805) in the service request for authorization for the SL positioning server WTRU or 5GC 807.

[0213] Alternatively, the WTRU (here, WTRU1 803) can be configured with a list of WTRU information from clients that are authorized to receive range and / or positioning information from WTRU 803.

[0214] If the UE client authorization fails in step 6, WTRU1 rejects the SL placement request from WTRU client 801 (e.g., in step 8) and the remaining steps in Figure 8 (including step 7) are not executed. The SL placement response message in step 8 may include a rejection code indicating that the authorization failed and may also include an indication of the reason.

[0215] If the WTRU client authorization for SL positioning is successful, then in step 7, before performing the reach operations, the WTRU (here, WTRU1 803) can perform the discovery of the other WTRU (here, WTRU2 805) and a PC5 connection setup procedure with the other WTRU (here, WTRU2 805).

[0216] In step 8, when the other WTRU (here, WTRU2 805) is not discovered or the WTRU (here, WTRU1 803) cannot establish a PC5 connection with the other WTRU (here, WTRU2 805), WTRU 803 can report to client WTRU 801 by sending an SL positioning rejection reply message. The SL positioning rejection can include a rejection code, such as the other WTRU not reachable.

[0217] If, on the other hand, a PC5 connection is successfully established with the other WTRU 805 in step 7, then instead of performing step 8, the Petition 870250084602, dated 09 / 19 / 2025, page 56 / 99 50 / 66 steps 9 and 10 are performed. Specifically, in step 9, after a successful PC5 connection setup between the two WTRUs (WTRU1 803 and WTRU2 805), a range operation between the two WTRUs can be performed.

[0218] In step 10, after the reach operation, the WTRU (here, WTRU1 801) can report the reach result to the WTRU 801 client.

[0219] In step 9, the service request information, including WTRU1 and WTRU2 information, can be reported to the SL or LMF 807 positioning server WTRU for coordination of the SL positioning operation, and the reach operation between the two WTRUs can be coordinated by the SL or LMF 807 positioning server WTRU.

[0220] Alternatively or additionally, the SL positioning service request received in step 5 may also be delivered to the other WTRU (here, WTRU2) by the WTRU (here, WTRU1 803).

[0221] Figure 9 is a flowchart that illustrates an example 900 process for SL placement by a client WTRU with client authorization for SL placement, according to some modalities, as seen from the perspective of the destination WTRU.

[0222] It should be noted that, prior to process 900 shown in Figure 9, a client WTRU for SL positioning may have issued a Request to a Reference SL WTRU including SL positioning service indication and Destination WTRU information (as illustrated in step 1 of Figure 6) and, in response, the Reference SL WTRU transmits a Request to the Destination WTRU.

[0223] Thus, in step 901, the destination WTRU receives a request message from a Reference SL WTRU. This message includes SL WTRU positioning information.

[0224] In step 903, the destination WTRU transmits a check of Petition 870250084602, dated 09 / 19 / 2025, p. 57 / 99 51 / 66 authorization for the network's SL positioning server WTRU or its LMF seeking to determine if the SL positioning WTRU is authorized by the network to receive positioning information about the destination WTRU.

[0225] In step 905, the destination WTRU receives a response from the SL or LMF positioning server WTRU.

[0226] In step 907, the destination WTRU analyzes the response from the SL or LMF positioning server WTRU to determine if the client WTRU for SL positioning is authorized to receive positioning information from the destination WTRU.

[0227] If authorization was successful in step 907, the flow proceeds to step 911, in which the destination WTRU transmits a response to the request, including SL positioning information from the WTRU and the destination WTRU.

[0228] If, on the other hand, authorization has not been successful in step 907, the flow proceeds to step 913, in which the destination WTRU transmits a rejection response to the request and, optionally, a rejection code indicating the reason for the rejection.

[0229] In one embodiment, the destination WTRU transmits the Authorisation Verification to the SL or LMF Positioning server WTRU in response to receiving the Request Request before transmitting a response to the Request Request.

[0230] In one embodiment, if the destination WTRU determines that the client WTRU for SL positioning is authorized to receive positioning information from the destination WTRU, it transmits a response message to the SL Reference WTRU in response to the request message.

[0231] In one embodiment, if the destination WTRU determines that the SL positioning WTRU is authorized to receive its positioning information, it will likely soon receive a request for Petition 870250084602, dated 09 / 19 / 2025, p. 58 / 99 52 / 66 WTRU Reference PC5 connection configuration from SL and will configure a PC5 connection with the WTRU Reference from SL.

[0232] In one embodiment, once the PC5 connection is established, the destination WTRU performs an SL positioning operation as requested by the client's WTRU for SL positioning with the Reference SL WTRU.

[0233] In another mode, the destination WTRU transmits a response to the request before transmitting the authorization check to the SL or LMF positioning server WTRU.

[0234] In one embodiment, after transmitting the response message to the SL Reference WTRU, the destination WTRU receives a PC5 connection configuration request from the SL Reference WTRU, and in which the destination WTRU transmits the authorization request message after receiving the PC5 connection configuration request.

[0235] In one embodiment, if the client WTRU for SL positioning is authorized to receive positioning information from the destination WTRU, the destination WTRU establishes a PC5 connection with the SL Reference WTRU and performs an SL positioning operation as requested by the client WTRU for SL positioning with the SL Reference WTRU.

[0236] Figure 10 illustrates an example flow diagram of a 1000 method, which can be implemented in a first wireless transmit / receive unit (WTRU). For example, in some embodiments, the method may include one or more of the steps performed by or associated with the SL Reference WTRU, Destination WTRU, WTRU1, and / or WTRU2, as discussed elsewhere in this document, as described or illustrated with reference to Figures 5-8. For example, the first WTRU implementing the 1000 method may be or include a Destination WTRU. It should also be understood that one or more steps of the method may be optional, may be omitted, and / or may be performed in a specific order. Petition 870250084602, dated 09 / 19 / 2025, p. 59 / 99 53 / 66 different.

[0237] In one embodiment, as illustrated in the example in Figure 10, method 1000 may include, in 1002, receiving information associated with SL positioning from a second WTRU (for example, a client WTRU for SL positioning). For example, the information associated with SL positioning may include one or more of the following: an indication of the SL positioning service and information associated with the first WTRU. However, note that in certain embodiments, the receipt of information associated with SL positioning, as shown in 1002, may be omitted.

[0238] In one embodiment, method 1000 may include, in 1004, sending to the second WTRU information associated with one or more reference WTRUs close to the first WTRU. In one embodiment, method 1000 may include, in 1006, receiving an SL positioning request from the second WTRU. For example, in some embodiments, the SL positioning request may indicate one or more of: (1) information associated with the second WTRU, (2) information associated with the first WTRU, and / or (3) information associated with one or more reference WTRUs.

[0239] In one embodiment, method 1000 may include, in 1008, determining whether the second WTRU is authorized to receive positioning information associated with the first WTRU. Provided the second WTRU is authorized to receive the positioning information associated with the first WTRU, method 1000 may include, in 1010, performing an SL positioning operation with at least one or more reference WTRUs and / or, in 1012, sending an SL positioning response indicating the positioning information to the second WTRU. On the condition that the second WTRU is not authorized to receive the positioning information associated with the first WTRU, method 1000 may include, in 1014, sending a rejection response to the second WTRU. In some embodiments, the rejection response may include a rejection code. Petition 870250084602, dated 09 / 19 / 2025, p. 60 / 99 54 / 66 indicating that the SL placement request was rejected due to an authorization failure.

[0240] In one embodiment, the determination of whether the second WTRU is authorized to receive the positioning information associated with the first WTRU, in 1008, may include one or more of the following: sending a request to a network element to determine whether the second WTRU is authorized to receive the positioning information associated with the first WTRU and / or receiving a response or indication indicating whether the second WTRU is authorized. For example, the network element may be or be included in any SL positioning server and / or 5GC node.

[0241] In one embodiment, determining whether the second WTRU is authorized to receive the positioning information associated with the first WTRU, in 1008, may include sending a message to at least one other WTRU (e.g., a third WTRU) to determine whether the second WTRU is authorized to receive the positioning information (e.g., as shown in step 8 of Figure 7, or steps 901 and 903 of Figure 9 discussed above). For example, the message may include at least the information associated with the second WTRU.

[0242] In some exemplary embodiments, method 1000 may include establishing a PC5 connection with the second WTRU and receiving the SL positioning request via the PC5 connection.

[0243] In some exemplary embodiments, method 1000 may include one or more of the following: sending an SL positioning request to at least one of the one or more reference WTRUs and / or establishing a PC5 connection with at least one of the one or more reference WTRUs. In one embodiment, the message that is sent to determine whether the second WTRU is authorized to receive the positioning information may be sent to at least one of the one or more reference WTRUs via the PC5 connection.

[0244] Note that the flow diagrams illustrated in Figures 9 and 10 are Petition 870250084602, dated 09 / 19 / 2025, p. 61 / 99 55 / 66 are provided as examples, and modifications to them are contemplated according to certain modalities. For example, one or more of the steps illustrated in Figures 9 and 10 may be omitted, combined and / or performed in a different order.

[0245] Although attributes and elements are provided above in particular combinations, one skilled in the art will appreciate that each attribute or element can be used alone or in any combination with the other attributes and elements. The present disclosure should not be limited in terms of the particular embodiments described in this application, which are intended to illustrate various aspects. Many modifications and variations can be made without departing from its spirit and scope, as will be evident to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods and apparatus within the scope of the disclosure, in addition to those enumerated herein, will be evident to those skilled in the art from the preceding descriptions. Such modifications and variations are intended to fall within the scope of the appended claims.This disclosure shall be limited only to the terms of the appended claims, together with the full scope of equivalents to which such claims are entitled. It should be understood that this disclosure is not limited to particular methods or systems.

[0246] The aforementioned modalities are discussed, for simplicity, with regard to the terminology and structure of devices with infrared capability, i.e., infrared emitters and receivers. However, the modalities discussed are not limited to these systems, but can be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves, such as acoustic waves.

[0247] It should also be understood that the terminology used in this document is for the purpose of describing particular modalities only and not Petition 870250084602, dated 09 / 19 / 2025, p. 62 / 99 Sections 56 / 66 are intended to be limiting. As used herein, the term video or the term images may mean any of a snapshot, single image and / or multiple images displayed over time. As another example, when referred to herein, the terms user equipment and its abbreviation UE, the term remote and / or the terms head-mounted display or its abbreviation HMD may mean or include (i) a wireless transmitting and / or receiving unit (WTRU); (ii) any series of embodiments of a WTRU; (iii) a wireless-enabled and / or wired (e.g., pluggable) device configured with, inter alia, some or all of the features and functionalities of a WTRU; (iv) a wireless-enabled and / or wired device configured with less than all of the features and functionalities of a WTRU; or (v) the like.Details of an example of WTRU, which may be representative of any WTRU cited herein, are provided herein with respect to Figures 1A-1D. As another example, several embodiments disclosed herein above and below are described as utilizing a head-mounted display. Those skilled in the art will recognize that a device other than the head-mounted display may be used, and some or all of the disclosures and several embodiments disclosed may be suitably modified without undue experimentation. Examples of other devices may include a drone or other device configured to stream information to provide the adapted reality experience.

[0248] In addition, the methods provided herein can be implemented in a computer program, software, or firmware embedded in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), a register, cache memory, semiconductor memory devices, media Petition 870250084602, dated 09 / 19 / 2025, pp. 63 / 99 57 / 66 magnetic media, such as internal hard drives and removable disks, magneto-optical media, and optical media, such as CD-ROMs and digital versatile discs (DVDs). A processor in conjunction with software can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, MME, EPC, AMF, or any host computer.

[0249] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the embodiments illustrated are only examples and should not be considered as limiting the scope of the claims below. For example, the embodiments provided herein include portable devices, which may include or be used with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0250] In addition, in the modalities provided above, processing platforms, computing systems, controllers, and other devices that include processors are observed. These devices may include at least one Central Processing Unit (CPU) and memory. According to the practices of people versed in the technique of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by various CPUs and memories. Such acts, operations, or instructions may be referred to as executed, computer-executed, or CPU-executed.

[0251] Someone versed in the art will realize that the acts and operations or instructions symbolically represented include the manipulation of electrical signals by the CPU. An electrical system represents bits of data that can cause a resulting transformation or reduction of the electrical signals and the maintenance of bits of data in memory locations in a memory system to thus reconfigure or alter the operation of the CPU, as well as other processing. Petition 870250084602, dated 09 / 19 / 2025, pp. 64 / 99 58 / 66 signals. The memory locations where the data bits are kept are physical locations that have specific electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the methods are not limited to the platforms or CPUs mentioned above and that other platforms and CPUs may support the methods provided.

[0252] Data bits may also be held on a computer-readable medium, including magnetic disks, optical disks, and any other volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read-only memory (ROM)) mass storage system readable by the CPU. Computer-readable media may include cooperative or interconnected computer-readable media, which exist exclusively within the processing system or are distributed among multiple interconnected processing systems that may be local to or remote from the processing system. It should be understood that the modalities are not limited to the aforementioned memories and that other platforms and memories may support the methods provided.

[0253] In an illustrative embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor in a mobile unit, a network element, and / or any other computing device.

[0254] There is little distinction between hardware and software implementations of system aspects. The use of hardware or software is generally (but not always, since in certain contexts the choice between hardware and software may become significant) a design choice that represents trade-offs between cost and efficiency. There may be several vehicles by which processes and / or systems and / or other technologies described herein may be affected (e.g., hardware, software, and / or firmware), and the preferred vehicle may vary according to the context. Petition 870250084602, dated 09 / 19 / 2025, pp. 65 / 99 59 / 66 in which processes and / or systems and / or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a primarily hardware and / or firmware vehicle. If flexibility is paramount, the implementer may opt for a primarily software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and / or firmware.

[0255] The preceding detailed description has presented various embodiments of the devices and / or processes via the use of block diagrams, flowcharts, and / or examples. To the extent that such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, it will be understood by those within the art that each function and / or operation within such block diagrams, flowcharts, or examples can be implemented, individually and / or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, various portions of the subject matter described herein can be implemented via Application-Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats.However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be implemented equivalently in integrated circuits, as one or more computer programs running on one or more computers (for example, as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (for example, as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and / or writing the code for the software and / or firmware would be within the ability of one skilled in the art in light of this disclosure. Furthermore, those skilled in the art will understand that the mechanisms of the matter described herein can be distributed as a program product. Petition 870250084602, dated 09 / 19 / 2025, pp. 66 / 99 60 / 66 a variety of forms, and that an illustrative embodiment of the matter described herein applies regardless of the particular type of signal carrier medium used to actually accomplish the distribution. Examples of a signal carrier medium include, but are not limited to, the following: a recordable type medium, such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium, such as a digital and / or analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communication link, a wireless communication link, etc.).

[0256] Those skilled in the art will recognize that it is common in the field to describe devices and / or processes in the manner set forth herein and subsequently use engineering practices to integrate such devices and / or processes described into data processing systems. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system via a reasonable amount of experimentation.Those skilled in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, memory, such as volatile and non-volatile memory, processors, such as microprocessors and digital signal processors, computational entities, such as operating systems, drivers, graphical user interfaces and application programs, one or more interaction devices, such as a touchpad or screen, and / or control systems, including feedback loops and control motors (e.g., feedback to sensor-detect position and / or speed, control motors to move and / or adjust components and / or quantities).A typical data processing system can be implemented using any suitable commercially available components, such as those typically found in data computing / communication systems and / or network computing / communication systems.

[0257] The material described here sometimes illustrates different components Petition 870250084602, dated 09 / 19 / 2025, pp. 67 / 99 61 / 66 included or connected with other components. It is important to understand that the architectures represented are merely examples and that, in fact, many other architectures can be implemented to achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively associated so that the desired functionality can be achieved. Therefore, any two components combined here to achieve a particular functionality can be seen as associated with each other, so that the desired functionality is achieved, regardless of the architectures or intermediate components.Similarly, any two components thus associated can also be seen as being operationally connected or operationally coupled to each other to achieve the desired functionality, and any two components capable of being thus associated can also be seen as being operationally coupleable to each other to achieve the desired functionality. Specific examples of operationally coupleable components include, but are not limited to, physically coupleable and / or physically interactive components and / or wireless components that can interact wirelessly and / or interacting wirelessly and / or logically interacting components and / or components that can interact logically.

[0258] With regard to the use of substantially any plural and / or singular terms herein, those skilled in the art may translate from plural to singular and / or from singular to plural, as appropriate to the context and / or application. The various singular / plural permutations may be expressly presented herein for the sake of clarity.

[0259] It will be understood by those skilled in the art that, in general, the terms used herein, and especially in the appended claims (e.g., bodies of the appended claims), are generally conceived as “open” terms (e.g., the term “including” should be interpreted as “including, but not including”). Petition 870250084602, dated 09 / 19 / 2025, pp. 68 / 99 62 / 66 limiting to”, the term “having” should be interpreted as “having at least”, the term “includes” should be interpreted as “includes, but is not limited to”, etc.) and / or “permissive” terms (for example, the term “is” and / or the term “are” can be interpreted as “can” and / or “could”, the terms “refer” can be interpreted as “can refer” and / or “can refer”, the terms “receive” can be interpreted as “can receive” and / or “can receive”, the term “support” can be interpreted as “can support” and / or “can support”, the terms “interface(s)” can be interpreted as can interact and / or can interact, the terms “transmit” can be interpreted as can interact and / or can interact, can transmit and / or can transmit, the terms “send” can be interpreted as can send and / or can send, the terms “does not refer” (and / or similar) can to be interpreted as may not refer and / or may not refer,The terms "does not receive" (and / or similar) can be interpreted as "may not receive" and / or "may not receive," the terms "does not support" (and / or similar) can be interpreted as "may not support" and / or "may not support," the terms "does not interface" (and / or similar) can be interpreted as "may not interface" and / or "may not interface," the terms "does not transmit" (and / or similar) can be interpreted as "may not transmit" and / or "may not transmit," the terms "does not send" (and / or similar) can be interpreted as "they may not send" and / or "you may not send," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such intention will be explicitly recited in the claim, and in the absence of such recitation, such intention will not be present. For example, when you want only one item, you can use the term "single" or similar language. As an aid to understanding,The claims attached below and / or the descriptions contained herein may include the use of at least one and one or more introductory phrases to introduce recitations of claims. However, the use of such phrases should not be interpreted as implying that the introduction of a recitation of, Petition 870250084602, dated 09 / 19 / 2025, p. 69 / 99 63 / 66 The claim by the indefinite articles "a" or "an" limits any specific claim, including such an introduced claim recitation, to modalities that include only one of these recitations, even when the same claim includes the introductory sentences "a or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles used to introduce recitations of claims. Furthermore, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted as meaning "at least the number recited" (e.g., the mere recitation of two recitations, without other modifiers, means "at least two recitations," or "two or more recitations").Furthermore, in cases where a convention analogous to at least one of A, B, and C, etc. is used, in general, such a construction is intended in the sense that someone versed in the art would understand the convention (for example, a system having at least one of A, B, and C would include, but not be limited to, systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.).It will be further understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood as encompassing the possibilities of including one of the terms, either of the terms, or both terms. For example, the sentence A or B will be understood as including the possibilities of A or B or A and B. Furthermore, the terms "any of" followed by a listing of "one" are also understood. Petition 870250084602, dated 09 / 19 / 2025, pp. 70 / 99 64 / 66 plurality of items and / or a plurality of item categories, as used herein, is intended to include any one of, any combination of, any multiple of, and / or any combination of multiples of the items and / or item categories, individually or in conjunction with other items and / or other item categories. Furthermore, as used herein, the term set is intended to include any number of items, including zero. Additionally, as used herein, the term number is intended to include any number, including zero. And the term multiple, as used herein, is intended to be synonymous with a plurality.

[0260] Furthermore, when attributes or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure will also be described in terms of any individual member or subgroup of members of the Markush group.

[0261] As will be understood by one skilled in the art, for all and any purposes, such as in terms of providing a written description, all the ranges disclosed herein also encompass all possible subranges and combinations of subranges thereof. Any listed range can be readily recognized as sufficiently descriptive and allowing the same range to be divided into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein can be easily divided into a lower third, a middle third, and an upper third, etc. As will also be understood by one skilled in the art, all language such as up to, at least, greater than, less than, and the like includes the recited number and refers to ranges that can be subsequently divided into subranges, as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual limb.Thus, for example, a group with 1-3 cells refers to groups with 1, 2, or 3 cells. Similarly, a group with 1 to 5 cells refers to groups with 1, 2, 3, 4, or 5 cells, and so on.

[0262] Furthermore, the claims should not be interpreted as Petition 870250084602, dated 09 / 19 / 2025, p. 71 / 99 65 / 66 limited to the order or elements provided, unless stated otherwise. Furthermore, the use of the terms "means to" in any claim is intended to invoke 35 USC §112, ^ 6 or the "means plus function" claim format, and any claim without the terms "means to" is not intended to do so.

[0263] Suitable processors include, by way of example, 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), Application-Specific Standard Products (ASSPs); Field-Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), and / or a state machine.

[0264] The WTRU can be used in conjunction with modules, implemented in hardware and / or software, including a Software Defined Radio (SDR) and other components, such as a camera, a video camera module, a videophone, a hands-free device, a vibration device, a loudspeaker, a microphone, a television transceiver, a hands-free headset, a keyboard, a Bluetooth® module, a frequency modulated (FM) radio unit, a Near Field Communication (NFC) module, a liquid crystal display (LCD) unit, an organic light-emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an internet browser and / or any Wireless Local Area Network (WLAN) or Ultra Wideband (UWB) module.

[0265] Although the various embodiments have been described in terms of communication systems, it is anticipated that the systems may be implemented in software on microprocessors / general-purpose computers (not shown). In certain embodiments, one or more functions of the various components may be implemented in software that controls a general-purpose computer. Petition 870250084602, dated 09 / 19 / 2025, p. 72 / 99 66 / 66

[0266] Furthermore, although the invention is illustrated and described herein with reference to specific embodiments, the invention is not intended to be limited to the details shown. Instead, various modifications may be made to the details within the scope and range of equivalents of the claims and without departing from the invention. References [1] TS 23.501 V18. 1.0: System architecture for the 5G (5GS) system [2] TS 23.502 vl8. 1.0: Procedures for the 5G (5GS) System [3] TS 23.273 vl8.1.0: 5G system(5GS) Location Services (LCS); Stage 2 [4] TS 38.305 vl7.4.0: NGRadio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN [5] TS 37.355 vl7.4.0: LTE Positioning Protocol (LPP) [6] TS 23.304 vl8.1.0: Proximity based Services(ProSe) in the 5G System(5GS) [7] TS 23.586 v0.2.0: Architectural Enhancements to support Ranging based services and Sidelink Positioning [8] TR 23.700-86 vl 8.0.0: Study on Architecture Enhancement to support Ranging based services and sidelink positioning Petição 870250084602, de 19 / 09 / 2025, pág. 73 / 99

Claims

1 / 5 CLAIMS 1. First wireless transmit / receive unit (WTRU), CHARACTERIZED in that it comprises: a set of circuits including any one of a processor, memory, transmitter and receiver, the set of circuits configured to receive, from a second WTRU, information associated with side link (SL) positioning; send, to the second WTRU, information associated with one or more reference WTRUs near the first WTRU; receive an SL positioning request, the SL positioning request indicating (1) information associated with the second WTRU, wherein the information associated with the second WTRU indicates that the second WTRU is a client WTRU requesting to receive positioning information, (2) information associated with the first WTRU and (3) information associated with one or more reference WTRUs;Based on the information associated with the second WTRU, determine whether the second WTRU is authorized to receive positioning information associated with the first WTRU; if the second WTRU is authorized to receive the positioning information associated with the first WTRU, perform an SL positioning operation with at least one of the one or more reference WTRUs; and send an SL positioning response indicating the positioning information to the second WTRU.

2. WTRU, according to claim 1, CHARACTERIZED in that, on the condition that the second WTRU is not authorized to receive the positioning information associated with the first WTRU, the circuit set is configured to send a rejection response to the second WTRU. Petition 870250084602, dated 09 / 19 / 2025, pp. 95 / 99 2 / 5 3. WTRU, according to claim 2, CHARACTERIZED in that the rejection response comprises a rejection code indicating that the SL placement request was rejected due to an authorization failure.

4. A WTRU, according to claim 1, CHARACTERIZED in that, to determine whether the second WTRU is authorized to receive the positioning information associated with the first WTRU, the first WTRU is configured to: send a request to a network element to determine whether the second WTRU is authorized to receive the positioning information associated with the first WTRU; and receive a response indicating whether the second WTRU is authorized.

5. WTRU, according to claim 4, CHARACTERIZED in that the network element comprises either an SL positioning server and a 5GC node.

6. WTRU, according to claim 1, CHARACTERIZED in that the first WTRU is configured to determine that the second WTRU is authorized to receive the positioning information associated with the first WTRU, based on a configured list of client WTRUs.

7. WTRU, according to claim 1, CHARACTERIZED in that the information associated with the SL positioning comprises any one of: an SL positioning service indication and information associated with the first WTRU.

8. WTRU, according to claim 1, CHARACTERIZED in that the circuit assembly is configured to: establish a PC5 connection with the second WTRU; and receive the SL positioning request through the PC5 connection.

9. WTRU, according to claim 1, CHARACTERIZED in that the circuit set is configured to: Petition 870250084602, dated 09 / 19 / 2025, p. 96 / 99 3 / 5 send an SL placement request to at least one of the one or more reference WTRUs.

10. WTRU, according to claim 1, CHARACTERIZED in that the circuit assembly is configured to: receive the SL positioning request from the second WTRU or from any one or more reference WTRUs.

11. WTRU, according to claim 1, CHARACTERIZED in that the first WTRU comprises a destination WTRU and the second WTRU comprises a client WTRU for SL placement.

12. Method implemented by a first wireless transmit / receive unit (WTRU), the method CHARACTERIZED in that it comprises: receiving, from a second WTRU, information associated with side link (SL) positioning; sending, to the second WTRU, information associated with one or more reference WTRUs near the first WTRU; receiving an SL positioning request, the SL positioning request indicating (1) information associated with the second WTRU, wherein the information associated with the second WTRU indicates that the second WTRU is a client WTRU requesting to receive positioning information, (2) information associated with the first WTRU and (3) information associated with one or more reference WTRUs; determining, based on the information associated with the second WTRU, whether the second WTRU is authorized to receive positioning information associated with the first WTRU;on the condition that the second WTRU is authorized to receive the positioning information associated with the first WTRU, perform an SL positioning operation with at least one of the one or more reference WTRUs; and Petition 870250084602, dated 09 / 19 / 2025, p. 97 / 99 4 / 5 send an SL positioning response indicating the positioning information to the second WTRU.; 13. Method according to claim 12, CHARACTERIZED in that, provided that the second WTRU is not authorized to receive the positioning information associated with the first WTRU, the method comprises sending a rejection response to the second WTRU.

14. Method, according to claim 13, CHARACTERIZED in that the rejection response comprises a rejection code indicating that the SL placement request was rejected due to an authorization failure.

15. Method according to claim 12, CHARACTERIZED in that determining whether the second WTRU is authorized to receive the positioning information associated with the first WTRU comprises: sending a request to a network element to determine whether the second WTRU is authorized to receive the positioning information associated with the first WTRU; and receiving a response indicating whether the second WTRU is authorized.

16. Method according to claim 15, CHARACTERIZED in that the network element comprises either an SL positioning server and a 5GC node.

17. Method, according to claim 12, CHARACTERIZED in that the determination of whether the second WTRU is authorized to receive the positioning information associated with the first WTRU, comprises determining whether the second WTRU is authorized to receive the positioning information associated with the first WTRU, based on a configured list of client WTRUs.

18. Method, according to claim 12, CHARACTERIZED in that the information associated with the SL positioning comprises any of: an SL positioning service indication and information associated with the first WTRU.

19. Method, according to claim 12, CHARACTERIZED in that it comprises: establishing a PC5 connection with the second WTRU; and receiving the SL positioning request through the PC5 connection.

20. Method, according to claim 12, CHARACTERIZED in that it comprises: sending an SL placement request to at least one of one or more reference WTRUs.

21. Method, according to claim 12, CHARACTERIZED in that receiving an SL positioning request comprises receiving an SL positioning request from the second WTRU or from any one or more reference WTRUs.

22. Method, according to claim 12, CHARACTERIZED in that the first WTRU comprises a destination WTRU and the second WTRU comprises a client WTRU for SL placement. Petition 870250084602, dated 09 / 19 / 2025, pp. 99 / 99

Images