Method for Positioning Delegation

Abstract

A wireless transmit-receive unit (WTRU) may be configured to perform one or more actions. The WTRU may receive positioning configuration information. The positioning configuration information may include an indication of one or more positioning delegation candidates for the WTRU and an indication of one or more conditions for starting or stopping positioning delegation. The WTRU may detect that a condition for starting positioning delegation is met for at least one of the positioning delegation candidates. The WTRU may send an indication to the network device that the WTRU is using the at least one positioning delegation candidate that meets the condition. The WTRU may detect that a condition for stopping positioning delegation is met for the at least one positioning delegation candidate. The WTRU may send an indication to the network device that the WTRU has stopped using the at least one positioning delegation candidate for positioning.

Description

Technical Field

[0001] Cross - Reference to Related Applications This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 257,413, filed Oct. 19, 2021, and U.S. Provisional Patent Application No. 63 / 407,363, filed Sep. 16, 2022, the entireties of which are incorporated herein by reference.

Background Art

[0002] Mobile communications using wireless communication are continuously evolving. The fifth generation of mobile communication radio access technology (RAT) can be referred to as the new radio (NR) of 5G. Previous (conventional) generations of mobile communication RAT can be, for example, the fourth - generation (4G) long - term evolution (LTE). A wireless communication device can establish communication with other devices and data networks via an access network such as a radio access network (RAN).

Summary of the Invention

[0003] Systems, methods, and means for location delegation are disclosed herein. A wireless transmit-receive unit (WTRU) can be configured using information regarding a location delegate that can obtain information regarding its own location. The WTRU can be configured using conditions for when to start using the location delegate and conditions for when to stop using the location delegate. The WTRU can determine the availability of the location delegate and, in response to the conditions for starting the use of the location delegate being satisfied, start using the location delegate to obtain its own location. The WTRU can stop using the location delegate to obtain its own location in response to determining that the location delegate is no longer available or that the conditions for using the location delegate are no longer satisfied. The WTRU can stop or minimize positioning-related operations while using the location delegate service. The WTRU can resume normal positioning-related operations when it stops using the location delegate service. The WTRU can notify the network of when it starts and stops using the location delegate service.

[0004] The WTRU can be configured to apply a selection mechanism when there are multiple location delegation candidates. The selection mechanism can be based on any combination of WTRU positioning requirements, the positioning capabilities of the delegate, current WTRU conditions, and / or the signal level between the WTRU and the delegate. In some examples, the WTRU can be configured to apply one or more offsets to measurements related to the location delegate cell.

[0005] The WTRU can receive positioning configuration information. The positioning configuration information can include an indication of one or more positioning delegation candidates for the WTRU and / or an indication of one or more conditions for enabling (e.g., starting) and / or disabling (e.g., stopping) the positioning delegation.

[0006] The WTRU may detect that conditions for enabling (e.g., starting) positioning delegation are satisfied for at least one of the positioning delegation candidates. The WTRU may send an indication (e.g., a start indication) to the network (e.g., an integrated access and backhaul node (IAB node)) that the WTRU is using at least one positioning delegation candidate for positioning. The WTRU may send the indication based on detecting that conditions for enabling positioning delegation are satisfied for the positioning delegation candidate. The WTRU may detect that conditions for disabling positioning delegation are satisfied for the positioning delegation candidate.

[0007] The WTRU may send an indication (e.g., a stop indication) to the network that the WTRU has stopped using the positioning delegation candidate for positioning. The WTRU may stop using the positioning delegate based on detecting that conditions for disabling positioning delegation are satisfied for the positioning delegation candidate.

[0008] The WTRU may be configured to send a message to the network requesting to perform positioning delegation.

[0009] The conditions for enabling positioning delegation may include detecting that the WTRU battery level is below a threshold, connecting to the positioning delegation candidate, and / or that the WTRU is within a proximity specified for the positioning delegation candidate.

[0010] The conditions for enabling the use of positioning delegation may include detecting that the WTRU is within a proximity specified for the positioning delegation candidate based on a signal strength measurement received from the positioning delegation candidate.

[0011] The WTRU may be configured to perform measurements of one or more positioning reference signals (PRS) transmissions and / or report PRS measurements. The configuration may be based on detecting that a condition for invalidating positioning delegation is satisfied for a positioning delegation candidate.

[0012] An indication transmitted by the WTRU that the WTRU is using a positioning delegation candidate for positioning may include location information about the positioning delegation candidate.

[0013] The WTRU may be configured to receive a positioning request from the network. An indication transmitted by the WTRU that the WTRU is using at least one positioning delegation candidate for positioning may be transmitted to the network in response to the positioning request.

[0014] The WTRU may be configured to transmit a location parallax report to the network, where the location parallax report indicates the difference between the location of the WTRU and the location of the positioning delegate.

[0015] The WTRU may be configured to transmit a location parallax report to the network based on the difference exceeding a parallax threshold over a predetermined time period.

[0016] The WTRU may be configured to perform positioning measurements for a specified duration after connecting to the positioning delegate. The WTRU may compare the location information it has determined with the location information provided by the positioning delegate.

[0017] The method performed by the WTRU may include receiving positioning configuration information. The positioning configuration information includes an indication of one or more positioning delegation candidates for the WTRU and an indication of one or more conditions for enabling or disabling positioning delegation.

[0018] The method may include detecting that conditions for enabling positioning delegation are satisfied for at least one of the positioning delegation candidates. The method may include sending an indication to the network that the WTRU is using at least one positioning delegation candidate for positioning. The selection may be based on detecting that conditions for enabling positioning delegation are satisfied for at least one positioning delegation candidate. The method may include detecting that conditions for disabling positioning delegation are satisfied for at least one positioning delegation candidate. The method may include sending an indication to the network that the WTRU has stopped using at least one positioning delegation candidate for positioning, based on detecting that conditions for disabling positioning delegation are satisfied for at least one positioning delegation candidate.

[0019] The method may include sending a message to the network requesting to perform positioning delegation.

[0020] The conditions for enabling positioning delegation may include one or more of detecting that the WTRU battery level is below a threshold, connecting to at least one positioning delegation candidate, and / or detecting that the WTRU is within a proximity specified for at least one positioning delegation candidate.

[0021] The conditions for enabling positioning delegation may include detecting that the WTRU is within a proximity specified for at least one positioning delegation candidate, based on signal strength measurements received from at least one positioning delegation candidate.

[0022] The method may include performing measurements of one or more PRS transmissions and / or reporting PRS measurement values based on detecting that conditions for invalidating positioning delegation are met for at least one positioning delegation candidate.

[0023] An indication, transmitted by a WTRU, that the WTRU is using at least one positioning delegation candidate for positioning includes location information indicating the location of the at least one positioning delegation candidate.

[0024] The WTRU may be configured to receive a positioning request from the network. An indication, transmitted by the WTRU, that the WTRU is using at least one positioning delegation candidate for positioning may be transmitted to the network in response to the positioning request.

[0025] The method may include receiving a positioning request from the network. An indication, transmitted by the WTRU, that the WTRU is using at least one positioning delegation candidate for positioning may be transmitted to the network in response to the positioning request.

[0026] The method may include transmitting a location parallax report to the network based on a difference exceeding a parallax threshold over a predetermined time period.

[0027] The WTRU may be configured to receive positioning configuration information. The WTRU may select a positioning delegation candidate for positioning based on the positioning configuration information. The WTRU may transmit an indication to the network that the WTRU is using a positioning delegation candidate for positioning. The WTRU may transmit an indication to the network that the WTRU has stopped using a positioning delegation candidate for positioning.

[0028] The WTRU may include positioning configuration information, which may include an indication for the WTRU and / or an indication of conditions for enabling or disabling positioning delegation. The positioning delegation candidates indicated by the positioning configuration information may include the selected positioning delegation candidate. The WTRU may be configured to detect that the conditions for enabling positioning delegation are met for the selected positioning delegation candidate. The WTRU may send an indication to the network that the WTRU is using the positioning delegation candidate selected for positioning. The WTRU may base the selection on detecting that the conditions for enabling positioning delegation are met for the selected positioning delegation candidate. The WTRU may detect that the conditions for disabling positioning delegation are met for the selected positioning delegation candidate. Based on detecting that the conditions for disabling positioning delegation are met for the selected positioning delegation candidate, the WTRU may send an indication to the network that it has stopped using the positioning delegation candidate selected for positioning.

[0029] The WTRU may be configured to receive positioning configuration information. The positioning configuration information may include an indication of one or more positioning delegation candidates for the WTRU and an indication of one or more conditions for enabling or disabling positioning delegation. The WTRU may detect that the conditions for enabling positioning delegation are met for at least one of the positioning delegation candidates. Based on detecting that the conditions for enabling the use of positioning delegation are met for at least one positioning delegation candidate, the WTRU may send an indication to the network that the WTRU is using at least one positioning delegation candidate for positioning.

[0030] Positioning configuration information that may include an indication of one or more conditions for enabling or disabling positioning delegation. The WTRU may detect that a condition for disabling positioning delegation is met for at least one positioning delegation candidate. Based on detecting that a condition for disabling positioning delegation is met for at least one positioning delegation candidate, the WTRU may send an invalidation indication to the network that it has stopped using at least one positioning delegation candidate for positioning.

[0031] The WTRU may send a message to the network requesting to perform positioning delegation.

[0032] The conditions for enabling positioning delegation may include one or more of the WTRU battery level being below a threshold, connecting to at least one positioning delegation candidate, and / or detecting that the WTRU is within the proximity specified for at least one positioning delegation candidate.

[0033] The conditions for enabling positioning delegation may include detecting that the WTRU is within the proximity specified for at least one positioning delegation candidate based on signal strength measurements received from at least one positioning delegation candidate.

[0034] The WTRU may perform measurements of one or more PRS transmissions and / or report PRS measurement values. The configuration may be based on detecting that a condition for disabling positioning delegation is met for at least one positioning delegation candidate.

[0035] The enabling indication may include location information indicating the location of at least one positioning delegation candidate. The WTRU may be configured to receive a positioning request from the network. The enabling indication may be sent to the network in response to the positioning request.

[0036] The WTRU may transmit a location disparity report to the network. The location disparity report may indicate the difference between the location of the WTRU and the location of the positioning delegate.

[0037] The WTRU may transmit a location disparity report to the network based on the difference exceeding a disparity threshold over a predetermined time period.

[0038] After connecting to the positioning delegate, the WTRU may perform positioning measurements over a specified duration. The WTRU may compare the location information it has determined with the location information provided by the positioning delegate.

[0039] The method performed by the WTRU may include receiving positioning configuration information. The positioning configuration information may include an indication of one or more positioning delegate candidates for the WTRU. The positioning configuration may include an indication of one or more conditions for enabling or disabling positioning delegation.

[0040] The method may include detecting that a condition for enabling positioning delegation is satisfied for at least one of the positioning delegate candidates. The method may include transmitting an indication to the network that the WTRU is using at least one positioning delegate candidate for positioning based on detecting that a condition for enabling positioning delegation is satisfied for at least one positioning delegate candidate.

[0041] The method may include an indication of one or more conditions for enabling or disabling positioning delegation. The method may include detecting that a condition for disabling positioning delegation is satisfied for at least one positioning delegation candidate. The method may include sending an indication to the network that the WTRU has stopped using at least one positioning delegation candidate for positioning, based on detecting that a condition for disabling positioning delegation is satisfied for at least one positioning delegation candidate.

[0042] The method may include sending a message to the network requesting to perform positioning delegation.

[0043] Conditions for enabling positioning delegation include one or more of detecting that the WTRU battery level is below a threshold, connecting to at least one positioning delegation candidate, and / or detecting that the WTRU is within a specified proximity to at least one positioning delegation candidate.

[0044] Conditions for enabling positioning delegation include detecting that the WTRU is within a specified proximity to at least one positioning delegation candidate, based on a signal strength measurement received from at least one positioning delegation candidate.

[0045] The method may include performing measurements of one or more PRS transmissions and reporting PRS measurement values, based on detecting that a condition for disabling positioning delegation is satisfied for at least one positioning delegation candidate.

[0046] The indication may include location information indicating the location of at least one positioning delegation candidate.

[0047] The method may include receiving a positioning request from the network, and the indication is sent to the network in response to the positioning request.

[0048] The method may include transmitting a location disparity report to the network based on a difference exceeding a disparity threshold over a predetermined time period.

[0049] A WTRU may receive positioning configuration information. The WTRU may select a positioning delegation candidate for positioning based on the positioning configuration information. The WTRU may transmit an activation indication to the network that the WTRU is using the positioning delegation candidate for positioning. The WTRU may transmit a deactivation indication to the network that the WTRU has stopped using the positioning delegation candidate for positioning.

[0050] The positioning configuration information may include an indication of one or more positioning delegation candidates for the WTRU. The positioning information may include an indication of one or more conditions for activating or deactivating the positioning delegation. The one or more positioning delegation candidates indicated by the positioning configuration information may include the selected positioning delegation candidate.

[0051] The WTRU may detect that a condition for activating the positioning delegation is satisfied for the selected positioning delegation candidate. Based on the detection that a condition for activating the positioning delegation is satisfied for the selected positioning delegation candidate, the WTRU may transmit an activation indication to the network that the WTRU is using the selected positioning delegation candidate for positioning. The WTRU may detect that a condition for deactivating the positioning delegation is satisfied for the selected positioning delegation candidate. Based on the detection that a condition for deactivating the positioning delegation is satisfied for the selected positioning delegation candidate, the WTRU may transmit a deactivation indication to the network that the WTRU has stopped using the selected positioning delegation candidate for positioning. BRIEF DESCRIPTION OF THE DRAWINGS

[0052]

Figure 1A

Figure 1B

Figure 1C

Figure 1D

Figure 2

Figure 3A

Figure 3B

Figure 4A

Figure 4B

Figure 4C

Figure 5

Best Mode for Carrying Out the Invention

[0053] FIG. 1A is a diagram illustrating an exemplary communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 can be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to a plurality of wireless users. The communication system 100 can enable a plurality of wireless users to access such content through sharing of system resources including wireless bandwidth. For example, the communication system 100 may use one or more channel access methods such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), orthogonal FDMA (OFDMA), Single-Carrier FDMA (SC-FDMA), Zero-Tail Unique-Word DFT-Spread OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), resource block filtered OFDM, Filter Bank Multi Carrier (FBMC).

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

[0055] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks such as CN106 / 115, the Internet 110, and / or other network 112. By way of example, base stations 114a, 114b may be a Base Transceiver Station (BTS), Node B, Enode B, Home Node B, Home eNode B, gNB, NR Node B, site controller, Access Point (AP), wireless router, etc. Although base stations 114a, 114b are each depicted as a single element, it will be understood that base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0056] Base station 114a may be part of RAN 104 / 113 and may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals at one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be an authorized spectrum, an unlicensed spectrum, or a combination of an authorized spectrum and an unlicensed spectrum. A cell may provide wireless service coverage to a specific geographic area that may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

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

[0058] More specifically, as described above, the communication system 100 may be a multiple access system and may use one or more channel access methods such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base stations 114a within RAN104 / 113 and the WTRUs 102a, 102b, 102c may implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interfaces 115 / 116 / 117. 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 UL Packet Access (HSUPA).

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

[0060] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as NR radio access, which may use New Radio (NR) to establish the radio interface 116.

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

[0062] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement wireless 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), IS-95, IS-856, Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0063] The base station 114b in FIG. 1A can be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area such as an office, a home, a vehicle, a campus, an industrial facility, an aerial corridor (e.g., for use by drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d can implement a wireless technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d can implement a wireless technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a pico cell or a femto cell. As shown in FIG. 1A, the base station 114b can have a direct connection to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106 / 115.

[0064] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, 102d. The data can have various quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or can implement high-level security functions such as user authentication. Although not shown in Figure 1A, it will be understood that RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that employ the same or a different radio access technology (RAT) as RAN 104 / 113. For example, in addition to being connected to a RAN 104 / 113 that can utilize New Radio (NR) radio technology, CN 106 / 115 may also communicate with another RAN (not shown) using GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0065] CN106 / 115 may also function as a gateway for WTRU102a, 102b, 102c, 102d to access the PSTN108, the Internet 110, and / or other networks 112. The PSTN108 may include a circuit-switched telephone network that provides Plain Old Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices, where these networks and devices use common communication protocols such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) of the TCP / IP Internet protocol suite. The network 112 may include a wired communication network and / or a wireless communication network that is owned and / or operated by another service provider. For example, the network 112 may include another CN connected to one or more RANs that may employ the same RAT as the RAN104 / 113 or a different RAT.

[0066] Some or all of the WTRU102a, 102b, 102c, 102d within the communication system 100 may include multimode capabilities (e.g., the WTRU102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). For example, the WTRU102c shown in Figure 1A may be configured to communicate with a base station 114a that may employ a cellular-based wireless technology and a base station 114b that may employ IEEE802 wireless technology.

[0067] Figure 1B is a system diagram illustrating an exemplary WTRU 102. As shown in Figure 1B, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, a non-removable memory 130, a removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripheral devices 138. It will be understood that the WTRU 102 may include any partial combination of the foregoing elements while remaining consistent with one embodiment.

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

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

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

[0071] The transceiver 120 can be configured to modulate signals transmitted by the transmitting / receiving element 122 and to demodulate signals received by the transmitting / receiving element 122. As described above, the WTRU 102 can have a multimode function. Thus, the transceiver 120 can include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs such as, for example, NR and IEEE 802.11.

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

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

[0074] Processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) via the air interface 116 and / or may determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may obtain location information by any suitable positioning method while remaining consistent with one embodiment.

[0075] Processor 118 may also be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connections. For example, the peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, 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 / Augmented Reality (VR / AR) device, an activity tracker, etc. The peripheral devices 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0076] The WTRU 102 may include a full-duplex radio in which the transmission and reception of some or all of the signals associated with a particular subframe (e.g., for both UL (e.g., for transmission) and downlink (e.g., for reception)) can be parallel and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and / or substantially eliminate self-interference, either via hardware (e.g., a choke) or via signal processing through a processor (e.g., a separate processor (not shown) or the processor 118). In one embodiment, the WRTU 102 may include a half-duplex radio for the transmission and reception of some or all of the signals (e.g., associated with a particular subframe for either UL (e.g., for transmission) or downlink (e.g., for reception)).

[0077] Figure 1C is a system diagram illustrating the RAN 104 and the CN 106, according to one embodiment. As described above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c via the air interface 116, employing the E-UTRA radio technology. The RAN 104 may also communicate with the CN 106.

[0078] The RAN 104 may include eNode-Bs 160a, 160b, 160c, although it will be understood that the RAN 104 may include any number of eNode-Bs while remaining consistent with one embodiment. Each of the eNode-Bs 160a, 160b, 160c may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c via the radio interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may transmit a radio signal to and / or receive a radio signal from the WTRU 102a using a plurality of antennas.

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

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

[0081] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, and 162c in the RAN 104 via the S1 interface and may function as a control node. For example, the MME 162 may authenticate users of the WTRUs 102a, 102b, and 102c, activate / deactivate bearers, select a specific serving gateway during the initial attach of the WTRUs 102a, 102b, and 102c, etc. The MME 162 may provide control plane functions for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies such as GSM and / or WCDMA.

[0082] SGW 164 can be connected to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. SGW 164 can generally route and transfer user data packets between the WTRUs 102a, 102b, and 102c. SGW 164 can perform other functions such as the function of anchoring the user plane during handover between eNode Bs, the function of triggering paging when DL data is available to the WTRUs 102a, 102b, and 102c, and the function of managing and storing the contexts of the WTRUs 102a, 102b, and 102c.

[0083] SGW 164 can be connected to PGW 166, but PGW 166 can provide the WTRUs 102a, 102b, and 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between the WTRUs 102a, 102b, and 102c and IP-compatible devices.

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

[0085] The WTRU is described as a wireless terminal in FIGS. 1A - 1D, but in certain representative embodiments, it is contemplated that such a terminal can use (e.g., temporarily or permanently) a wired communication interface with the communication network.

[0086] In a representative embodiment, the other network 112 can be a WLAN.

[0087] A WLAN in infrastructure basic service set (BSS) mode can have an access point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to another type of wired / wireless network that carries traffic entering and / or exiting the distribution system (DS) or BSS. Traffic to an STA originating outside the BSS can reach and be delivered to the STA through the AP. Traffic originating from an STA to a destination outside the BSS can be sent to the AP and then sent to their respective destinations. Traffic between STAs within the BSS can be sent, for example, through the AP, where the source STA sends the traffic to the AP and the AP delivers the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be sent (e.g., directly) between the source STA and the destination STA using direct link setup (DLS). In a particular representative embodiment, the DLS can use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (e.g., all of the STAs) can communicate directly with each other. The IBSS mode of communication can be referred to herein as the "ad hoc" communication mode.

[0088] When using the 802.11ac infrastructure operation mode or a similar operation mode, the AP may transmit beacons on a fixed channel such as the primary channel. The primary channel can be of a fixed width (e.g., a 20 MHz-wide bandwidth) or a width dynamically set via signaling. The primary channel can be the operating channel of the BSS, but can also be used by the STA to establish a connection with the AP. In certain representative embodiments, for example, in an 802.11 system, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) can be implemented. In the case of CSMA / CA, STAs including the AP (e.g., all STAs) can sense the primary channel. If the primary channel is detected / determined to be busy by a particular STA, the particular STA can back off. Only one STA (e.g., only one station) can transmit at any given time in a given BSS.

[0089] A High Throughput (HT) STA can use a 40 MHz-wide channel for communication, and this 40 MHz-wide channel can be formed, for example, through a combination of a primary 20 MHz channel and an adjacent or non-adjacent 20 MHz channel.

[0090] A Very High Throughput (VHT) STA can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. A 40 MHz and / or 80 MHz channel can be formed by combining a plurality of consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels, which can be referred to as an 80+80 configuration. In the case of the 80+80 configuration, after channel coding, the data can pass through a segment parser that can split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing can be performed separately on each stream. The streams can be mapped to two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration can be reversed, and the combined data can be transmitted to the Medium Access Control (MAC).

[0091] The sub-1 GHz operating mode is supported by 802.11af and 802.11ah. The channel operating bandwidth and carrier frequency 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 TV White Space (TVWS) spectrum, and 802.11ah supports bandwidths of 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz using non-TVWS spectrum. According to an exemplary embodiment, 802.11ah may support meter type control / machine type communication, such as MTC devices within a macro reach area. The MTC device may have limited capabilities, including support for a particular and / or limited bandwidth (e.g., support only therefor). The MTC device may include a battery having a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0092] A WLAN system that supports a plurality of channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah includes channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or restricted by an STA from among all STAs operating in a BSS that supports a minimum bandwidth operation mode. In the example of 802.11ah, the primary channel is 1 MHz wide for an STA (e.g., an MTC type device) that supports the 1 MHz mode (e.g., supports only that) even when the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operation modes. Carrier sensing and / or Network Allocation Vector (NAV) setting may depend on the status of the primary channel. For example, if the primary channel is busy due to an STA transmitting to the AP (supporting only the 1 MHz operation mode), the entire available frequency band may be considered busy even though most of the frequency band remains idle and available.

[0093] In the United States, the available frequency bands that can be used by 802.11ah are 902 MHz to 928 MHz. In Korea, the available frequency bands are 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code.

[0094] FIG. 1D is a system diagram illustrating RAN 113 and CN 115 according to one embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, 102c via wireless interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

[0095] RAN 113 may include gNBs 180a, 180b, and 180c, but it should be understood that RAN 113 may include any number of gNBs while remaining consistent with one embodiment. Each of gNBs 180a, 180b, and 180c may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via radio interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 108b may use beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Thus, gNB 180a may transmit and / or receive radio signals to / from WTRU 102a using, for example, multiple antennas. In one embodiment, gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB 180a may transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0096] WTRUs 102a, 102b, and 102c may communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable numerology. For example, the OFDM symbol interval and / or the OFDM sub-carrier interval may vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c may communicate with gNBs 180a, 180b, and 180c using sub-frames (e.g., including a varying number of OFDM symbols and / or having an absolute time duration of varying length) or transmission time intervals (TTIs) of various or scalable lengths.

[0097] gNBs 180a, 180b, and 180c may be configured to communicate with WTRUs 102a, 102b, and 102c in a stand-alone configuration and / or a non-stand-alone configuration. In a stand-alone configuration, WTRUs 102a, 102b, and 102c may communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c, etc.). In a stand-alone configuration, WTRUs 102a, 102b, and 102c may utilize one or more of gNBs 180a, 180b, and 180c as a mobility anchor point. In a stand-alone configuration, WTRUs 102a, 102b, and 102c may communicate with gNBs 180a, 180b, and 180c using signals in an unlicensed band. In a non-stand-alone configuration, WTRUs 102a, 102b, and 102c may communicate with and connect to gNBs 180a, 180b, and 180c while also communicating with and connecting to another RAN such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c may implement a DC principle for communicating with one or more gNBs 180a, 180b, and 180c and one or more eNode-Bs 160a, 160b, and 160c substantially simultaneously. In a non-stand-alone configuration, eNode-Bs 160a, 160b, and 160c may function as a mobility anchor for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, and 102c.

[0098] Each of gNBs 180a, 180b, and 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decision-making, handover decision-making, user scheduling in UL and / or DL, support for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to user plane functions (UPFs) 184a, 184b, and routing of control plane information to access and mobility management functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, gNBs 180a, 180b, and 180c may communicate with each other via the Xn interface.

[0099] CN 115 shown in FIG. 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 optionally data networks (DNs) 185a, 185b. Although each of the foregoing elements is depicted as part of CN 115, it will be understood that any of these elements may be owned and / or operated by entities other than the CN operator.

[0100] AMF 182a and 182b can be connected to one or more of gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can function as control nodes. For example, AMF 182a and 182b can play roles such as authentication of users of WTRUs 102a, 102b, and 102c, support for network slicing (e.g., handling different PDU sessions with different requirements), selection of specific SMFs 183a and 183b, management of the registration area, termination of NAS signaling, and mobility management. Network slices can be used by AMF 182a and 182b to customize the CN support for WTRUs 102a, 102b, and 102c based on the type of service being utilized by WTRUs 102a, 102b, and 102c. For example, different network slices can be established for different use cases such as services that rely on ultra-reliable low latency (URLLC) access, services that rely on enhanced massive mobile broadband (eMBB) access, and services for machine type communication (MTC) access. AMF 162 may provide control plane functions for exchange between RAN 113 and other RANs (not shown) that use other radio technologies such as non-3GPP access technologies like LTE, LTE-A, LTE-A Pro, and / or WiFi.

[0101] SMF183a and 183b can be connected to AMF182a and 182b in CN115 via the N11 interface. SMF183a and 183b can also be connected to UPF184a and 184b in CN115 via the N4 interface. SMF183a and 183b can select and control UPF184a and 184b and configure the routing of traffic through UPF184a and 184b. SMF183a and 183b can perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, enforcing policies and controlling QoS, and providing downlink data notifications. The PDU session type can be IP-based, non-IP-based, Ethernet-based, etc.

[0102] UPF184a and 184b can be connected to one or more of gNB180a, 180b, and 180c in RAN113 via the N3 interface, thereby providing WTRU102a, 102b, and 102c access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, and 102c and IP-compatible devices. UPF184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-home PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

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

[0104] Referring to FIGS. 1A - 1D and the corresponding descriptions thereof, one or more of the functions described herein with respect to one or more of the WTRUs 102a - d, base stations 114a - b, eNode - Bs 160a - c, MME 162, SGW 164, PGW 166, gNBs 180a - c, AMFs 182a - b, UPFs 184a - b, SMFs 183a - b, DNs 185a - b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). An emulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functionality.

[0105] An emulation device can be designed to perform one or more tests of other devices in a laboratory environment and / or an operator network environment. For example, one or more emulation devices may perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more emulation devices may perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. An emulation device can be directly coupled to another device for testing purposes and / or can perform tests using terrestrial wireless communication.

[0106] One or more emulation devices can perform one or more functions, including all, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, an emulation device can be utilized in a test scenario in a test laboratory and / or a non-deployed (e.g., for testing) wired and / or wireless communication network to implement tests of one or more components. One or more emulation devices can be test equipment. Direct RF coupling and / or wireless communication via an RF circuit (which may include one or more antennas) can be used by an emulation device to transmit and / or receive data.

[0107] References to gNB in this specification refer to a representative base station, and the gNB can be replaced with any other suitable base station.

[0108] A WTRU can perform one or more operations related to positioning.

[0109] A WTRU may receive configuration information from the network to determine a location delegate node and / or cell. The WTRU may obtain its location information from the configuration information (e.g., without necessarily performing measurement-related operations). For example, the location node and / or cell may be included in a list of delegate serving nodes / cells and / or a list of neighboring cells that may operate as delegates.

[0110] A WTRU may receive an indication from a serving node and / or cell or neighboring cell (e.g., via broadcast signaling and / or a dedicated RRC / MAC message). The indication may indicate that the serving node and / or cell or neighboring cell may be able to operate as a location delegate.

[0111] A WTRU may receive configuration information from the network, which may include conditions for using a location delegate. The conditions may include that the signal level towards the location delegate exceeds a certain level (e.g., a specific level), that the current WTRU battery level is below a certain level (e.g., a specific level), and / or that the location accuracy of the WTRU itself is below a certain level (e.g., a specific accuracy level).

[0112] When determining the availability of a location delegate, e.g., when a node and / or cell capable of location delegation becomes the serving cell of the WTRU, the WTRU may be able to measure neighboring cells where location delegation can be performed (e.g., with good radio quality, etc.). When one or more of the conditions for using the location delegate are satisfied, the WTRU can perform one or more operations. For example, the WTRU can obtain location information from the delegate, including reading broadcast location information and / or explicitly requesting location information from the relevant node and / or cell. The WTRU can stop or suspend location-related operations (e.g., measurements, UL signal / report transmissions, etc.). The WTRU can transmit information to the network. This information transmitted by the WTRU can indicate that location delegation has been initiated.

[0113] When determining that the location delegate is unavailable, e.g., when disconnecting from a node and / or cell where the WTRU operates as a location delegate, the WTRU may not be able to measure neighbors that operate as location delegates (e.g., with good radio quality, etc.). When one or more of the conditions for using the location delegate are satisfied (e.g., and no more are satisfied), the WTRU may perform one or more of the operations. For example, the WTRU can start or resume location-related operations (e.g., measurements, UL signal / report transmissions, etc.). The WTRU can transmit information to the network. The information can indicate that location delegation has stopped.

[0114] Positioning operations may be implemented. A protocol for positioning operations may be implemented. FIG. 2 illustrates an exemplary protocol 200 used in a positioning operation configured between a WTRU 202 and a network node, e.g., gNB 204a.

[0115] The protocols used for positioning can be, for example, the new radio (NR) positioning protocol A (NRPPa) 208a and 208c, which can be between gNBs 204a and 204c and the location management function (LMF) 206. The protocols used for positioning can be, for example, the LTE positioning protocol (LPP) 210, which can be between the WTRU 202 and the LMF 206.

[0116] The LMF function can be implemented. Based on the positioning capability information transmitted by the WTRU 202, the LMF 206 can determine the positioning methods to be supported by the WTRU 202 (e.g., WTRU-assisted / WTRU-based, downlink (DL)-based / uplink (UL)-based). The LMF 206 can provide one or more positioning reference signal (PRS) configurations (e.g., for DL-based positioning) to the WTRU and / or provide one or more sounding reference signal (SRS) configurations (e.g., for UL-based positioning) to the gNB / transmission reception point (TRP). In the case of WTRU-assisted positioning, the LMF 206 can perform the calculation of the location information of the WTRU 202 based on the measurement report transmitted by the WTRU 202. In the case of WTRU-based positioning, the LMF 206 can transfer the location information of the WTRU 202 (which can be transmitted by the WTRU, for example) to an external application / location service client. The LMF 206 may depend on the information transmitted by the WTRU 202.

[0117] The content of the NRPPa 208a and 208b protocols can include SRS or PRS configurations so that the gNB / TRP knows what to transmit and / or receive.

[0118] (For example, from LMF206) The content of the LPP210 protocol may include a location request for the WTRU202 (e.g., for the WTRU202 to start a positioning process such as performing measurements). The PRS configuration may be associated with the serving cell and neighboring cells' gNB / TRP of the WTRU202 (e.g., so that the WTRU knows what to receive), and / or may be associated with measurement details (e.g., so that the WTRU knows how / what to measure).

[0119] (For example, from the WTRU202) The content of the protocol LPP210 may include positioning capability information, a support data request when the WTRU202 does not have a PRS configuration, a measurement report for WTRU-assisted positioning, and / or location information for WTRU-based positioning. The LPP210 message may be carried in a non-access stratum protocol data unit (NAS PDU).

[0120] For example, when using the protocol RRC 212 for DL-based positioning, the WTRU202 may be able to access one or more PRS configurations via parameters (e.g., posSIB). The WTRU may be able to request the gNB to configure a measurement gap, for example, as preparation for starting the implementation of DL-PRS measurements.

[0121] For example, when using the protocol RRC 212 for UL-based positioning, the WTRU202 can receive one or more SRS configurations from the serving gNB.

[0122] The DL positioning method described in this specification may refer to a positioning method that uses a downlink reference signal such as a positioning PRS. The WTRU 202 may receive a plurality of reference signals from the TP, and may measure the DL reference signal time delay (RSTD) and / or the reference signal received power (RSRP). Examples of the DL positioning method may include, for example, downlink angle of departure (DL-AoD) positioning and / or downlink time difference of arrival (DL-TDOA) positioning.

[0123] The UL positioning method described in this specification may refer to a positioning method that uses an uplink reference signal such as a positioning SRS. The WTRU 202 may transmit SRS to a plurality of reception points (RPs), and the RP may measure the uplink relative time of arrival (UL RTOA) and / or the RSRP. Examples of the UL positioning method may include, for example, uplink time difference of arrival (UL-TDOA) positioning and / or uplink angle of arrival (UL-AoA) positioning.

[0124] The DL and UL positioning methods described in this specification may refer to positioning methods that use uplink reference signals and downlink reference signals for positioning. For example, a WTRU may transmit SRS to multiple TRPs, and a gNB may measure the time difference between the reception and transmission (Rx-Tx) of the SRS. For example, a gNB may measure the RSRP for the received SRS. A WTRU may measure the Rx-Tx time difference for PRS transmitted from multiple TRPs. For example, a WTRU may measure the RSRP for the received PRS. For example, the round-trip time may be calculated using the Rx-TX difference measured at the TRU and gNB, and optionally the RSRP. In this specification, the difference between Rx and Tx refers to the difference between the arrival time of the reference signal transmitted by the TRP and the transmission time of the reference signal transmitted from the WTRU. An example of the DL and UL positioning method may be multi-Round Trip Time (RTT) positioning.

[0125] Integrated Access and Backhaul (IAB), where a portion of the radio spectrum can be used for backhaul connections of base stations instead of fiber, may enable a more flexible and less expensive deployment of high-density networks (e.g., compared to a deployment where dedicated fiber links to base stations exist). IAB solutions may be based on a split architecture (e.g., centralized unit (CU) and / or distributed unit (DU) architecture) that may be specified for NR.

[0126] Figures 3A - 3B illustrate examples of Integrated Access and Backhaul (IAB) architectures. A representative architecture may include a user plane (UP) 300 for IAB and a control plane (CP) protocol architecture 350.

[0127] The protocol stack of the IAB node 304a may include two sides, namely, the mobile termination (MT) 308a - b part that can be used to communicate with the parent node, and the DU 306a - b part that can be used to communicate with the child node or the WTRU 302 (e.g., a normal WTRU). An IP address may be assigned to each IAB node 304a - b. The IP address may be routable from the donor base station (and the associated L2 address). The intermediate IAB nodes 304a - b may forward packets (e.g., transparently) based on the route identifier and / or the destination address. The IAB nodes 304a - b may terminate the DU 306c function. The base station referred to as the IAB donor 304c may terminate the CU 310 function. The IAB nodes (304a, 204b) and the donor CU 310 can form one logical base station unit regardless of the number of hops physically separating them. For example, the IAB nodes 304a - b may adopt a CU / DU split architecture where the IAB nodes 304a - b are regarded as the DU 306c and the CU 310, which is the CU part of the IAB donors 304a - b, is regarded as the CU. The IAB node 304a that provides services to the WTRU 302 may be referred to as an access IAB node. The node between the DU 306c of the IAB donor 304c and the access IAB node 304a may be known as the intermediate IAB node 304b. The IAB nodes 304a - b may serve as the access IAB node 304a (e.g., for the WTRU 302 directly connected to the access IAB node 304a) and may also serve as the intermediate IAB node 304b (e.g., for the WTRU 302 served by its descendant IAB nodes).

[0128] Hop-by-hop (H2H) RLC 314a-c may be used between IAB nodes 304a-c (e.g., instead of end-to-end (E2E) RLC between donor DU 306c and WTRU 302). Adaptation layers 316a-b, which may be referred to as backhaul adaptation protocol (BAP), may be used to enable efficient multi-hop transfer. IAB donor 304c may assign a unique L2 address (BAP address) to each IAB node 304a-b controlled by IAB donor 304c. In the example, multiple route IDs may be associated with each BAP address. The BAP of the originating node (e.g., DU 306c of IAB donor 304c for DL traffic and access IAB node 306a for UL) may add a BAP header to the packets they are transmitting, and the BAP header may include a BAP routing ID (e.g., the BAP address and path ID of the destination / source IAB nodes 304a-c).

[0129] When a packet arrives that has a BAP routing ID including a BAP address equal to the BAP address of IAB nodes 304a - b, IAB nodes 304a - b can know that the packet is intended to be received by IAB nodes 304a - b. IAB nodes 304a - b can pass this packet to the upper layer for processing (e.g., an F1 - C / U message destined for the DU of the IAB node, an F1 - C message including SRB data for the WTRU 302 directly connected to IAB node 304a, and / or an F1 - U message including DRB data for the WTRU directly connected to IAB node 304a). In the example, IAB nodes 304a - c may employ a routing table and / or a mapping table to determine where to forward the data. Each of IAB nodes 304a - c may have a routing table (e.g., configured by the IAB donor CU 310), and the routing table may include a next - hop identifier for each BAP routing ID. The DL and UL directions may maintain separate routing tables. The DL table may be used by the DU parts 306a - c of IAB nodes 304a - c, and the MT parts 308a - b of IAB nodes 304a - b may use the UL table.

[0130] The backhaul (BH) RLC channel may be used to transport packets between IAB nodes 304a - c (or between IAB donor DU 306c and IAB node 304b). The BH RLC channel configuration may include associated RLC and / or logical channel configurations. Between the WTRU 302 radio bearers and the BH RLC channel, a multi - to - one (N:1) or one - to - one (1:1) mapping may be implemented. The N:1 mapping may multiplex several WTRU 302 radio bearers onto a single BH RLC channel based on certain parameters (e.g., the QoS profile of the bearer). The N:1 mapping may be suitable for bearers that do not have very strict requirements (e.g., best - effort bearers). The 1:1 mapping may map each WTRU 302 radio bearer onto a separate BH RLC channel. The 1:1 mapping can be designed to ensure finer QoS granularity at the WTRU 302 radio bearer level. The 1:1 mapping may be suitable for bearers that have strict throughput requirements and / or latency requirements (e.g., guaranteed bit rate (GBR) bearers and / or Voice over Internet Protocol (VoIP) bearers).

[0131] If IAB nodes 304a - c detect a BH radio link failure (RLF), IAB nodes 304a - c may send a BH RLF indication to other nodes (e.g., to the descendant nodes of IAB nodes 304a - c). The BH RLF indication may be a BAP control PDU. In response to receiving the BH RLF indication from the parent node, IAB nodes 304a - c may initiate procedures such as re - establishment to another parent. IAB nodes 304a - c may suspend transmission and / or reception with the relevant parent. The behavior regarding the reception of the BH RLF indication may be part of the IAB / network implementation.

[0132] In a multi-hop IAB network, data congestion may occur on the intermediate IAB node 304b, which may lead to packet drops (e.g., if left unresolved). In an example, a higher layer protocol (e.g., TCP) may be used to ensure reliability. TCP congestion avoidance functions and / or slow start mechanisms can be very costly to the overall end-to-end performance (e.g., throughput degradation). Therefore, the IAB network may adopt flow control. In an example, for the DL case, E2E and H2H flow control mechanisms may be available.

[0133] DL E2E flow control may be based on the DL data delivery status (DDDS) specified for the CU / DU split architecture (e.g., in NR). In DDDS, the DU (e.g., the DU part of the access IAB node in the context of the IAB network) can report different forms of information (e.g., the desired buffer size per DRB, the desired data rate per DRB, the highest PDCP SN for successful delivery, lost packets (e.g., packets not acknowledged by DU 306a - c at the RLC 314a - b level)) to the CU (e.g., the donor CU 310, specifically CU-UP in the context of the IAB network). The access IAB nodes 304a - c (e.g., only the access IAB nodes 304a - b) may implement the DDDS (e.g., IAB may report only information regarding the DRBs of the WTRU 302 that they directly serve). The access IAB nodes 304a - c may not need to provide information regarding the BH RLC channel.

[0134] In the case of DL H2H flow control, the IAB nodes 304a - c may generate a flow control message (which may be a BAP control PDU) (e.g., when the buffer load of the IAB nodes 304a - c exceeds a specific level and / or when the IAB nodes 304a - c receive a flow control polling message from a peer BAP entity (e.g., a child node)). The H2H flow control information may indicate the available buffer size. In an example, the indicated available buffer size may be at the granularity of the BH RLC channel (e.g., if the available buffer = value_1 when it is equal to BH RLC channel number 1, the available buffer is equal to value_2 or equal for each BH RLC channel number 2, etc.), and in an example, the indicated available buffer size may be at the granularity of the destination routing ID (e.g., if the destination routing ID is equal to address 1, the available buffer is equal to value_1, if the destination routing ID equals address2, the available buffer is equal to value_2, etc.). The IAB nodes 304a - c that receive the flow control message may use this information to control the traffic flow towards the transmitting side (e.g., if the flow control message indicates that there is less available buffer for the relevant traffic, suppress or pause the traffic associated with a specific BH RLC channel or / and destination, if the flow control indicates that there are more available buffer values for the traffic flow, increase the traffic flow, etc.). The actions taken for flow control, as well as the configuration and / or values of the thresholds and other parameters (e.g., buffer thresholds, polling duration (e.g., polling timer), etc.) for triggering the flow control message may be part of the IAB / network implementation.

[0135] Preemptive buffer status reporting (BSR) may be implemented. The IAB nodes 304-a to 304-c may trigger a BSR to their parent node before data (e.g., new data) arrives at their UL buffer (e.g., based on the BSR received by the IAB nodes 304a to 304c from their child nodes and / or WTRU302, and / or based on the scheduling grants (e.g., indication of expected data) provided to them by the IAB nodes 304a to 304c). In an example, the IAB nodes 304a to 304c may control the flow of UL data from their child nodes and / or WTRU302 by providing appropriate UL scheduling grants to them (e.g., based on the BSR received from them). The IAB nodes 304a to 304c may be assumed to be static nodes. A handover, also referred to as a transfer or relocation of the IAB nodes 304a to 304c from one donor to another donor, may be supported for load balancing and / or to handle RLFs caused by interference (e.g., caused by a moving object (e.g., a vehicle), seasonal changes (e.g., tree leaves), and / or infrastructure changes (new buildings)). In an example, in-donor CU handover (e.g., in-donor CU handover only) may be supported (e.g., the target parent DU and the source parent DU of the IAB nodes 304a to 304c may be controlled by the same donor CU). In an example, inter-donor CU handover may be supported.

[0136] IAB connectivity may be supported via multi-RAT dual connectivity (MR-DC). For example, the IAB nodes 304a to 304c may be connected to the network via evolved new radio dual connectivity (EN-DC), the master node may be an LTE node, and the secondary node may be an NR node.

[0137] In an example, the IAB nodes 304a-c may be transparent (e.g., fully transparent) to the WTRU 302 (e.g., from the perspective of the WTRU 302, the IAB nodes 304a-c may appear as normal base stations).

[0138] In an example, mobile IAB may be used to provide connectivity to one or more WTRU 302s (e.g., when one or more WTRU 302s are in motion (e.g., on a bus, train, airplane, etc.)).

[0139] The IAB nodes 304a-c may operate as a fixed wireless access (FWA) point for connectivity for one or more WTRU 302s. For example, the IAB nodes 304a-c may be installed outside, e.g., at a home, building, shopping mall, etc., and may provide connectivity to WTRU 302s located indoors.

[0140] In examples where WTRU302s may be in proximity to each other (e.g., on a bus, train, airplane, within the same building, etc.), the location and / or position of the WTRU302s may be approximately the same for practical purposes. The implementation of positioning (e.g., independent) for each WTRU302 (e.g., WTRU - based or network - based) may be below a threshold (e.g., below an optimal threshold). Reasons for implementing positioning below the threshold for each WTRU302 may include unnecessary power consumption of the WTRU302 (e.g., for performing PRS measurements, for transmitting SRS, for performing global navigation satellite system (GNSS) measurements, etc.). Another reason may include unnecessary signaling and / or resource utilization (e.g., transmission of PRS, and / or transmission of SRS, etc.) when positioning can be performed via the mobile network. Another reason may include low GNSS positioning accuracy (e.g., in the case of indoor WTRU302). Another reason may include throughput loss of the WTRU302. For example, when network - based positioning (e.g., as a measurement gap) can be used by the WTRU302 to perform positioning - related measurements.

[0141] The use of the IAB nodes described herein is an illustrative example. For example, when a group of WTRU302s are in proximity to each other and can be served by the same node or neighboring nodes.

[0142] The methods applicable to the WTRU302 may also be applicable to entities such as IAB nodes 304a - c that can be served by other IAB nodes 304a - c (e.g., IAB nodes 304a - c having functions like a WTRU).

[0143] In an example, the methods described herein may consider GNSS as an alternative to cellular network-based positioning available to the WTRU 302. Multiple positioning methods not based on the mobile network may be available as described herein. In an example, a method of utilizing GNSS location (e.g., to verify a location provided by a delegate) may be applied.

[0144] The term position delegate or location delegate may be used to refer to an entity (e.g., a gNB having IAB nodes 304a - c and / or a small coverage area, etc.) that performs positioning-related operations (e.g., measurements, calculations, and / or reporting, etc.) on behalf of the WTRU 302.

[0145] A non-limiting example of a node or entity (e.g., a network node or entity) that may be used for and / or to assist in positioning includes the LMF. Any other suitable node or entity may be used in place of the LMF and may be consistent with this application.

[0146] The performance of positioning for a plurality of WTRU 302s (e.g., performing positioning-related DL measurements, transmitting UL signaling for network-based / network-assisted positioning, and / or performing positioning calculations, etc.) may be delegated to a node (e.g., IAB nodes 306a-c that serve a group of WTRU 302s). Delegating the performance of positioning for a plurality of WTRU 302s to a node may provide one or more advantages (e.g., power savings for the WTRU 302). For example, a subset of the plurality of WTRU 302s (or, e.g., none of the WTRU 302s if a network node can delegate positioning on behalf of the WTRU 302) may perform positioning-related measurements, signaling, and / or calculations. For example, by delegating positioning to a node, signaling optimization and / or resource optimization can be improved (e.g., less signaling can be used by the network and / or the WTRU 302 to perform measurements via a subset of the WTRU 302s and / or the delegated node). For example, by delegating positioning to a node, the positioning accuracy of indoor WTRU 302s can be improved (e.g., as compared to indoor positioning via GNSS and / or via GNSS only). For example, by delegating positioning to a node, the throughput of the WTRU 302 can be improved (e.g., as a subset of the WTRU 302s or, in the case of delegation to a network node, none of the WTRU 302s). The WTRU 302 may be involved in measurements related to positioning that may require measurement gaps.

[0147] A node (e.g., IAB nodes 304a-c, gNB, etc.) can provide an explicit indication to the WTRU 302 served by this node that this node can delegate positioning measurements, decisions, reports, etc. For example, the delegating node and / or delegating cell can broadcast positioning measurements, decisions, reports, etc. in the system information block (SIB) of the serving cell. For example, this information may be provided in a dedicated manner (e.g., RRC / MAC signaling from the gNB, etc.).

[0148] The WTRU 302 may be configured by the network using information regarding one or more location delegates. For example, the one or more location delegates may be a cell or a list of cells (e.g., cell IDs of small cells that can provide IAB nodes 304a-c or location delegation). Dedicated signaling (e.g., via RRC, MAC), and / or broadcast in the current serving cell (e.g., via SIB) may communicate the information of the cell or list of cells to the WTRU 302. The WTRU may be configured using the information of the cell or list of cells by the application layer and / or manually, etc.

[0149] The WTRU 302 can request the network (e.g., gNB and / or LMF) for information associated with possible position delegates. The WTRU 302 can include in the request information such as the current location, the current serving cell, and / or measurements of neighboring cells. In response, the network (e.g., gNB and / or LMF) can provide the WTRU 302 with information (e.g., a list of cell IDs). The network (e.g., gNB, LMF) can consider the current WTRU 302 location (e.g., the current location and / or current serving cell information provided by the WTRU 302) when considering a list of possible delegates within the coverage area of the current serving cell or in its vicinity. The information may be provided in a dedicated message (e.g., an RRC message) or may be broadcast (e.g., via the SIB of the current serving cell).

[0150] The indication of position delegation can be an implicit indication. For example, a cell can broadcast location information. The WTRU 302 can receive the broadcast of location information from the cell. The location information can have an associated LPP session ID. The LPP session ID can be a unique ID for the WTRU 302 or for a group of WTRUs (e.g., associated with a radio network temporary identifier (RTNI)) indicating that a node and / or cell has established an LPP session with the LMF on behalf of the WTRU 302.

[0151] An example of the benefit of the implicit indication of position delegation can be that the WTRU 302 does not need to send a request to the LMF for assistance information for positioning. By not having to send a request for assistance information to the LMF instead of for positioning, the latency associated with positioning can be reduced.

[0152] In an example, the location delegate may be a node and / or cell that provides service to the WTRU 302 (e.g., IAB nodes 306a-c, and / or gNB, etc.). The location delegate may be a primary cell (Pcell and / or PSCell). The location delegate may be a secondary cell (Scell).

[0153] In an example, the WTRU 302 may connect to a node and / or cell that is the location delegate (e.g., when the WTRU 302 is handed over to a cell that provides location delegation, when the cell that provides location delegation is added as an Scell in carrier aggregation, when the cell that provides location delegation is added as a PSCell and / or SCG Scell in dual connectivity, etc.). When the WTRU 302 connects to the node and / or cell that is location delegated, the WTRU 302 may send specific information to the network (e.g., LMF). The information may indicate that the location of the node and / or cell can be assumed to be the location of the WTRU 302. The WTRU 302 may send specific information (e.g., including the identification information of the WTRU 302, the cell-RNTI (C-RNTI) associated with the master cell group (MCG) or secondary cell group (SCG), the cell ID of the location delegate, and / or the MT identification information of the location delegate if the location delegate is one of the IAB nodes 306a-c, etc.) to the network. The gNB may send the information (e.g., send on behalf of the WTRU 302 and / or forward the information provided by the WTRU 302).

[0154] In an example, when the WTRU 302 connects to a node and / or cell that is a location delegate, the WTRU 302 can continue to perform location measurements and / or determinations and can compare the location measurements and / or determinations with the location provided by the delegate. The WTRU 302 can determine whether the location difference between the location measured by the WTRU 302 and the location provided by the delegate is consistent over a certain duration (e.g., is approximately the same for a given duration and / or configured duration, and / or the difference between different but given durations and / or configured durations is the same, etc.). If the WTRU 302 determines that the measurements are consistent, the WTRU 302 can send an indication (e.g., a start indication) to the network that the location delegation has been initiated. If the WTRU 302 determines that the measurements are not consistent, the WTRU 302 can send an indication to the network that the location delegation may not be accepted.

[0155] In an example, when the WTRU 302 is disconnected from a cell that is a location delegate (e.g., when the WTRU 302 is handed over to another cell, when the cell providing the location delegation is a SCell and the cell is released, and / or when the cell providing the location delegation is a PSCell and the SCG is released, etc.), information indicating that the location of the cell cannot (e.g., can no longer) be assumed to be the location of the WTRU 302 can be sent to the network (e.g., the LMF).

[0156] The location delegate may be a node and / or cell that is not currently providing service to the WTRU 302 (e.g., a neighboring node and / or cell, etc.). In an example, the WTRU 302 may receive from a cell a condition indicating when that cell should be considered as a location delegate. For example, thresholds for RSRP, reference signal received quality (RSRQ), and / or received signal-to-noise indicator (RSNI) may be configured, and the WTRU 302 may consider (e.g., only when satisfied) a neighboring cell whose signal level meets the configured threshold as the location delegate of the WTRU 302. For example, the WTRU 302 may continue to perform location measurements and / or determinations, and may compare the location measurements and / or determinations with the location broadcast by a neighboring cell. The WTRU 302 may consider (e.g., accept) a neighboring cell as the location delegate of the WTRU 302 if the location difference between the location measured by the WTRU 302 and the location broadcast by the neighboring cell is consistent over a certain duration (e.g., approximately the same as a given duration and / or a configured duration, the difference between different but given durations and / or configured durations is the same, etc.).

[0157] In an example, the information indicating the location of the neighboring cell may also be assumed to be the location of the WTRU 302. For example, if the WTRU 302 determines that a neighboring cell satisfies the conditions for operating as a location delegate, this information indicating the location of the neighboring cell, which is assumed to be the location of the WTRU 302, may be sent to the network (e.g., the LMF). The information may be sent to the network by the WTRU 302 (e.g., including the identification information of the WTRU 302, the C-RNTI associated with the MCG or SCG, the cell ID of the location delegate, and / or the MT identification information of the location delegate if the location delegate is an IAB node, etc.).

[0158] In an example, the information indicating the location of neighboring cells may also be assumed to be the location of the WTRU 302. This information may further indicate that the neighboring cell can no longer be assumed to be the location of the WTRU 302. For example, if the WTRU 302 determines that the neighboring cell no longer meets the conditions for operating as a location delegate, this information indicating that the location of the neighboring cell can no longer be assumed to be the location of the WTRU 302 may be sent to the network (e.g., the LMF). The information may be sent to the network by the WTRU 302 (including, for example, the identification information of the WTRU 302, the C-RNTI associated with the MCG or SCG, the cell ID of the location delegate, and / or the MT identification information of the location delegate if the location delegate is an IAB node, etc.).

[0159] The WTRU 302 may determine that the serving cell or a neighboring cell meets the conditions for operating as a location delegate. The WTRU 302 may determine that there is some consistent location difference between the location determined by the WTRU 302 and the location provided by the delegate. Based on this determination, the WTRU 302 may send location difference information to the network. For example, the location difference information may be included in the same message indicating location delegation that the WTRU 302 sends to the network. The WTRU 302 may send the location difference information when the WTRU 302 connects to the serving cell that provides location delegation and / or when the WTRU 302 determines that the neighboring cell meets the delegation requirements.

[0160] The WTRU 302 may be able to determine that the serving cell may be able to operate as a location delegate. Upon determining that the serving cell may be able to operate as a location delegate, the WTRU 302 may send a request to the network (e.g., the serving node and / or serving cell, the master node in the case of a DC, IAB nodes 306a-c, etc.) for location information. The request may be based on conditions such as the WTRU 302 not being able to perform positioning, the RSRP of the synchronization signal block (SSB) from the serving cell being below a threshold, the WTRU 302 having a pending request for location information from the network (e.g., the LMF, etc.).

[0161] The WTRU 302 may not need to receive location information from the delegate (e.g., in response to sending the request and / or not obtaining location information according to the expected time for periodic location updates, etc.). Accordingly, the WTRU 302 may send a message to the network indicating that the WTRU may not need to receive location information. The WTRU 302 may also indicate a request for assistance information (e.g., PRS configuration) and may perform positioning independently.

[0162] The WTRU 302 may be able to determine the location delegation capabilities of the serving cell or neighboring cells. The WTRU 302 may be able to stop performing location-related measurements and / or calculations and / or transmitting UL signaling related to the measurements (e.g., transmitting UL SRS measurement values and / or PRS measurement reports, etc.).

[0163] The WTRU 302 may be configured using a duration for waiting. In an example, the WTRU may respond to the expiration of this duration and / or may stop positioning-related activities (e.g., in response to a determination regarding the location delegation capabilities of the serving cell and / or neighboring cells). The WTRU 302 may specify a distance and / or location value and / or range (e.g., instead of or in addition to the duration). In an example, the WTRU 302 may make this specification when the WTRU 302 is not moving and / or has not moved beyond a particular distance.

[0164] The WTRU 302 may determine that the location delegate is unavailable (e.g., in response to disconnecting from the serving cell which is the location delegate and / or when the signal level of a neighboring cell which is the location delegate falls below a particular threshold). In response, the WTRU 302 may start location-related measurements, perform calculations, and / or transmit UL signaling related to the measurements (e.g., transmit UL SRS measurement values, transmit PRS measurement reports, etc.). The WTRU 302 may send a message indicating a request for assistance information (e.g., PRS configuration) to the network and may perform positioning independently.

[0165] An explicit message from the network may be sent to the WTRU 302 to delegate positioning (e.g., to one of the serving cells of the WTRU 302, to a neighboring cell, etc.). The WTRU 302 may independently stop performing positioning-related operations (e.g., immediately after receiving the message, after a given time, during a given duration, while stationary, etc.).

[0166] An explicit message from the network may be sent to the WTRU 302 to stop an ongoing location delegation. The WTRU 302 may independently start and / or resume performing positioning-related operations (e.g., immediately after receiving the message, after a given time, during a given duration, while stationary, etc.).

[0167] Location information may be communicated between a location delegate, a WTRU 302, and / or the network. For example, the delegate may provide location information from the location delegate to the WTRU 302 in a broadcast manner (e.g., via SIB broadcast). For example, the delegate may provide location information to the WTRU 302 via dedicated signaling (e.g., RRC, and / or MAC, etc.). For example, the WTRU may request location information from the location delegate by transmitting a dedicated message (e.g., RRC, and / or MAC, etc.). For example, the location information provided from the delegate to the WTRU 302 may include two or more locations. For example, the location information may be a set of time and / or location values (e.g., locations for the past 10 minutes, and / or locations every minute) including historical location values from the delegate. For example, the location information may include a set of time and / or location values, in which case some of the values may refer to a future expected location (e.g., when the delegate is a moving IAB node 306a - c having a predetermined route such as a train and / or a tram).

[0168] The WTRU 302 may subscribe to receive location information updates from the location delegate (e.g., periodically every x milliseconds (ms), every time the location changes by y meters, etc.). The WTRU 302 may send requests to the location delegate, a gNB (e.g., in the case of an IAB network) that directly or indirectly provides services to the WTRU 302, and / or the LMF. The subscription of the WTRU 302 for location information may be valid for a duration (e.g., a specific duration such as the next 30 minutes) and / or a location duration (e.g., until the location stops changing for more than 400 ms, etc.).

[0169] The WTRU 302 may request location information (e.g., once, periodic subscription, etc.). The WTRU 302 may include duration information about the location (e.g., location information every minute for the last 10 minutes, location information every minute for the last 5 minutes and the next 5 minutes, etc.).

[0170] The delegate may receive an indication about the validity period of the location information (e.g., the provided location is valid for 1 minute) as part of the location information. The WTRU 302 may be notified of the length of time for which the location information received from the delegate remains valid (e.g., during the configuration and / or determination of the location delegate).

[0171] The WTRU 302 may receive a positioning request from a network (e.g., LMF, gNB). As a response, if available, the WTRU 302 may return location information obtained from the location delegate. The location information may include information about the location delegate (e.g., the cell ID of the gNB / IAB node that is the location delegate). The WTRU 302 may include the location information in an LPP message (e.g., in a request for assistance information) and send it to the LMF (e.g., if the LPP session is active). If the LPP session is not active, the WTRU 302 may send the location information to the serving gNB (e.g., via UCL, MAC-CE, and / or RRC). The serving gNB may transfer the location information to the LMF (e.g., via NRPPa).

[0172] A location delegate can send its own location information to a network (e.g., gNB, LMF, etc.) in response to a request from the network (e.g., in response to an explicit request, configured to report periodically, etc.). The network can distribute the location information to the WTRU 302 (e.g., via RRC signaling) (e.g., in response to a request from the WTRU 302, periodically, in a push-like manner without an explicit WTRU request and / or updated subscription, etc.).

[0173] The delegate can include time information in the provided location information. The time information included in the location information can indicate when the location was determined.

[0174] The delegate can provide location information (e.g., accurate location information) periodically (e.g., every x milliseconds on the SIB).

[0175] The delegate can provide location information (e.g., accurate location information) if, for example, the location has changed by a specific amount (e.g., by a relative margin and / or an absolute margin) (e.g., only in that case).

[0176] The delegate may provide location information (e.g., accurate location information) less frequently and may provide the difference from the previously provided accurate location information more frequently (e.g., the accurate location is provided every 5 seconds and the difference from the previous accurate location is provided every 1 second).

[0177] The MTs of the IAB nodes 306a - c may perform positioning (e.g., using NR positioning, GNSS positioning, etc.) and communicate this information to the WTRU 302 served by the IAB nodes 304a - c.

[0178] For example, the location information can be provided to the WTRU 302 and / or the child IAB nodes 304a-c in a broadcast manner (e.g., via SIB broadcast). For example, the location information can be provided to the WTRU 302 and / or the child IAB nodes 304a-c via dedicated signaling (e.g., MAC and / or BAP, etc.). For example, the WTRU 302 or the child IAB nodes 304a-c can request location information from the IAB node by, for example, transmitting a dedicated message (e.g., MAC and / or BAP, etc.).

[0179] For example, the WTRU 302 or the child IAB nodes 304a-c may request location information from the IAB node via the gNB (e.g., sent to the donor gNB via an RRC message, and the donor gNB can then forward the request to the IAB node). The IAB nodes 304a-c can transmit the location information to the WTRU 302 and / or the child IAB nodes 304a-c (e.g., directly) via (e.g., MAC and / or BAP). The IAB nodes 304a-c can transmit the location information via SIB signaling. The IAB nodes 304a-c may transmit the location information, or the IAB nodes 304a-c can transmit the information to the gNB. The gNB can forward the information to the WTRU 302 (e.g., via RRC). The WTRU 302 can send a request to the LMF, and the LMF can forward the location information of the serving IAB nodes 304a-c to the WTRU 302.

[0180] The WTRU 302 and / or the child IAB nodes 304a-c may be considered location delegates for the serving IAB node and / or cell (e.g., in response to determining that the cell belongs to a mobile IAB node). For example, the WTRU 302 and / or the child IAB nodes 304a-c may determine a location delegate based on the IAB node broadcasting that the IAB node is mobile and / or that the WTRU 302 is configured with a PCI value associated with a cell such as the mobile IAB nodes 304a-c.

[0181] The IAB nodes 304a-c (e.g., IAB-MT) can send their own location information to the network (e.g., gNB and / or LMF, etc.) in response to a request from the network (e.g., in response to an explicit request and / or configured to report periodically, etc.). The network can distribute the location information of the IAB nodes 304a-c to the WTRU 302 and / or the child nodes of the IAB nodes 304a-c (e.g., via RRC signaling) (e.g., in response to a request from the WTRU 302 or a child node, periodically, in a push-like manner without an explicit WTRU 302 request or updated subscription, etc.).

[0182] The WTRU 302 can send a request to the network to obtain the location of the IAB nodes 304a-c within the serving cell, for example, based on certain conditions (e.g., when the RSRP of the SSB from the serving cell falls below a threshold). The WTRU 302 can receive a list (e.g., cell IDs) of the IAB nodes 304a-c within (or in the vicinity of) the serving cell from the network (e.g., LMF and / or gNB). The WTRU 302 can receive this list from the serving gNB and / or within the SIB via a dedicated message.

[0183] When the WTRU 302 is connected to IAB nodes 304a-c that provide location delegation, the information may be sent to the LMF. The information can indicate that the locations of the IAB nodes 304a-c can be assumed to be the location of the WTRU 302. The WTRU 302 may send the information to the LMF (e.g., directly). The donor gNB may send the information.

[0184] When the WTRU 302 is handed over from IAB nodes 304a-c that provide location delegation to another node that does not provide location delegation (e.g., IAB nodes 304a-c and / or gNB), information indicating that the locations of the IAB 304a-c nodes can no longer be associated with the location of the WTRU 302 (e.g., and can no longer be) may be sent to the LMF. The information may be sent to the LMF by the WTRU 302 (e.g., directly). The donor gNB may send the information.

[0185] The IAB nodes 304a-c (e.g., IAB node MT), donor gNB, AMF, and / or another network unit may send information to the LMF that includes information about the cell (e.g., PCI, CGI, etc.) served by the IAB node 304a-c (e.g., DU 304c of the IAB node). The WTRU 302 that connects to and / or disconnects from the IAB nodes 304a-c that delegate location information can send information about the connection and / or disconnection to the IAB nodes 304a-c, for example, by indicating the cells of the IAB nodes 304a-c that serve them. The gNB (e.g., donor gNB) can send information to the LMF, for example, in response to the WTRU 302 being connected / disconnected to / from the IAB nodes 304a-c.

[0186] The IAB nodes 304a - c can notify the WTRU 302 or the IAB child node served by the IAB nodes 304a - c about the identification information of the MT of the IAB nodes 304a - c (e.g., via SIB broadcast, MAC, BAP, etc.). The association in the LMF between the WTRU 302 designated as a location delegate and / or the child IAB nodes 304a - c and / or the parent IAB nodes 304a - c may be established and / or implemented via this IAB identification information. For example, the WTRU 302 and / or the gNB can send the identification information of the MT to the LMF when the WTRU / gNB connects to / disconnects from the IAB nodes 304a - c. The LMF can associate / disassociate the location of the MT with the related WTRU 302 (e.g., therefrom onwards).

[0187] When the IAB nodes 304a - c start and / or stop operating as a location delegate for a WTRU 302 (e.g., a specific WTRU 302), the IAB nodes 304a - c can communicate information to the LMF (e.g., including the WTRU 302 identification information and / or the identification information of the IAB nodes 304a - c, such as MT identification information, IAB cell identification information, etc.).

[0188] The delegated IAB nodes 304a - c may request a measurement gap, for example, for positioning that depends on a plurality of WTRU 302 and child IAB nodes 306a - c served by the delegated IAB nodes 304a - c. For example, when the delegated IAB nodes 304a - c serve many WTRU 302 to obtain more accurate positioning measurement values, a longer measurement gap may be required.

[0189] The delegate IAB nodes 304a - c may request a measurement gap for positioning depending on, for example, the load experienced by the IAB nodes 304a - c. For example, the load may be UL / DL data in transmission reservation at the IAB nodes 304a - c, and a longer measurement gap for positioning may worsen the congestion at the IAB nodes 304a - c.

[0190] The WTRU 302 may be configured to conditionally perform positioning - related measurements and / or signaling. For example, the WTRU 302 may be configured to perform a location determination (e.g., its own location determination). For example, the WTRU 302 may be configured to assist the network (e.g., perform GNSS measurements, perform DL PRS measurements, transmit positioning SRS to the network, etc.) based on, for example, a threshold related to the battery level of the WTRU 302. For example, the WTRU 302 may be configured to stop measurements (e.g., PRS and / or GNSS) and / or positioning - related UL signaling when the battery level of the WTRU 302 falls below a configured threshold. For example, the WTRU 302 may be configured to start measurements or UL signaling when the battery level of the WTRU 302 rises above a configured threshold. Different power level thresholds may be configured for different aspects of location determination or assistance information provision (e.g., threshold_1 related to the performance of GNSS measurements, threshold_2 related to the performance of DL PRS measurements, and / or threshold_3 related to the performance of UL SRS signaling, etc.).

[0191] The WTRU 302 can be configured to perform location determination (e.g., its own positioning), for example, based on the overheat level of the WTRU 302, and / or to assist the network (e.g., perform GNSS measurements, perform DL PRS measurements, and / or transmit positioning SRS to the network, etc.). For example, the WTRU 302 can be configured to stop measurements (e.g., PRS and / or GNSS) and / or positioning related to UL signaling when the overheat level of the WTRU 302 rises above a configured threshold. The WTRU 302 can be configured to start measurements and / or UL signaling when the overheat level of the WTRU falls below a configured threshold. Different overheat level thresholds may be configured for different aspects of location determination and / or providing assistance information (e.g., threshold_1 related to the performance of GNSS measurements, threshold_2 related to the performance of DL PRS measurements, and / or threshold_3 related to the performance of UL SRS signaling, etc.).

[0192] The WTRU 302 may be configured to perform location determination (e.g., its own location determination). The WTRU 302 may be configured to assist the network (e.g., perform GNSS measurements, perform DL PRS measurements, transmit positioning SRS to the network, etc.). The configuration of the WTRU 302 may be based on, for example, thresholds related to the UL / DL data throughput of the WTRU. For example, the WTRU 302 may be configured to stop measurements (e.g., PRS and / or GNSS) and / or UL signaling-related positioning when the UL / DL throughput rises above a configured threshold. The WTRU 302 may be configured to start measurements and / or UL signaling when the UL / DL throughput falls below a configured threshold. Different thresholds may be provided for UL and DL throughput levels. Different thresholds may be configured for different modes of location determination or assistance information provision (e.g., UL throughput threshold_1 for performing GNSS measurements, DL throughput threshold_2 for performing DL PRS measurements, DL throughput threshold_3 for performing DL PRS measurements, and / or UL throughput threshold_4 for UL SRS signaling, etc.).

[0193] The WTRU 302 can be configured to perform location determination (e.g., its own location determination). The WTRU 302 can be configured to assist the network (e.g., perform GNSS measurements, perform DL PRS measurements, transmit positioning SRS to the network, etc.). The configuration of the WTRU 302 can be based on, for example, thresholds related to the UL / DL buffer level of the WTRU 302 (e.g., the available absolute level or percentage level, the used absolute level or percentage level, etc.). For example, the WTRU 302 can be configured to stop measurements (e.g., PRS, and / or GNSS) and / or UL signaling related positioning when the available UL / DL buffer rises above a configured threshold. The WTRU 302 can be configured to start measurements or UL signaling when the available UL / DL buffer falls below a configured threshold. Different thresholds may be provided for the UL and DL buffer levels. Different thresholds may be configured for different modes of location determination or assistance information provision (e.g., UL buffer threshold_1 for performing GNSS measurements, DL threshold_2 for performing DL PRS measurements, DL buffer threshold_3 for performing DL PRS measurements, and / or UL buffer threshold_4 for UL SRS signaling, etc.).

[0194] The WTRU 302 can be configured to perform location determination (e.g., its own location determination). The WTRU 302 can be configured to assist the network (e.g., perform GNSS measurements, perform DL PRS measurements, transmit positioning SRS to the network, etc.). The configuration of the WTRU 302 can be based on, for example, a threshold related to the DL signal level of the serving cell. For example, the WTRU 302 can be configured to stop measurements (e.g., PRS and / or GNSS) and / or positioning related to UL signaling when the DL signal level (e.g., RSRP) of the serving cell rises above a certain level and / or is within a certain range. The WTRU 302 can be configured to start measurements or UL signaling when the signal of the serving cell falls below a certain level. Different DL signal level thresholds may be configured for different modes of location determination or assistance information provision (e.g., threshold_1 related to the performance of GNSS measurements, threshold_2 related to the performance of DL PRS measurements, and / or threshold_3 related to the performance of UL SRS signaling, etc.).

[0195] The WTRU 302 may be configured to perform location determination (e.g., its own location determination). The WTRU 302 may be configured to assist the network (e.g., perform GNSS measurements, perform DL PRS measurements, transmit positioning SRS to the network, etc.). The configuration of the WTRU 302 may be based on a threshold related to the current UL power level. For example, the WTRU 302 may be configured to stop measurements (e.g., PRS and / or GNSS) and / or positioning related to UL signaling when the WTRU 302 uses a UL power level that exceeds a specific level or is within a specific range (e.g., an absolute power level or a percentage of the maximum WTRU 302 power level). The WTRU 302 may be configured to start measurements or UL signaling when the power level drops below a specific level. Different power level thresholds may be configured for different modes of location determination or assistance information provision (e.g., threshold_1 related to the performance of GNSS measurements, threshold_2 related to the performance of DL PRS measurements, and / or threshold_3 related to the performance of UL SRS signaling, etc.).

[0196] Regarding implementing the methods described herein, the WTRU 302 may be configured to perform location determination in a manner other than stopping and / or starting location determination, based on, for example, different conditions. For example, when one or more of the conditions related to the battery level of the WTRU 302, the overheat level of the WTRU 302, the throughput level of the WTRU 302, the buffer level of the WTRU 302, the DL signal level of the WTRU 302, and / or the UL power usage level of the WTRU 302 are met, the WTRU 302 may perform location measurements in a relaxed manner. When the conditions are not met (e.g., no longer met), the WTRU 302 may perform location measurements as normal.

[0197] The WTRU 302 may be configured to conditionally report positioning information to the network. For example, the WTRU 302 may conditionally report its location information (e.g., location collected via GNSS and / or DL PRS measurements) depending on the difference between the location determined by the WTRU 302 and the location provided to the WTRU 302 by a positioning delegate (e.g., IAB nodes 304a - c). This difference may be referred to as a location disparity. For example, a threshold (e.g., in meters) may be specified, and for example, the WTRU 302 may send a location report to the network if (e.g., only if) the location disparity remains above the threshold.

[0198] For example, the WTRU 302 may be configured to report its location if (e.g., only if) the location disparity persists for a particular duration (e.g., x milliseconds).

[0199] For example, the WTRU 302 may be configured using a set of values for the location disparity and the duration of the detected location disparity. In the example, the WTRU 302 may be configured to report its location if a 0.5 - meter disparity is detected for more than 5 seconds, or a 1 - meter disparity is detected for more than 3 seconds, and / or a 4 - meter disparity is detected for more than 2 seconds.

[0200] For example, the WTRU 302 may be configured to report its location if (e.g., only if) the location disparity is detected more than a certain number of times (e.g., 3 times). For example, the WTRU 302 may be configured using a set of values for the location disparity and the number of times the location disparity is detected. For example, the WTRU 302 may be configured to report its location if a 0.5 - meter disparity is detected 6 or more times, or a 1 - meter disparity is detected 4 or more times, and / or a 4 - meter disparity is detected 2 or more times.

[0201] For example, the WTRU 302 may be configured to report its location information depending on (e.g., instead of and / or in addition to location disparity) timing information. In an example, the WTRU 302 may be configured to report its location every x milliseconds regardless of any location reports sent due to other triggers (e.g., location disparity). If location disparity triggered a location report, the duration (e.g., a timer) associated with the periodic report may be restarted.

[0202] For example, the WTRU 302 may be configured to report its location information depending on, for example, a change in location (e.g., absolute location or relative location). In an example, the WTRU 302 may be configured to report its location whenever its location has changed by x meters from the previous location report triggered by a location change, regardless of any location reports sent due to other triggers (e.g., location disparity and / or timing related location reports). The WTRU 302 may be configured to maintain the location included in the previous location report sent due to a location change. The WTRU 302 can use this location as a baseline location for determining a location change. If location disparity or timing information triggered a location report, the last reported location of the WTRU 302 may be updated to the location included in the last location report.

[0203] For example, the WTRU 302 may be configured to report its location information based on, for example, a threshold related to the power of the WTRU 302. In an example, the WTRU 302 may be configured to stop reporting location information when the battery level of the WTRU 302 drops below a configured threshold. The WTRU 302 may be configured to start reporting when the battery level of the WTRU 302 rises above the configured threshold.

[0204] For example, the WTRU 302 may be configured to report its own location information based on, for example, a threshold related to the overheating level of the WTRU 302. In an example, the WTRU 302 may be configured to stop reporting location information when the overheating level of the WTRU 302 rises above a configured threshold. The WTRU 302 may be configured to start reporting when the overheating level of the WTRU 302 falls below the configured threshold.

[0205] For example, the WTRU 302 may be configured to report its own location information based on, for example, a threshold related to the activity of the WTRU 302. In an example, the WTRU 302 may be configured to stop and / or skip reporting location information when the WTRU 302 has data to transmit. The WTRU 302 may be configured to defer transmitting location reports until it has other data to transmit.

[0206] For example, the WTRU 302 may be configured to report its own location based on, for example, a threshold related to the DL signal level of the serving cell (e.g., the signal levels of SSB, CSI-RS, and / or PRS). In an example, the WTRU 302 may be configured to stop reporting its location when the DL signal level of the serving cell (e.g., RSRP) rises above a certain level and / or is within a certain range. The WTRU 302 may be configured to start reporting when the serving cell falls below a certain level.

[0207] For example, the WTRU 302 may be configured to report its location based on, for example, a threshold related to the DL signal level of neighboring cells (e.g., the signal level of SSB and / or PRS). In an example, the WTRU 302 may be configured to stop reporting its location when the DL signal level of a neighboring cell (e.g., RSRP) rises above a certain level or is within a certain range. The WTRU 302 may be configured to start reporting when the serving cell drops below a certain level.

[0208] Regarding implementing the methods described herein, the WTRU 302 may be configured to perform location determination in a manner other than stopping and / or starting reporting its location based on, for example, different conditions. For example, the WTRU 302 may perform location reporting less frequently when one or more of the conditions described herein are met (e.g., the location disparity is small and / or the WTRU 302 battery level is below a threshold, etc.). The WTRU 302 may transmit more frequent location reports, for example, when the location disparity is large.

[0209] The WTRU may request to delegate / stop positioning. For example, the WTRU 302 may send a request to a network (e.g., IAB nodes 304a - c, gNB, LMF, etc.), and the request may indicate that the WTRU 302 prefers to delegate its positioning. For example, the WTRU 302 may send a request to the network, and this request may indicate the reason for the delegation (e.g., low battery level and / or WTRU overheating, etc.). The network may respond to the WTRU 302 with an acknowledgement. The acknowledgement may indicate to the WTRU 302 to stop performing positioning measurements and / or determinations. The acknowledgement may also indicate to the WTRU 302 to perform the measurements and / or determinations conditionally (e.g., as described herein).

[0210] The WTRU 302 may send a request to a network (e.g., IAB nodes 304a - c, gNB, LMF, etc.), and the request may indicate that the WTRU 302 prefers to send its location. For example, the WTRU 302 may send a request to the network, and this request may indicate reasons for not preferring to send a delegation report (e.g., low battery level and / or WTRU overheating, etc.). The network may respond to the WTRU 302 by way of an acknowledgement. The acknowledgement may indicate to the WTRU 302 to stop reporting its location and / or to report them conditionally (e.g., as described herein). In an example, the request asking to stop reporting its location and / or to report them conditionally may be a message (e.g., a new message and / or a message not associated with an existing message). In an example, the request asking to stop reporting its location and / or to report them conditionally may be a modification of a message (e.g., an existing message), such as WTRU 302 assistance information.

[0211] The WTRU 302 may continue to perform measurements via a non - mobile - based implementation (e.g., via GNSS). The WTRU 302 may be configured to send an instruction to the network to delegate positioning in the event that the determined location becomes less accurate (e.g., when the WTRU 302 enters an indoor area where location information is unavailable and / or less reliable).

[0212] The accuracy and / or delta of location information provided by a location delegate may be determined. For example, the WTRU 302 may be configured using timing information (e.g., a specified duration). The WTRU 302 may be configured using location margin information (e.g., an absolute offset and / or a relative offset) that may be associated with performing measurements. The WTRU 302 may be configured using location margin information while connected to a node that may be a location delegate. For example, the WTRU 302 may be configured to continue performing positioning measurements over a specified duration (e.g., in response to connecting to a location delegate). For example, the WTRU 302 may be configured to compare location information determined by the WTRU 302 (e.g., based on location measurements) with location information provided by the delegate.

[0213] For example, during a specified duration, the WTRU 302 may determine a location that is the same as the location provided by the location delegate within a specified absolute and / or relative location margin. The WTRU 302 may consider that the location determination provided by the delegate is accurate enough and may stop performing location determination (e.g., performing GNSS or PRS measurements). The WTRU 302 may, for example, check the location accuracy provided by the delegate to the WTRU 302 and send an indication (e.g., a stop indication) indicating that it has stopped performing measurements to a network (e.g., the LMF).

[0214] The WTRU 302 can compare the location disparity between the location information it has determined and the instructions provided by the location delegate over a specified duration. The WTRU 302 can determine the difference between the two (e.g., exceeding a certain margin). The WTRU 302 can determine whether the difference is consistent (e.g., within another specified margin of x meters). The WTRU 302 can consider the location information provided by the delegate to be accurate and can stop location determination (e.g., performing GNSS or PRS measurements). The WTRU 302 can send an indication to the network (e.g., the LMF) indicating, for example, that the WTRU 302 has checked the location accuracy provided by the delegate and / or has detected a consistent difference between the two (e.g., a consistent difference of x meters) and has stopped performing measurements. In response, the LMF can apply the difference in addition to the location provided by the delegate, for example, to determine a more accurate location of the WTRU 302.

[0215] The WTRU 302 can be configured to start location measurements and / or determinations (e.g., sporadically or periodically) to check whether the location provided by the delegate remains accurate and / or whether the difference remains consistent. For example, the WTRU 302 can be configured to perform location determination / comparison every minute. The WTRU 302 can send an indication to the network if the location information remains accurate and / or consistent.

[0216] The methods described herein for performing and / or determining a location may be applicable when the network performs a location determination (e.g., based on PRS measurement reports transmitted by the WTRU 302 and / or the WTRU 302 transmitting SRS). For example, the WTRU 302 may periodically transmit PRS measurements while it is connected to a location delegate. The network may determine the location of the WTRU 302 based on the reports. The network may compare the determined location of the WTRU 302 with the location reported by the delegate. The network may consider consistent delta values reported by the WTRU 302 (e.g., previously). If the network (e.g., LMF) determines that the location is not valid (e.g., is no longer valid), the network may send an instruction to the WTRU 302. This instruction may indicate that the WTRU 302 may start performing location measurements and / or determinations, start transmitting location reports, and / or start transmitting UL SRS signals for location determination by the network. In an example, the WTRU 302 may transmit to the network a location determined via another means (e.g., via GNSS) based on some configuration (e.g., periodically). The network may use this information to compare and / or determine the location accuracy of the delegate for the WTRU 302.

[0217] The WTRU 302 may be configured to select one or more of a plurality of location delegates. For example, a plurality of delegates may be available to a given WTRU 302. One or more of the plurality of location delegates may meet the location delegation requirements and / or conditions of the WTRU 302 (e.g., if the signal level between the location delegate and the WTRU 302 rises above a required threshold). One or more of the plurality of location delegates that meet the location delegation requirements of the WTRU 302 may be referred to as candidate location delegates.

[0218] The WTRU 302 may be configured to determine details of the positioning capabilities of a location delegate. For example, the WTRU 302 may be configured to determine the positioning method employed by the delegate (e.g., UE-assisted, UE-based, DL-based, and / or UL-based, etc.). For example, the WTRU 302 may be configured to determine the accuracy level and / or estimate of the positioning performed by the location delegate (e.g., confidence intervals in percentage or absolute value, and / or confidence level and / or accuracy level and / or percentage, etc.). For example, the WTRU 302 may be configured to determine how the location delegation is provided. Methods of providing a location delegate that the WTRU 302 can determine include, for example, push mechanisms such as broadcast (e.g., may include information regarding location broadcast periodicity), pull mechanisms such as by WTRU 302 request, and / or a combination where the WTRU 302 can request and / or subscribe to location delegation and the location delegate can provide locations to the WTRU 302 at an agreed-upon periodicity (e.g., supported periodicity).

[0219] The WTRU 302 may receive (e.g., directly or indirectly) information regarding the capabilities of the location delegate from the location delegate itself. For example, the WTRU 302 may send a request to the location delegate to transmit its positioning capabilities and / or current positioning mechanism. For example, information regarding the location delegate capabilities and / or the current positioning mechanism being used may be provided to the WTRU 302 via broadcast signaling from the location delegate.

[0220] Alternatively or additionally, the WTRU 302 may receive information regarding the capabilities of one or more location delegates from a network (e.g., the current serving gNB, and / or the LMF, etc.). In an example, the information regarding the capabilities of one or more location delegates (e.g., received from the network) may include a list of pairs of location delegate identification information (e.g., mobile cell ID) and corresponding capabilities. For example, the WTRU 302 may send a request to the network (e.g., the current serving gNB, LMF, etc.) regarding the location delegate capabilities and / or requirements regarding the current positioning mechanism used by a particular location delegate. In some examples, the WTRU 302 may send a request to the network (e.g., the current serving gNB, and / or the LMF, etc.) for a list of location delegates having a particular positioning capability.

[0221] The WTRU 302 may be configured to select a location delegate (e.g., from among one or more location delegates that meet the WTRU 302's location delegation requirements / conditions) that, for example, satisfies the best signal levels (e.g., RSRP, RSRQ, etc.), is the most accurate, can provide location via a push mechanism, and / or has more frequent updates.

[0222] The WTRU 302 may consider handovers, cell reselections, and / or measurement capabilities of one or more serving cells when determining location delegation.

[0223] In an example, the WTRU 302 can be configured to apply a positive offset on measurements of cells that can provide position delegation (e.g., the current serving cell, and / or neighboring cells, etc.). Alternatively or additionally, the WTRU 302 can be configured to apply a negative offset on measurements of cells that do not provide position delegation (e.g., the current serving cell, and / or neighboring cells, etc.). In an example, handover and / or cell reselection to a cell that supports position delegation may be prioritized compared to a cell that does not support position delegation. For example, if the second cell supports position delegation and the first cell does not support position delegation, the WTRU 302 may perform a handover and / or cell reselection to a second neighboring cell that has a signal level slightly worse than that of the first neighboring cell.

[0224] The WTRU 302 may be configured using different offset values / ranges. For example, depending on the delegated position capabilities (e.g., different accuracy levels, positioning techniques, different values or ranges of values for position update periodicity, etc.).

[0225] The WTRU 302 can be configured to apply an offset depending on the current state of the WTRU 302 (e.g., apply different offsets). For example, the WTRU 302 can be configured to apply an offset to the position delegate cell and / or use a higher offset when the battery level of the WTRU 302 drops below a certain level and / or when the WTRU 302 determines that its own positioning determination is no longer accurate (e.g., when the WTRU 302 is indoors and below the accuracy threshold, etc.).

[0226] The WTRU 302 can send location delegation requests / interests (e.g., via MAC CE) to the mobile IAB nodes 304a-c. The mobile IAB (e.g., the MT of the mobile IAB) can send a request for a positioning configuration (e.g., a PRS configuration and / or an SRS configuration) to a network (e.g., a donor CU 310 and / or an LMF, etc.). For example, the mobile IAB can send a delegation request when it receives a certain number of delegation requests from different WTRU 302s and / or when the mobile IAB serves a WTRU that exceeds a certain percentage. The request can indicate the reason for the requested positioning configuration (e.g., including the number or percentage of WTRU 302s that requested the delegation and / or information regarding what type of positioning accuracy / mechanism the WTRU 302 is interested in, etc.). Based on this request, the network can configure the mobile IAB using the desired positioning measurements and / or signaling configuration. The mobile IAB can notify the WTRU 302 that requested the positioning delegation when the mobile IAB is ready to provide positioning delegation (e.g., broadcast signaling and / or individual MAC CE, etc.).

[0227] Figures 4A-4C illustrate a WTRU 402 that requests, participates in, and ultimately stops using a delegation candidate. In Figure 4A, the system 400 can include a moving train. The moving train can include a network device 404 (e.g., an IAB node) connected to a network and a plurality of WTRU 406. In the system 400, the WTRU 402 can be located outside the coverage area 408 of the network device 404 (e.g., outside the train), and thus can perform its own location determination and / or measurements.

[0228] In system 420 (see, e.g., FIG. 4B), the WTRU 402 can enter the coverage area 408 of the network device 404. The WTRU 402 can connect to the network device 404. The WTRU 402 can select the network device 404 as a positioning delegate. For example, the WTRU 402 can start using the location information and / or measurements of the network device 404 and / or can stop performing its own location determination and / or measurements. In some examples, the WTRU 402 can receive the location determination and / or measurements of the network device 404 via broadcast information received from the network device 404 and / or within one or more messages sent from the network device 404 in response to a request sent by the WTRU 402. In some examples, the WTRU 402 can receive positioning configuration information (e.g., from the network device 404 when entering the coverage area 408). The positioning configuration information can include an indication of one or more positioning delegate candidates for the WTRU 402.

[0229] The positioning configuration information can include an indication of one or more conditions for starting or stopping positioning delegation. The WTRU 402 can determine to use the network device 404 as a positioning delegate based on detecting that the conditions for starting positioning delegation are met. The WTRU 402 can send an indication (e.g., a start indication) to the network (e.g., the network device 404) indicating that the WTRU has started using the network device 404 as a positioning delegate. Further, in some examples, the WTRU 402 can send a location disparity report to the network device, where the location disparity report indicates the difference between the location of the WTRU 402 and the location of the positioning delegate.

[0230] In system 440 (see, e.g., FIG. 4C), the WTRU 402 can exit the coverage area 408 of the network device 404 and, in response, can stop using the network device 404 as a positioning delegate. For example, the WTRU 402 can detect that conditions for stopping positioning delegation are met. The WTRU 402 can send an indication (e.g., a stop indication) to the network (e.g., the network device 404) indicating that the WTRU has stopped using the network device 404 as a positioning delegate. The WTRU 402 can then resume performing its own location determination and / or measurements.

[0231] FIG. 5 depicts a flowchart of an exemplary procedure 500 performed by a WTRU (e.g., WTRU 302 and / or WTRU 402). The WTRU can perform procedure 500, e.g., send a location delegation request, monitor conditions for using a positioning delegate, and / or send an indication to the network that the WTRU has started and / or stopped performing positioning measurements and determinations, to obtain configurations related to positioning delegation.

[0232] At 502, the WTRU can send a location delegation request to a network device (e.g., an IAB node). The WTRU can send a message requesting to perform positioning delegation to a network device (e.g., an IAB node), and the location delegation request can include a reason for the request. At 504, the WTRU can receive a configuration related to location delegation. The configuration can include, e.g., delegate positioning candidate information and / or trigger conditions for determining whether to use a positioning candidate. At 506, the WTRU can monitor conditions for starting to use a location delegate.

[0233] At 508, the WTRU determines whether the conditions for starting the use of the location delegate are satisfied. If the WTRU determines that the conditions for starting the use of the location delegate are not satisfied, the WTRU may continue to monitor the conditions for starting the use of the location delegate at 510. If the WTRU determines that the conditions for starting the use of the location delegate are satisfied, the WTRU may stop performing location measurements and / or determinations at 512. If the WTRU determines that the conditions for starting the use of the location delegate are satisfied, the WTRU may start obtaining location information from the positioning delegate candidates at 512.

[0234] The WTRU may perform measurements related to positioning reference signal (PRS) transmission. The WTRU may report the PRS measurement values based on detecting that the conditions for invalidating the positioning delegation are satisfied for the delegation candidate. After connecting to the positioning delegate, the WTRU may perform positioning measurements over a specified duration and compare the location information determined by the WTRU with the location information provided by the positioning delegate.

[0235] At 514, the WTRU has selected a location delegate and may send an indication (e.g., a start indication) to a network device (e.g., an IAB node) that location delegation has been initiated and / or is still in progress. The WTRU may send an indication to a network device (e.g., an IAB node) that the WTRU is using at least one positioning delegation candidate for positioning, based on detecting that the conditions for enabling (e.g., starting) positioning delegation for at least one positioning delegation candidate are met. The indication may include location information indicating the location of the positioning delegation candidate. In an example, the WTRU may receive a positioning request from a network device (e.g., an IAB node), and then the WTRU may send an indication to the network device (e.g., an IAB node) in response to the positioning request.

[0236] The conditions for enabling (e.g., starting) positioning delegation may include, for example, the WTRU battery level falling below a threshold, the WTRU connecting to at least one positioning delegation candidate, and / or the WTRU detecting that it is within the proximity specified for at least one positioning delegation candidate. The conditions for enabling positioning delegation may include the WTRU detecting that it is within the proximity specified for at least one positioning delegation candidate based on signal strength measurements received from the positioning delegation candidate.

[0237] The WTRU may send a location parallax report to the network device, where the location parallax report indicates the difference between the location of the WTRU and the location of the location delegate.

[0238] At 516, the WTRU determines whether the conditions for stopping the use of the location delegate are met. If the WTRU determines that the conditions for stopping the use of the location delegate are not met, the WTRU may continue to monitor the conditions for stopping the use of the location delegate and may determine whether the conditions for stopping the use of the location delegate are met at 516. In some examples, if the WTRU determines that the conditions for stopping the use of the location delegation are not met, the WTRU may send two or more indications (e.g., stop indications) indicating that the location delegation remains in progress. If the WTRU determines that the conditions for stopping the use of the location delegate are met, the WTRU may, at 518, stop the use of the location delegation (e.g., invalidate the location delegation) and may start performing its own location measurements and / or determinations.

[0239] At 520, the WTRU may send an indication (e.g., a stop indication) to a network device (e.g., an IAB node) that the location delegation has stopped (e.g., been invalidated) and / or that the WTRU is performing its own location measurements and / or determinations. The WTRU may send an indication to the network device that it has stopped using at least one positioning delegation candidate for positioning based on detecting that the conditions for invalidating the positioning delegation are met for at least one positioning delegation candidate.

[0240] In some examples, the WTRU may perform 502 - 514 (e.g., 502 - 514 only) and may not perform 516 - 522. For example, the WTRU may perform only 502 - 514 if, for example, the WTRU is disconnected from the network.

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

[0242] While the implementations described herein may take into account 3GPP-specific protocols, it will be understood that the implementations described herein are not limited to this scenario and may be applicable to other wireless systems. For example, while the solutions described herein take into account LTE, LTE-A, New Radio (NR), or 5G-specific protocols, it will be understood that the solutions described herein are not limited to this scenario and may be further applicable to other wireless systems. For example, the system has been described with reference to 3GPP, 5G, and / or NR network layers, but the envisioned embodiments extend beyond implementations that use a specific network layer technology. Similarly, potential implementations span all types of service layer architectures, systems, and embodiments. The techniques described herein can be applied independently and / or in combination with other resource configuration techniques.

[0243] The processes described herein may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (sent via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, magnetic media such as read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, internal hard disks, and removable disks, magneto-optical media, and / or optical media such as compact disc (CD)-ROM disks and / or digital versatile disk (DVD), etc. A processor associated with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC (Radio Network Controller), and / or any host computer.

[0244] It is understood that an entity implementing the processes described herein may be a logical entity implemented in the form of software (e.g., computer-executable instructions) stored in the memory of a mobile device, network node, or computer system and executed on its processor. That is, the process may be implemented in the form of software (e.g., computer-executable instructions) stored in the memory of a mobile device and / or a network node such as a node or computer system, and the computer-executable instructions, when executed by the processor of the node, implement the processes discussed. Also, it is understood that any transmission and reception processes illustrated in the drawings may be implemented by the communication circuit of the node under the control of the processor of the node and the computer-executable instructions (e.g., software) that it executes.

[0245] The various technologies described herein may be implemented in relation to hardware or software, or a combination of both as necessary. Accordingly, implementations of the subject matter described herein, apparatuses, or specific aspects or portions thereof may take the form of program code (e.g., instructions) embodied in a tangible medium including any other machine-readable storage medium, and when the program code is loaded and executed on a machine such as a computer, the machine becomes an apparatus for implementing the subject matter described herein. When the program code is stored in a medium, the program code may be stored in one or more media that collectively execute actions, i.e., the one or more media together contain code for executing the actions, provided that when there are two or more individual media, no particular portion of the code need be stored on any particular medium. In the case of program code execution on a programmable device, the computing device generally includes a processor, a storage medium readable by the processor (including volatile memory and non-volatile memory and / or storage elements), at least one input device, and at least one output device. For example, one or more programs that can implement or utilize the processes described in relation to the subject matter described herein through the use of, e.g., an API, reusable controls, etc. Such programs are preferably implemented in a high-level procedural or object-oriented programming language for communicating with a computer system. However, the programs can be implemented in assembly language or machine language as necessary. In any case, the language may be a compiled or interpreted language and may also be combined with a hardware implementation.

[0246] Exemplary embodiments may refer to utilizing aspects of the subject matter described herein in the environment of one or more stand-alone computing systems, but the subject matter described herein is not so limited and may rather be implemented in connection with any computing environment such as a network or distributed computing environment. Still further, aspects of the subject matter described herein may be implemented within or across multiple processing chips or devices, and storage may be similarly affected across multiple devices. Such devices may include, by way of example, personal computers, network servers, handheld devices, supercomputers, or computers integrated into other systems such as automobiles and airplanes.

[0247] In describing preferred embodiments of the subject matter of this disclosure, specific terms are used for clarity as illustrated in the figures. However, the claimed subject matter is not intended to be limited to the specific terms so selected, and it is to be understood that each specific element includes all technical equivalents that operate in a similar manner to achieve a similar purpose.

Claims

1. A wireless transmit / receive unit (WTRU) comprising a processor and a memory, wherein the processor and the memory receive positioning configuration information including an indication of one or more positioning delegation candidates for the WTRU and an indication of one or more conditions for starting or stopping the use of positioning delegation, detect that a condition for starting the use of the positioning delegation is satisfied for at least one of the positioning delegation candidates, based on the detection that the condition for starting the use of the positioning delegation is satisfied for the at least one positioning delegation candidate, transmit to the network a start indication that the WTRU is using the at least one positioning delegation candidate for positioning, detect that a condition for stopping the positioning delegation is satisfied for the at least one positioning delegation candidate, and based on the detection that the condition for stopping the positioning delegation is satisfied for the at least one positioning delegation candidate, transmit to the network a stop indication that the WTRU has stopped using the at least one positioning delegation candidate for positioning, a WTRU configured as such.

2. The WTRU according to claim 1, wherein the processor and the memory are configured to transmit to the network a message requesting to perform positioning delegation.

3. The condition for starting the use of the positioning delegation includes detecting that the WTRU is within a specified proximity to the at least one positioning delegation candidate based on a signal strength measurement received from the at least one positioning delegation candidate, the WTRU according to claim 2.

4. The conditions for starting the use of the positioning delegation include one or more of the following: the WTRU battery level falling below a threshold, connecting to the at least one positioning delegation candidate, or detecting that the WTRU is within the proximity specified for the at least one positioning delegation candidate. The WTRU according to claim 1.

5. The processor and the memory are configured to perform measurements of one or more positioning reference signal (PRS) transmissions and report PRS measurement values based on detecting that the conditions for stopping the use of the positioning delegation are satisfied for the at least one positioning delegation candidate. The WTRU according to claim 1.

6. The start indication includes location information indicating the location of the at least one positioning delegation candidate. The WTRU according to claim 1.

7. The processor and the memory are configured to receive a positioning request from a network, and the start indication is transmitted to the network in response to the positioning request. The WTRU according to claim 6.

8. The processor and the memory are configured to transmit a location parallax report to the network, and the location parallax report indicates the difference between the location of the WTRU and the location of the positioning delegate. The WTRU according to claim 1.

9. The processor and the memory are configured to transmit the location parallax report to the network based on the difference exceeding a parallax threshold over a predetermined time period. The WTRU according to claim 8.

10. The processor and the memory are After connecting to a positioning delegate, performing positioning measurements over a specified duration, and comparing the location information determined by the WTRU with the location information provided by the positioning delegate, the WTRU according to claim 1. **Claim 11** A method performed by a wireless transmit / receive unit (WTRU), receiving positioning configuration information including an indication of one or more positioning delegation candidates for the WTRU and an indication of one or more conditions for starting or stopping the use of positioning delegation; detecting that a condition for starting the use of the positioning delegation is satisfied for at least one of the positioning delegation candidates; transmitting to the network a start indication that the WTRU is using the at least one positioning delegation candidate for positioning based on detecting that the condition for starting the use of the positioning delegation is satisfied for the at least one positioning delegation candidate; detecting that a condition for stopping the use of the positioning delegation is satisfied for the at least one positioning delegation candidate; transmitting to the network a stop indication that the WTRU has stopped using the at least one positioning delegation candidate for positioning based on detecting that the condition for stopping the use of the positioning delegation is satisfied for the at least one positioning delegation candidate, the method comprising. **Claim 12** The method according to claim 11, further comprising transmitting to the network a message requesting to perform positioning delegation. **Claim 13** The method according to claim 11, wherein the condition for starting the use of the positioning delegation includes one or more of the following: the WTRU battery level is below a threshold value, connecting to the at least one positioning delegation candidate, or detecting that the WTRU is within the proximity specified for the at least one positioning delegation candidate.

14. The method according to claim 13, wherein the condition for starting the use of the positioning delegation includes detecting that the WTRU is within the proximity specified for the at least one positioning delegation candidate based on a signal strength measurement received from the at least one positioning delegation candidate.

15. Based on detecting that the condition for stopping the positioning delegation is satisfied for the at least one positioning delegation candidate, performing measurements of one or more positioning reference signal (PRS) transmissions and reporting the PRS measurement values. The method according to claim 11, further comprising the above.

16. The method according to claim 11, wherein the indication includes location information indicating the location of the at least one positioning delegation candidate.

17. The method according to claim 16, further comprising receiving a positioning request from a network, wherein the indication is transmitted to the network in response to the positioning request. The method according to claim 16.

18. Transmitting a location parallax report to the network based on the difference exceeding a parallax threshold value over a predetermined time period. The method according to claim 11, further comprising the above.

19. A wireless transmit / receive unit (WTRU) comprising a processor and a memory, wherein the processor and the memory receive positioning configuration information. Based on the positioning configuration information, select a positioning delegation candidate for positioning, send a start indication to the network that the WTRU is using the positioning delegation candidate for positioning, and A WTRU configured to send a stop indication to the network that the WTRU has stopped using the positioning delegation candidate for positioning.

20. The positioning configuration information includes an indication of one or more positioning delegation candidates for the WTRU and an indication of one or more conditions for starting or stopping positioning delegation, and the one or more positioning delegation candidates indicated by the positioning configuration information include the selected positioning delegation candidate, The processor and the memory are detect that the conditions for starting positioning delegation are met for the selected positioning delegation candidate, Based on detecting that the conditions for starting positioning delegation are met for the selected positioning delegation candidate, send the start indication to the network that the WTRU is using the selected positioning delegation candidate for positioning, detect that the conditions for stopping positioning delegation are met for the selected positioning delegation candidate, and The WTRU according to claim 19, configured to send the stop indication to the network that the WTRU has stopped using the selected positioning delegation candidate for positioning based on detecting that the conditions for stopping the use of the positioning delegation are met for the selected positioning delegation candidate.

Images