METHOD AND WTRU FOR POSITIONING WITH REDUCED LATENCY IN A WIRELESS COMMUNICATION SYSTEM - Patent application

Abstract

The present disclosure relates to a method and apparatus for performing positioning of a wireless transmitting and / or receiving unit (WTRU) in a wireless communication system. In an embodiment, a WTRU may receive configuration information indicating one or more measurement gap patterns, which may be associated with any of a measurement gap length, a measurement gap periodicity, and a measurement gap identifier. The WTRU may measure a first positioning reference signal transmission during a first measurement gap period and may transmit a request for a first measurement gap pattern of the one or more indicated measurement gap patterns based on the measured first positioning reference signal transmission. The WTRU may receive second information indicating to activate a second measurement gap pattern of the one or more indicated measurement gap patterns and may measure the second positioning reference signal transmission during the second measurement gap period.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 168,142, filed March 30, 2021, U.S. Provisional Patent Application No. 63 / 228,787, filed August 3, 2021, U.S. Provisional Patent Application No. 63 / 249,168, filed September 28, 2021, U.S. Provisional Patent Application No. 63 / 257,414, filed October 19, 2021, and U.S. Provisional Patent Application No. 63 / 275,175, filed November 3, 2021, the contents of each of which are incorporated by reference herein.

[0002] The present disclosure relates to a method and apparatus for performing positioning of a wireless transmit and / or receive unit (WTRU) in a wireless communication system. [Background technology]

[0003] The present disclosure relates to wireless and / or wired communication networks, including but not limited to methods, apparatus, systems, etc. directed to positioning in wireless communication systems. [Brief description of the drawings]

[0004] A more detailed understanding can be had from the following detailed description, given in conjunction with the drawings that accompany this specification by way of example. The figures in such drawings, like the detailed description, are illustrative. Thus, the figures and detailed description should not be considered as limiting, as other equally effective examples are possible and likely. Moreover, like reference numerals ("ref") in the figures ("FIG") indicate like elements. [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system. [Figure 1B] FIG. 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A. [Figure 1C]FIG. 1B is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communication system illustrated in FIG. 1A. [Figure 1D] FIG. 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system illustrated in FIG. 1A. [Diagram 2] FIG. 1 is a timing diagram illustrating various parameters associated with a measurement gap. [Diagram 3] FIG. 1 is a signaling flow diagram illustrating an example of signal exchange between a WTRU, a gNB, and a Location Management Function (LMF). [Figure 4] FIG. 11 is a timing diagram illustrating an example of the difference between an initial measurement gap pattern and a newly requested measurement gap pattern. [Diagram 5] 1 is a set of three timing diagrams illustrating possible measurement gap patterns according to an embodiment. [Figure 6] 1 is a set of three timing diagrams showing three examples of measurement gap patterns. [Figure 7] FIG. 11 is a timing diagram showing an example of an initial measurement gap pattern and an example of a newly requested measurement gap pattern. [Figure 8] FIG. 11 is a timing diagram illustrating another example of an initial measurement gap pattern and another example of a newly requested measurement gap pattern. [Figure 9] FIG. 11 is a signal flow diagram illustrating an example of a signal exchange between a WTRU, a gNB, and an LMF to request a new positioning reference signal (PRS) configuration. [Figure 10] FIG. 1 is a timing diagram illustrating an example of PRS prioritization window durations. [Figure 11] 1 illustrates an example method for configuring measurement gaps for WTRU positioning determination. [Figure 12] 13 illustrates another example of a method for configuring measurement gaps for WTRU positioning determination. [Figure 13]13 illustrates another example of a method for configuring measurement gaps for WTRU positioning determination. [Figure 14] 13 illustrates another example of a method for configuring measurement gaps for WTRU positioning determination. [Figure 15] FIG. 1 illustrates an example of a method for requesting a measurement gap configuration. [Figure 16] FIG. 13 illustrates another example of a method for requesting a measurement gap configuration. [Figure 17] FIG. 13 illustrates another example of a method for requesting a measurement gap configuration. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0005] 1. Introduction In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the embodiments and / or examples disclosed herein. It will be understood, however, that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the following description. Furthermore, embodiments and examples not specifically described herein may be practiced in place of, or in combination with, the embodiments and other examples explicitly, implicitly and / or inherently described, disclosed or otherwise provided herein (collectively "provided").

[0006] 1.1 Exemplary Network for Implementation of the Embodiments 1A illustrates an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcasts, etc., to multiple wireless users. The communication system 100 may enable the multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communications 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 multicarrier (FBMC), etc.

[0007] 1A, communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of 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, any of which may be referred to as a “station” and / or “STA,” may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated processing chain context), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.

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

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

[0010] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an 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 air interface 116 may be established using any suitable radio access technology (RAT).

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

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

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

[0014] 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, e.g., using dual connectivity (DC) principles. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).

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

[0016] 1A may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as a location of a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio 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 may implement a radio technology, such as IEEE 802.15, to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). As shown in FIG. 1A, the base station 114b may 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.

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

[0018] The CN 106 / 115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a public switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP), and / or the internet protocol (IP) of the TCP / IP Internet protocol suite. The network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the network 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

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

[0020] 1B is a system diagram illustrating an example WTRU 102. As shown in FIG. 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, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be understood that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0021] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

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

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

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

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

[0027] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding a current location of the WTRU 102. In addition to or in lieu of information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of signals being received from two or more nearby base stations. It will be understood that the WTRU 102 may obtain location information by way of any suitable location determination method while remaining consistent with an embodiment.

[0028] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), 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 and / or augmented reality (VR / AR) device, an activity tracker, and the like. The peripherals 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.

[0029] The WTRU 102 may include a full-duplex radio where the transmission and reception of some or all of the signals (e.g., associated with a particular subframe for both the UL (e.g., for transmission) and the downlink (e.g., for reception)) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit 139 to reduce and or substantially eliminate self-interference either through hardware (e.g., chokes) or signal processing via a processor (e.g., via a separate processor (not shown) or processor 118). In an embodiment, the WTRU 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 the UL (e.g., for transmission) or the downlink (e.g., for reception)).

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

[0031] 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 an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a may, for example, use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

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

[0033] 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 shown 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.

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

[0035] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-eNode B handover, triggering paging when DL data is available to the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, etc.

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

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

[0038] Although the WTRU is depicted in FIGS. 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may use a wired communications interface (e.g., temporarily or permanently) with the communications network.

[0039] In an exemplary embodiment, the other network 112 may be a WLAN.

[0040] A WLAN in infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating from outside the BSS to the STAs may arrive through the AP and be delivered to the STAs. Traffic originating from the STAs to destinations outside the BSS may be sent to the AP and transmitted to the respective destination. Traffic between STAs within the BSS may be transmitted, for example, through the AP, where the source STA may transmit traffic to the AP, which may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be viewed and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be transmitted between the source STA and the destination STA (e.g., directly between them) in a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may be referred to herein as an "ad-hoc" communication mode.

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

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

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

[0044] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz and 20 MHz bandwidths in TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter-type control / machine-type communication, such as MTC devices in macro coverage areas. MTC devices may have specific capabilities, including, for example, support for (e.g., support only for) specific and / or limited bandwidths. MTC devices may include batteries with above-threshold battery life (e.g., to maintain very long battery life).

[0045] WLAN systems that may support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that may be designated as a primary channel. 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 may be configured and / or limited by the STAs among all STAs operating in the BSS that support the smallest bandwidth operating mode. In an 802.11ah example, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only) the 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the state of the primary channel. For example, if the primary channel is busy due to STAs (that only support the 1 MHz mode of operation) transmitting to the AP, the entire available frequency band may be considered busy even though most of the frequency band may remain idle and available for use.

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

[0047] 1D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As mentioned above, the RAN 113 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using NR radio technology. The RAN 113 may also communicate with the CN 115.

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

[0049] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting different lengths of absolute time).

[0050] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing another RAN (e.g., eNode-Bs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate with and connect to a gNB 180a, 180b, 180c while also communicating with and connecting to another RAN, such as an eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, while the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0051] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the 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, routing of control plane information to Access and Mobility Management Functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.

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

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

[0054] The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 115 via an N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 115 via an N4 interface. The SMFs 183a, 183b may select and control the UPFs 184a, 184b and configure the routing of traffic through the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0055] The UPFs 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPFs 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0056] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or communicate with an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. Additionally, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In an embodiment, the WTRUs 102a, 102b, 102c may be connected to 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.

[0057] 1A-1D and the corresponding description thereof, one or more or all of the functions described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNodeBs 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). The emulation devices may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0058] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or an operator network environment. For example, one or more emulation devices may perform one or more or all functions while fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices in the communication network. One or more emulation devices may perform one or more or all functions while temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation devices may be directly coupled to another device for testing purposes and / or may perform testing using terrestrial wireless communication. The one or more emulation devices may perform one or more functions, inclusive, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in test scenarios in a test lab and / or in an undeployed (e.g., test) wired and / or wireless communication network to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, for example, one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0059] In Rel.16 (3GPP), downlink, uplink, and downlink and uplink positioning methods may be used.

[0060] In a downlink positioning method, positioning reference signals (PRS) may be transmitted to a WTRU from multiple transmit / receive points (TRPs) of a wireless communication network. The WTRU may observe multiple reference signals and measure the arrival time difference between pairs of PRS. For example, the WTRU may return (e.g., send information indicative of) a measured reference signal time difference (RSTD) to a location management function (LMF). For example, the WTRU may return (e.g., send information indicative of) a measured reference signal received power (RSRP) for (e.g., each) PRS. Based on the returned measurements, the LMF may perform positioning of the WTRU. In another example, the WTRU may report (e.g., send information indicative of) an RSRP for a downlink (DL) angle-based positioning method.

[0061] In an uplink positioning method, the WTRU may transmit, for example, a sounding reference signal (SRS) for positioning configured by the radio resource control (RRC) to either the reception point (RP) or the TRP. In the case of a timing-based method, the TRP may measure the relative time of arrival (RTOA) of the received SRS signal and report the measurement (e.g., send information indicative thereof) to the LMF. In the angle-based uplink positioning method, either the RP or the TRP may measure the angle of arrival and report it (e.g., send information indicative thereof) to the LMF.

[0062] For example, in either the uplink or downlink positioning method, the WTRU may measure the Rx-Tx time difference between the received PRS and the transmitted SRS. Information indicative of the Rx-Tx time difference may be transmitted to the LMF. The WTRU may also report (e.g., send information indicative of) the measured RSRP for the PRS, and the TRP may calculate the Rx-Tx difference between the received SRS and the transmitted PRS.

[0063] A "DL positioning method" may be referred to herein as any positioning method that may be based on a downlink reference signal, such as a PRS. In such positioning techniques, the WTRU may receive multiple reference signals from the TP and measure any of the DL RSTD and RSRP. Examples of DL positioning methods may include any of the Downlink-Angle-of-Departure (DL-AoD) and Downlink-Time-Difference-of-Arrival (DL-TDoA) positioning.

[0064] A "UL positioning method" may be referred to herein as any positioning technique that may be based on an uplink reference signal, such as SRS for positioning. In such a technique, the WTRU may transmit SRS to multiple RPs or TRPs, which may measure any of the UL RTOA and RSRP. Examples of UL positioning methods may include any of the uplink-time difference of arrival (UL-TDoA) positioning and uplink-angle of arrival (UL-AoA) positioning.

[0065] A "DL and UL positioning method" may be referred to herein as any positioning method that may be based on both uplink and downlink reference signals for positioning. In an example, a WTRU may transmit an SRS to multiple TRPs and a gNB may measure an Rx-Tx time difference. The gNB may measure an RSRP for the received SRS. A WTRU may measure an Rx-Tx time difference for PRS transmitted from multiple TRPs. The WTRU may measure an RSRP for the received PRS. The Rx-Tx difference, and for example, the measured RSRP at the WTRU and the gNB, may be used to determine (e.g., calculate) a round trip time. The Rx and Tx difference may be referred to herein as the difference between the arrival time of a reference signal transmitted by a TRP and the transmission time of a reference signal transmitted from the WTRU. An example of a DL and UL positioning method may be a multi-RTT (round trip time) positioning.

[0066] DL-based positioning (and, e.g., DL and UL positioning) may be either WTRU-based (e.g., the WTRU may perform the positioning) or WTRU-assisted (e.g., the network may perform the positioning operation using measurement reports sent from the WTRU).

[0067] In the embodiments described herein, the term "network" may include any of AMF, LMF, and NG-RAN.

[0068] The terms "pre-configured" and "configured" may be used interchangeably throughout the embodiments described herein.

[0069] The terms "non-serving gNB" and "neighboring gNB" may be used interchangeably throughout the embodiments described herein.

[0070] The terms “gNB,” “base station,” and “TRP” may be used interchangeably throughout the embodiments described herein.

[0071] The terms "PRS" and "PRS resource" may be used interchangeably throughout the embodiments described herein.

[0072] The terms "PRS" and "PRS resource" may be used interchangeably throughout the embodiments described herein. The above-mentioned terms "PRS" and "PRS resource" may belong to different PRS resource sets.

[0073] The terms "PRS," "DL-PRS," and "DL PRS" may be used interchangeably throughout the embodiments described herein.

[0074] The terms "RRC IDLE," "IDLE," and "idle" may be used interchangeably throughout the embodiments described herein and may refer to any idle state of a WTRU according to any communication network.

[0075] The terms "RRC INACTIVE", "INACTIVE", and "inactive" may be used interchangeably throughout the embodiments described herein and may refer to any inactive state of a WTRU with any communication network.

[0076] The terms "RRC CONNECTED," "CONNECTED," and "connected" may be used interchangeably throughout the embodiments described herein and may refer to any connection state of a WTRU with any communication network (e.g., at least one connection with the network may be established).

[0077] The terms "measurement gap" and "measurement gap pattern" may be used interchangeably throughout the embodiments described herein. The term "measurement gap pattern" as mentioned above may include parameters such as, for example, any of the measurement gap duration, the measurement gap repetition period, and the measurement gap periodicity.

[0078] The term "PRS resource" may be used to refer to a time and / or frequency resource (eg, OFDM symbol, resource element) occupied by a PRS.

[0079] 1.2 Positioning measurements in networks The WTRU may, for example, send a request (e.g., information indicative thereof) to initiate measurements for positioning, and the WTRU may receive a configuration (e.g., information indicative thereof) of one or more measurement gaps (e.g., measurement gap patterns). The WTRU may use the measurement gaps to perform PRS measurements. For example, the WTRU may perform PRS measurements during one or more measurement gaps (e.g., configured measurement gaps).

[0080] The PRS may be either transmitted by and received from one or more gNBs, which may be a serving gNB or another gNB, such as a neighboring gNB.

[0081] The PRS may be either transmitted by and received from a TRP in one or more cells, which may be either the serving cell or another cell, such as a neighboring cell.

[0082] The WTRU may send a request for configuration of a measurement gap (e.g., requesting configuration of a measurement gap) to a gNB (e.g., a serving gNB). The request may be sent by the WTRU via RRC signaling. The gNB may, for example, send the configuration of the measurement gap (e.g., information indicating thereof) to the WTRU in response to the request.

[0083] The WTRU may send a request (e.g., information indicating) to the gNB to stop measurements. The request (e.g., information) may include (e.g., indicate) a request to release a measurement gap configuration for the WTRU.

[0084] A Location Management Function (LMF) may be a non-limiting example of a node or entity (e.g., a network node, a network entity, or a network element) that may be used for or to support positioning. Any other network element may be substituted for (e.g., used as) an LMF and may be applicable to the embodiments described herein.

[0085] The configuration of the measurement gap(s) via RRC may be semi-static and may lack support for dynamic configuration. The measurement gap(s) may cause inefficiencies since they may interfere with the transmission and reception of data during the active bandwidth portion (BWP).

[0086] For example, in 3GPP, the serving gNB may configure (e.g., send configuration information indicating) measurement gaps for the WTRU such that the WTRU may observe signals outside its bandwidth (BW), e.g., an active BWP. During the measurement gaps, transmission and reception using the active BW may be disabled, e.g., such that the WTRU may switch frequencies to measure outside the active BW.

[0087] 2.Improvement of positioning procedures Methods for dynamic reconfiguration of measurement gaps based on conditions are described herein. The WTRU may send a request (e.g., a message indicating a request) for reconfiguration of a measurement gap, which may be signaled or indicated, for example, by either a MAC Control Element (MAC-CE) and an Uplink Control Information (UCI). The WTRU may decide to send a request based on any of the following types of conditions: Condition-based measurements ●Scheduling request from the gNB.

[0088] 2.1 Example of measurement gap configuration based on measurement status Example of a WTRU sending a request based on measurements In one example, the WTRU may send a request (e.g., information indicative thereof) to a gNB (e.g., a serving gNB) to change the measurement gap configuration, e.g., via any of a Medium Access Control-Control Element (MAC-CE) and an Uplink Control Information (UCI). The MAC-CE may be referred to herein as an information element that may be inserted into a transport block to be transported over any type of transport channel of a wireless network. The WTRU may send (e.g., decide to send) the request based on a measurement status (e.g., quality or value) of one or more PRS resources. The WTRU may receive information indicative of the PRS configuration, e.g., from an LMF. The information indicative of the PRS configuration may be received via signaling, such as LTE Positioning Protocol (LPP) signaling (e.g., an LPP message). The WTRU may, for example, initially send (e.g., to a gNB) a request (e.g., information indicative thereof) to configure a measurement gap. The configuration of the measurement gap(s) may comprise a configuration of measurement gap parameters, which may include any of a measurement gap length, a measurement gap periodicity, and a measurement gap offset. The WTRU may make (e.g., send) a request so that the WTRU may perform measurements on PRSs from either one or more serving and non-serving gNBs. Parameters related to measurement gaps, such as measurement gap length, measurement gap periodicity, and measurement gap offset, are shown in FIG. 2. During a measurement gap, the length of which is shown as measurement gap length in FIG. 2, the WTRU may not be expected to transmit or receive data. Outside of the measurement gap, the WTRU may be expected to make measurements on the PRS(s).

[0089] The WTRU may be configured with (e.g., receive configuration information indicating) a measurement gap configuration (e.g., pattern) and any of one or more thresholds, one or more time windows, and one or more durations that the WTRU may use to determine to request a measurement gap configuration (e.g., pattern) update, e.g., a change. The configuration information indicating any of the thresholds, time windows, and durations may be received from either a gNB (e.g., a serving gNB) or an LMF.

[0090] The WTRU may send (e.g., determine) a request for (e.g., information indicative thereof) for either a measurement gap pattern and a measurement gap pattern update when the quality of one or more PRS or PRS-related measurements meets a criterion (e.g., above (or below) a preconfigured threshold). For clarity, meeting a (e.g., strength, quality, stability) criterion (e.g., condition) is described throughout the embodiments described herein in comparison to a (e.g., threshold) value threshold (e.g., at, above, or below). The embodiments described herein are not limited to threshold-based criteria (e.g., conditions). Any type of other conditions and parameters (e.g., within or outside a range of values, etc.) may be applicable to the embodiments described herein. The terms "criterion" and "condition" may be used interchangeably throughout the embodiments described herein. For example, the WTRU may request (e.g., determine) either a measurement gap configuration (e.g., pattern) and a measurement gap configuration (e.g., pattern) change based on one or more of the following criteria (e.g., conditions): • Either the RSRP of the PRS and the linear average of the RSRP of the PRS (eg, over a configured time window) is greater than or equal to (or less than) a configured threshold. • Either the RSRP of the PRS and the linear average of the RSRP of the PRS (eg, over a configured time window) is above (or below) a configured threshold for a configured duration. ● Either the variance and standard deviation of the WTRU's location estimate (e.g., in the case of WTRU-based positioning) is below (or above) a configured threshold that the WTRU may receive (e.g., from a gNB or LMF).

[0091] For example, the PRS may be transmitted from a TRP in either the serving gNB / cell and the non-serving gNB / cell. The information indicating the measurements made on the PRS and the associated measurement report may include information indicating one or more of the following, such that the LMF or gNB may associate the reported measurements with the PRS: Physical Cell ID ● Global Cell ID Absolute Radio Frequency Channel Number (ARFCN) ●PRS ID ●TRP Synchronization Signal Block (SSB) Configuration ●PRS resource ID ●PRS Resource Set ID PRS sequence ID

[0092] A request for a measurement gap pattern (or pattern update) may be sent by the WTRU to the serving gNB.

[0093] The WTRU may determine (eg, calculate) any of the linear mean, variance, and standard deviation of the RSRP based on measurements of the received PRS.

[0094] The WTRU may send a request for (eg, information indicative of) a new measurement gap configuration pattern when the WTRU is performing either WTRU-assisted positioning or WTRU-based positioning.

[0095] For example, if the WTRU determines that the RSRP of the PRS received from the serving gNB meets a criterion (e.g., above a threshold), the WTRU may send a request to the gNB (e.g., via either the MAC-CE and UCI) for a measurement gap pattern. The WTRU may request a measurement gap pattern that may not match (e.g., exactly) the PRS duration (e.g., the measurement gap pattern may be configured for a portion of the PRS duration such that the WTRU may perform partial measurements of the transmitted PRS). As described in more detail below, the WTRU may include information in the request indicating one or more of the following indicators: a measurement gap pattern index (e.g., identifier); the number of symbols or slots to include in the measurement gap; - The start and end position of the requested measurement gap, for example indicated by symbol, slot and frame numbers.

[0096] In another example, the WTRU may send (e.g., decide to send) a request to the gNB for a configuration of a measurement gap pattern if the RSRP of the PRS meets a criterion (e.g., remains at, exceeds, or falls below a configured threshold) for a configured duration. For example, if the WTRU performs WTRU-based positioning, the WTRU may obtain its location estimate. In one example, the WTRU may send (e.g., decide to send) a request to the gNB for a measurement gap pattern if measurements made on the PRS are stable (e.g., meet a stability criterion). The WTRU may determine that some PRS measurements may be either skipped and stopped, for example, based on determining that one or more PRS measurements are stable. The WTRU may request (e.g., send information to request) to disable all or a portion of a measurement gap or measurement gap pattern. A request for either a measurement gap pattern and a measurement gap pattern update may comprise or correspond to a request to disable all or a portion of a measurement gap or gap pattern.

[0097] The WTRU may determine the stability of the measurements based on whether a stability metric (e.g., either the variance or standard deviation of the WTRU's location estimate) meets a stability condition (e.g., is at, above, or below a preconfigured threshold). For example, the WTRU may determine that the PRS measurements are stable (e.g., meets the stability criterion) if either the variance and standard deviation of the WTRU's location estimate are below a configured threshold.

[0098] In another example, the WTRU may stop measuring PRSs for which an RSRP above a preconfigured threshold may be obtained. In another example, the WTRU may stop measuring (e.g., all) PRSs (e.g., used for WTRU-based positioning) if the WTRU determines that the location estimate satisfies a stability condition (e.g., is stable). The WTRU may, for example, send a request (e.g., to the gNB) to disable any of all and any of the measurement gaps and measurement gap patterns such that the WTRU may transmit or receive data in an active BWP.

[0099] For example, the WTRU may determine that a location estimate meets a stability condition (eg, is stable) if either the variance and standard deviation of the location estimate are below a configured threshold.

[0100] The WTRU may send a request, for example by MAC-CE and UCI, to turn off, disable, or change the measurement gaps and the measurement gap pattern. The request may include information indicating to the gNB or LMF that the WTRU may stop making measurements for the indicated PRS and all PRS.

[0101] 3 is a signaling flow diagram illustrating an example of signal exchange between the WTRU 301, gNBs 303, 305, 307, and the LMF 309. FIG. 3 illustrates, as an example, a serving gNB 303 and two non-serving gNBs, Neighbor_A gNB 305 and Neighbor_B gNB 307. At 312, the WTRU may receive PRS configuration information from the LMF 309, e.g., via LPP. For example, the WTRU may send a location measurement indication 314 to the serving gNB via RRC, which may include information indicating a configuration for measurement gaps. For example, the WTRU may receive a measurement configuration 316 from the network, e.g., via RRC.

[0102] The WTRU may receive, for example, PRSs 318, 320, 322 transmitted from the serving gNB and non-serving gNBs, or TRPs in either the serving cell and neighboring cells. For example, at 324, the WTRU may perform measurements on the received PRSs. The WTRU may return a measurement report 326 to the LMF 309 (e.g., send information indicating the same). For example, the measurements may be in NAS format, and they may be sent to the serving gNB 303 in a physical uplink shared channel (PUSCH). From the gNB, they may be transmitted to the LMF. For example, the WTRU may send a measurement gap configuration request 328 to the serving gNB 303 (e.g., via either the MAC-CE and UCI), for example, based on configured measurement conditions. For example, the WTRU may receive measurement gap configuration information from the serving gNB 303 (e.g., via RRC, MA-CE, or DCI).

[0103] Preconfigured measurement gaps may be requested by the WTRU using the UL-MAC-CE. For example, the WTRU may receive (e.g., a priori) configuration information indicating one or more measurement gap patterns, where the measurement gap pattern may be associated with any of a measurement gap length, a measurement gap periodicity, and a measurement gap identifier.

[0104] The WTRU may send a request to the gNB to activate a first measurement gap (e.g., pattern), e.g., via the UL-MAC-CE, based on a set of preconfigured measurement gap patterns. The WTRU may include (e.g., in the request) an index, e.g., in the UL-MAC-CE, that is assigned to a preconfigured measurement gap pattern and corresponds to the requested first measurement gap (e.g., pattern). The WTRU may receive information from the gNB, e.g., indicating activation of the requested measurement gap (e.g., pattern) by the DL-MAC-CE. The WTRU may determine that the DL-MAC-CE activation for the requested measurement gap may be activation for the associated semi-persistent PRS. The WTRU may receive information indicating a configuration for the semi-persistent PRS from the network (e.g., gNB, LMF).

[0105] The WTRU may send a request for a semi-persistent PRS to the network. The request may include information indicating any of a start time, an end time, and a duration. The request may be sent to the network using any of UCI, MAC-CE, RRC, and LPP messages. Any of the start time and end time may be indicated with respect to a reference time (e.g., the timing at which the WTRU may send an on-demand request).

[0106] For example, the WTRU may receive (e.g., determine to receive) a semi-persistent PRS in the requested measurement gap. For example, the requested measurement gap may be deactivated by information that may be received in the MAC-CE from the gNB. In another example, the requested measurement gap may be deactivated based on expiration of a timer, which may have been started once the WTRU may receive an activation command for the measurement gap from the gNB (e.g., the requested measurement gap may be deactivated after a period of time has elapsed since receiving a command indicating activation of the measurement gap). After the requested measurement gap may be deactivated, the WTRU may determine that the associated semi-persistent PRS may be deactivated.

[0107] 2.2 Example of measurement gap configuration based on scheduling Examples of Measurement Gap Patterns and Types For example, the measurement gap pattern may be determined, predefined, or configured (e.g., by receiving configuration information from either the serving gNB or the LMF) using one or more parameters including, but not limited to: A measurement gap duration (e.g., length), which may be based on any of the following units: number of slots, number of symbols, and ms. The periodicity of the measurement gap duration, which can be expressed in units of slots, symbols, or time (e.g., ms). ●Offset (e.g., either slot or symbol)

[0108] For example, the measurement gap type may be either defined, determined, and configured (e.g., by the serving gNB or LMF), and the measurement gap type may be a function of either priority level and time domain behavior.

[0109] With regard to the priority level, for example, a first priority level of the measurement gap and a second priority level of the measurement gap may be used, and the priority level of the measurement gap may be used by the WTRU to determine the WTRU behavior when one or more (e.g., predefined) conditions are met. For example, the measurement gap may overlap with one or more physical downlink control channel (PDCCH) search spaces, and if at least one of the PDCCH search spaces has a higher priority than the measurement gap, the WTRU may monitor the PDCCH search space and may not measure the PRS (e.g., may skip the measurement associated with the measurement gap or may measure a reference signal within the available time after the PDCCH search space monitoring). Otherwise, the WTRU may make measurements and may skip monitoring the PDCCH search space that overlaps with the measurement gap. The priority of the measurement gap may be set to a predefined number (e.g., the same priority as eMBB). The priority level of the measurement gap may be associated with the priority level of the measurement RS (e.g., PRS) associated with the measurement gap.

[0110] For example, a PDCCH search space priority may be configured via higher layer signaling (by receiving configuration information) for its associated search space or control resource set (CORESET).

[0111] For example, the priority level of a search space may be determined based on the associated CORESETPoolIndex of the corresponding CORESET.

[0112] For example, the priority level for a search space may be determined based on whether a priority index exists (or is configured) for a DCI monitored in the search space. For example, if a priority index exists for a DCI format in the search space, the search space may be determined to be of higher priority than a search space in which the monitored (e.g., all) DCI formats may not include a priority index.

[0113] For example, the priority level for a search space may be determined based on the search space identity (e.g., identifier, id). For example, a search space with a lower search space id may be of higher priority than a search space with a higher search space id, and a search space id may be configured for (e.g., each) search space.

[0114] With respect to the time domain behavior (e.g., periodic, aperiodic, or semi-persistent), aperiodic measurement gaps may have a higher priority than periodic or semi-persistent measurement gaps. For example, if an aperiodic measurement gap overlaps with a PDCCH search space, the WTRU may perform the aperiodic measurement gap, and if it overlaps with a periodic measurement gap, the WTRU may monitor the PDCCH search space. The time domain behavior of the measurement gap may be associated with the time domain behavior of the PRS. For example, an aperiodic measurement gap may be associated with an aperiodic PRS. In another example, a semi-persistent PRS may be associated with a semi-persistent measurement gap.

[0115] Example of measurement gap pattern determination In an embodiment, the WTRU may transmit information indicating a request for one or more measurement gap patterns, and each (e.g., each) measurement gap pattern may be associated with a priority level (or type). The WTRU may be configured with (e.g., receive configuration information indicating) one or more measurement gap patterns, e.g., in response to a request from the WTRU. The WTRU may receive information indicating the configuration, e.g., from a serving gNB. The measurement gap patterns may be selected and used based on one or more of the measurement gap pattern determination conditions. A measurement gap pattern among the configured measurement gap patterns may be determined based on one or more of the following example measurement gap pattern determination conditions: A traffic type (e.g., URLLC) may be either configured or supported. For example, a first traffic type (e.g., URLLC) may be either configured or supported if one or more of the following conditions are met: o Either short TTI physical downlink shared channel (PDSCH) reception and short TTI physical uplink shared channel (PUSCH) may be either configured and supported, and the short TTI PDSCH or PUSCH may be a PDSCH or PUSCH transmission that may occupy fewer symbols than the symbols available for DL ​​or UL in a slot. ○ Priority indication may be configured in DCI format. The PDCCH search space may be configured with priority levels higher than a threshold. • The PRS may be configured with a priority level higher than a threshold. ● Bandwidth Part ID (BWP-ID), Carrier index or cell index, ● Bandwidth and / or subcarrier spacing.

[0116] In an embodiment, a set of measurement gap patterns may be determined based on one or more measurement gap pattern determination conditions, and the WTRU may be permitted (e.g., only) to request a measurement gap pattern from that set from the LMF (e.g., or gNB).

[0117] In an embodiment, the set may be determined as a function of the measurement gap duration. For example, a first set of measurement gap patterns may have a measurement gap duration within a first threshold and a second set of measurement gap patterns may have a measurement gap duration within a second threshold. The first set of measurement gap patterns may be a subset of the second set of measurement gap patterns.

[0118] Example of WTRU Behavior After Higher Priority Traffic May Be Admitted In an embodiment, the WTRU may request (e.g., decide to request) a measurement gap pattern that may enable the WTRU to receive any of a downlink signal (e.g., a channel state information reference signal (CSI-RS), SSB), a data channel (e.g., a PDSCH), and a control channel (e.g., a PDCCH), for example, if the WTRU is scheduled to receive downlink signals and / or channels with a higher priority than an initial (e.g., default) measurement gap pattern.

[0119] In an embodiment, for example, after receiving either a downlink signal and a downlink channel, if no higher priority downlink signals and / or channels are scheduled, the WTRU may determine that an initial (e.g., default) measurement gap pattern may be configured (e.g., activated) by the gNB without obtaining additional messages from either the LMF or the gNB. In such an embodiment, the WTRU may determine that an initial (e.g., default) PRS configuration associated with the initial (e.g., default) measurement gap pattern may also be configured (e.g., activated) by the LMF without obtaining additional messages from either the LMF or the gNB.

[0120] Measurement Gap Interruption Example In an embodiment, the WTRU may monitor the PDCCH search space within a measurement gap period if one or more of the following conditions are met (otherwise, the WTRU may skip monitoring the PDCCH search space within the measurement gap period): ●The WTRU may be receiving a first type of data within a first time window before the measurement gap, and the first type of data may be a PDSCH scheduled by a DCI having a priority index (e.g., priority index=1). o The first time window may start x1 slots and end x2 slots from the first slot of the associated measurement gap. ■ x1 may be determined based on at least one of the following: ●Upper layer configuration ●Predetermined value As a function of measurement gap duration As a function of the priority level associated with either the PDCCH search space and the measurement gap ●Subcarrier Spacing Bandwidth portion identity (e.g., identifier) ■ x2 may be determined based on at least one of the following: WTRU processing time (e.g., WTRU capabilities) ●Subcarrier Spacing Bandwidth portion identity (e.g., identifier) ● The WTRU may have transmitted a NACK in the first time window and its associated PDCCH search space for retransmission may be located within the measurement gap. The WTRU may receive an indication from the gNB, for example via a DCI.

[0121] In another example, the WTRU may monitor the PDCCH search space within a measurement gap period if the PDCCH search space is located within a second time window, which may be located within the measurement gap and may be equal to or shorter than the measurement gap. One or more of the following actions may apply: The second time window may start from the first slot of the measurement gap. The second time window length may be determined based on any one or more of the following: Upper layer configuration ○Predetermined value Function of measurement gap duration ○ A function of the priority level associated with either the PDCCH search space and the measurement gap Subcarrier Spacing ○ Bandwidth Partial Identity Length of the first time window

[0122] Example of measurement gap configuration based on demand-free scheduling In another example, the WTRU may receive information from the gNB (e.g., via MAC-CE or DCI) indicating a measurement gap pattern. The information indicating the measurement gap pattern may be received, for example, without a request for a measurement gap from the WTRU. The WTRU may receive information from the gNB indicating the measurement gap pattern along with DCI that may schedule reception of either PDCCH and PDSCH.

[0123] The WTRU may measure a portion of the PRS resource using a measurement gap pattern configured by the gNB. For example, if the PRS resource has a duration of 2 ms and the measurement gap pattern applies to the last 1 ms of the PRS resource, the WTRU may perform measurements over the first 1 ms and may report the measurements to the LMF (e.g., may send information indicating the same).

[0124] For example, the WTRU may send an indication to the LMF that measurements of the PRS may be incomplete due to a new measurement gap configuration. Given the indication, the LMF may send information indicating the measurement gap configuration so that the WTRU may perform observations (e.g., measurements) on the PRS transmitted by the TRP.

[0125] In another example, the WTRU may report (eg, send information indicating) to the LMF the number of resources on which the WTRU may be able to perform measurements.

[0126] In another example, the WTRU may report (eg, transmit information indicative of) quality indicators to the LMF for measurements on PRSs for which the WTRU has performed partial measurements.

[0127] 2.3 Details regarding measurement gap patterns Measurement gap pattern example An example of the difference between an initial measurement gap (e.g., any of the configured initial default gaps, or any other configured gaps in use prior to the request for a new measurement gap configuration) and a requested measurement gap pattern is shown in Figure 4. The initial measurement gap is shown at the top, and the requested measurement gap pattern is shown at the bottom. In the requested pattern, the measurement gap length may be reduced (e.g., compared to the initial measurement gap).

[0128] In one example, the measurement gap pattern may comprise a number of units, and the duration of the unit may be indicated. For example, there may be multiple values ​​for the duration of the measurement gap. The duration of the unit may be expressed, for example, in seconds, symbols, and slots. For example, the unit may comprise one or more subunits, and the location of the (e.g., each) subunit within a group in the measurement gap may be indicated. For example, the unit may include either adjacent and non-adjacent subunits in the time domain.

[0129] For example, the WTRU may be configured to measure and report (e.g., receive information indicative of) two PRS resources, e.g., each lasting 2 ms, in which case the measurement gap may be configured with a length of 4 ms. For example, the measurement gap pattern may include two groups, and the duration of the first group and the second group may be 2 ms.

[0130] In another example, a measurement gap pattern may be a set of periods of duration (e.g., length) that may be repeated with periodicity. A measurement gap pattern may be represented by (e.g., associated with) a periodicity and duration of a time pattern. A measurement gap pattern may be assigned (e.g., associated with) an index (e.g., that may be used as an identifier). The terms "index" and "identifier" associated with a measurement gap pattern may be used interchangeably throughout the embodiments described herein to refer to how a measurement gap pattern may be identified (e.g., distinguished) from another measurement gap pattern. The WTRU may include an indication of the index in either the MAC-CE and UCI when a measurement gap is requested.

[0131] Another set of examples is shown in FIG. 5. In this example, the measurement gap length may be 2T, where T may correspond to the duration of one unit in the measurement gap pattern. Measurement gap pattern (e.g., assigned) index 0 may correspond to a measurement gap having a duration of 2T. Measurement gap pattern (e.g., assigned) index 1 may correspond to a measurement gap having a duration of 1T, where the first half (e.g., only the first half) of the duration may be activated. Measurement gap pattern (e.g., assigned) index 2 may correspond to a measurement gap having a duration of 1T, where the second half (e.g., only the second half) of the duration may be activated. Although not shown in FIG. 5, another measurement gap pattern (e.g., index 3) may correspond to the case where no measurement gap is configured.

[0132] In another example, the WTRU may indicate the measurement gap pattern via a bitmap, as also shown in Figure 5. For example, the measurement gap pattern associated with index 0 may correspond to a bitmap pattern of "11", where (e.g., each) bit may correspond to a 1T time unit, the first bit may correspond to a first half of a 2T long measurement gap, and the second bit may correspond to a second half of the 2T long measurement gap. For example, the measurement gap pattern associated with index 1 may correspond to a bitmap pattern of "10", and the measurement gap pattern associated with index 2 may correspond to a bitmap pattern of "01".

[0133] In the example shown in FIG. 5, the WTRU may perform measurements on PRS transmitted from any of the serving gNBs and TRPs in the serving cell between times t=0 and t=T. Between t=T and t=2T, the WTRU may perform measurements on PRS transmitted from any of the serving gNBs and TRPs in the neighboring cells. If the measurements performed on the PRS transmitted from any of the serving gNBs and TRPs in the serving cell, such as RSRP, satisfy a condition (e.g., exceed a pre-configured threshold), the WTRU may send a request to the serving gNB for a measurement gap pattern associated with index 2, or bitmap pattern "01".

[0134] The embodiments described herein are not limited to measurement gap patterns of 2T duration as shown in the example illustrated in Figure 5. The embodiments described herein may be applicable to any duration of the measurement gap.

[0135] Another example of a measurement gap pattern is shown in FIG. 6. In this example, a measurement gap unit may comprise four subunits, where (e.g., each) subunit may be of duration T / 2. There may be different patterns of subunit location relative to the pattern. For example, in a measurement gap pattern associated with index 1, the subunits may be located at t=0 and t=T. For example, (e.g., each) measurement gap pattern may be indicated by (e.g., associated with) a bitmap pattern. For example, the measurement gap pattern associated with index 1 may be indicated as "1010" as shown in FIG. 6.

[0136] Examples of measurement gap configurations based on measurement conditions In an example, the WTRU may reduce (e.g., decide to reduce) the number of measurements based on the measurement conditions. For example, in the example shown in FIG. 6, for a measurement gap pattern "1010", the first "10" may correspond to a period during which the WTRU may receive a PRS from a serving gNB. In the same pattern, the second "10" may correspond to a period during which the WTRU may receive a PRS from a non-serving gNB. For example, the WTRU may measure and process measurements during the measurement gap, and the WTRU may reduce (e.g., decide to reduce) any of the measurement and processing durations of the PRS during the durations indicated by "0".

[0137] The WTRU may reduce (e.g., decide to reduce) either the measurement duration and the number of measurement samples based on conditions (e.g., RSRP of the PRS, configuration from the network). For example, if the RSRS of the PRS from the serving gNB is above a threshold, the WTRU may reduce (e.g., decide to reduce) the number of measurement samples and request a measurement gap pattern with a shorter duration of the measurement gap during the period during which the WTRU may receive the PRS from the serving gNB. In another example, the WTRU may receive an explicit instruction from the network to reduce the number of measurement samples. The WTRU may configure (e.g., decide to configure) a measurement gap with a duration during which the WTRU may collect an indicated number of measurement samples.

[0138] For example, during a shorter duration of a measurement gap, the WTRU may measure (e.g., decide to measure) a smaller number of measurement samples. For example, the WTRU may measure and / or process (e.g., decide to) half the PRS resources configured by the network. The WTRU may decide to request a measurement gap (e.g., send requesting information) via any of the UCI, MAC-CE, and RRC based on at least one of the following conditions: a quality metric (e.g., one of the RSRP of the PRS and a linear average of the RSRP of the PRS) representative of the quality of the measured PRS, e.g., meeting a first criterion (e.g., above a (e.g., configured) threshold) over a (e.g., configured) time window; a quality metric (e.g., one of the RSRP of the PRS and a linear average of the RSRP of the PRS) representative of the quality of the measured PRS, e.g., meeting a second criterion (e.g., above a (e.g., configured) threshold) for a (e.g., configured) duration over a (e.g., configured) time window; A stability metric, such as, for example, any of the variance and standard deviation of a location estimate of a WTRU (e.g., in the case of WTRU-based positioning) that meets a third criterion (e.g., below a (e.g., configured) threshold that the WTRU may receive (e.g., from a gNB or LMF); ● Explicit instructions from the network (e.g., gNB, LMF).

[0139] For example, the requested measurement gap may be active for a (e.g., configured) duration, e.g., tracked by a configured timer. For example, the WTRU may receive either an activation or deactivation command for the measurement gap (e.g., indicating either activation or deactivation of the measurement gap) from the gNB, e.g., via the MAC-CE.

[0140] Example of PRS configuration for updated measurement gaps In an embodiment, the WTRU may determine that the PRS may be configured in the LMF after the gNB may have acknowledged a configuration request for the measurement gap, such that the WTRU may receive the PRS from the serving / neighboring gNB / TRP within the configured measurement gap (e.g., only within that measurement gap). For example, in such an embodiment, if a bitmap pattern is used for the configuration request, the WTRU may determine that the LMF may configure the PRS such that the WTRU may not receive the PRS during the portion of the measurement gap indicated by a "0" in the bitmap pattern. The gNB may, for example, send a measurement gap configuration request generated by the WTRU to the LMF so that the LMF may update the PRS configuration using the measurement gap configuration information.

[0141] Example of activating or deactivating a measurement gap: Semi-persistent measurement gap pattern In one example, the WTRU may send a request (e.g., information indicative thereof) to activate a measurement gap pattern to the gNB (e.g., via any of the MAC-CE and UCI). For example, the gNB may accept the request from the WTRU to activate the measurement gap pattern. For example, after the WTRU receives information indicating acceptance from the gNB, the measurement gap pattern may be activated for the WTRU. For example, as information indicating acceptance from the gNB, the gNB may send information indicating any of the accepted measurement gap configuration parameters (e.g., any of the measurement gap pattern, measurement gap index, measurement gap length, and measurement gap periodicity) to the WTRU. For example, the acceptance indication from the gNB may include information indicating an explicit acceptance of the request.

[0142] The WTRU may include a measurement gap pattern index in the request to indicate the measurement gap pattern that may be requested to be activated.

[0143] For example, the WTRU may send a request to the gNB, which includes information indicating the requested pattern by other means, such as a bitmap, as previously illustrated by Figure 5. More generally, any kind of identifier capable of identifying (e.g., differentiating, distinguishing) a measurement gap pattern in a set of measurement gap patterns may be applicable to the embodiments described herein.

[0144] Following the request (e.g., in response to the request), the WTRU may receive information from the gNB indicating gap pattern activation. For example, a gap pattern may not be considered active or activated until activation information may be received from the gNB. For example, the gap pattern that may be activated may be the same as the pattern that may have been requested (e.g., may include the requested pattern) (e.g., gaps in the requested pattern may be included in gaps of the activated pattern) or may be a different pattern.

[0145] In another example, the measurement gap pattern may be activated for a preconfigured duration (e.g., only that duration). For example, the WTRU may transmit a request including information indicating the (e.g., requested) duration of the measurement gap activation. For example, the WTRU may start an activation timer when the gNB configures the measurement gap or thereafter (e.g., after receiving information indicating gap pattern activation). The measurement gap may be deactivated when the timer expires (e.g., upon determining that an amount of time (e.g., corresponding to the timer) has elapsed after receiving information indicating gap pattern activation).

[0146] In another example, the measurement gap pattern may not indicate a duration, and the WTRU may send a request to the gNB to deactivate an active measurement gap pattern. The WTRU may include in the request information indicating a measurement gap pattern index that may be associated with the measurement gap pattern that may be requested to be deactivated.

[0147] As mentioned above, a measurement gap pattern may be assigned (e.g., associated with) a unique index (e.g., an identifier that can be used to identify the measurement gap pattern). Either the WTRU or the gNB may indicate the gap pattern by a configured or associated index. Information indicating the gap pattern (e.g., an index) may be included in any of the measurement gap pattern request, measurement gap pattern configuration, measurement gap pattern activation, and measurement gap pattern deactivation. For example, if the WTRU sends information indicating a request for either a measurement gap pattern or a measurement gap pattern change, the WTRU may indicate the requested measurement gap pattern using (e.g., by including) (e.g., in the information) a corresponding measurement gap pattern index.

[0148] In another example, the measurement gap pattern may be configured with or associated with a bitmap pattern. Either the WTRU or the gNB may indicate the gap pattern by the configured or associated bitmap pattern. Information indicating the gap pattern (e.g., a bitmap) may be included in any of the measurement gap pattern request, measurement gap pattern configuration, measurement gap pattern activation, and measurement gap pattern deactivation. For example, if the WTRU sends information indicating a request for either a measurement gap pattern or a measurement gap pattern change, the WTRU may indicate the requested measurement gap pattern using (e.g., by including) a bitmap pattern (e.g., in the information).

[0149] In another example, the new measurement gap pattern may be configured with any of a different measurement gap length, a different measurement gap offset, and a different periodicity. For example, in the example shown in Figure 4, when the WTRU requests a change in the measurement gap configuration, the WTRU may include information in the request that may indicate the new length of the measurement gap L'.

[0150] In the request, the WTRU may include those parameters (e.g., only those parameters) that may differ from the originally (previously) configured parameters for the measurement gap. For example, using the example shown in FIG. 7, where the original measurement gap pattern is shown at the top and the newly requested measurement gap pattern is shown at the bottom, the WTRU may include the requested measurement gap length L′ (e.g., only), which may be the parameter (e.g., only) that may differ from the originally configured parameters.

[0151] In one example, the WTRU may send a request to the gNB in ​​any of the MAC-CE, UCI, PUSCH, and PUCCH including information indicating to activate or deactivate a measurement gap. As a response to the request from the WTRU, the WTRU may receive information indicating an activation or deactivation command for the requested measurement gap in any of the DCI, MAC-CE, PDCCH, and PDSCH. In another example, the WTRU may receive information indicating a deactivation command from the network via the MAC-CE, e.g., without a request to deactivate the measurement gap. For example, the WTRU may determine that the requested measurement gap may be deactivated after a (e.g., configured) duration (e.g., the length of the measurement gap in terms of any number of slots, symbols, frames, subframes, or seconds) may be reached. In another example, the WTRU may receive information from the network via the MAC-CE indicating a deactivation command to deactivate the requested measurement gap, i.e., the first measurement gap. The deactivation command may activate (e.g., simultaneously) the second measurement gap. The second measurement gap may be the same as the first measurement gap in terms of configuration (e.g., “on” and / or “off” duration, length, periodicity). Such a (e.g., simultaneous) activation / deactivation scheme may allow reducing signaling overhead for either activation and deactivation when the (e.g., each) measurement gap has a (e.g., same) duration. In another example, the WTRU may send a request to the network for two measurement gaps (e.g., a first and a second measurement gap), where the configurations for the first and second measurement gaps may be different. In one example, the WTRU may send a request to the network including information indicating either activation and deactivation of the measurement gap via either the UCI and the MAC-CE based on a condition that a list of (e.g., pre-configured) measurement gaps is available in either the WTRU or the network (e.g., gNB, LMF).If a list of (e.g., pre-configured) measurement gaps is not available at either the WTRU or the network (e.g., gNB, LMF), the WTRU may use either the fallback and default methods to send a request for a measurement gap to the network, e.g., send a request to configure a measurement gap via RRC. In another example, the WTRU may receive an indication from the network (e.g., LMF, gNB) that a measurement gap may already be requested by the network. For example, the LMF may send a request to the serving gNB to configure a measurement gap based on the PRS configuration(s) given to the serving gNB from the LMF. The WTRU may receive information such as, for example, DCI, MAC-CE, RRC, and measurement gaps associated with network (e.g., LMF or gNB) configured PRSs via any of the DCI, MAC-CE, RRC, and LPP messages. For example, the WTRU may decide to either cancel and skip sending a request to the network for a measurement gap if it receives an indication from the network indicating that a measurement gap may already be configured such that the WTRU may perform and process measurements on a configured PRS.

[0152] Example of measurement gap triggering: aperiodic measurement gap pattern In one example, the WTRU may transmit information indicating a request for a measurement gap pattern via a UCI. For example, via the UCI, the WTRU may transmit information that may indicate a particular time at which the measurement gap pattern may be triggered. For example, the timing of activation of an active measurement gap pattern may be preconfigured by the gNB. The WTRU may be preconfigured with (e.g., may have received configuration information indicating) a trigger timing for a measurement gap. For example, the WTRU may be configured to start using the requested measurement gap pattern X slots after the WTRU may have sent a UCI to the gNB requesting the measurement gap pattern.

[0153] Example of the content of the request for measurement gap pattern In one example, the information indicating a request for a measurement gap may include one or more of the following: a measurement gap pattern index (e.g., identifier); Duration of the measurement gap pattern for semi-persistent measurement gaps When measurement gaps can be activated

[0154] Information indicating a request for either a measurement gap pattern and a measurement gap pattern update may be sent via physical layer signaling, such as via either the MAC-CE and via any of the UCI, PUCCH, and RRC signaling. The UCI may include a field that may be reserved for the measurement gap pattern request.

[0155] Example WTRU behavior after timer expiration for semi-persistent measurement gap: Measurements may be triggered and fallback actions may be triggered. In an embodiment, the WTRU may determine that an initial (e.g., default) measurement gap may be configured by either the gNB and the LMF, for example, if at least one of the following conditions is met: ● A timer associated with a semi-persistent measurement gap may expire; ● A duration during which a semi-persistent measurement gap may be active may have elapsed; The WTRU may send information indicating a deactivation command to the gNB / LMF to deactivate the semi-persistent measurement gap. If at least one of the above conditions is met, the WTRU may receive the PRS within an initial (e.g., default) measurement gap after a (pre-)configured duration (e.g., any of a slot, symbol, frame, time, etc.).

[0156] In an embodiment, (1) when an aperiodic measurement gap is triggered and (2) when the aperiodic measurement gap becomes inactive (e.g., once at that time, etc.), the WTRU may determine that an initial (e.g., default) measurement gap may be configured by either the gNB and the LMF. The WTRU may receive a PRS within the initial (e.g., default) measurement gap after a (pre-)configured duration (e.g., any of a slot, symbol, frame, time, etc.).

[0157] In an embodiment, the measurement gaps may be configured by the WTRU as required by the bitmap pattern. For example, the WTRU may determine that different measurement gaps may be configured by either the gNB and the LMF if at least one of the following conditions is met: ● A first quality metric, such as, for example, either the RSRP of a PRS corresponding to a "1" in a bitmap pattern within the measurement gap and a linear average of the RSRP, satisfies a first condition (e.g., is below a (e.g., (pre)configured) threshold for a (e.g., pre-configured) duration). A first stability metric, such as, for example, any of the standard deviation, range, variance, etc., of the RSRPs corresponding to "1's" in the bitmap pattern within the measurement gap, satisfies a second condition (e.g., is greater than or equal to a (pre)configured threshold for a preconfigured duration); and In the case of WTRU-based positioning, a second stability metric, such as any of the standard deviation, range, variance, etc. of the WTRU's estimated location meets a third condition (eg, above a threshold).

[0158] In an embodiment, a measurement gap with a bitmap pattern of "0" may indicate that no PRS may be transmitted during the duration of the "0" if, for example, the quality of the PRS corresponding to the region is above a threshold. Further, in such an embodiment, if the above conditions indicate that the quality of the received PRS is degraded (e.g., overall), the omitted PRS may be (e.g., should be) restored, e.g., to improve the quality of the positioning.

[0159] In an embodiment, if at least one of the above conditions is met, the WTRU may determine that an initial (e.g., default) measurement gap (e.g., a bitmap pattern including only "1's" (e.g., "1's") may be configured. In such a case, the WTRU may receive the PRS within the initial (e.g., default) measurement gap. For example, the WTRU may receive the PRS after a duration (e.g., any of a preconfigured slot, symbol, frame, time, etc.).

[0160] In an embodiment, the WTRU may receive a configuration message from either the gNB or the LMF that includes information indicating that a default measurement gap may be configured. In such an embodiment, the WTRU may determine that a default (e.g., initial) measurement gap may be configured, and it may be the case that the WTRU may (e.g., further) determine that an initial (e.g., default) PRS configuration associated with the default (e.g., initial) measurement gap may be configured.

[0161] 2.4 Example of PRS Reconstruction Based on Measurement Gap Reconstruction In an embodiment, the request for a new measurement gap may be associated with a request for a new PRS configuration. For example, the WTRU may extend the measurement gap length so that the WTRU may receive additional PRS within the measurement gap. For example, the WTRU may receive the new PRS configuration in an LPP message, which may enable the WTRU to select and request a measurement gap pattern that can be adapted to the new PRS configuration.

[0162] The WTRU may decide to send a request for a measurement gap if the quality of one or more PRS or PRS-related measurements meets a criterion (e.g., is above a (e.g., preconfigured) threshold). For example, the WTRU may decide to request a measurement gap configuration based on one or more of the following (e.g., a condition is met): ● A quality metric, such as either the RSRP of the PRS and a linear average of the RSRP of the PRS, meets a first condition, such as exceeding a (e.g., configured) time window or being above (or below) a (e.g., configured) threshold. ● A second condition is met, such as, for example, a quality metric, such as either the RSRP of the PRS or a linear average of the RSRP of the PRS, being above or below a certain (e.g., configured) threshold for a certain (e.g., configured) duration, over a certain (e.g., configured) time window. ● A stability metric, such as either the variance and standard deviation of the location estimate of the WTRU (e.g., in the case of WTRU-based positioning), meets a third condition, such as being below a (e.g., configured) threshold that the WTRU may receive (e.g., from a gNB or LMF).

[0163] After the gNB may receive a request for a new measurement gap configuration from the WTRU, the gNB may send a request for a new PRS configuration to the LMF. The WTRU may receive a corresponding message from the LMF regarding (e.g., indicating) the new PRS configuration. The WTRU may receive assistance data from the LMF, which may include the new PRS configuration.

[0164] The gNB may include a request for the LMF (e.g., via NR Positioning Protocol A (NRPPa)) in one or more of the following: A request for a new PRS configuration based on a received measurement gap configuration request from a WTRU; The additional length of the measurement gap that the WTRU may provide; - Change in the period of the measurement gap, ● Measurement reports for the PRS that may be associated with a measurement gap configuration request from the WTRU.

[0165] The measurement gap length may be able to accommodate multiple PRS within its window. The different PRS may have the same or different durations and may be transmitted from different TRPs. The LMF may configure a new PRS that may be transmitted over the requested measurement gap. For example, in the example shown in the timing diagram of FIG. 8, the WTRU may send information to the gNB asking (e.g., requesting) the gNB to increase the current length L of its measurement gap by length L″ so that the WTRU may receive the additional PRS within the gap. The gNB may send the requested measurement gap (or measurement gap configuration change) to the LMF, which may configure a new PRS that may be transmitted within duration L″-L. The new (or additional) PRS configuration may be transmitted from any of the different TRPs and one of the existing TRPs with duration L″-L.

[0166] An example of signaling exchange between a WTRU 901, gNBs 903, 905, 907, 909, and an LMF 911 is shown in Figure 9. Figure 9 shows, as an example, a serving gNB 903 and three non-serving gNBs: Neighbor_A gNB 905, Neighbor_B gNB 907, and Neighbor_C gNB 909.

[0167] For example, the WTRU 901 may receive PRS configuration information from the network (e.g., from the LMF 911 via the LPP) (920). For example, the WTRU may send a location measurement indication, which may include a configuration for measurement gaps, to the serving gNB 909 via the RRC 922.

[0168] For example, the WTRU 901 may receive information indicating a measurement configuration from the network (e.g., RRC) via, for example, the RRC 924. The WTRU 901 may receive PRS 926, 928, 930 transmitted from the serving gNB 909 and two non-serving gNBs, namely, Neighbor_B gNB 905 and Neighbor_A gNB 907.

[0169] For example, the WTRU 901 may perform measurements on the received PRS at 934. For example, the WTRU 901 may return (e.g., send information indicating thereof) a measurement report 936 to the LMF 911 (e.g., via the gNB). For example, the measurements may be in a NAS format and may be sent in a PUSCH to the serving gNB 909 and then from the serving gNB 909 to the LMF 911.

[0170] For example, the WTRU 901 may send a request for a measurement gap (e.g., configuration) 938 to the serving gNB 909 (e.g., via either the MAC-CE and UCI), e.g., based on configured measurement conditions.

[0171] The serving gNB 909 may send a request for a new PRS configuration 940 to the LMF 911 based on the measurement gap request (938) from the WTRU 901.

[0172] Although not shown in the figure, the LMF 911 may send an acknowledgement message for the new / requested PRS configuration to the serving gNB 909. For example, the LMF 911 may send information to the WTRU 901 indicating the new PRS configuration, including the PRS configuration that may have been configured in step 920.

[0173] For example, the WTRU 901 may receive measurement gap configuration 942 information from a serving gNB (e.g., via any of RRC, MA-CE, and DCI), for example, indicating to activate a new measurement gap.

[0174] In this example, the new measurement gap may be longer than the previous length L (e.g., may include additional length L″ for a total length of L+L″) so that the WTRU may receive and perform measurements on additional PRS, for example, from a third neighbor cell, Neighbor_C gNB903. For example, the WTRU901 may start receiving PRSs 944, 946, 948, 950 from the serving cell 909 and the three neighboring gNBs 903, 905, 907 using the new measurement gap pattern configuration.

[0175] Example of how a WTRU may determine the duration of a measurement gap In an embodiment, the WTRU may be pre-configured with (e.g., may receive configuration information indicating a list of) one or more measurement gaps from a gNB. The WTRU may receive an indication to request a measurement gap having a longer duration than an initial (e.g., default) measurement gap, e.g., if one or more (e.g., (pre)configured) conditions are met. For example, the (e.g., each) measurement gap may have a length longer than the length of the initial (e.g., default) measurement gap. For (e.g., each) length, the WTRU may receive, e.g., from the LMF, an association with a PRS configuration. In such an embodiment, if the duration of the default measurement gap is 10 ms, the duration of the (e.g., each) measurement gap is 10 ms. The PRS transmitted from different TRPs may be 2 ms, and there may be five TRPs for transmitting PRS during the default measurement gap. The WTRU may receive information indicating (e.g., a list of) measurement gaps having durations of 12 ms and 14 ms from the serving gNB. From the LMF, the WTRU may receive a TRP ID (e.g., TRP6 and TRP7) along with an indication that the TRP ID may be associated with an additional length of the measurement gap provided by the gNB. The WTRU may determine that during a 12 ms measurement gap, the WTRU may receive PRSs transmitted from the five TRPs, plus PRSs having a duration of 2 ms from TRP6. The WTRU may determine that during a 14 ms measurement gap, the WTRU may receive PRSs transmitted from the five TRPs, plus PRSs having a duration of 2 ms from TRP6 and TRP7.

[0176] In an embodiment, the WTRU may receive from the LMF information including parameters that may be associated with an extended measurement gap, such as any of the following parameters. A (one or more) PRS resource ID having a (one or more) duration (e.g., any of a repetition factor, number of symbols, number of slots); A PRS resource set ID having the PRS resource ID. Any of such parameters may be associated with an ID associated with an extended measurement gap ID. For example, using the above example, extended measurement gaps having 12 ms and 14 ms durations may have IDs, MG1 and MG2, respectively.

[0177] In an embodiment, for example, in the case of the foregoing conditions, the WTRU may determine to request one of the (pre)-configured measurement gaps from the gNB. For example, the WTRU may receive from the LMF information indicating one or more thresholds. In such an embodiment, if either the RSRP over time received from the TRP for one or more PRSs or the linear average of the RSRP over the PRS exceeds a first threshold but is less than a second threshold, the WTRU may determine to send a request for the corresponding extended measurement gap. Based on the (pre)-configured association between the extended measurement gap and the PRS configuration, the WTRU may determine to receive the associated PRS. In an embodiment, using the previous example, the WTRU may be configured with three thresholds, a1, a2, and a3, where a1 < a2 < a3, and the three thresholds may be for the RSRP. If the RSRP of one or more PRSs is less than a1, the WTRU may request a 14 ms measurement gap. If the RSRP is between a1 and a2, the WTRU may request a 12 ms measurement gap. If the RSRP exceeds a3, the WTRU may determine to use the default measurement gap configuration.

[0178] In an embodiment, the WTRU may determine to send a request including information indicating an extended measurement gap if at least one of the following conditions is met: ● A quality metric, such as, for example, any of the RSRP and a linear average of the RSRP over time for at least one PRS, meets a first condition (eg, is less than or equal to a threshold). A stability metric, such as any of the standard deviation, range, and variance of the estimated location of the WTRU, satisfies a second condition (e.g., is greater than or equal to a threshold); and ● The time remaining until the latency (e.g., value, characteristic) satisfies a third condition (e.g., is less than or equal to a threshold).

[0179] Example of PRS reception without measurement gaps In an embodiment, the WTRU may receive a PRS from either the serving gNB and a neighboring gNB without a measurement gap. The WTRU may receive information from the LMF indicating a configuration using time or frequency resources associated with (e.g., dedicated to) receiving the PRS. For example, the WTRU may receive information from the network (e.g., gNB or LMF) indicating a configuration for a bandwidth (e.g., bandwidth portion) that may be dedicated to transmitting the PRS. If the WTRU receives information indicating a bandwidth portion (BWP) configuration dedicated to the PRS, the WTRU may determine that a measurement gap may not be configured. As referred to herein, a BWP in which the WTRU may receive a PRS (e.g., only the PRS) may be referred to as a PRS-BWP.

[0180] In an embodiment, the WTRU may not (e.g., should not) receive signals and / or channels other than the PRS in the PRS-BWP. In an embodiment, the WTRU may receive information from the LMF indicating a PRS configuration associated with the PRS-BWP. The PRS-BWP may have (e.g., may be associated with) a particular ID, center frequency, and / or frequency layer ID that may be sent to the WTRU by either the LMF or the gNB. In an embodiment, the WTRU may receive an indication from the gNB that the configured BWP may be a PRS BWP. Such an indication may be sent by either the DCI, MAC-CE, and RRC.

[0181] In an embodiment, the WTRU may receive information indicating a hopping pattern for the BWP from either the gNB or the LMF. For example, such a hopping pattern may be represented by a sequence of time and center frequency / bandwidth / BWP where the WTRU may find the PRS-BWP. Such a hopping pattern may exist within the BWP. For example, the WTRU may be configured with sub-bands within the BWP and with the hopping pattern of the sub-bands.

[0182] In an embodiment, the WTRU may receive an indication from the gNB to switch to the PRS-BWP. The WTRU may receive the indication from the gNB via any of DCI, MAC-CE, and RRC. In an embodiment, such an indication may be sent after the WTRU may receive information indicating the PRS-BWP and PRS configuration from the LMF.

[0183] In an embodiment, the WTRU may receive additional configuration information associated with the PRS-BWP, such as a duration of activation of the PRS-BWP. In an embodiment, the WTRU may start a timer after it may receive a PRS in the PRS-BWP. In such an embodiment, the WTRU may determine that a default method reception of the PRS (e.g., PRS reception using measurement gaps, initial / default measurement gaps, and associated PRS configuration) may be configured, for example, when the activation period ends or the timer expires (e.g., the timer value reaches a (e.g., preconfigured) time limit, which may be configured by either the LMF or the gNB, e.g., via configuration information).

[0184] In an embodiment, the above-mentioned procedure may have the following sequence: 1. The WTRU may receive, from the LMF, first information indicating a PRS configuration dedicated to the PRS-BWP; 2. The WTRU may receive second information indicating a BWP configuration from the gNB and an indication that the BWP may correspond to a PRS-BWP, e.g., via RRC; 3. The WTRU may receive an indication from the gNB via DCI that the PRS-BWP may be scheduled; 4. The WTRU may receive the PRS in the PRS-BWP, e.g., the WTRU may start a timer; and 5. Once the timer expires (eg, after an amount of time corresponding to the timer has elapsed since receiving the PRS), the WTRU determines that an initial (eg, default) measurement gap may be configured and an associated PRS configuration may be configured.

[0185] Configuring the window for determining PRS prioritization The WTRU may be configured by the network (e.g., may receive configuration information from the network) to receive the PRS outside of the measurement gap. If the WTRU is configured to receive the PRS outside of the measurement gap, the WTRU may determine a prioritization of the PRS and other channels (e.g., PDCCH, PDSCH) or signals (e.g., SSB, CSI-RS). For example, the WTRU may be implicitly or explicitly configured (e.g., may receive configuration information indicating, implicitly or explicitly) with a window during which the PRS may be prioritized or non-prioritized compared to other channels.

[0186] If the window is explicitly configured (e.g., configuration information has been received that explicitly indicates the window), the WTRU may receive information from the network (e.g., either the gNB or the LMF) indicating either the start position, duration, and end position of the window. If the window is implicitly configured, the WTRU may determine the start of the window as either the first transmission and reception opportunity of the PRS, and may determine the end of the window as either the last transmission and reception opportunity of the PRS.

[0187] For example, the WTRU may determine either the start location, end location, and duration of the window based on at least one or a combination of the following factors (e.g., criteria): The start of the window as the first transmission or reception opportunity of the PRS, and the end of the window as the last transmission or reception opportunity of the PRS, ● The start of the window as the first transmission or reception opportunity of the PRS and the end of the window as time (e.g., expressed as any number of symbols, slots, frames, and / or seconds since the first transmission / reception of the PRS). The WTRU may send its last measurement report (e.g., any of an RSRP report, an RSTD report, or an Rx-Tx time difference). The start of the window as the first transmission or reception opportunity of the PRS and the end of the window as the time (e.g., expressed as any number of symbols, slots, frames, and seconds since the last transmission / reception of the PRS) the WTRU may process the measurements (e.g., any of the RSRP report, RSTD report, Rx-Tx time difference). An example is shown in FIG. 10 where the window may start (t1) when (e.g., after) the WTRU 1001 may receive the first PRS and end (t2) when (e.g., after) the WTRU may complete processing of the measurements. ● The window begins as the start of the preparation time to receive the PRS before the first transmission or reception opportunity of the PRS, and ends as the time (e.g., expressed in any number of symbols, slots, frames, and / or seconds from the first transmission / reception of the PRS) by which the WTRU may have completed processing the PRS measurements (e.g., RSTD, RSRP, Rx-Tx time difference).

[0188] For example, the PRS described herein may be any of periodic, semi-persistent, and aperiodic PRS. In the case of a semi-persistent PRS, the MAC-CE may be used by the gNB to either activate or deactivate the semi-persistent PRS.

[0189] Example of determining a window's priority level For example, the WTRU may determine either the priority level of the window and the priority level of the PRS in the window based on at least one of the following: Receiving information including an explicit indication from the network regarding the priority level. For example, the indication may be received in any of the LPP messages (e.g., any of the LPP Assistance Data and LPP Location Request messages) and in Access Stratum (AS) layer messages (e.g., any of the RRC, MAC CE, and DCI). ● The time for reporting the first measurement from the first receipt of the PRS (eg, a shorter time limit may indicate a higher priority and a longer time limit may indicate a lower priority). ● The PRS type configured for the window (e.g., periodic, semi-persistent, or aperiodic). For example, the WTRU may determine that either an aperiodic PRS or a semi-persistent PRS may be associated with a higher (e.g., highest) priority level. Priority level associated with a logical channel. The WTRU may decide to configure either the PDSCH and the PDCCH with a priority level that is the same as the priority level of the associated logical channel. For example, the WTRU may determine that if the priority level of the logical channel associated with the PDSCH is a first level (e.g., "high"), then the priority level of the PDSCH may be a first level (e.g., "high"). • The configuration associated with the PRS (e.g., any of the following: time density, frequency density, duration, repetition factor, or comb pattern). Decode time for either the PDCCH and the PDSCH. For example, the WTRU may be configured with (e.g., receive configuration information indicating) a threshold by (e.g., from) the network. If the decode time for the PDCCH is above the threshold, the WTRU may determine that a priority level associated with the PDCCH may be higher than a PRS (e.g., a priority level associated with the PRS).

[0190] In an example, a WTRU may be configured with (e.g., may receive information indicative of) one or more PRS configurations that may be associated with a window. Different PRS configurations may be assigned (e.g., configured) with different priority values, and the priority values ​​may be pre-configured in the WTRU along with the PRS configurations, for example. Both the window and the priority of the PRS configurations may be determined by the WTRU based on either explicit or implicit indications (e.g., information including same). The WTRU may receive one or more PRSs associated with different PRS configurations, for example, when (e.g., after) a window may be configured. If the WTRU receives one or more PRSs (e.g., after a window may be configured), the WTRU may determine which PRS to measure and / or process the measurements based on the priority values ​​associated with the PRS configurations and the window. For example, the WTRU may select the PRS for either measurement and processing according to a priority order (higher to lower) of the priority value, which may be less than or equal to the priority of the window. In such a case, the WTRU may select a PRS with a higher (e.g., highest) priority value, which may be less than or equal to the priority of the window, and then, for example, select a PRS with the next higher (e.g., highest) priority level. The WTRU may select a second PRS, for example, if measurements performed using the first PRS do not meet a condition (e.g., the RSRP measurement of the first PRS is below an RSRP threshold).

[0191] If (i) the WTRU is unable to determine a PRS configuration having a priority level equal to or lower than the window priority, and / or (ii) the WTRU determines the availability of at least one PRS configuration having a priority level equal to or higher than the window priority, and no other PRS having a lower priority is available, the WTRU may perform one or more of the following: Sending information to the network including an indication to change the priority of the window, e.g., to match the priority of a PRS that may be determined by the WTRU to be available; Sending information to the network including an instruction to release the window; • Sending information to the network including an indication requesting that a measurement gap be configured, for example to enable measurements to be performed using an available PRS.

[0192] Example of reception of DL channel / signal or UL channel / signal during a window The WTRU may receive the PRS during the window, perform measurements on the PRS, and process the measurements to generate a measurement report. For example, the processing may include any of buffering the measurements and calculations (e.g., averaging) using the measurements. For example, the WTRU may not receive any DL channel during the window depending on (e.g., based on) a priority associated with the window. For example, the WTRU may not receive a DL channel whose priority may be lower than a priority associated with the window. In another example, the WTRU may receive a DL channel during the window if a priority associated with the window is lower than the DL channel.

[0193] For example, the WTRU may either postpone or drop any UL channel (e.g., any PUCCH, PUSCH) and signal (e.g., SRS) transmissions having a lower priority compared to the priority level associated with the window if they are scheduled within the window before or after the configuration of the window. For example, if the WTRU is scheduled to transmit any UL channel and signal having a higher priority than the priority level associated with the window, the WTRU may either transmit on the channel and transmit the signal during the window.

[0194] Example of WTRU behavior when window is interrupted A window may be interrupted, for example, by either DL reception or UL transmission, which has a higher priority compared to the priority level of the window. The WTRU may stop the window before either DL reception or UL transmission, and may resume the window after either DL reception or UL transmission may be completed.

[0195] The conditions for the WTRU to stop the window may be one or more of the following: The WTRU may send information indicating a scheduling request (SR) to the network; The window may overlap with a configured grant for uplink transmission; The WTRU may send information to the network indicating a buffer status report; ● The WTRU may receive either a high priority PDCCH (eg, containing URLLC data) and a high priority PDSCH.

[0196] In an embodiment, the decision to stop the window, e.g., to stop measuring the PRS, and e.g., to stop processing the PRS measurements, may depend on the duration of the interruption, e.g., the duration of either the DL reception or UL transmission, which has a higher priority.

[0197] For example, after the WTRU may stop a window, the WTRU may decide to restart the window at another opportunity. The WTRU may receive information indicating configuration from the network with one or more windows. The WTRU may decide to restart PRS measurements and, for example, PRS processing at the next (e.g., earliest) opportunity of the window. The WTRU may receive information indicating a configuration from the network (e.g., one of a gNB, an LMF) for one or more windows characterized by (e.g., based on) one or a combination of the following parameters: ● Periodicity of window occurrence, ● Window duration, ● The time offset of the window.

[0198] Example of WTRU behavior during windows for DL ​​and UL positioning In case of DL and UL positioning (e.g., multi-RTT), the WTRU may receive the PRS, transmit an SRS for positioning (SRSp), and report (e.g., transmit information indicative thereof) to the network the difference between the transmission time of the SRSp and the reception time of the PRS (e.g., Rx-Tx time difference). During the time window, the WTRU may associate a priority level of the window to the SRSp. For example, the WTRU may determine to prioritize the transmission of the SRSp over other UL transmissions (e.g., PUSCH, PUCCH, SRS) that may be scheduled before or after the window may be configured, and may transmit the SRSp during the window. This example embodiment is described below. 1. The WTRU may be configured with (eg, receive configuration information indicating) a multi-RTT positioning method from the LMF. 2. The WTRU may receive (eg, first) information indicating a configuration for a semi-persistent PRS from the LMF. 3. The WTRU may receive (e.g., second) information indicating an SRSp configuration from the gNB. 4. The WTRU may determine either the window duration and start time based on the configuration for the PRS received from the LMF (eg, start time of transmission of the PRS, duration of the PRS transmission). 5. Based on the type of PRS (eg, semi-persistent PRS), the WTRU may determine that the window and SRSp transmission may be associated with high (eg, highest) priority. 6. The WTRU may receive (e.g., third) information indicating permission for SRSp transmission from a gNB associated with the PRS to determine the Rx-Tx time difference. 7. The WTRU may receive (e.g., fourth) information from the gNB indicating a request for an uplink transmission that may overlap with the SRSp transmission. 8. The WTRU may decide to prioritize SRSp transmission. 9. The WTRU may receive the PRS. 10. The WTRU may transmit the SRSp, may determine the Rx-Tx time difference, and may report the determined Rx-Tx time difference to the LMF (eg, may transmit information indicating same). 11. Steps 6-10 may be repeated. The WTRU may determine to stop the window after the WTRU may receive the last PRS opportunity. The WTRU may send a corresponding SRSp and may report (e.g., transmit information indicating) the Rx-Tx time difference after the end of the window.

[0199] The WTRU may request (e.g., determine, determine) a measurement gap based on a priority level associated with the priority level of the PRS indicated by the serving gNB. For example, if the WTRU receives a first (e.g., "high") priority level associated with the PRS from the serving gNB, the WTRU may determine that the PRS from the serving gNB and non-serving gNBs may be received without a measurement gap. For example, if the priority level is a second (e.g., "low") priority level (e.g., lower than the first priority level), the WTRU may determine that the PRS may be received from either the serving gNB and non-serving gNB in ​​the measurement gap.

[0200] Exemplary embodiments are described below. 1. The WTRU may receive information from the LMF indicating a PRS configuration. 2. If the WTRU receives information indicating a PRS priority level from the serving gNB set to a first level (e.g., “high”), steps 3-5 may be executed. If the received (e.g., indicated) priority level is set to a second level (e.g., “low”, lower than the first level), steps 6-7 may be executed. 3. The WTRU may receive information indicating an activation command for the prioritization window via the MAC-CE or a timer for the window. 4. The WTRU may receive PRS from either the serving and non-serving gNB. 5. The WTRU may receive information via the MAC-CE indicating deactivation of the prioritization window command or a timer may expire. 6. The WTRU may request (e.g., send information indicating the request) a measurement gap to the gNB via the MAC-CE (if pre-configured MGs are available and they meet the quality conditions for the PRS (e.g., they are good enough)). 7. In the absence of a priority indication from the gNB, the WTRU may make a request (e.g., send information indicating the request) for measurement gaps via either the RRC and MAC-CE (if pre-configured MGs are available and they meet the quality conditions for the PRS (e.g., they are good enough)).

[0201] In another example, when the priority level of the PRS is at a second level (e.g., “low”), the WTRU may receive (e.g., determine, determine) any of the channels and signals having a higher priority than the second level associated with the PRS from the serving gNB. For example, the WTRU may receive (e.g., determine to receive) a PDSCH including URLLC on the PRS. The WTRU may be scheduled to receive a PDSCH including URLLC and a PRS in the same OFDM symbol. In such a case, if the priority level of the PDSCH including URLLC is higher than the priority level of the PRS, the WTRU may receive (e.g., determine to receive) the PDSCH including URLLC and may not receive the PRS. For example, the WTRU may receive (e.g., determine to receive) (e.g., both) a PRS transmitted from a non-serving gNB and a higher priority channel / signal (e.g., any of PDCCH, PDSCH, CSI-RS) from the serving gNB. In such a case, the WTRU may treat the PRS transmitted from the non-serving gNB as interference and may, for example, perform an interference cancellation method to cancel the PRS transmitted from the non-serving gNB from the received signal.

[0202] The WTRU may receive information indicating the PRS configuration from the LMF, e.g., via the LPP, and the gNB may receive information indicating the PRS configuration it may be responsible for transmitting from the LMF. In another example, the WTRU may send information to the serving gNB, via either the MAC-CE and UCI, indicating configuration details (e.g., parameters) for the PRS transmitted from the non-serving gNB. For example, the WTRU may send information indicating at least one of the following to the serving gNB to indicate the location of the PRS in the time domain: ●A window indicated by either a start time and an end time relative to the timing of transmission of the PRS from the serving gNB (e.g., a time offset from the end of transmission of the PRS from the serving gNB). ● The duration of the PRS configured to be transmitted from a non-serving gNB.

[0203] Depending on the configuration, the WTRU may receive information indicating either a priority (e.g., level) for a window and a location of the PRS symbol. For example, if the WTRU receives information indicating the priority (e.g., level) of a window, the WTRU may associate the priority level with a PRS received within the window. For example, if the priority level of the window is at a first level (e.g., "high"), the WTRU may determine to receive a PRS (e.g., only the PRS) within the window.

[0204] If any of the other channels and signals have a lower priority than the PRS, the WTRU may receive (e.g., decide to receive), e.g., process, the PRS within the window and may not receive (e.g., decide not to receive), e.g., process, any of the other channels and signals based on at least one or more of the following conditions: In case of collision between the PRS and any of the other channels and other signals having a lower priority level in the same symbol, for example, the WTRU may receive (e.g., may decide to receive) any of the other signals and channels in a symbol in which the PRS may not be scheduled; If any other channels and other signals with a lower priority level are scheduled within the window in symbols in which the PRS cannot be scheduled. For example, the WTRU may be configured with the following slots: PPPPPPBBBBBBBB, where "P" and "B" may indicate PRS symbols and non-scheduled symbols, respectively. For example, a prioritization window may be associated with the slot. If the priority level of the window is at a first level (e.g., "high"), the WTRU may not receive any other channels and signals with a priority level lower than the first level in either the PRS symbols or non-scheduled symbols in order to perform measurements on the PRS and, for example, process measurements obtained from the PRS during the duration of the window.

[0205] In an embodiment, the WTRU may receive a PRS from a serving gNB between a first time t=0 and a second time t=4T, where T may be a duration of the PRS transmission. The WTRU may receive a PRS from a non-serving gNB starting between a second time t=4T and a third time t=8T. In such a case, the WTRU may inform (e.g., send information) to the serving gNB of (e.g., indicating) a timing offset of 0 for the end of the PRS transmission from the serving gNB and a duration of 4T for the PRS transmitted from the non-serving gNB.

[0206] In another embodiment, the WTRU may receive (e.g., information indicative of) a muting pattern from the network (e.g., the WTRU may assume that the muting pattern may be applied to a PRS if the priority level of the PRS is indicated as a second level (e.g., “low”) lower than the first level). In such a case, the WTRU may receive (e.g., determine to receive) any channel and signal having a higher priority (e.g., second level) than the PRS in a symbol in which the WTRU may expect to receive the PRS.

[0207] 3. Example of upper layer latency reduction Examples of Latency Reduction Techniques for Upper Layers In one embodiment, the WTRU may proactively perform one or more positioning procedures, e.g., prior to receiving a higher layer positioning information request, based on any of one or more (e.g., configured) conditions and one or more events as described herein.

[0208] For example, in a proactive behavior, the WTRU may perform an action based on either one or more (eg, configured) conditions and one or more events.

[0209] In this case, the positioning information request may relate to, for example, any of a mobile originated location request (MO-LR) and a mobile terminated location request (e.g., any of MT-LR and delayed MT-LR). A positioning procedure proactively performed by the WTRU may result in information associated with supporting a positioning method (e.g., WTRU capabilities, assistance data) being identified, delivered, and stored in advance such that positioning measurements and calculations can be performed with low (e.g., reduced) latency after receiving a positioning information request.

[0210] In a WTRU-initiated example, the WTRU may proactively initiate a positioning procedure (e.g., autonomously) based on detection of at least one configured condition and / or event trigger. In a network-initiated example, the WTRU may be triggered by the network (e.g., the LMF) to initiate the positioning procedure. In both the WTRU-initiated and network-initiated examples, the positioning procedure may be initiated, for example, prior to receiving a positioning information request.

[0211] The positioning procedure proactively performed by the WTRU may include one or more of the following: -Ability transfer procedure: o For example, the WTRU may transmit capability information associated with positioning to the network based on detection of either a trigger condition or an event trigger. The WTRU may transmit capability information (e.g., proactively) as, for example, part of an LPP procedure. The capability information transmitted by the WTRU may be stored in either the LMF / AMF in the CN and in the RAN, for example, as context information associated with positioning. For example, the capability information transmitted by the WTRU may be associated with either an identifier and a version ID for storing in the context information. The stored capability information in the positioning context may be retrieved by the LMF upon receiving, for example, a positioning information request (e.g., MO-LR, MT-LR). -Assistance data transfer procedure: o For example, in a WTRU-initiated example, the WTRU may (e.g., proactively) send a request for assistance data (e.g., information request) when the WTRU is triggered by either a condition and event trigger, e.g., to request one or more PRS configurations. In a network-initiated example, the WTRU may proactively receive information indicative of assistance data (e.g., including PRS configurations) from the network, which may be applied by the WTRU to perform measurements on the PRS after receiving a positioning information request (e.g., information indicative thereof). The assistance information received by the WTRU may be pre-stored in the WTRU as positioning context information and may be retrieved, e.g., after receiving a positioning information request. -Location request transfer procedure: For example, the WTRU may (e.g., proactively) receive a location request message (e.g., LPP) from the network and may use the received location request to transmit positioning information (e.g., any of measurements and location information) after receiving a positioning information request (e.g., MO-LR, MT-LT). The location request received by the WTRU may, for example, be stored in the WTRU as positioning context information. -Measurement gap configuration: For example, the WTRU may (e.g., proactively) send a request (e.g., information request) for one or more measurement gap configurations to the network in case of a triggered condition. In such a case, the WTRU may, for example, send a request for measurement gap configurations before receiving a positioning information request from the network. The one or more measurement gap configurations received by the WTRU may, for example, be stored in the WTRU as positioning context information. -Positioning information report: For example, the WTRU may proactively send positioning information, including either measurement reports and location information, when the WTRU is triggered by a (eg, configured) condition.

[0212] In an example, the received information indicating one or more positioning configurations (e.g., any of assistance data, measurement gap configurations), which may be stored as positioning context information at the WTRU, may be associated with a validity metric. For example, the validity metric may relate to (e.g., be associated with) any of a duration and an area (e.g., a set of one or more cell IDs) for which the stored positioning information is valid and may be used after receiving a positioning information request (e.g., MO-LR, MT-LR). In such a case, the WTRU may use the context information for positioning if a criterion associated with the validity metric is met (e.g., the context information is within any of a validity duration and validity area). The WTRU may trigger (e.g., execute) one or more positioning procedures, e.g., to update the context information, e.g., after detecting expiration of the validity metric.

[0213] Any of the condition and event triggers configured in the WTRU for performing any of the positioning procedures (e.g., proactively) may include one or more of the following: Changes in WTRU capabilities related to positioning In an example, the WTRU capability information associated with positioning may include either static capability information (e.g., types of positioning methods supported) and dynamic capability information (e.g., total bandwidth available for performing positioning measurements). In such a case, the WTRU may transmit (e.g., be triggered to transmit) the capability information to the network after detecting a change in either the static capability information or the dynamic capability information. For example, the WTRU may transmit information indicating an update to the dynamic capability information if the bandwidth available for performing positioning measurements meets a condition, e.g., either an increase or a decrease by a threshold (which may be configured by the LMF, for example). -Timer / Periodic For example, the WTRU may perform one or more positioning procedures (e.g., request assistance data) if a certain duration (e.g., either a minimum duration or a maximum duration) has elapsed since the last same / correlated positioning procedure may have been performed. In an example, the WTRU may set a timer after sending a first request for assistance information and send a second request for assistance information after expiration of the timer (e.g., the second request for assistance information may be sent if it is determined that an amount of time corresponding to the timer has elapsed after the first request for assistance information was sent). The timer duration may be configured by the LMF. In another example, the WTRU may perform (e.g., trigger) a positioning procedure periodically (e.g., repeatedly) based on a configured periodicity (e.g., configured by the LMF). -RRC state change For example, the WTRU may perform (e.g., trigger) one or more positioning procedures if the WTRU RRC state in either the RAN or CN changes (e.g., CM connected to CM IDLE and vice versa, RRC connected to RRC INACTIVE and vice versa). -Area changes For example, the WTRU may perform positioning procedures when either entering, leaving, or camping in an area configured in the WTRU. The configured area, e.g., configured by either the LMF and the gNB, may be represented as a tracking area, e.g., in the form of one or more cell IDs. -Detection of new TRP / gNBs For example, the WTRU may perform (e.g., trigger) a positioning procedure after detecting a new TRP / gNB (cell ID) / satellite / other entity (e.g., high altitude platform station) that may be outside the configured list of TRPs / gNBs / satellites / other entities (e.g., high altitude platform stations) associated with the current active aiding information (e.g., PRS configuration). -Changes in WTRU behavior For example, the WTRU may (e.g., proactively) perform (e.g., trigger) a positioning procedure after detecting that the WTRU may have moved a certain distance from a previous location. In another example, the WTRU may perform (e.g., trigger) the procedure if the speed at which the WTRU may be moving satisfies a speed condition (e.g., the speed has either increased or decreased by a threshold (which may be configured by the LMF, for example)). - Changes in the WTRU radio environment For example, the WTRU may perform a positioning procedure (e.g., proactively) after detecting either an increase or decrease in either multipath and interference, e.g., if the increase / decrease satisfies a condition, e.g., exceeds a configured threshold (e.g., configured by the LMF).

[0214] Example Procedure for WTRU Initiated On-Demand PRS for MO-LR Positioning Service For example, the WTRU may send an on-demand PRS request to the network (e.g., to either the LMF or the gNB) based on receiving or detecting an MO-LR indication. For example, an on-demand PRS request message to request a PRS configuration change or update may be sent by the WTRU along with (e.g., together with) the MO-LR location service request, e.g., by encapsulating it within the same MO-LR message (e.g., within a NAS PDU). In another example, the on-demand PRS request message may be sent by the WTRU separately from the MO-LR message (e.g., in a separate NAS PDU, separate LPP message), e.g., including information that may reference the MO-LR request message (e.g., by including an ID of the MO-LR in the on-demand PRS message).

[0215] For example, the MO-LR positioning service may comprise any of the location services (LCS) client and application functions that may be hosted within the WTRU. The MO-LR positioning service may be applicable to WTRU-based positioning and WTRU-assisted positioning, and positioning information determined (e.g., estimated) by the WTRU (or LMF) based on measurements performed by the WTRU may be sent to any of the LCS clients and applications. Information included in the MO-LR location service request may include (e.g., indicate) one or more of the following: -An identifier associated with either the service request (e.g., MO-LR service ID) and the service entity (e.g., LCS client ID, application ID, WTRU ID). -Requirements for WTRU location estimation o The MO-LR request may or may not include instructions to establish an LPP session with the network if there is no ongoing (e.g., existing) LPP session. o The MO-LR request may include information indicating that if there is at least one ongoing (e.g., existing) LPP session, a location request is to be sent over the LPP session, e.g., including an update to a previous request for location estimation or a new request for location estimation. A request for measurements associated with a location estimate of the WTRU. - Positioning QoS information associated with the location estimate (e.g., any of the positioning accuracy, latency, reliability, and / or completeness properties). - Any of the (e.g., intended) destination and routing information for transmitting the WTRU's location estimate (e.g., any of the LMF ID, WTRU ID, application function ID, LCS client ID). - A request for assistance data (e.g., PRS configuration(s)).

[0216] In the following, an example procedure for supporting WTRU-initiated on-demand PRS for MO-LR is described. The WTRU may receive the MO-LR from either an LCS client or an application located at a higher layer in the WTRU. In an example where the WTRU may establish an LPP session, e.g., based on an indication in an MO-LR location request, the WTRU may send capability information, e.g., via the AMF, to the LMF to indicate support for one or more positioning methods and / or to request to establish an LPP session with the LMF in the absence of at least one ongoing or pre-established LPP session. The WTRU may include information in the capability information, e.g., indicating a cause for establishing an LPP session, including any of the received MO-LR and information associated with the MO-LR (e.g., positioning QoS).

[0217] The WTRU may receive assistance information from the LMF including (e.g., indicative of) one or more pre-configured PRS configurations and / or PRS parameters. In an example, the PRS configuration(s) received by the WTRU may be associated with either (e.g., parameters) of a non-on-demand PRS configuration(s) and (e.g., parameters) of an on-demand PRS configuration(s). The non-on-demand PRS (e.g., pre-configured) configuration(s) may be used by the WTRU, for example, to perform (e.g., conventional) positioning measurements. The on-demand (e.g., pre-configured) PRS configuration(s) may be associated with a PRS configuration (e.g., parameters such as PRS periodicity, bandwidth, etc.) that may be supported (e.g., allowed) by the network, for example, when the WTRU sends an on-demand PRS request. In such a case, the WTRU may determine (e.g., select) one or more PRS configurations (e.g., parameters) from the on-demand PRS configurations, for example, when the non-on-demand PRS configuration(s) does not satisfy a condition associated with, for example, the MO-LR. The WTRU may transmit information to the network indicating the determined (e.g., selected) PRS configuration (e.g., parameters), such as, for example, an ID of the PRS configuration / parameter in the on-demand PRS request. In another example, the assistance information including (e.g., indicating) one or more PRS configurations (e.g., parameters) received by the WTRU may not be associated with any of the non-on-demand PRS configuration(s) and the on-demand PRS configuration(s). In such a case, the WTRU may determine (e.g., select) one or more PRS configurations (e.g., parameters) from the received pre-configured PRS configurations (e.g., parameters) and may include information indicating the determined (e.g., selected) PRS configuration (e.g., parameters) in the on-demand PRS request.

[0218] The assistance information received by the WTRU, including (e.g., indicating) the PRS configuration (e.g., parameters), may be determined by the LMF based on an interaction involving request / response signaling between the LMF and a RAN node (e.g., gNB / TRP), for example, via NRPPa procedures. The assistance information received by the WTRU may include (e.g., indicate) any of a trigger condition and a validity condition for determining when to transmit any of the on-demand PRS request messages and information to be included in the on-demand PRS request message. For example, any of the trigger condition and the validity condition may indicate one or more conditions that may be monitored (e.g., detected) by the WTRU (e.g., RSRP of a PRS measured by the WTRU using a non-on-demand PRS configuration is above / below an RSRP threshold, positioning accuracy is below / above an accuracy threshold). For example, the assistance information may also include a mapping (e.g., association) relationship / function to map (e.g., associate) from the detected trigger / validity condition to one or more PRS configurations or parameters that the WTRU may identify and include in the on-demand PRS request.

[0219] In an example, the WTRU may perform measurements of the PRS (e.g., initially) using the received PRS configuration, or may perform measurements on non-positioning RS (e.g., any of CSI-RS, SSB, RRM measurements). Based on the measurements, the WTRU may determine whether to send an on-demand PRS request to the LMF for either changing and updating the PRS configuration (e.g., parameters), e.g., if a trigger condition is detected and / or if any of the performed measurements and calculated positioning estimates do not meet MO-LR criteria. In an example, the WTRU may send any of the initial measurements and positioning estimates to the LCS client and application to verify whether any of the determined measurements and positioning estimates are appropriate (e.g., meet criteria).

[0220] The WTRU may send an on-demand PRS request to the network when a message (e.g., an indication) is received from either the LCS client and application, e.g., in either a new MO-LR or an update to an existing MO-LR, indicating to perform new measurements using a different PRS configuration (e.g., parameters) and determine a new position estimate for the WTRU. The WTRU may determine the PRS configuration (e.g., parameters) to use for the new measurements based on additional information (e.g., increased / decreased periodicity of measurements performed, increased / decreased measurement duration / bandwidth) that may be included in the received new (e.g., updated) MO-LR. In such a case, the indication received from either the LCS client and application may be used as a trigger to either send an on-demand PRS request to the network or to determine the on-demand PRS configuration (e.g., parameters) to indicate (e.g., include) in the on-demand PRS request.

[0221] After receiving either an explicit or implicit indication (e.g., information) from the network indicating whether the transmitted on-demand PRS request is satisfied, the WTRU may perform a new set of measurements and may send the measurements to the LMF (for WTRU-assisted positioning) or may determine (e.g., estimate) its positioning information based on the measurements (for WTRU-based positioning). The WTRU may send the positioning information determined (e.g., estimated) by the WTRU or the LMF to either the LCS client and application.

[0222] Example of a WTRU sending an on-demand PRS request outside of an active LPP session In an embodiment, the WTRU may send an on-demand PRS request to the network (e.g., to either the LMF or the gNB) when outside an LPP session and / or when an active LPP session is either not configured and not available. In an example, the WTRU may receive an indication to provide either a location estimate and a positioning measurement in an MO-LR location service request, e.g., from either an LCS client and application. If the WTRU receives assistance information including (e.g., indicating) a PRS configuration (e.g., parameters) from a positioning system information block (posSIB), the WTRU may perform measurements on the PRS using the received PRS configuration (e.g., parameters) and send a location estimate to either an LCS client and application. For example, the WTRU may perform measurements on the PRS and determine a location estimate using a pre-configured PRS configuration (e.g., parameters), which may be determined by the WTRU to be valid prior to performing the measurements. In these examples, positioning measurements may be performed by the WTRU in the following scenarios: - for the duration of any of the positioning measurements and location determinations (e.g., estimations), without the need to establish an LPP session; -Before establishing an LPP session, -Outside of an active LPP session.

[0223] In these scenarios, when the WTRU sends an on-demand PRS request message, e.g., either together with the MO-LR service request message or in a separate message, an LPP session may or may not be established (e.g., activated) depending on, e.g., whether the request message sent by the WTRU included instructions to establish (e.g., activate) an LPP session.

[0224] In an example, a WTRU that may receive information indicating a PRS configuration (e.g., parameters) from a posSIB or may have access to a pre-configured PRS configuration (e.g., parameters) may send an on-demand PRS request message to the network to request either a change or an update of the PRS configuration (e.g., parameters). In such a case, the WTRU may send an on-demand PRS request in response to one or more of the following triggers (e.g., conditions): Receiving a MO-LR location service request: For example, the WTRU may transmit an on-demand PRS when an MO-LR request is received and / or when the WTRU determines that the available PRS configuration (e.g., parameters) are insufficient / inadequate to meet the MO-LR positioning QoS criteria (e.g., accuracy, latency). In such cases, the WTRU may transmit the on-demand PRS, for example, before or after performing measurements using the available PRS configuration (e.g., parameters). The WTRU may send an on-demand PRS to the network along with the MO-LR request message, e.g., for WTRU-assisted positioning. In case of WTRU-based positioning, the WTRU may send an on-demand PRS request along with the MO-LR request or in a separate message (e.g., NAS message), e.g., including either an indication of support for WTRU-based positioning or an indication to not establish an LPP session by supporting WTRU-based positioning. Receiving information in posSIB: o For example, the WTRU may transmit an on-demand PRS if the posSIB does not contain a PRS configuration (eg, parameters) that may be suitable for the WTRU to perform (eg, allow) positioning measurements. o For example, the WTRU may perform measurements on non-positioning RSs (e.g., CSI-RS, SSB, any of the RRM measurement configurations) that may be in a quasi-co-location (QCL) relationship with the PRS configurations (e.g., parameters) received via posSIB. The WTRU may send an on-demand PRS request for either an update and change of the PRS configurations (e.g., parameters), for example, if the measurements made on the non-positioning RSs that may be in a QCL relationship do not meet the criteria. o For example, the WTRU may receive (e.g., information indicative of) one or more trigger conditions (e.g., RSRP of measurements made on the PRS may be below / above an RSRP threshold, number of variations in measurements over a duration may be above / below a threshold, detection of non-line-of-sight (NLOS), number of detected multipaths may be above / below a threshold) associated with the PRS configuration (e.g., parameters) received in the posSIB. In this case, the trigger condition (e.g., information indicative of) may be received in the posSIB or the trigger condition may be pre-configured in the WTRU by the network (e.g., via RRC, LPP). The WTRU may transmit an on-demand PRS, for example, if one or more of the trigger conditions are detected (e.g., met). Validity condition detection: For example, the WTRU may transmit an on-demand PRS if a PRS configuration (e.g., parameters) received via the posSIB or preconfigured in the WTRU is determined to be not valid (e.g., has failed) with respect to one or more validity conditions. Information indicative of a validity condition (e.g., any of the cell IDs in an area validity condition, duration in a time validity condition) associated with the PRS configuration (e.g., parameters) may be received, at least in part, by the WTRU from, for example, the network (via any of the posSIB, LPP signaling, RRC signaling) or from any of the LCS client, applications, and higher layer functions.

[0225] If the WTRU does not have at least one existing or active LPP session, the WTRU may send an on-demand PRS to the network via one or more of the following network elements: ●To serving gNB: For example, the WTRU may send an on-demand PRS (e.g., information) in access stratum (AS) layer signaling to the serving gNB, including any of an RRC message, a MAC CE, an on-demand SIB message, and a UCI, indicating to update the PRS configurations (e.g., parameters) available at the WTRU. The WTRU may send information to the serving gNB indicating identifiers (e.g., IDs) of one or more PRS configurations (e.g., parameters) to be changed (e.g., updated). The serving gNB may forward the on-demand PRS request to any of the AMF and LMF to update the PRS configuration(s) (e.g., parameters). To AMF / LMF: o For example, the WTRU may send an on-demand PRS (e.g., information) to either the AMF and LMF without including an LPP session ID indicating, for example, to change the PRS configuration (e.g., parameters) (if the routing ID of the LMF is known to the WTRU). In another example, if the WTRU decides (e.g., intends) to establish an LPP session (e.g., based on either unavailability of an existing (e.g., active) LPP session, triggered by a higher layer location service request, and receiving an LPP message from the network), the WTRU may send the on-demand PRS (e.g., information) to the AMF / LMF by sending (e.g., piggybacking) a message along with a capability information message (e.g., in an LPP capability provision message) or along with an assistance information request message (e.g., an LPP assistance data request message). In such a case, the WTRU may include, for example, a flag and / or an indicator (e.g., information) in the on-demand PRS indicating whether an LPP session should be established or not. o For example, if the WTRU has one or more LPP sessions that are deactivated (e.g., suspended), the WTRU may send an on-demand PRS (e.g., information) to the AMF / LMF along with the LPP message (e.g., including IDs of the deactivated (e.g., suspended) LPP sessions). The WTRU may also include in the on-demand PRS any of flags and indicators (e.g., information) indicating, for example, whether to reactivate the deactivated (e.g., suspended) LPP sessions and / or establish new LPP sessions.

[0226] If the WTRU does not have at least one existing or active LPP session, the WTRU may send an on-demand PRS (e.g., information) to the network to indicate whether to either establish and activate an LPP session (e.g., using either a flag and indicator along with the on-demand PRS (e.g., information)) based on detection of one or more of the following conditions: Type of MO-LR service request: For example, the WTRU may send an on-demand PRS (e.g., information) including a flag and / or indicator if, for example, a MO-LR message is received that includes an instruction to establish an LPP session. In another example, the WTRU may include a flag and / or indicator for establishing and activating an LPP session if the positioning QoS information provided with the MO-LR request indicates parameter values. In such a case, the WTRU may include a flag and / or indicator if the indicated positioning accuracy and latency meet the conditions (e.g., above / below accuracy / latency thresholds). Types of PRS configuration (e.g. parameters) accessible via posSIB: For example, the WTRU may include a flag and / or indicator with the on-demand PRS (e.g., information) for any of the establishment and activation of an LPP session if it is determined that the PRS configuration (e.g., parameters) available via the posSIB for measurements does not meet the criteria (e.g., positioning QoS criteria associated with the MO-LR service request, etc.). In such a case, the WTRU may include a flag and / or indicator if the measurement duration for performing measurements using the PRS configuration (e.g., parameters) available via the posSIB does not allow for determining a location estimate.

[0227] For example, after sending an on-demand PRS (e.g., information) message to the network, the WTRU may receive either explicit or implicit information from the network indicating whether the requested on-demand PRS is fulfilled (e.g., accepted) by the network.

[0228] The explicit information may be received in one or more of the following types of messages: ● LPP message: For example, the WTRU may receive explicit information from the LMF / AMF in an explicit LPP message indicating whether the on-demand PRS is satisfied (e.g., accepted) (with a new LPP Session ID or without an LPP Session ID). ● NAS message: For example, the WTRU may receive explicit information from the AMF in an explicit message (eg, either a NAS message, a non-LPP message) indicating the (eg, fulfillment) status of the on-demand PRS. ● AS message: For example, the WTRU may receive explicit information from the gNB in ​​an explicit message in any of the RRC, MAC CE, and DCI indicating the (e.g., fulfillment) status of the on-demand PRS.

[0229] The implicit information may be received in one or more of the following: ●posSIB: o For example, the WTRU may determine whether a requested on-demand PRS is fulfilled (e.g., accepted) based on monitoring the posSIB. If the posSIB is updated and includes the requested PRS configuration (e.g., parameters) in the on-demand PRS, the WTRU may, for example, consider the request to be fulfilled (e.g., accepted). For example, receiving an updated posSIB including the requested PRS configuration(s) (e.g., parameters) may be an example of implicit information indicating acceptance of the request. ●PRS measurement: o For example, the WTRU may perform a measurement of the PRS using one or more PRS configurations (e.g., parameters) indicated in the on-demand PRS request message, e.g., after a configured duration after transmitting the on-demand PRS to the network. If the WTRU performs a PRS measurement that is aligned (e.g., meets an associated condition) with the requested PRS configuration (e.g., parameters), the WTRU may, for example, consider the request to be fulfilled (e.g., accepted). An example of a condition associated with the requested PRS configuration(s) (e.g., parameters) may be that the RSRP of the PRS measurement is above or below an RSRP threshold. For example, performing a PRS measurement that is aligned (e.g., meets an associated condition) with the requested PRS configuration(s) (e.g., parameters) may be an example of implicit information indicating acceptance of the request.

[0230] If the WTRU receives either explicit or implicit information indicating that a requested update to the PRS configuration / parameters is not satisfied (e.g., is rejected), the WTRU may perform one or more of the following actions (e.g., operations): On-demand PRS retransmission: o For example, the WTRU may retransmit the on-demand PRS, e.g., after waiting for a (e.g., configured) duration (e.g., inhibit time), e.g., using one or more of the approaches described above (e.g., for any of the serving gNB, AMF, and LMF). In such a case, the WTRU may use, e.g., the same approach to transmit the on-demand PRS in the first instance and the second instance (e.g., retransmission). In another example, the WTRU may use a second approach to transmit the on-demand PRS in the second instance, which may be different from the first approach used to transmit in the first instance. ● Reuse of available PRS configurations (e.g. parameters): o For example, the WTRU may use an available PRS configuration (e.g., parameters), which may either have been received via, e.g., posSIB, or may be pre-configured in the WTRU, to perform measurements, e.g., after receiving an indication that the on-demand PRS request cannot be satisfied (e.g., rejected), e.g., after waiting for a (e.g., configured) duration (e.g., reuse duration). Sending instructions to (re)establish an LPP session: o For example, the WTRU may send an instruction to (re)establish an LPP session, e.g., by sending either a positioning service request and an LPP request to the AMF / LMF, if a requested on-demand PRS request is not fulfilled (e.g., rejected).

[0231] Example of a WTRU performing grouping of PRS parameters / configuration for transmitting on-demand PRS In an example, the WTRU may either select and perform one or more PRS parameter groupings when it is determined that the PRS parameters should be updated (e.g., changed) and, for example, when an on-demand PRS request message is transmitted. For example, the on-demand PRS request message may include information indicating the selected (e.g., determined) PRS parameter group (e.g., set) to the network (e.g., either the LMF or the gNB). In an example, the PRS parameters (e.g., may be grouped) may be pre-configured in the WTRU, e.g., separately from PRS configurations that may be configured in the WTRU. In another example, the PRS parameters (e.g., may be a part or subset of one or more PRS configurations (e.g., within the PRS configuration(s)) pre-configured in the WTRU, e.g., that may be enabled to be grouped differently from the PRS configurations.

[0232] In an example, the PRS parameters that may be either selected or grouped by the WTRU to send an on-demand PRS request message may be parameters that may be supported or permitted by the network to be grouped (e.g., flexibly) by the WTRU. In such a case, the WTRU may receive information from the network (e.g., either the LMF or the gNB) indicating one or more PRS parameters, e.g., along with any of the properties and types of parameters that are allowed to be grouped. The information may be included, for example, in the on-demand PRS. The WTRU may also receive information indicating, for example, rules (e.g., restrictions) indicating how the PRS parameters may be grouped by the WTRU. For example, the WTRU may receive information indicating, for example, conditions (e.g., criteria) that may be monitored by the WTRU to determine which of the parameters and rules (e.g., restrictions) to apply for grouping the parameters. For example, the WTRU may receive information for grouping from the network, e.g., in an LPP message (e.g., LPP assistance information), including (e.g., indicating) any of the PRS parameters, conditions for triggering grouping, and rules for grouping. In another example, the WTRU may receive a portion of the grouping information, including an indication of any of the PRS parameters, conditions, and rules, from the LMF (e.g., in an LPP message), and the remaining grouping information from the gNB (e.g., in an RRC, MAC CE, or DCI).

[0233] The information indicating the PRS parameters that may be received by the WTRU for grouping in the on-demand PRS may include one or more of the following (e.g., an indication): Any of the following: PRS periodicity, PRS resource bandwidth, PRS resource density, start time, stop time, time offset, repetition, muting bandwidth, comb pattern, number of symbols per PRS resource. For example, a request from a WTRU for a specific value of any of the following: PRS periodicity, PRS resource bandwidth, PRS resource density, start time, stop time, time offset, repetition, muting bandwidth, comb pattern, number of symbols per PRS resource may be applicable to a specific (e.g., a portion of) PRS resources, resource set, TRP resource, resource set, TRP, or frequency layer. For example, if the WTRU requests a specific start and stop time for a PRS, the request may apply to the PRS transmitted from the configured TRP. In another example, if the WTRU requests a (e.g., specific) number of PRS symbols, the request may be applicable to (e.g., all) PRS transmitted from the TRP that the WTRU may indicate in the request. - Either the TX power indication and frequency of the PRS, for example to measure low RSRP on the PRS. - PRS QCL information, eg, other RSs or channels that may have a QCL relationship with the DL PRS. ● Change the number of beams, turn beams on / off, or change the beams sent by the TRP / cell ● The number of the TRP / gNB transmitting the PRS or the ID of the TRP / gNB. • On / off or mute PRS from TRP / cell, for example to measure high interference. • For example, measurement gap configuration parameters associated with the updated PRS configuration.

[0234] Conditions that may be configured and monitored (eg, detected) by the WTRU for performing grouping between different PRS parameters may include one or more of the following: Measurement RSRP: For example, the condition may be met if the RSRP of a measured PRS or non-positioning RS / channel (e.g., CSI-RS, SSB, any other channel) falls below / above a (e.g., configured) RSRP threshold and / or if the RSRP remains above / below the RSRP threshold for a (e.g., configured) duration. WTRU radio environment: For example, the condition may be met if the number of detected paths exceeds the number of multipaths. o For example, the condition may be met if a NLOS condition is detected. WTRU mobility: o For example, the condition may be met if the WTRU mobility / movement increases / decreases by a mobility threshold.

[0235] The following illustrates any example set of properties, rules, and conditions that may be associated with grouping of PRS parameters, which may indicate how the grouping may be performed by the WTRU: Set 1 of PRS parameters (e.g., allowed to be grouped) ○{parameter1_1, parameter2_1, parameter3_1, ..., parameterN_1} A set of K PRS parameters (e.g., allowed to be grouped together) ○{parameter1_K, parameter2_K, parameter3_K, ..., parameterN_K} Properties of Set 1, Set 2, ... Set K: Property 1: Set 1, Set 2...Set K may contain PRS parameters that may be common to multiple sets (e.g., one or more parameters in Set 1 may be the same as a parameter in Set 2) Property 2: Set 1, Set 2...Set K may contain PRS parameters that may be mutually exclusive (e.g., every parameter in Set 1 may differ from the corresponding parameter in Set 2) Property 3: Set 1, Set 2, ..., Set K (e.g., each) may be associated with a different PRS configuration (e.g., PRS configuration ID 1, ..., PRS configuration ID K). ●Conditions ○Condition set 1: {Condition 1, Condition 2..., Condition V1} ○Condition set 2: {Condition 1, Condition 4, ...Condition V2} ○ Condition set 3: {Condition 1, Condition 3..., Condition V3} ○Condition set 4: {Condition 1, Condition 5, ...Condition V4} ● Rules for grouping PRS parameters from set 1, ... set K: Rule 1: One or more of the parameters from Set 1 (e.g., all or a subset of Set 1) may be grouped with one or more parameters in Set 2 (e.g., all or a subset of Set 2) when realizing (e.g., determining) a new set (e.g., Set {1+2}). Rule 2: One or more parameters in set 1 may not be grouped with parameters in set 2 when realizing (e.g., determining) a new set (e.g., set {2-1}). Conditions associated with either the property or the rule: Property 1 and Rule 1 may be applied if a condition from Condition Set 1 is detected (e.g., satisfied) Property 1 and rule 2 may be applied if a condition from condition set 2 is detected (e.g., satisfied) Property 2 and rule 1 may be applied if a condition from condition set 3 is detected (e.g., satisfied) Property 2 and rule 2 may be applied if a condition from condition set 4 is detected (e.g., satisfied)

[0236] For example, after performing the grouping of PRS parameters, the WTRU may send an on-demand PRS request message to the network including information indicating the determined group. The determined grouping of PRS parameters may be grouped into a new PRS configuration, for example, with a new ID. The information related to the PRS parameter grouping included in the on-demand PRS request message may include (e.g., may be indicated) one or more of the following: - ID of each grouped parameter, The ID of the parameter set used for grouping, The ID of the detected condition for grouping, The ID of the rule that was applied for the grouping.

[0237] The WTRU may send an on-demand PRS, including information related to PRS parameter grouping, to the network, for example, in an LPP message (e.g., any of LPP Request Assistance Data, LPP Providing Capability Information, LPP Providing Location Information) or an AS layer message (e.g., any of RRC signaling, MAC CE, UCI).

[0238] If the WTRU is not pre-configured with one or more PRS parameters and / or does not have information regarding valid PRS parameters that may be allowed to be selected for indication in the on-demand PRS, the WTRU may perform one or more of the following: Send a message to the network indicating a request for an Assistance Data message. For example, the WTRU may send either an LPP message (e.g., LPP Request Assistance Data) and an AS layer message (e.g., RRC, MAC CE, on-demand SIB, UCI) to request assistance data. In such a case, the WTRU may request PRS parameters, for example, by including an indication (e.g., a flag) indicating unavailability of valid PRS parameters for selection. Determine from available (e.g. existing) PRS configurations o For example, the WTRU may select (e.g., determine) PRS parameters to indicate to be updated / changed in the on-demand PRS from one or more valid PRS configurations pre-configured at the WTRU (e.g., via LPP assistance data) and / or accessible via the posSIB. The WTRU may identify a PRS configuration that may be marked (e.g., indicated) by the network, and the WTRU may select (e.g., determine) from that PRS configuration, e.g., PRS parameters to be updated and indicated in the on-demand PRS.

[0239] Example of a WTRU Using Validity Conditions for Determining PRS / SRSp Configuration (e.g., Parameters) In an example, the WTRU may use a validity condition associated with one or more preconfigured PRS configurations (e.g., parameters) to determine which of the configurations (e.g., parameters) to select and / or use to perform DL PRS measurements. For example, for a UL SRSp transmission, the WTRU may use a validity condition associated with one or more preconfigured SRSp configurations (e.g., parameters) to determine which configurations (e.g., parameters) to select and / or use. Information indicative of the validity condition may be received by the WTRU from the network (e.g., any of the LMF and gNB), for example, in any of the LPP messages (e.g., any of the LPP Provides Assistance Data, LPP Requests Location Information), Positioning Service Request messages (e.g., any of the MT-LR, Delayed MT-LR, MO-LR), and AS layer messages (e.g., via any of the RRC signaling, MAC CE, DCI). The validity condition received by the WTRU (e.g., indicated to the WTRU) may be associated with a type of event (e.g., area, periodic location) that is configured if the WTRU supports the delayed MT-LR service (e.g., procedure). The information indicative of validity conditions associated with the PRS / SRSp configuration(s) (e.g., parameters) may include a combination of one or more of the following: Area Effectiveness: o For example, any of the Cell ID, RAN Notification Area (RNA), and CN Area for which pre-configured PRS / SRSp configurations and / or parameters may be valid for use. ● Time validity: o For example, the duration during which a PRS / SRSp configuration may be valid for use (e.g., from a start time to an expiration time). The WTRU may start a timer upon receiving a PRS / SRSp configuration (e.g., in assistance data) and may use the configuration for PRS measurements or SRSp transmissions, for example, as long as the timer may be valid within the configured duration (e.g., if the amount of time corresponding to the timer has not elapsed). WTRU mobility conditions: For example, the WTRU may use a pre-configured PRS / SRSp configuration (e.g., parameters) when the WTRU velocity is below / above a configured velocity threshold. For example, the WTRU may use a pre-configured PRS / SRSp configuration when the amount and / or rate of the WTRU movement / orientation increases / decreases by a threshold. WTRU radio environment: For example, the WTRU may change from a first set including one or more pre-configured PRS / SRSp configurations to a second set if any of the RSRPs of measurements performed on the PRSs and non-positioning RS / channels (e.g., CSI-RS, SSB) associated with the first set meet a criterion (e.g., above / below an RSRP threshold). The WTRU may change from a first set including one or more pre-configured PRS / SRSp configurations to a second set, for example, if the number of multipaths meets a criterion (e.g., above / below a threshold) and / or if an NLOS condition is detected. WTRU RRC state (e.g. CONNECTED, INACTIVE, IDLE): o For example, the WTRU may change from using a first set containing one or more PRS / SRSp configurations to a second set when the WTRU operates in different RRC states. The WTRU may, for example, use the first set of PRS / SRSp configurations when the WTRU operates in an RRC_CONNECTED state, the second set of PRS / SRSp configurations when the WTRU operates in an RRC_INACTIVE state, and the third set of PRS / SRSp configurations when the WTRU operates in an RRC_Idle state. In such a case, the first, second, and third sets associated with the different RRC states may include, for example, subsets of PRS configurations that may be common across the sets. In another example, the PRS / SRSp configurations may be mutually exclusive across different sets associated with different RRC states.

[0240] One or more validity conditions received by (e.g., indicated to) the WTRU may apply to all or a subset of PRS / SRSp configurations (e.g., parameters) preconfigured in the WTRU. For example, in an example, a first validity condition may apply to a first PRS / SRSp configuration and a second validity condition may apply to a second PRS / SRSp configuration. In another example, the first validity condition may apply to (e.g., all) PRS / SRSp configurations and the second validity condition may apply to, for example, a subset (e.g., only the subset) of PRS / SRSp configurations received by (e.g., indicated to) the WTRU. In such a case, the WTRU may use the first PRS / SRSp configuration as long as the first validity condition applies and may use the second PRS / SRSp configuration while (e.g., if) the second validity condition applies. For example, if a time-based validity condition is used, the WTRU may be provided with (e.g., information indicative of) different PRS / SRSp configurations along with (e.g., information indicative of) different validity condition parameters (e.g., start time, validity duration, expiration time) associated with (e.g., each) PRS / SRSp configuration. For example, the WTRU may select a PRS / SRSp configuration based on the parameters of the time-based validity condition. Information indicative of the mapping (e.g., association) between the validity condition and the applicable PRS / SRSp configurations (e.g., parameters) may be received by the WTRU in assistance data along with the validity condition and information indicative of any of the PRS / SRSp configurations (e.g., via an LPP message, RRC signaling, posSIB, for example).

[0241] In an example, the WTRU may use validity conditions, e.g., in conjunction with priority values ​​associated with PRS / SRSp configurations preconfigured in the WTRU. For example, if there are multiple PRS / SRSp configurations that satisfy a validity condition, the WTRU may use the PRS / SRSp configuration that is assigned (e.g., associated) with a higher (e.g., highest) priority value, followed by the next higher (e.g., highest) priority value, e.g., if a validity condition associated with a previous PRS / SRSp configuration expires or is determined to be no longer valid. Selection of a PRS / SRSp configuration based on either the assigned priority and the validity conditions may, for example, enable reducing the number of occurrences of changing (e.g., updating) a PRS / SRSp configuration during use.

[0242] If the WTRU determines that one or more of the PRS / SRSp configurations is no longer valid (e.g., a validity condition indicates expiration of the PRS / SRSp configuration) or is not satisfied, the WTRU may perform one or more of the following: Sending information (e.g. instructions) to the network: o For example, the WTRU may send information to the network indicating either a PRS / SRSp configuration identifier (e.g., ID) and an expiration status of the configuration. The information may indicate, for example, to update the PRS / SRSp configuration and any validity condition(s) associated with the indicated PRS / SRSp configuration. The information may be sent to the network, for example, as an LPP message, an on-demand PRS message (e.g., to either the LMF and gNB), and an AS layer message (via RRC, MAC CE, UCI). ● Change to a valid (e.g., alternate) PRS / SRSp configuration: For example, the WTRU may use a second PRS / SRSp configuration that may be determined to meet its validity conditions if the first PRS / SRSp configuration is determined to be no longer valid. If there are multiple PRS / SRSp configurations (e.g., determined to be valid), the WTRU may, for example, select a configuration that is assigned (e.g., associated with) a high (e.g., highest) priority as the second PRS / SRSp configuration. PRS / SRSp configuration update (e.g., forwarding) validity conditions: o For example, if the WTRU determines that a PRS / SRSp configuration is no longer valid based on the validity conditions, the WTRU may update (e.g., transfer) its validity conditions, e.g., based on the validity conditions of another PRS / SRSp configuration that is determined to be valid. In such a case, the WTRU may change the first validity conditions (e.g., associated with the first PRS / SRSp configuration) to be similar to those of the second validity conditions (e.g., associated with the second PRS / SRSp configuration), e.g., if the first validity condition expires and the second validity condition is active (e.g., determined to be active) during (e.g., at, after) the expiration of the first validity condition. The WTRU may, for example, transmit information to the network indicating the status of the update (e.g., transfer) of the validity conditions from one PRS / SRSp configuration to another PRS / SRSp configuration.

[0243] After receiving information indicating the pre-configured PRS / SRSp configurations and associated validity conditions, the WTRU may perform PRS measurements or SRSp transmissions using the configurations determined to be valid based on receiving a trigger indication. In such a case, the trigger indication may be received, for example, in any of the LPP messages (e.g., LPP request for location information), positioning service requests (e.g., MO-LR, MT-LR, delayed MT-LT), and AS layer messages (e.g., RRC signaling, MAC CE, DCI).

[0244] Example of a WTRU sending an on-demand PRS request to indicate a PRS configuration (e.g., parameters) selected from different sets determined to be either enabled or disabled Throughout the embodiments described herein, a PRS configuration may include either a single PRS parameter or a set (e.g., multiple) PRS parameters. When used in connection with a PRS configuration, the term "parameter" may be used interchangeably with the term "PRS parameter" throughout the embodiments described herein. For example, a PRS configuration may include any of: (1) DL PRS transmission start and end time, (2) DL PRS resource bandwidth, (3) DL PRS resource set ID, (4) DL PRS resource ID, (5) DL PRS transmission periodicity and offset, (6) DL PRS resource repetition factor, (7) number of DL PRS symbols per DL PRS resource, (8) DL PRS muting pattern, (9) DL PRS QCL information, (10) number of TRPs, (11) number of PRS resources per PRS resource set, (12) number of frequency layers or frequency layer indicators, (13) beam direction, (14) DL PRS combsize, starting PRB, point A, and (15) DL PRS on / off indicator.

[0245] In an embodiment, if a PRS configuration (e.g., parameters) accessible at the WTRU is determined to be either invalid and unavailable, the WTRU may send information indicating either an on-demand request or a request for assistance data (e.g., in an LPP message) to the network (e.g., either the LMF or the base station) to request one or more PRS configurations and parameters of the PRS configurations.

[0246] For example, the WTRU may receive configuration information from the network indicating one or more PRS configurations and parameters associated with the PRS configurations (e.g., PRS bandwidth, PRS periodicity, TRP (e.g., gNB), etc.). The WTRU may receive the configuration information indicating the PRS configuration (e.g., PRS configuration ID, parameters, parameter ID) via, for example, a system information block (SIB) such as a posSIB, assistance data (e.g., LPP assistance data, etc.), and pre-configuration at the WTRU (e.g., pre-configured PRS configurations (e.g., parameters) that may have been received either in a previous LPP session and outside an LPP session). For example, the WTRU may receive information indicating validity conditions (e.g., parameters) associated with the PRS. For example, the validity conditions may be received implicitly (e.g., via a SIB indicating, for example, a time and area (e.g., cell ID) for which the PRS configuration (e.g., parameters) may be considered valid). In another example, the information indicating the validity conditions may be received explicitly (e.g., via LPP assistance data). The WTRU may determine that any of the PRS configurations and PRS parameters accessible by the WTRU (e.g., via any of the SIBs) and pre-configured PRS configurations (e.g., parameters) may not be valid, e.g., with respect to a validity condition. In such a case, the WTRU may transmit request information indicating either an on-demand request or a request for assistance data. For example, the request information may include an indication of any of one or more PRS configurations and parameters that may be determined to be invalid. In another example, the request information may include an indication of any of one or more PRS configurations and parameters that may not be associated with at least one of the PRS configurations (e.g., parameters) that may have been pre-configured in the WTRU (e.g., in either a previous LPP session and outside an LPP session).

[0247] For example, a PRS configuration (e.g., parameters) received by the WTRU may be determined to be either invalid, unavailable, and unsupported (e.g., by the network) due to (e.g., based on) any of the following conditions (e.g., events): • Expiration of time validity associated with one or more PRS configurations (e.g., one or more parameters); Changes in area (e.g., cell ID), for example due to WTRU mobility and cell (re)selection, where accessible and pre-configured PRS configurations (e.g., parameters) may be determined to be either available or unavailable for use; ● A change in WTRU mobility attributes (eg, the WTRU may use a different mobility path (eg, orbit)), where a pre-configured PRS configuration (eg, parameters) may be determined to be either valid or invalid.

[0248] For example, the PRS configurations (e.g., parameters) accessible by the WTRU (e.g., via any of the SIBs, assistance data, and pre-configuration) may correspond to (e.g., only) a subset of the PRS configurations (e.g., parameters) that may be supported and available for use in the network. In another example, additional PRS configurations (e.g., parameters) may be any of those available in the network and supported by the network, but may not be any of those accessible by the WTRU and available at the WTRU.

[0249] For example, the WTRU may determine a PRS configuration (e.g., parameters) for use and indicate in the on-demand PRS request even if the determined PRS configuration (e.g., parameters) may be invalid, unavailable, and unsupported. In an example, the WTRU may be configured with positioning QoS parameters (e.g., targets), such as any of accuracy, latency, reliability, and completeness, which may be associated with a positioning service (e.g., any of MO-LR, MT-LR, delayed MT-LR) and / or a mapping relationship (e.g., configuration, association) between the positioning QoS parameters (e.g., targets) and one or more PRS configurations (e.g., parameters) to use in conjunction with the positioning QoS parameters (e.g., targets). The WTRU may determine a PRS configuration (e.g., parameters) to indicate in the on-demand request based on any of the positioning QoS parameters (e.g., targets) and the mapping relationship.

[0250] In an example, a WTRU may have access to one or more sets of PRS configurations (e.g., parameters), and at least one of the sets may be determined to be valid and / or at least one of the sets may be determined to be either invalid and unavailable. For example, a set of PRS configurations (e.g., parameters) may be determined to be invalid by the WTRU if any of the following events (e.g., conditions) occur: ● It is not accessible by the WTRU via the SIB (eg, posSIB). ●It may be determined that one or more of the preconfigured PRS configurations (e.g., parameters) preconfigured in the WTRU do not meet a validity condition (e.g., a time validity event has expired, the WTRU is located outside the validity area or outside a valid cell ID, the RSRP of the PRS measurement is above / below the RSRP threshold, the number of multipaths is below / above a multipath threshold). ● Received by the WTRU outside an ongoing LPP session (e.g., via LPP assistance data), which may be determined to be active, and received by the WTRU in a previous LPP session, which may be determined to be either inactive, released, or expired. ● Received by the WTRU with either an implicit or explicit indication from the network indicating that one or more PRS configurations (e.g., one or more parameters) may not be valid, available, supported, etc.

[0251] In an example, the WTRU may select (e.g., determine) a PRS configuration (e.g., parameters) to indicate in the on-demand PRS request by first identifying (e.g., determining) an appropriate (e.g., candidate) PRS configuration (e.g., parameters) from a set determined to be valid (e.g., having a higher priority), e.g., a set that may match (e.g., satisfy) the positioning QoS parameters (e.g., requirements, goals), e.g., based on a mapping relationship. If the WTRU is unable to determine an appropriate (e.g., candidate) PRS configuration (e.g., parameters) from a set determined to be valid, the WTRU may select an appropriate (e.g., candidate) PRS configuration (e.g., parameters) from a set determined to be either invalid and unavailable, e.g., based on a mapping relationship. To assist the WTRU in determining a PRS configuration (e.g., parameters), the WTRU may receive information from the network (e.g., in assistance data) indicating any of the following: • Validity status, which indicates that any of the PRS configurations and parameters can be either valid or invalid. ● Priority information associated with either the priority (e.g., parameter(s)) of the PRS configuration(s) and the priority of the validity status may be associated with different validity conditions. For example, a PRS configuration (e.g., parameter) that may satisfy an area validity condition may be assigned (e.g., associated) with a priority value of p1, a PRS configuration (e.g., parameter) that may satisfy a time validity condition may be assigned (e.g., associated) with a priority value of p2, and a PRS configuration (e.g., parameter) that may not satisfy an area validity condition may be assigned (e.g., associated) with a priority value of p3. For example, the WTRU may determine the PRS configuration (e.g., parameter) to indicate in the on-demand request based on an order of priority, where, for example, a first priority p1 may be a higher priority than a second priority p2, which may be a higher priority than a third priority p3 (e.g., p1>p2>p3). Other methods of mapping priorities to validity conditions may be applicable to the embodiments described herein.

[0252] In another example, the WTRU may select (e.g., determine) a PRS configuration (e.g., parameter) to indicate an on-demand PRS request that may be suitable and / or meet a positioning QoS objective regardless of (independently of) whether the PRS configuration (e.g., parameter) may be determined to be valid or invalid. In another example, the WTRU may determine a PRS configuration (e.g., parameter) to indicate an on-demand PRS request based on a combination of PRS configurations (e.g., parameters) from a set determined to be either valid and invalid. For example, the WTRU may determine one or more PRS configurations or groups of PRS parameters to indicate in the on-demand PRS request, where a first PRS configuration (e.g., parameter) may be determined from a valid set and a second PRS configuration (e.g., parameter) may be determined from an invalid set.

[0253] For example, after selecting a (eg, appropriate) PRS configuration (eg, parameters), the WTRU may send either an on-demand PRS request and a request for assistance data that includes information that may be indicative of any of the following information: ● An identifier (e.g., ID) associated with either the selected PRS configuration(s) and selected PRS parameters, e.g., along with the status of the selection. The PRS configuration (e.g., parameters) may be selected by the WTRU from a set of PRS configurations (e.g., parameters) that may be i) determined to be valid (e.g., either accessible via the SIB or pre-configured in the WTRU), ii) determined to be invalid (e.g., either not accessible from the SIB or pre-configured whose validity has expired), and iii) determined to be a combination of valid and invalid. Any of the identifiers and flags indicating the validity status of the selection, e.g., whether the selected PRS configuration (e.g., parameters) may be selected from the determined set to be valid or invalid (e.g., unavailable). For example, the WTRU may indicate an ID (e.g., flag) associated with an invalid set if any of the selected, determined, and indicated PRS configurations (e.g., parameters) are from outside of either the posSIB and the LPP session. Events (e.g., conditions) associated with validity conditions that may be determined to be either valid and invalid, associated with any of the indicated selected PRS configurations (e.g., parameters) and the indicated status of the selection. For example, the WTRU may include information in the on-demand request indicating which of the validity conditions (e.g., time validity, area validity) have been determined to be met and / or not met. Timing information (eg, a timestamp) indicating a time associated with the on-demand request. For example, the time may indicate when the indicated PRS configuration (eg, parameters) in the one-demand request may be requested by the WTRU. Information indicating whether the indicated PRS configuration (e.g., parameters) (valid / invalid) may be used by the WTRU on a best-effort basis for the WTRU or on a required (e.g., guaranteed) basis. For example, the WTRU may indicate an invalid 1 PRS configuration, and a first PRS configuration may be determined from the invalid set and used by the WTRU on a best-effort basis. For example, the WTRU may indicate a second PRS configuration, which may be determined from the valid set and may be requested by the WTRU. For example, the information may indicate that both the first and second PRS configurations may be used to satisfy positioning QoS parameters (e.g., requirements, goals). For example, an indication sent by the WTRU may enable the network to provide the first PRS configuration (e.g., best-effort) if the network is unable to provide the second PRS configuration.

[0254] For example, in the case of MO-LR, when there may not be any LPP sessions in progress and the previous LPP session may have been released, the WTRU may send information indicating an on-demand PRS request to the network (e.g., either the LMF or the base station) along with (e.g., included in) the MO-LR location service request message. In such a case, the on-demand PRS request sent by the WTRU may include information indicating the PRS configuration (e.g., parameters) (e.g., ID) selected by the WTRU. For example, the on-demand PRS request sent by the WTRU along with (e.g., included in) the MO-LR service request may include information as described above (e.g., indicating whether the indicated PRS configuration (e.g., parameters) may be from a valid set or an invalid set). If the WTRU sends a first on-demand request (e.g., with an MO-LR service request) including information indicating that the indicated PRS configuration (e.g., parameters) may have been selected from an invalid set, the WTRU may receive a response from the LMF (e.g., after LPP session establishment, e.g., when providing LPP assistance data). For example, the response may include information indicating a set of one or more PRS configurations (e.g., parameters) that may be valid, available, and supported. For example, the WTRU may send a second on-demand request to the network that includes information indicating a PRS configuration (e.g., parameters) that may be selected (e.g., determined) from the valid set.

[0255] Example of a WTRU performing UL SRSp transmission in inactive state to support delayed MT-LR In an embodiment, a WTRU, which may be operating in an RRC inactive state, may perform an SRSp transmission for UL-based positioning based on detecting one or more events associated with either an MT-LR and a delayed MT-LR positioning service. A delayed MT-LR positioning service may be referred to herein as a procedure in which a higher layer (e.g., an application), such as, for example, an LCS client, located in, for example, a network, may cause (e.g., send) one or more instructions to, for example, an LMF, a base station (e.g., any of a serving and non-serving gNB (e.g., TRP)) and the WTRU to establish and configure a location service session (e.g., an LPP session). In such a case, for example, after receiving a delayed MT-LR service request from the network (e.g., any of the LMF and base station), the WTRU may receive information from the network indicating one or more SRSp configurations (e.g., any of periodic, semi-persistent, and aperiodic) for performing an UL SRSp transmission for UL-based positioning. For example, the WTRU may also receive one or more trigger events (e.g., information indicative thereof) that may be associated with the delayed MT-LR, e.g., for the WTRU to either monitor and / or perform a UL-SRSp transmission if at least one of the configured trigger events is detected. The triggers described herein may include one or more of the following: ● Time event: a periodic time event in which the WTRU may transmit the SRSp periodically, based on a periodicity that may be configured, for example, by receiving configuration information indicating a time event (eg, trigger event) configuration. ● Area Event: For example, an area event may be associated with one or more cells (eg, cell IDs) to which the WTRU may transmit an SRSp if a cell (eg, cell ID) associated with the configured area event is detected. ● Mobility event: For example, a mobility event may be related to the mobility attributes of the WTRU (e.g., any of the WTRU speed, direction of movement, and trajectory (e.g., route)), and the WTRU may transmit an SRSp when a change in one or more mobility attributes is detected (e.g., WTRU speed goes above / below a threshold, WTRU trajectory changes by a threshold, ...).

[0256] For example, the WTRU may perform SRSp transmission until a stop event (e.g., condition) associated with stopping (e.g., pausing) the SRSp transmission may be detected by the WTRU. The SRSp transmitted by the WTRU may be measured by the base station and the measurements may be reported to the LMF, which may then determine (e.g., estimate) the location of the WTRU based on the measurements. For example, the LMF may send information indicating the determined location (e.g., estimate) to an application (e.g., an LCS client).

[0257] In an example, the delayed MT-LR procedure (e.g., method) may be performed by a WTRU operating in any of the RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE states. For example, the information indicating the SRSp configuration received by the WTRU to operate UL-based positioning may be used by the WTRU regardless of whether the WTRU may be operating in any of the (e.g., RRC) states. For example, both the trigger event to start SRSp transmission and the stop event to stop (e.g., pause, end) transmission may also be used by the WTRU regardless of the (e.g., RRC) state. In another example, the delayed MT-LR procedure (e.g., method) may be performed with awareness of the (e.g., RRC) states in which the WTRU may operate. In such a case, the WTRU may receive information indicating different SRSp configurations depending on the (e.g., RRC) state of the WTRU. For example, the WTRU may use different SRSp configurations depending on the (e.g., RRC) state of the WTRU (e.g., may use different SRSp configurations for different (e.g., RRC) states). For example, both the trigger event for starting SRSp transmission and the stop event for stopping (e.g., pausing, terminating) SRSp transmission may depend on (e.g., may be associated with) the (e.g., RRC) state in which the WTRU may operate.

[0258] In an example, the WTRU may receive information indicating one or more SRSp configurations (e.g., in any of an RRC message, MAC CE, and DCI) when the WTRU is operating in an RRC_CONNECTED state. The WTRU may store the SRSp configuration in the WTRU context and use it for SRSp transmission when the WTRU is operating in an INACTIVE state, e.g., after detecting one or more trigger events (e.g., any of a time event, an area event). In another example, the WTRU may receive information indicating one or more SRSp configurations when the WTRU is operating in an RRC inactive state. In such a case, the WTRU may receive information indicating the SRSp configuration in an RRC message (e.g., an RRC release message with a suspend configuration indication), e.g., to transition from a CONNECTED state to an INACTIVE state.

[0259] If the WTRU detects one or more trigger events, e.g., the WTRU may operate in an INACTIVE state, the WTRU may send an indication (e.g., to either the LMF or the gNB) to the network to indicate either an event indication and an event report regarding the detection of the trigger events. For example, information may be sent by the WTRU to the network, which may indicate that a trigger event may have been detected. For example, the WTRU may transmit information (eg, an indication) in a small data transmission (SDT), eg, using resources associated with the SDT (eg, either a random access SDT or a configured grant SDT).

[0260] For example, the WTRU may request an SRSp configuration. If the WTRU determines that the preconfigured SRSp configuration is not valid (e.g., with respect to one or more validity conditions described herein) and / or if the WTRU requests (e.g., sends information indicating a request) to update the validity conditions, the WTRU may send an indication (e.g., information indicating the same) requesting activation of the preconfigured SRSp configuration (e.g., either periodic, semi-persistent, or aperiodic). The WTRU may send the first information indicating either the event indication and the event report, and the second information indicating the request for the SRSp configuration (e.g., activation of the SRSp configuration) in one indication (e.g., information piece) or two indications (e.g., information pieces). The WTRU may send one or more indications (e.g., information pieces) along with (e.g., included in) the SDT (e.g., using the SDT resources) if, for example, the WTRU operates in an INACTIVE state.

[0261] In an example, the first indication that may be transmitted by the WTRU may include information indicating one of an event indication, an event report, and a request for SRSp configuration, and the second indication that may be transmitted by the WTRU may include information indicating one of a request for SRSp configuration and an activation of an SRSp configuration. In another example, the WTRU may transmit the first indication indicating one of an event indication and a request for SRSp configuration, and the WTRU may transmit the second indication indicating an event report, e.g., the second indication may be transmitted after performing an UL SRSp transmission using the received SRSp configuration.

[0262] For example, the one or more indications may be sent by the WTRU explicitly in any of the LPP messages to the LMF and in any of the AS layer messages (e.g., any of the RRC messages, MAC CE, and UCI) to the gNB. The explicit indication (e.g., a piece of information) may be sent by the WTRU along with (e.g., included in) the SDT (e.g., using any of the SDT-SRB2 and SDT resources), for example, when the WTRU is operating in an INACTIVE state. In another example, the WTRU may send an indication (e.g., any of the event indications, a request for SRSp configuration, a request for SRSp activation) to the network implicitly (e.g., without sending explicit information). For example, the WTRU may be pre-configured with any of one or more SRSp configurations, parameters associated with the SRSp configurations (e.g., any of the periodicity, time / frequency resource sets, frequency layers, etc.), and mappings (e.g., sets of associations) between different indications and any of the SRSp configurations and parameters. In such a case, the WTRU may send a first indication (e.g., an event indication) using the first SRSp configuration (e.g., parameters), e.g., when a trigger event is detected, and send a second indication (e.g., indicating a request to activate the SRSp configuration) using the second SRSp configuration (e.g., parameters), e.g.

[0263] For example, after sending either an indication (e.g., information indicative thereof) of an event indication and an event report, the WTRU may receive information indicative of an SRSp configuration from the network. For example, after sending an indication to the network, the WTRU may (e.g., further) receive an activation indication (e.g., information indicative of activation) for activating one or more pre-configured SRSp configurations, e.g., in either the MAC CE and the DCI. For example, the WTRU may receive an activation indication (e.g., information indicative of activation of transmission) for activating a semi-persistent SRSp transmission. For example, a configuration for a semi-persistent SRSp may have been pre-configured in the WTRU. For example, a configuration for a semi-persistent SRSp may have been received by the WTRU from the network, e.g., in an activation indication. For example, the WTRU may receive (e.g., similarly) a similar activation indication (e.g., in the DCI) for activating a non-periodic SRSp transmission.

[0264] For example, the WTRU may stop (eg, suspend) SRSp transmission in the INACTIVE state based on one or more of the following stopping events (eg, conditions): ● Receiving an indication (e.g., information) from the network: For example, the WTRU may stop (e.g., suspend) SRSp transmission if the WTRU receives one or more indications (e.g., pieces of information) indicating any of the following: deactivation, suspension, termination, and release of an SRSp configuration available at the WTRU. In an example, a WTRU performing periodic SRSp transmission (using an SRSp configuration for periodic SRSp) may stop (e.g., suspend) SRSp transmission if information indicating the stop (e.g., suspend) is received from the network. For example, the WTRU may receive information of the INACTIVE state via any of the LPP messages and access stratum (AS) layer messages (e.g., RRC messages, MAC CE, and DCI). Expiration of a validity condition: For example, the WTRU may stop (e.g., pause) the SRSp transmission if the SRSp configuration used for the SRSp transmission is determined to be invalid with respect to one or more associated validity conditions. In an example, the SRSp configuration may be associated with a timing advance (TA) timer as a validity condition (as described herein) for performing the SRSp transmission. For example, when the TA timer expires (e.g., when it is determined that the TA time has elapsed), the WTRU may either stop (e.g., pause) the SRSp transmission or release the SRSp configuration. Per parameters of the SRSp configuration: For example, the WTRU may stop (e.g., pause) the SRSp transmission based on parameters of the SRSp configuration. For example, the parameters may include any of the SRSp duration, periodicity, resource set, frequency layer, etc. In such a case, the WTRU may stop transmitting the semi-persistent SRSp, for example, at the end of a duration associated with the semi-persistent SRSp.

[0265] Example of validity conditions for using SRSp configuration during inactive state operation The WTRU may receive from the network (e.g., any of the LMF and gNB) one or more validity conditions (e.g., criteria) associated with (e.g., information indicative of) an SRSp configuration, e.g., for use in the INACTIVE state. For example, the validity conditions (e.g., criteria) associated with the SRSp configuration may include one or more of the following: Area validity: For example, any of the Cell ID, RAN Notification Area (RNA), and CN area for which any of the pre-configured SRSp configurations and parameters may be valid for use. ● Time validity: e.g., the duration during which an SRSp configuration may be valid for use (e.g., from a first (e.g., start) time instance to a second (e.g., expiration) time instance). The WTRU may start a timer upon receiving information indicating an SRSp configuration, and may use the configuration for SRSp transmission as long as the timer is valid within the configured duration and / or has not expired. For example, the WTRU may use the SRSp configuration for SRSp transmission for a duration after receipt of the SRSp configuration information. WTRU mobility conditions: For example, the WTRU may use a pre-configured SRSp configuration when the WTRU velocity is below / above a configured velocity threshold. Similarly, the WTRU may use a pre-configured SRSp configuration when either the amount and velocity (e.g., orientation) of the WTRU movement increases / decreases by a threshold. ● Timing Advance (TA) validity: For example, the TA validity for use of an SRSp configuration may be associated with a Timing Advance (TA) configured in the WTRU (e.g., TA configuration information may be received by the WTRU from the network). For example, the TA validity for use of an SRSp configuration may be associated with a TA timer associated with the configured TA. For example, a TA may be valid across one or more cells in which the WTRU may be mobile, and the validity of the TA may be determined, for example, based on a TA timer. For example, the WTRU may use a pre-configured SRSp configuration as long as any of the TA configurations may be valid and the TA timer may not have expired. WTRU radio environment For example, a WTRU that may be pre-configured with one or more SRSp configurations may change from using a first SRSp configuration to a second SRSp configuration if the RSRP of measurements made on any of the PRS and non-positioning RS / channels (e.g., any of the CSI-RS, SSB) is above / below an RSRP threshold. For example, the WTRU may change from a first SRSp configuration to a second SRSp configuration if the number of multipaths is above / below (eg, detected) a threshold and / or if a NLOS condition is detected. Indication from the network: For example, the WTRU may determine that an SRSp configuration is valid if an indication (e.g., information) is received from the network (e.g., either the LMF or the gNB) indicating that the SRSp configuration (e.g., an ID of the SRSP configuration) may be used for SRSp transmission. For example, the indication (e.g., information) may be received by the WTRU in any of an LPP message, an RRC message, a MAC CE, and a DCI. RRC state of the WTRU (e.g., CONNECTED, INACTIVE, IDLE): For example, the WTRU may change from using a first SRSp configuration for SRSp transmission to a second SRSp configuration when the WTRU changes (e.g., transitions) from a first RRC state to a second RRC state. In such a case, the WTRU may stop (e.g., suspend, release) the first SRSp configuration before using the second SRSp configuration (e.g., when transitioning from the first RRC state to the second RRC state).

[0266] The validity conditions may be used by the WTRU to determine whether an SRSp configuration (e.g., any of those received and stored by the WTRU) may be enabled or disabled for use, for example, to initiate an SRSp transmission when one or more triggering events (e.g., associated with a delayed MT-LR) are detected. Different types of SRSp configurations (e.g., periodic, semi-persistent, and aperiodic) may be associated with different validity conditions. For example, an SRSp configuration used for periodic SRSp transmission may be associated with a first set of one or more validity conditions (e.g., area validity), and an SRSp configuration used for semi-persistent SRSp transmission may be associated with a second set of one or more validity conditions (e.g., time validity). For example, a validity condition may be associated with one or more SRSp configurations and any of the other UL configurations (e.g., CG, RACH, SDT configurations). For example, the WTRU may receive (e.g., information indicative of) a common set of one or more validity conditions that may apply to a first SRSp / UL configuration and a second SRSp / UL configuration.

[0267] In an example, the information indicating the validity condition may be explicitly received by the WTRU in one or more indications (e.g., messages) (e.g., via any of an LPP message, a SIB, an RRC message, a MAC CE, and a DCI), e.g., when information indicating any of an SRSp configuration and a trigger event is received. In another example, the information indicating the validity condition may be received implicitly, which may indicate that the SRSp configuration may be valid for use (e.g., only if) the WTRU camps within any of the cells and coverage areas of the gNB that may receive the information indicating the SRSp configuration. In another example, the implicit validity condition indication may be based on an association between different SRSp / UL configurations. In such a case, when the WTRU receives a first SRSp / UL configuration and any of a first set of one or more validity conditions, the WTRU may apply the first set of validity conditions to the second SRSp / UL configuration, e.g., when it is determined that the first SRSp / UL configuration is associated with the second SRSp / UL configuration.

[0268] In an example, the validity condition (e.g., for determining whether an SRSp configuration available (e.g., stored) at the WTRU is valid or invalid for use) may be associated with a delayed MT-LR positioning service (e.g., procedure) and any of the trigger events used to initiate an SRSp transmission. For example, the WTRU may initiate (e.g., perform) an SRSp transmission using a pre-configured SRSp configuration if one or more trigger events (e.g., any of a time event and an area event) are detected. For example, the WTRU may initiate (e.g., perform) an SRSp transmission using a pre-configured SRSp configuration if the pre-configured SRSp configuration is determined to be valid (e.g., any of the TA timers are valid and may not have expired).

[0269] For example, the information indicative of one or more validity conditions may be received by the WTRU in any of the following examples: If a trigger event (e.g., information indicating such) is received: For example, the WTRU may receive information indicating a validity condition from the LMF when information indicating either a delayed MT-LR service request or a triggering event is received. For example, the information indicating the validity condition may be included in the information indicating either a delayed MT-LR service request or a triggering event. ●If information is received indicating an SRSp setting: For example, the WTRU may receive information indicative of one or more validity conditions from a network (e.g., any of the gNB and LMF) in the RRC_CONNECTED state, e.g., when information indicating an SRSp configuration is received. For example, the information indicative of the validity conditions may be included in the information indicating the SRSp configuration. For example, the WTRU may store the validity conditions along with the SRSp configuration, and when a triggering event is detected, the WTRU may determine whether the stored configured SRSp is valid for use based on whether an associated validity condition is satisfied. o In another example, the WTRU may receive information indicating one or more validity conditions (e.g., a TA timer) from a network (e.g., one of a gNB and an LMF) in an RRC inactive state, e.g., when information indicating an SRSp configuration is received. For example, the information indicating the one or more validity conditions may be included in the information indicating the SRSp configuration. For example, the WTRU may use the SRSp configuration for UL SRSp transmission as long as the SRSp configuration is determined to be valid (e.g., the TA timer may either be valid or not expired). The WTRU may suspend (e.g., release) the SRSp configuration if the validity condition is not met (e.g., when a TA time associated with the TA timer is determined to have elapsed). In another example, the WTRU may receive the information indicating the validity condition separately from receiving the information indicating the SRSp configuration. For example, the WTRU may receive the information indicating the validity condition before / after receiving the information indicating the SRSp configuration. For example, the WTRU may receive the first information indicating the validity condition and the second information indicating the SRSp configuration in separate (e.g., different) messages (e.g., signaling) from the network. For example, the validity condition may be associated with the SRSp configuration via a mapping relationship that indicates a mapping (e.g., association) between the validity condition and an ID of the SRSp configuration. When instructions are sent to the network: o For example, the WTRU may receive information indicative of one or more validity conditions after sending an indication to the network (e.g., either gNB or LMF), e.g., with the SDT and / or using SDT resources (e.g., RA-SDT, CG-SDT). In an example, a WTRU that may be configured with a trigger event (for a delayed MT-LR) and either operate in an INACTIVE state may send an indication (e.g., information indicative of either a location event indication and a location event report) if one or more trigger events are detected. For example, the WTRU may receive from the network, e.g., information indicative of an SRSp configuration and an instruction to use a pre-configured SRSp configuration (e.g., an ID of the configuration) for use in the INACTIVE state. The WTRU may also receive information indicative of one or more validity conditions to assist in determining whether to use or deactivate an SRSp configuration for UL SRSp transmission, e.g., after sending an indication to the network.

[0270] If the pre-configured SRSp configuration is determined to be invalid, for example after detecting one or more triggering events, the WTRU may do any of the following: Sending instructions to the network: o For example, the WTRU may send an indication (e.g., information) to the network indicating either detection of a trigger event and an SRSp configuration identifier (e.g., ID). For example, the (information sent by) the WTRU may indicate an expiration status of the SRSp configuration. For example, the (information sent by) the WTRU may indicate a request to update the SRSp configuration and any validity conditions associated with the indicated SRSp configuration. For example, the indication (e.g., information) may be sent to the network in any of an LPP message, an on-demand PRS message (e.g., to any of the LMF and gNB), and an AS layer message (via any of the RRC, MAC CE, and UCI). ● Change to an alternative valid SRSp configuration: o For example, the WTRU may use a second SRSp configuration that may be determined to meet its validity condition if the first SRSp configuration is determined to be no longer valid. If there are multiple (e.g., two or more) SRSp configurations that are determined to be valid and if the first SRSp configuration is determined to be invalid, the WTRU may select a second SRSp configuration from the valid configurations. For example, the second SRSp configuration may be selected based on a priority (e.g., may be assigned the highest priority). If all available SRSp configurations are determined to be invalid and / or no SRSp configuration that may be valid is available, the WTRU may select a second SRSp configuration from an invalid set of SRSp configurations, e.g., based on a priority (e.g., the selected SRSp configuration is assigned the highest priority). ● Either of the following conditions for updating SRSp settings and enabling transfer: o For example, if the WTRU determines that an SRSp configuration is no longer valid, e.g., based on a validity condition (e.g., a TA timer), the WTRU may update and forward its validity conditions, e.g., based on validity conditions associated with either another SRSp configuration and another UL configuration associated with the SRSp configuration that may be determined to be valid. In such a case, the WTRU may change a first validity condition (e.g., associated with a first SRSp configuration) to be similar to that of a second validity condition (e.g., associated with either a second SRSp configuration and UL configuration), e.g., if the first validity condition expires and the second validity condition is found to be active (e.g., valid) during (e.g., after) the expiration of the first validity condition. For example, if the validity conditions (e.g., TA timer) for any of the associated second SRSp configurations and associated UL configurations (e.g., any of the CG and SDT) are determined to be valid, the WTRU may update the validity conditions of the first SRSp configuration (e.g., by extending the TA timer), e.g., before / after determining that the validity conditions of the first SRSp configuration are either not valid and dissimilar compared to any of the second SRSp and UL configurations. For example, the WTRU may send an indication (e.g., information) to the network indicating (e.g., requesting) an update and transfer of the validity conditions from the first SRSp / UL configuration to the second SRSp configuration.

[0271] 11 illustrates an example of a method 1100 for (e.g., dynamically) configuring measurement gaps for WTRU positioning determination. For example, method 1100 may be implemented in a WTRU. For example, in step 1110, the WTRU may determine a status of PRS resources. For example, in step 1120, the WTRU may send a request for measurement gap reconfiguration to the wireless network. For example, in step 1130, the WTRU may receive a measurement gap configuration (e.g., information indicative thereof) from the network, for example, in response to the request.

[0272] For example, the request may be sent via one of the MAC-CE and UCI.

[0273] For example, the WTRU may send a request to the LMF via the gNB and may receive a measurement gap configuration (e.g., information indicative thereof) from the LMF via the gNB.

[0274] For example, the measurement gap configuration (e.g., information indicative thereof) may be received via LPP signaling.

[0275] For example, the status of the PRS resource may include at least one of: (a) the RSRP of the PRS satisfying a first threshold; (b) a linear average of the RSRP of the PRS over a first time window satisfying a second threshold; (c) the RSRP of the PRS over a second time window satisfying a third threshold; (d) a linear average of the RSRP of the PRS over a third time window satisfying a fourth threshold over the third time window; (e) the variance of the WTRU's location estimate satisfying a fifth threshold; and (f) the standard deviation of the WTRU's location satisfying a sixth threshold.

[0276] For example, the measurement gap configuration (eg, information indicative thereof) may indicate any of a measurement gap length, a measurement gap periodicity, and a measurement gap offset.

[0277] For example, the request may include (eg, requested) parameters of the measurement gap.

[0278] For example, the request may include a request (eg, information indicating so) to disable all or part of the measurement gap.

[0279] For example, method 1100 may further include determining a time window during which the PRS may be assigned priority relative to other receiving channels. For example, method 1100 may further include determining a priority of the PRS relative to other receiving channels during the time window. If the PRS is received outside the measurement gap and simultaneously with data on one of the other receiving channels during the time window, the WTRU may determine whether to process the PRS or the other channel based on the priority.

[0280] For example, determining the time window may include receiving configuration information from a network that indicates the time window.

[0281] For example, the time window may start after a first transmission or reception opportunity of the PRS by the WTRU and may end after a last reception or transmission opportunity of the PRS by the WTRU.

[0282] For example, the method 1100 may further include (1) determining to reduce at least one of the measurement duration and the number of measurement samples to be performed based on the condition, and (2) in response to the determination, sending a measurement gap reconfiguration request to the network.

[0283] For example, the condition may be that the RSRP of the PRS is above a threshold.

[0284] For example, the condition may be receipt of an explicit instruction from the network to reduce the number of measurement samples.

[0285] For example, the method 1100 may further include measuring a portion of the PRS resources configured by the network.

[0286] For example, the method 1100 may further include transmitting configuration information regarding the PRS transmitted from the non-serving gNB to the serving gNB.

[0287] For example, the configuration information regarding a PRS from a non-serving gNB may include (e.g., may indicate) at least one of: (1) a time offset from the end of transmission of the PRS from the serving gNB for the PRS to be transmitted from the non-serving gNB; and (2) a duration of the PRS configured to be transmitted from the non-serving gNB.

[0288] FIG. 12 illustrates another example of a method 1200 for configuring a measurement gap for WTRU positioning determination. For example, the method 1200 may be implemented in a WTRU. For example, in step 1210, provided that the WTRU determines that the base station acknowledges the configuration request for the measurement gap, the WTRU may determine that the PRS may be configured in the LMF such that the WTRU may receive the PRS from either the serving base station and a neighboring base station within the configured measurement gap. For example, in step 1220, the WTRU may determine whether an initial (e.g., default) measurement gap is configured by the base station, provided that a preconfigured condition is met. For example, in step 1230, the WTRU may (1) receive the PRS from either the serving base station and a neighboring base station without a measurement gap, and (2) receive information configuration from the LMF indicating either time and frequency resources for receiving the PRS.

[0289] FIG. 13 illustrates another example of a method 1300 for configuring a measurement gap for WTRU positioning determination. For example, the method 1300 may be implemented in a WTRU. For example, in step 1310, PRS configuration information (e.g., dedicated) for a PRS-BWP may be received from an LMF. For example, in step 1320, information indicating a BWP configuration may be received from a base station, and a first indication that a BWP may correspond to a PRS-BWP may be received via an RRC. For example, in step 1330, a second indication indicating that a PRS-BWP may be scheduled may be received from a base station via a DCI. For example, in step 1340, a PRS may be received in a PRS-BWP. For example, in step 1350, upon determining that a certain amount of time has elapsed after a PRS may be received in a PRS-BWP, it may be determined that an initial measurement gap may be configured and an associated PRS configuration may be configured.

[0290] FIG. 14 illustrates another example of a method 1400 for configuring measurement gaps for WTRU positioning determination. For example, the method 1400 may be implemented in a WTRU. For example, in step 1410, a mobile originated location request (MO-LR) may be received from a location services (LCS) client in the WTRU. For example, in step 1420, in response to the MO-LR, capability information may be transmitted to the network indicating support for one or more positioning methods and requesting to establish an LPP session. For example, in step 1430, assistance information may be received in response to the capability information transmission indicating at least one PRS configuration. For example, in step 1440, measurements of the PRS may be performed using the indicated at least one PRS configuration.

[0291] 15 illustrates an example of a method 1500 for requesting a measurement gap configuration. For example, the method 1500 may be implemented in a WTRU. For example, in step 1510, configuration information indicating at least one PRS configuration may be received. For example, in step 1520, at least one first PRS configuration may be selected from the indicated at least one PRS configuration. For example, in step 1530, information indicating a request for the selected at least one first PRS configuration may be transmitted, for example, to a network.

[0292] For example, it may be determined by the WTRU whether the indicated at least one PRS configuration may be either valid or invalid.

[0293] For example, the indicated at least one PRS configuration may be determined to be either valid or invalid based on a validity condition associated with the indicated at least one PRS configuration.

[0294] For example, the validity condition may be based on any of a time parameter associated with the indicated at least one PRS configuration, an area parameter associated with the indicated at least one PRS configuration, and a WTRU mobility attribute.

[0295] For example, the at least one first PRS configuration may be selected from the at least one indicated PRS configuration that may be determined to be valid.

[0296] For example, the at least one first PRS configuration may be selected from the at least one indicated PRS configuration that may be determined to be invalid, provided that all of the at least one indicated PRS configuration may be determined to be invalid.

[0297] For example, the transmitted information may further indicate at least one identifier associated with the selected at least one first PRS configuration.

[0298] For example, the transmitted information may further indicate whether the selected at least one first PRS configuration may have been determined to be valid or invalid.

[0299] For example, the transmitted information may further indicate event information associated with a validity condition used to determine whether the selected at least one first PRS configuration may be determined to be valid or invalid.

[0300] For example, the transmitted information may further include time information indicating a time associated with a request for the selected at least one first PRS configuration.

[0301] For example, the transmitted information may further indicate whether the selected at least one first PRS configuration may be associated with a best effort mode of operation or a guaranteed mode of operation.

[0302] FIG. 16 illustrates another example of a method 1600 for requesting a measurement gap configuration. For example, the method 1600 may be implemented in a WTRU. For example, in step 1610, the WTRU may receive configuration information indicating one or more measurement gap patterns, where the measurement gap pattern may be associated with any of a measurement gap length, a measurement gap periodicity, and a measurement gap identifier. For example, in step 1620, the WTRU may measure a first positioning reference signal transmission (e.g., perform a first positioning reference signal measurement) during a first measurement gap period, where the first measurement gap period may be determined based on the initial measurement gap length and the initial measurement gap periodicity. For example, in step 1630, the WTRU may transmit a request for a first measurement gap pattern of the indicated one or more measurement gap patterns based on the measured first positioning reference signal transmission (e.g., the first positioning reference signal measurement), where the request may include first information indicating a first measurement gap identifier associated with the first measurement gap pattern. For example, at step 1640, the WTRU may receive second information indicating to activate a second measurement gap pattern of the indicated one or more measurement gap patterns, where the second information may indicate a second measurement gap identifier associated with the second measurement gap pattern. For example, at step 1650, the WTRU may measure a second positioning reference signal transmission (e.g., perform a second positioning reference signal measurement) during a second measurement gap period, where the second measurement gap period may be determined based on a second measurement gap length and a second measurement gap periodicity, which may be associated with the second measurement gap pattern.

[0303] For example, the second measurement gap identifier may correspond to (eg, be the same as) a first measurement gap identifier associated with the first measurement gap pattern.

[0304] For example, the second measurement gap identifier may be different from the first measurement gap identifier associated with the first measurement gap pattern.

[0305] For example, the WTRU may receive initial configuration information indicating either an initial measurement gap length and an initial measurement gap periodicity.

[0306] For example, the WTRU may transmit report information indicating one or more second metrics obtained from a measured second positioning reference signal transmission (eg, a second positioning reference signal measurement performed).

[0307] For example, the request may be sent via the MAC-CE.

[0308] For example, the second information may be received via a MAC-CE.

[0309] For example, the second measurement gap periodicity may be the same period as the initial measurement gap periodicity.

[0310] For example, the second measurement gap length may be different from the initial measurement gap length.

[0311] For example, a request for a first measurement gap pattern may be transmitted on the condition that one or more first metrics obtained from a measured first positioning reference signal transmission satisfy a criterion (e.g., a condition).

[0312] For example, the one or more first metrics may include a quality metric representative of a quality of a measured first positioning reference signal transmission (eg, a first positioning reference signal measurement performed).

[0313] For example, the quality metric may include either the reference signal received power or an average of the reference signal received power over the first duration.

[0314] For example, the one or more first metrics may include a stability variability metric that represents a stability variability of the location of the WTRU.

[0315] For example, the stability variability metric may include either the variance and standard deviation of the locations of the WTRUs.

[0316] For example, the second measurement gap length may be shorter than the initial measurement gap length.

[0317] For example, the one or more first metrics that meet the criteria may include a quality metric that is above a threshold.

[0318] For example, the criteria may include a quality metric exceeding a threshold for a second duration.

[0319] For example, the one or more first metrics that meet the criteria may include a stability variability metric that is below a threshold.

[0320] For example, the threshold may be a configurable threshold.

[0321] For example, a request for a first measurement gap pattern may be sent on the condition that scheduling information is received indicating one or more downlink transmissions, where the one or more downlink transmissions may be associated with a higher priority than an initial priority associated with the initial measurement gap length and initial measurement gap periodicity.

[0322] For example, the one or more downlink transmissions may include any of channel state information, data channel information, and control channel information.

[0323] For example, the WTRU may receive a data transmission after the end of the second measurement gap period and before the end of the first measurement gap period.

[0324] For example, upon determining that a period of time may have elapsed after receiving second information indicating to activate the second measurement gap pattern, a third positioning reference signal transmission may be measured during a third measurement gap period determined based on the initial measurement gap length and the initial measurement gap periodicity.

[0325] For example, the second measurement gap length may be longer than the initial measurement gap length.

[0326] For example, the one or more first metrics that meet the criteria may include a quality metric that is below a threshold.

[0327] For example, the criteria may include a quality metric being below a threshold for a second duration.

[0328] For example, the one or more first metrics that meet the criteria may include a stability variability metric that is above a threshold.

[0329] For example, the threshold may be a configurable threshold.

[0330] For example, the WTRU may receive positioning reference signal configuration information indicating additional positioning reference signal resources associated with an activated second measurement gap pattern.

[0331] FIG. 17 illustrates another example of a method 1700 for requesting a measurement gap configuration. For example, the method 1700 may be implemented in a WTRU. For example, in step 1710, the WTRU may receive configuration information indicating, for example, a first positioning configuration associated with a validity metric. For example, in step 1710, the WTRU may determine, based on the validity metric, that the first positioning configuration may be invalid. For example, in step 1720, the WTRU may transmit first information requesting assistance data. For example, the first information may indicate that a second positioning configuration may be requested. For example, in step 1730, the WTRU may receive second information indicating a second positioning configuration to be activated.

[0332] For example, the second indicated positioning configuration may be activated.

[0333] For example, the first positioning configuration may be further determined to be invalid on condition that the speed at which the WTRU may be moving meets a criterion (e.g., the speed has either an increase or decrease by a threshold value).

[0334] For example, the threshold may be configurable.

[0335] For example, the effectiveness metric may include either a time effectiveness indication or an area effectiveness indication.

[0336] For example, the area validity indication may be associated with a tracking area.

[0337] For example, the area availability indication may include one or more cell identifiers.

[0338] For example, the first positioning configuration may be further determined to be invalid upon a condition that the WTRU moves to a second area that is different from the first area indicated by the area validity indication.

[0339] For example, the first positioning configuration may be further determined to be invalid upon determining that a certain amount of time has elapsed since completion of the last positioning configuration.

[0340] For example, the amount of time may be configurable.

[0341] Throughout the described embodiments, the terms "configurable parameter," "pre-configured parameter," and "configuration parameter" may be used herein to refer to a parameter of a WTRU that may be configured at the WTRU by receiving configuration information associated with that parameter and indicating the value to which the parameter may be configured.

[0342] Throughout the embodiments described herein, the (e.g., configuration) information may be described as being received by the WTRU from the network, e.g., through system information or via any type of protocol message. Although not explicitly mentioned throughout the embodiments described herein, the same (e.g., configuration) information may be initially configured in the WTRU (e.g., via any type of configuration method, such as, e.g., via a factory setting) such that this (e.g., configuration) information may be used by the WTRU without being received from the network.

[0343] Any features, variations, or embodiments described in the methods are compatible with an apparatus device comprising means for processing the disclosed methods, a device comprising circuitry including any of a transmitter, receiver, processor, and memory configured to process the disclosed methods, a computer program product including program code instructions, and a non-transitory computer readable storage medium having the program instructions stored thereon.

[0344] 4. Conclusion Although the features and elements are described above in certain combinations, one skilled in the art will understand that each feature or element may be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of non-transitory computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in the WTRU 102, a WTRU, a terminal, a base station, an RNC, or any host computer.

[0345] Furthermore, in the above embodiments, processing platforms, computing systems, controllers, and other devices including processors are described. These devices may include at least one central processing unit ("CPU") and memory. In accordance with the practices of those skilled in the art of computer programming, references to operations and symbolic representations of operations or instructions may be performed by various CPUs and memories. Such operations and operations or instructions may be referred to as being "executed," "executed by a computer," or "executed by a CPU."

[0346] Those of ordinary skill in the art will appreciate that the operations and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. The electrical system represents data bits that can cause a resultant transformation or reduction of the electrical signals, and maintains the data bits in memory locations of the memory system, thereby reconfiguring or otherwise altering the operation of the CPU and the processing of other signals. The memory locations in which the data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be appreciated that the exemplary embodiments are not limited to the platforms or CPUs mentioned above, and that other platforms and CPUs may support the methods provided.

[0347] The data bits may also be maintained on a computer readable medium, including magnetic disks, optical disks, and any other volatile (e.g., random access memory ("RAM")) or non-volatile (e.g., read only memory ("ROM")) mass storage system readable by a CPU. The computer readable medium may include computer readable media that resides exclusively on a processing system, or distributed, cooperative, or interconnected among multiple interconnected processing systems that may be local or remote to a processing system. It is understood that representative embodiments are not limited to the memories described above, and that other platforms and memories may support the methods described.

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

[0349] There is little distinction between hardware and software implementations of aspects of the system. The use of hardware or software is generally (though not always, in certain circumstances the choice between hardware and software may be significant) a design choice that implies a trade-off between cost versus efficiency. There may be a variety of vehicles (e.g., hardware, software, and / or firmware) in which the processes and / or systems and / or other techniques described herein may be effective, and the preferred vehicle may vary depending on the context in which the processes and / or systems and / or other techniques are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may select a primarily hardware and / or firmware vehicle. If flexibility is paramount, the implementer may select a primarily software implementation. Alternatively, the implementer may select some combination of hardware, software, and / or firmware.

[0350] The foregoing detailed description has illustrated various embodiments of devices and / or processes through the use of block diagrams, flow charts, and / or examples. To the extent that such block diagrams, flow charts, and / or examples include one or more functions and / or operations, those skilled in the art will appreciate that each function and / or operation in such block diagrams, flow charts, or examples may be individually and / or collectively implemented by a wide variety of hardware, software, firmware, or substantially any combination thereof. Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), an application specific standard product (ASSP), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), and / or a state machine.

[0351] Although features and elements are provided above in specific combinations, those of ordinary skill in the art will understand that each feature or element can be used alone or in any combination with other features and elements. The present disclosure is not limited in terms of the specific embodiments described in this application, which are intended as examples of various aspects. As will be apparent to those skilled in the art, many modifications and variations can be made without departing from the spirit and scope of the present invention. No element, operation, or instruction used in the description of this application should be construed as critical or essential to the invention unless expressly set forth as such. In addition to those enumerated herein, functionally equivalent methods and apparatuses within the scope of the present disclosure will be apparent to those skilled in the art from the foregoing description. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that the present disclosure is not limited to any particular method or system.

[0352] It should also be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, when referred to herein, "station" and its abbreviation "STA", "user equipment" and its abbreviation "UE" may mean (i) a wireless transmit and / or receive unit (WTRU) such as the described infrastructure, (ii) any of several embodiments of a WTRU such as the described infrastructure, (iii) a wireless and / or wired (e.g., tethered) device configured with some or all of the structure and functionality of a WTRU such as the described infrastructure, among others, (iii) a wireless and / or wired device configured with less than all of the structure and functionality of a WTRU such as the described infrastructure, or (iv) others. Details of an exemplary WTRU that may be representative of any WTRU enumerated herein are provided below with respect to Figures 1A-1E.

[0353] In certain representative embodiments, some portions of the subject matter described herein may be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein may be equivalently implemented in whole or in part in an integrated circuit as one or more computer programs running on one or more computers (e.g., one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), as firmware, or as substantially any combination thereof, and that designing circuitry and / or writing software and / or firmware code is within the skill of those skilled in the art in light of this disclosure. In addition, those skilled in the art will recognize that the mechanisms of the subject matter described herein may be distributed as a program product in various forms, and that the exemplary embodiments of the subject matter described herein apply regardless of the particular type of signal-bearing medium used to actually effect the distribution. Examples of signal bearing media include, but are not limited to, recordable type media such as floppy disks, hard disk drives, CDs, DVDs, digital tape, computer memory, and transmission type media such as digital and / or analog communications media (e.g., fiber optic cables, wave guides, wired communications links, wireless communications links, etc.).

[0354] The subject matter described herein may in some cases depict different components that are included within or connected to different other components. It should be understood that such illustrated architectures are merely examples, and that in fact many other architectures that achieve the same functionality may be implemented. Conceptually, any arrangement of components to achieve the same functionality is effectively "associated" such that a desired functionality may be achieved. Thus, any two components combined herein to achieve a particular functionality may be viewed as "associated" with one another such that a desired functionality is achieved, regardless of architecture or intermediate components. Similarly, any two components so associated may also be considered to be "operably connected" or "operably coupled" with one another to achieve a desired functionality, and any two components that may be so associated may also be considered to be "operably coupled" with one another to achieve a desired functionality. Examples of operably coupleable include, but are not limited to, physically matable and / or physically interacting components, and / or wirelessly interacting and / or wirelessly interacting components, and / or logically interacting and / or logically interacting components.

[0355] With respect to the use of substantially any plural and / or singular term herein, one of ordinary skill in the art can convert from plural to singular and / or from singular to plural as appropriate to the context and / or application. Various singular / plural permutations may be expressly set forth herein for purposes of clarity.

[0356] In general, those skilled in the art will understand that the terms used in this specification, and particularly in the appended claims (e.g., the body of the appended claims), are generally intended as "non-limiting" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," and the term "including" should be interpreted as "including but not limited to"). Furthermore, those skilled in the art will understand that where a specific number of recitations of an introduced claim are intended, such intent is expressly set forth in the claim, and in the absence of such recitation, no such intent exists. For example, where only one item is intended, the term "single" or similar language may be used. To aid in understanding, the following appended claims and / or the description of this specification may include the use of the introductory phrases "at least one" and "one or more" to introduce the claim recitations. However, the use of such phrases should not be interpreted as meaning that the introduction of a claim recitation with the indefinite article "a" or "an" limits any particular claim that includes such an introduced claim recitation to an embodiment that includes only one such recitation, even if the same claim includes the introductory phrase "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim recitations. In addition, those skilled in the art will recognize that even if a specific number of recitations of an introduced claim are explicitly recited, such recitation should be interpreted to mean at least the recited number (e.g., the simple recitation "two recitations" without other qualifiers means at least two recitations, or more than two recitations).Furthermore, when notation similar to "at least one of A, B, and C" is used, such structure is generally intended as a person of ordinary skill in the art would understand the notation (e.g., "a system having at least one of A, B, and C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together). When notation similar to "at least one of A, B, or C" is used, such structure is generally intended as a person of ordinary skill in the art would understand the notation (e.g., "a system having at least one of A, B, or C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together). Those skilled in the art will further appreciate that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" should be understood to include the possibility of "A" or "B" or "A and B." Additionally, as used herein, the term "any of" followed by a list of items and / or a list of categories of items is intended to include "any of," "any combination of," "any more than," and / or "any more than," of the items and / or categories of items, individually or in combination with other items and / or categories of items. Additionally, as used herein, the term "set" or "group" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero.

[0357] In addition, where features or aspects of the disclosure are described in terms of a Markush group, those skilled in the art will recognize that the disclosure is also described thereby in terms of any individual members or subgroups of members of the Markush group.

[0358] As will be understood by those skilled in the art, for all purposes, including in terms of providing a written description, all ranges disclosed herein encompass any possible subranges and combinations of subranges thereof. Any recited range can be readily recognized as fully descriptive and allowing the same range to be broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range described herein can be readily broken down into a lower third, a middle third, an upper third, etc. As will also be understood by those skilled in the art, all words such as "up to," "at least," "greater than," "less than," etc., refer to ranges that include the recited numbers and that can be further broken down into subranges as described above. Finally, as will be understood by those skilled in the art, ranges include each individual element. Thus, for example, a group having 1 to 3 cells refers to a group having 1, 2, or 3 cells. Similarly, a group having 1 to 5 cells refers to a group having 1, 2, 3, 4, or 5 cells, and so on.

[0359] Moreover, the claims should not be read as limited to the provided order or to the provided elements unless specifically so recited. In addition, the use of the term "means for" in any claim is intended to be relied upon under 35 U.S.C. 112, paragraph 6, or means-plus-function claim format, and no claim without the term "means for" is so intended.

[0360] Although the invention is illustrated and described herein with reference to specific embodiments, the invention is not intended to be limited to the details shown. Rather, various modifications in the details can be made within the scope of the claims and their equivalents and without departing from the invention.

[0361] Throughout this disclosure, those skilled in the art will appreciate that certain representative embodiments may be used in the alternative or in combination with other representative embodiments.

[0362] Although the features and elements are described above in certain combinations, one skilled in the art will understand that each feature or element may be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of non-transitory computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor associated with software may be used to implement a radio frequency transceiver for use in a UE, WTRU, terminal, base station, RNC, or any host computer.

[0363] Furthermore, in the above embodiments, processing platforms, computing systems, controllers, and other devices including processors are described. These devices may include at least one central processing unit ("CPU") and memory. In accordance with the practices of those skilled in the art of computer programming, references to operations and symbolic representations of operations or instructions may be performed by various CPUs and memories. Such operations and operations or instructions may be referred to as being "executed," "executed by a computer," or "executed by a CPU."

[0364] Those of ordinary skill in the art will understand that the operations and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. The electrical system represents data bits that can cause a resultant transformation or reduction of the electrical signals, and maintains the data bits in memory locations of the memory system, thereby reconfiguring or otherwise altering the operation of the CPU and the processing of other signals. The memory locations in which the data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties that correspond to or represent the data bits.

[0365] The data bits may also be maintained on a computer readable medium, including magnetic disks, optical disks, and any other volatile (e.g., random access memory ("RAM")) or non-volatile (e.g., read only memory ("ROM")) mass storage system readable by a CPU. The computer readable medium may include computer readable media that resides exclusively on a processing system, or distributed, cooperative, or interconnected among multiple interconnected processing systems that may be local or remote to a processing system. It is understood that representative embodiments are not limited to the memories described above, and that other platforms and memories may support the methods described.

[0366] No element, act, or instruction used in the description of this application should be construed as critical or essential to the invention unless expressly described as such. Additionally, as used herein, the article "a" is intended to include one or more items. When only one item is intended, the term "one" or similar language may be used. Also, as used herein, the term "any of" followed by a list of items and / or a list of categories of items is intended to include "any of," "any combination of," "any more than one of," and / or "any more than one of" the items and / or categories of items, individually or in combination with other items and / or categories of items. Also, as used herein, the term "set" is intended to include any number of items, including zero. Also, as used herein, the term "number" is intended to include any number, including zero.

[0367] Moreover, the claims should not be read as limited to the described order or to the provided elements unless specifically so stated. In addition, the use of the term "means for" in any claim is intended to invoke 35 U.S.C. 112, paragraph 6, and no claim without the word "means for" is intended to do so.

[0368] Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), an application specific standard product (ASSP), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), and / or a state machine.

[0369] A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit / receive unit (WTRU), user equipment (UE), terminal, base station, mobility management entity (MME) or evolved packet core (EPC), or any host computer. The WTRU may be used in conjunction with modules implemented in hardware and / or software, such as, for example, a Software Defined Radio (SDR), and may be implemented in other components, such as a camera, a video camera module, a video phone, a speaker phone, a vibration device, a speaker, a microphone, a television transceiver, a hands-free headset, a keyboard, a Bluetooth module, a frequency modulation (FM) radio unit, a Near Field Communication (NFC) module, a liquid crystal display (LCD) display unit, an organic light emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and / or a wireless local area network (WLAN) or an Ultra Wide Band (UWB) module.

[0370] Although the present invention has been described with respect to a communications system, it is contemplated that the system may be implemented in software on a microprocessor / general purpose computer (not shown). In particular embodiments, one or more of the functions of the various components may be implemented in software controlling a general purpose computer.

[0371] In addition, although the invention is illustrated and described herein with reference to specific embodiments, the invention is not intended to be limited to the details shown. Rather, various modifications can be made in the details within the scope of the claims and equivalents thereof and without departing from the invention.

[0372] 5.References The following references may have been mentioned above and are incorporated by reference herein in their entireties. [1] 3GPP, “User Equipment (UE) positioning in NG-RAN,” TS 38.305, ver.16.2.0, September 2020.

Claims

1. 1. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: receiving configuration information indicating a time window associated with a positioning, the configuration information indicating any of a duration of the time window and a periodicity of the time window; receiving first scheduling information indicating transmitting a first uplink transmission comprising a sounding reference signal (SRS) transmission, the first uplink transmission not including a positioning SRS (SRSp) transmission; receiving second scheduling information indicating transmitting a second uplink transmission including an SRSp transmission; transmitting the second uplink transmission during the time window under the condition that the second uplink transmission is scheduled for transmission during the time window, and transmitting the first uplink transmission only when the first uplink transmission is scheduled for transmission outside the time window; The method includes:

2. The method of claim 1 , wherein the configuration information indicates a plurality of time windows.

3. The method of claim 1 or claim 2, wherein the duration is indicated as any of one or more symbols, one or more slots, one or more frames, and one or more seconds.

4. 4. The method of claim 1, further comprising: when the first uplink transmission is scheduled for transmission during the time window, postponing the first uplink transmission for transmission outside the time window.

5. 5. The method of claim 1, further comprising dropping the first uplink transmission when the first uplink transmission is scheduled for transmission during the time window.

6. The method of claim 1 , wherein the time window is associated with a priority, and the SRS transmission is of a lower priority than the priority associated with the time window.

7. 7. The method of claim 1, comprising receiving third scheduling information indicating to transmit a third uplink transmission comprising one of a physical uplink control channel transmission and a physical uplink shared channel transmission.

8. 8. The method of claim 7, comprising transmitting a third uplink transmission only when the third uplink transmission is scheduled for transmission outside the time window, provided that the second uplink transmission is scheduled for transmission during the time window.

9. The method of claim 1 , further comprising receiving fourth scheduling information indicating downlink transmissions scheduled during said time window.

10. The method of claim 9 , comprising receiving the downlink transmission during the time window.

11. 1. A wireless transmit / receive unit (WTRU) comprising circuitry including a transmitter, a receiver, a processor, and a memory, the WTRU comprising: receiving configuration information indicating a time window associated with a positioning, the configuration information indicating any of a duration of the time window and a periodicity of the time window; receiving first scheduling information indicating transmitting a first uplink transmission comprising a sounding reference signal (SRS) transmission, the first uplink transmission not including a positioning SRS (SRSp) transmission; receiving second scheduling information indicating transmitting a second uplink transmission including an SRSp transmission; configured to run a WTRU configured to transmit the second uplink transmission during the time window, provided that the second uplink transmission is scheduled for transmission during the time window, and to transmit the first uplink transmission only when the first uplink transmission is scheduled for transmission outside the time window.

12. The WTRU of claim 11 , wherein the configuration information indicates a plurality of time windows.

13. The WTRU of claim 11 or 12, wherein the duration is indicated as any of one or more symbols, one or more slots, one or more frames, and one or more seconds.

14. 14. The WTRU of claim 11, wherein the WTRU is configured to postpone a first uplink transmission for transmission outside the time window when the first uplink transmission is scheduled for transmission during the time window.

15. The WTRU of claim 11 , wherein the WTRU is configured to drop the first uplink transmission when the first uplink transmission is scheduled for transmission during the time window.

16. The WTRU of claim 11 , wherein the time window is associated with a priority, and the SRS transmission is of a lower priority than the priority associated with the time window.

17. The WTRU of claim 11, wherein the WTRU is configured to receive third scheduling information indicating transmitting a third uplink transmission including one of a physical uplink control channel transmission and a physical uplink shared channel transmission.

18. 18. The WTRU of claim 17, wherein the WTRU is configured to transmit the third uplink transmission only when the third uplink transmission is scheduled for transmission outside the time window, provided that the second uplink transmission is scheduled for transmission during the time window.

19. The WTRU of claim 11 , wherein the WTRU is configured to receive fourth scheduling information indicating downlink transmissions scheduled during the time window.

20. The WTRU of claim 19 , wherein the WTRU is configured to receive the downlink transmission during the time window.

Images